Re: My provider cut me off!!!

James Neeley (
Mon, 23 Oct 1995 13:42:38 -0800

Brett Harvey replied to Jim Neeley's comments about Teleport blocking CU:

>Hello Jim,
>I personally would be very interested in seeing Teleport's explanation. I
>currently am a "regular" user of CUSM and frequent Cornell a lot.
>Some of the "regulars" also have a mailing list that is designed to talk
>about gatherings of CUSM people and general gossip. Some of the "regulars"
>have been affected by this also. People are heavily discussion the
>ramifications of the actions being taken place and I for one prefer to have
>as much information as possible to work with.
>I am also concerned because CUSM will be used be the new high school we
>have built that commences teaching next fall. If people are being cut off
>around the nation/world, we may need to rethink some of our approaches.
>Thanks for your time and I look forward to reading Teleport's explanation.

Enough people have mailed me privately about this to warrant posting
Teleport's response here. Here is their message, in it's entirety.

As you will see, not only did they decide to block CU, they perceive CU's
current implementation as using an excessive amount of their resources,
hence they gave no advanced notice and are not offering refunds to people
wanting to switch providers.

While I have not mentioned this to my ISP, they did make a similar comment
to me a month or so ago. I truly hope that the developers will offer some
relief. CU is an excellant concept, but the more popular CU becomes the
larger the impact on the providers and the more providers that are likely to
follow after Teleport.

Jim Neeley


Newsgroups: teleport.announce
Subject: We've disabled CU-SeeMe access.
Date: 20 Oct 1995 10:08:10 -0700
Organization: Teleport tester for internet service
Message-ID: <>

Users should take note that Teleport has found it necessary to

lock out CU-SeeMe for the forseeable future. CU-SeeMe in its

current versions uses the UDP data transmission protocol, which, unlike

TCP/IP does not require that the sending machine receive confirmation

that packets are arriving safely in order to continue transmitting.

Those familiar with the concept will no doubt realize that the program

generates an extraordinary number of packets, and is bandwidth intensive

even on a ethernet connection. The combination produces vastly more

packets than can be transmitted over a modem line, causing a growing

backlog of undelivered, and undeliverable packets. Those packets collect

on our side within the router, and degrade its performance visibly. As

each router can be attempting to route the traffic for 32 modems, the

degradation affects the other users on that router.

Teleport has always maintained that the overburdening of

resources by one user is unacceptable, when that behaviour affects other

users on the system. Our decision to move from discouraging CU-CMe to

blocking it is an extension of the rule regarding system resources.

A quote from the 'rules' help file states the following:

Here are the things you MAY NOT DO with a Teleport account:

5. Consume excessive system resources, such as disk space, RAM, or

processor time.

For example: do not fill up public temporary space with files, or

run programs that eat up huge amounts of RAM or CPU. You also

can't run processes while you are not logged in (leaving detached

screen processes running, or running an IRC bot, for example).

We hope that the creators of CU-SeeMe will design a future release to

handle modem communication better. Until such time, CU-SeeMe will not be

usable through our service. Questions regarding this decision can be

directed to

Ted Dewey

Tech Support Mgr.

Teleport Internet Services



Help Support get you a faster answer: 1) Check the help files and manual

first, send e-mail to with only the word 'help' in the

subject line for instructions on accessing help files; 2) Include any

previous email between you and Support; and 3) Be as specific as you

can--the more detail you give, the faster we can track the problem down.

(This is a signature file; it's automatically attached to everything.)

============================================================================ ============