From:      skunk-works-digest-owner@harbor.ecn.purdue.edu
To:        skunk-works-digest@harbor.ecn.purdue.edu
Subject:   Skunk Works Digest V4 #88
Reply-To:  skunk-works-digest@harbor.ecn.purdue.edu
Errors-To: skunk-works-digest-owner@harbor.ecn.purdue.edu
Precedence: bulk

Skunk Works Digest        Sunday, 12 December 1993      Volume 04 : Number 088

In this issue:

	Who thinks up code names?
	Re:  Who thinks up code names?

See the end of the digest for information on subscribing to the skunk-works
or skunk-works-digest mailing lists and on how to retrieve back issues.

----------------------------------------------------------------------

From: TRADER@cup.portal.com
Date: Sat, 11 Dec 93 09:38:48 PST
Subject: Who thinks up code names?

Various military agencies use code words to describe projects, such as
SENIOR CITIZEN, MERIDIAN, COPPER CANYON, TRACTOR PULL, MISTY ECHO, etc.
(I used capitol letters because the military does that when referring
to them). My question is: who thinks up these names? Is there some
secret committee somewhere who creates these code names, assigns them,
and makes sure that they aren't re-used?

Hypothetical dialog:
Committee member #1: We have a new Air Force program supported by DARPA.
  That means we need a HAVE designator. How about HAVE STAFF ?
Committee member #2: No, too phallic. How about HAVE FLAG?
          etc.
Paul McGinnis / TRADER@cup.portal.com

------------------------------

From: dadams@netcom.com (Dean Adams)
Date: Sat, 11 Dec 1993 10:52:43 -0800
Subject: Re:  Who thinks up code names?

>Various military agencies use code words to describe projects, such as
>SENIOR CITIZEN, MERIDIAN, COPPER CANYON, TRACTOR PULL, MISTY ECHO, etc.
>(I used capitol letters because the military does that when referring
>to them). My question is: who thinks up these names?

I'm pretty sure that the NSA is responsible for generating
new code names for the rest of the government/military,
but I suppose we can't be 100% certain about these things.

- -dean


------------------------------

End of Skunk Works Digest V4 #88
********************************

To subscribe to skunk-works-digest, send the command:

    subscribe skunk-works-digest

in the body of a message to "listserv@harbor.ecn.purdue.edu".  If you want
to subscribe something other than the account the mail is coming from,
such as a local redistribution list, then append that address to the
"subscribe" command; for example, to subscribe "local-skunk-works":

    subscribe skunk-works-digest local-skunk-works@your.domain.net

To unsubscribe, send mail to the same address, with the command:

	unsubscribe skunk-works-digest

in the body.

Administrative requests, problems, and other non-list mail can be sent
to either "skunk-works-digest-owner@harbor.ecn.purdue.edu" or, if you
don't like to type a lot, "prm@ecn.purdue.edu".

A non-digest (direct mail) version of this list is also available; to
subscribe to that instead, replace all instances of "skunk-works-digest"
in the commands above with "skunk-works".

Back issues are available for anonymous FTP from harbor.ecn.purdue.edu, in
/pub/skunk-works/digest/vNN.nMMM (where "NN" is the volume number, and "MMM"
is the issue number).