1993-08-13 - Secure voice software issues

Header Data

From: karn@qualcomm.com (Phil Karn)
To: honey@citi.umich.edu
Message Hash: b73898a9e1ebf8c04338f9fc2a7bdd95cb73e233d08523994be1192bada9397a
Message ID: <9308131721.AA21363@servo>
Reply To: <9308131255.AA23722@toad.com>
UTC Datetime: 1993-08-13 17:22:57 UTC
Raw Date: Fri, 13 Aug 93 10:22:57 PDT

Raw message

From: karn@qualcomm.com (Phil Karn)
Date: Fri, 13 Aug 93 10:22:57 PDT
To: honey@citi.umich.edu
Subject: Secure voice software issues
In-Reply-To: <9308131255.AA23722@toad.com>
Message-ID: <9308131721.AA21363@servo>
MIME-Version: 1.0
Content-Type: text/plain


>> do not use error correction or compression.  (they will slow you down)

>huh?!?  my file transfer times would *double* if i turned off v.42bis
>(modem compression).  *that* would slow me down.  and you can't run
>v.42bis without running the error handling protocol (v.42), for obvious
>reasons.  what's more, v.42 gives an immediate 20% (or so) increase in
>throughput, by eliminating start and stop bits.

I think there's a confusion here between the conflicting goals of low
delay and high throughput. Depending on which is more important to
your application, V.42bis will either "slow you down" or "speed you
up". Unfortunately, most modems don't give the user any way to say
whether delay or throughput is more important to you at the moment;
the modems themselves try to infer this automatically from the data
streams you send them. And they bias the decision in favor of greater
throughput. This is right for most computer applications, but not so
for real time voice.

Phil





Thread