[9102] in Commercialization & Privatization of the Internet
Re: The Buffalo Free-Net / NYSERNet / PSI problems
daemon@ATHENA.MIT.EDU (Richard Mandelbaum)
Fri Dec 17 09:55:27 1993
To: com-priv@psi.com
Cc: schoff@psi.com
In-Reply-To: Your message of Thu, 16 Dec 93 18:31:43 +0000.
Date: Fri, 17 Dec 93 09:54:58 -0500
From: Richard Mandelbaum <rma@photon.poly.edu>
Just for the record we do not agree with Mr. Schoffstall's interpretation
of the events surrounding the filtering of traffic originating at the
University of Buffalo server which provides service to the University of i
Buffalo FreeNet Project and
have so informed PSI in writing. However we do not feel that com-priv is
the appropriate venue to discuss business dealings between NYSERNet and
PSI.
The bottom line, though is that PSI has stopped filtering the University of
Buffalo server which provides service for the University of
Buffalo FreeNet project and NYSERNet has made arrangements for the University
of Buffalo, which sponsors the FreeNet , to receive service from
one of NYSERNet's alternative Network Service provider who has no problem
with the continued presence of FreeNet customers on the UB server
supporting the Freenet project
Richard Mandelbaum
President
NYSERNet, Inc
____________________
Yes we do have a position. But I'm sure that it will be a controversi
al.
It boils down to the fact that we sell retail connections for the most
part,
and this connection was and is a retail connection to another party.
First for some facts to remove some misconceptions:
- we were never a provider of service to Buffalo FREENet
- contacting them was not part of the program as they were not
our customer, SUNY Buffalo was (through NYSERNet), NYSERNet was
contacted and this was a long term discussion
- the goal (and as far as we can tell what happened) was not to
disturb the paying customer, SUNY Buffalo
- we had discussed the Buffalo FREENET situation for many months with
NYSERNet
- we were meeting with NYSERNet the morning we turned them off, though
they were not the reason for meeting, nor more than a few minut
e
discussion
- Buffalo FREENET was turned back on Saturday morning, I remember it b
ecause
I had to wrestle my beeper out of my two year old's hands as we
were
driving in the truck to buy a new deer rifle: that would be 3
days
if we started on Thursday, though I believe that date is also i
ncorrect
- we were the ones that suggest FREENET go elsewhere, both prior to th
is, and
suggested the criteria to get them back on immediately
- up until this event we believed that NYSERNet was behind our positio
n and
policy, all discussions prior led us to believe that. that day
's face
to face even reinforced that. but the email following it was
definitely different!
- we had wanted to do this much earlier but up until the week before w
ere
not 100% sure that the customer traffic wouldn't be affected, s
o we
delayed (undoubtedly too long)
- as part of one of our services we offer free dialups to students and
faculty
of our customers throughout the US as they travel, vacation or
whatever. BuffaloFreeNet people were using capability
removing the resource from our customers.
PSI has had a few similiar situations, all of which have been handled
in a similiar fashion. We talk to the customer first, well before any
action is taken. Those that attach through some technical means are a
t risk,
but they put themselves at risk.
There are many people that want something for nothing. Last night I be
gan
reading "Lenin's Tomb, the Last days of the Soviet Empire", chapter on
e
discusses some examples of this and the implications on (Soviet) socie
ty.
Possibly FREENet's are an example of this?
I'm sure none of this is Politically Correct (PC), but PC issues domin
ate
politics they don't have to dominate society, economic systems, or
institutions outside of the BeltWay.
Marty
> Message-Id: <9312152002.AA06588@rampage.psi.net>
> Date: Wed, 15 Dec 1993 10:42:34 -0500
> Reply-To: "Communet: Community and Civic Network Discussion List" <
> COMMUNET%UVMVM.BITNET@uga.cc.uga.edu>,
> Jim Gerland - Network Consultant <GERLAND%UBVMS.BITNET@uga.c
c.
> uga.edu> Sender: "Communet: Community and Civic Network Discussion
> List"
> <COMMUNET%UVMVM.BITNET@uga.cc.uga.edu>
> >From: Jim Gerland - Network Consultant <GERLAND%UBVMS.BITNET@uga.cc
.
> >uga.edu>
> Organization: University at Buffalo
> Subject: The Buffalo Free-Net / NYSERNet / PSI problems - resol
ved
> X-To: communet@uvmvm.BITNET, publib@nysernet.org
> To: Multiple recipients of list COMMUNET
> <COMMUNET%UVMVM.BITNET@uga.cc.uga.edu>
>
> This message is being sent to COMMUNET & PUBLIB.
>
> I am not on either of these lists so if you want me to see your
> response then send it to me.
>
> I have already explained what happened on a few other lists but for
the
> sake of those who have not read it and are interested I will risk
> boring the uninterested with yet another explanation.
>
> Let me start by saying the NYSERNet (and everyone at NYSERNet) has b
een
> wonderful and helpful and <put you own best compliment here> during
the
> problems the Buffalo Free-Net had with PSI, Inc. and our Internet
> connection!!!!!!
>
> PSI placed a filter which blocked all BFN access to the Internet on
a
> Thursday afternoon. We discovered that the next day. PSI did not
> advise us ahead of time of their actions.
>
> We contacted NYSERNet and they (and our BOD) contected PSI to try an
d
> work things out. The bottom line was that a week later Internet acc
ess
> for the Buffalo Free-Net was once again established. PSI had grante
d
> NYSERNet, the University at Buffalo, and the BFN 60 days to switch t
he
> UB/BFN internet connection to another service provider. NYSERNet is
in
> the process of doing this.
>
> That's all I am going to say publicaly or privately.
>
> If you have any comments about this, please feel free to let me know
.
>
> Please *DO NOT* bother the NYSERNet folks about this.
>
> Thanks,
> Jim...
>
> Jim Gerland
> Manager, Network user Support
> University at Buffalo
> BoD Buffalo Free-Net
> BoT National Public Telecomputing Network
> gerland@ubvms.cc.buffalo.edu
>
>
> ------- End of Forwarded Message
>
