Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!zaphod.mps.ohio-state.edu!usc!elroy.jpl.nasa.gov!peregrine!sceard!ncr-sd!simasd!jadpc!jdeitch
From: jdeitch@jadpc.cts.com (Jim Deitch)
Newsgroups: comp.unix.sysv386
Subject: Re: slip
Message-ID: <1990Nov06.064509.195@jadpc.cts.com>
Date: 6 Nov 90 06:45:09 GMT
References: <1990Nov01.025031.12861@virtech.uucp> <1990Nov01.145738.16101@nstar.uucp> <600@nih-csl.nih.gov>
Organization: Network Engineering Technologies
Lines: 26

In article <600@nih-csl.nih.gov> crtb@helix.nih.gov (Chuck Bacon) writes:
>Larry, SLIP is just IP using an async. RS-232 port.  Error correction is
>done by TCP.  This requires fast turnaround, however, and so the best bet
>is V.32 with *NO* packetizing, error correction or compression by the
>modem.  A true V.32 rate of 9600 should give an effective data throughput
>close to 80%, or near 760 bytes per second.
>
>--
>Chuck Bacon - crtb@helix.nih.gov - 301-496-4823
>	"People who like this kind of thing
>	 will find this the sort of thing they like." --A. Lincoln

What do you mean no compression?  If you are moving text files around,
ftp or telnet, then compression can increase throughput by about
10-15%.  The only place the compression takes place is between your
modem and the host's modem.  That way the info can get into the faster
transport sooner.  Unless of course the host you are talking to also
uses slip without compression.

Jim

-- 

UUCP: nosc!jadpc!jdeitch
ARPA: jadpc!jdeitch@nosc.mil
INET: jdeitch@jadpc.cts.com