Bounced message from Colin Mick <ckm@xxxxxxxxxxxxx>
Please reply to Colin Mick <ckm@xxxxxxxxxxxxx>
owner-stds-802-3-hssg@xxxxxxxx on 09/02/2000 18:35:51
Sent by: owner-stds-802-3-hssg@xxxxxxxx
To: owner-stds-802-3-hssg@xxxxxxxxxxxxxxxxxx
cc: (David Law/GB/3Com)
Subject: BOUNCE stds-802-3-hssg@xxxxxxxxxxxxxxxxxx
From owner-stds-802-3-hssg@xxxxxxxx Wed Feb 9 13:35:51 2000
Received: from gemini.ieee.org by ruebert.ieee.org (8.9.3/8.9.3) with ESMTP
id NAA12019; Wed, 9 Feb 2000 13:35:50 -0500 (EST)
Received: from smtp1a.ispchannel.com (cluster.ispchannel.com [24.142.63.7])
by gemini.ieee.org (8.9.3/8.9.3) with ESMTP id NAA15038
for <stds-802-3-hssg@xxxxxxxx>; Wed, 9 Feb 2000 13:35:49 -0500 (EST)
Received: from Tiger ([24.142.101.37]) by smtp1a.ispchannel.com
(InterMail vK.4.02.00.00 201-232-116 license
7d3764cdaca754bf8ae20adf0db2aa60)
with ESMTP id <20000209183615.WYIW9448.smtp1a@Tiger>
for <stds-802-3-hssg@xxxxxxxx>; Wed, 9 Feb 2000 10:36:15 -0800
Message-Id: <4.2.0.58.20000209102412.00ab1d20@xxxxxxxxxxxxxxxxxx>
X-Sender: ckm@xxxxxxxxxxxxxxxxxx
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.58
Date: Wed, 09 Feb 2000 10:34:45 -0800
To: stds-802-3-hssg@xxxxxxxx
From: Colin Mick <ckm@xxxxxxxxxxxxx>
Subject: reflector et al
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
I agree with both Howard and Brian than an open reflector is essential.
The sheer magnitude of content presented on this reflector is a major
problem to new members and, probably, to many of us who are observing but
not actively participating in the discussion. The problem is only going to
get worse.
It would be extremely helpful to all but the rabidly enthusiastic (and
eclectic, given the range of proposals I've seen) if some one or some group
spent some time preparing and maintaining an organized summary/history of
events. Simpler projects have made do--sort of--with archives (e.g., the
two inches of paper we distributed for Fast Ethernet and the email archives
we started during the gigabit project) but this one is too complex and has
too many options and far too much content already.
It would behoove the task force to create an organized archive/history
now--both as an aid to folks who will be joining this conference in the
future and as an aid to other 802 and sponsor ballot folks who will have to
vote on this project at some time in the future.
Then again, there is always that chance that the group may go down a blind
alley and have to back up and consider other options. In such a case a
detailed map of your journey might prove invaluable.
Colin