Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!csd4.csd.uwm.edu!bionet!apple!oliveb!olivey!jerry
From: jerry@olivey.olivetti.com (Jerry Aguirre)
Newsgroups: news.config
Subject: Re: Warp speed Mr. Scott!
Summary: fast and slow are relative terms
Message-ID: <47647@oliveb.olivetti.com>
Date: 6 Sep 89 19:50:26 GMT
References: <1989Aug21.124002.11054@robohack.uucp> <1059@aurora.AthabascaU.CA> <7561@cloud9.Stratus.COM> <6064@ficc.uu.net>
Sender: news@oliveb.olivetti.com
Reply-To: jerry@olivey.UUCP (Jerry Aguirre)
Organization: Olivetti ATC; Cupertino, Ca
Lines: 19

In article <6064@ficc.uu.net> sms@ficc.uu.net (Stanley M. Sutton) writes:
>Why not just use minutes?  Integers are easier to track than floating.
>However, the mean time for transfer may not be as useful as some of the
>terms, if they are consitently used.  I.E., once a day would be a mean

Here is an example of the source of the confusion.  Some people are
thinking of delays in terms of minutes while others are thinking in
terms of seconds or less.  Some think a connection should be DEDICATED
if it can connect in less than one minute while others think that should
be reserved for values less than one second.

Without absolute values the terms are subject to individual
interpretation.  I propose that the "delays" encoded into the pathalias
costs be specified.  A "DIRECT" or "DEMAND" cost should indicate a
connection setup time of about 20 seconds.  A "DEDICATED" cost should
indicate a setup time of less than 2 seconds.

If the setup times were specified the people would be able to assign
consistant costs.