Path: utzoo!telecom-request
Date: 20 Jun 91 19:33:58 GMT
From: Jeff Carroll <ssc-bee!ssc-vax!carroll@cs.washington.edu>
Newsgroups: comp.dcom.telecom
Subject: Re: Comsec Data Security
Reply-To: Jeff Carroll <ssc-vax!carroll@cs.washington.edu>
Message-ID: <telecom11.472.7@eecs.nwu.edu>
Organization: Boeing Aerospace & Electronics
Sender: Telecom@eecs.nwu.edu
Approved: Telecom@eecs.nwu.edu
X-Submissions-To: telecom@eecs.nwu.edu
X-Administrivia-To: telecom-request@eecs.nwu.edu
X-Telecom-Digest: Volume 11, Issue 472, Message 7 of 11
Lines: 27

In article <telecom11.471.3@eecs.nwu.edu> herbison@ultra.enet.dec.com
(B.J.  19-Jun-1991 1142) writes:

>> I would like to know, what are ya'lls opinions on Comsec Data Security?

> In my opinion, the phrase `Communication Security Data Security'
> sounds like gibberish.  If you meant `Data Comsec', then I'm in favor
> of it.  I would like to have the option to encrypt everything (data or
> voice) I send over telephone connections (both the old-fashioned kind
> and cellular).

I could see this coming.

COMSEC is a military term, the meaning of which I won't go into here.
Those with a need to know are adequately familiar with its meaning.

"Comsec Data Security" is apparently the name of a consulting
enterprise recently launched by ex-LoD-types. A spectacularly
inappropriate name, if you ask me.

Neither, strictly speaking, has anything to do with encryption of
commercial data, using DES or otherwise.


Jeff Carroll		carroll@ssc-vax.boeing.com