Delivery-Date: Thu, 19 Jun 2014 11:12:22 -0400
Return-Path: <tor-talk-bounces@lists.torproject.org>
X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on moria.seul.org
X-Spam-Level: 
X-Spam-Status: No, score=-4.9 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_MED,
	RP_MATCHES_RCVD autolearn=ham version=3.3.1
X-Original-To: archiver@seul.org
Delivered-To: archiver@seul.org
Received: from eugeni.torproject.org (eugeni.torproject.org [38.229.72.13])
	(using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits))
	(No client certificate requested)
	by moria.seul.org (Postfix) with ESMTPS id 5C31D1E0BD4
	for <archiver@seul.org>; Thu, 19 Jun 2014 11:12:18 -0400 (EDT)
Received: from eugeni.torproject.org (localhost [127.0.0.1])
	by eugeni.torproject.org (Postfix) with ESMTP id 36E8D30160;
	Thu, 19 Jun 2014 15:12:16 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by eugeni.torproject.org (Postfix) with ESMTP id AEE73300EA
 for <tor-talk@lists.torproject.org>; Thu, 19 Jun 2014 14:59:55 +0000 (UTC)
X-Virus-Scanned: Debian amavisd-new at eugeni.torproject.org
Received: from eugeni.torproject.org ([127.0.0.1])
 by localhost (eugeni.torproject.org [127.0.0.1]) (amavisd-new, port 10024)
 with ESMTP id jjXCdL4LZ1U4 for <tor-talk@lists.torproject.org>;
 Thu, 19 Jun 2014 14:59:55 +0000 (UTC)
Received: from ccs.nrl.navy.mil (mx0.ccs.nrl.navy.mil [132.250.118.211])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA (256/256 bits))
 (Client did not present a certificate)
 by eugeni.torproject.org (Postfix) with ESMTPS id 921A72FF61
 for <tor-talk@lists.torproject.org>; Thu, 19 Jun 2014 14:59:55 +0000 (UTC)
Received: from buridan.fw5540.net (fw5540.nrl.navy.mil [132.250.196.100])
 by ccs.nrl.navy.mil (8.14.4/8.14.4) with ESMTP id s5JExn0l022534
 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT);
 Thu, 19 Jun 2014 10:59:50 -0400
Date: Thu, 19 Jun 2014 10:59:50 -0400
From: Paul Syverson <paul.syverson@nrl.navy.mil>
To: tor-talk@lists.torproject.org
Message-ID: <20140619145950.GC1187@buridan.fw5540.net>
References: <53A0B996.80008@general-changelog-team.fr>
 <53A1DE17.2090205@googlemail.com> <53A21CF0.5020506@gmx.com>
 <58e6f39c-5ade-430c-9fc4-26a96cb19c08@email.android.com>
MIME-Version: 1.0
Content-Disposition: inline
In-Reply-To: <58e6f39c-5ade-430c-9fc4-26a96cb19c08@email.android.com>
User-Agent: Mutt/1.5.23 (2014-03-12)
X-CCS-MailScanner: No viruses found.
X-CCS-MailScanner-Info: See: http://www.nrl.navy.mil/ccs/support/email
Subject: Re: [tor-talk] Presentation material in LaTeX
X-BeenThere: tor-talk@lists.torproject.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: tor-talk@lists.torproject.org
List-Id: "all discussion about theory, design,
 and development of Onion Routing" <tor-talk.lists.torproject.org>
List-Unsubscribe: <https://lists.torproject.org/cgi-bin/mailman/options/tor-talk>, 
 <mailto:tor-talk-request@lists.torproject.org?subject=unsubscribe>
List-Archive: <http://lists.torproject.org/pipermail/tor-talk/>
List-Post: <mailto:tor-talk@lists.torproject.org>
List-Help: <mailto:tor-talk-request@lists.torproject.org?subject=help>
List-Subscribe: <https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-talk>, 
 <mailto:tor-talk-request@lists.torproject.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: tor-talk-bounces@lists.torproject.org
Sender: "tor-talk" <tor-talk-bounces@lists.torproject.org>

To see more than you probably care to know on the history of the
names 'onion routing' and 'Tor' cf. pages 129, 135 of 
http://www.acsac.org/2011/program/keynotes/syverson.pdf

Two things that I see were not mentioned there: Nick Mathewson pointed
out to me and I confirmed in email exchanges that we actually started
using 'Tor' to refer to the basic onion routing system design that
we were working on before the design now generally called "Tor".
'Tor' also means a fine-meshed net in Turkish.

aloha,
Paul

On Wed, Jun 18, 2014 at 10:49:01PM -0400, Griffin Boyce wrote:
> Hi jOe,
> 
> Perhaps because it's not an acronym. ;-) And keep in mind that calling something "the" onion router would be rather incorrect as there are now multiple onion routing projects.
> 
> ~Griffin
> 
> Joe Btfsplk <joebtfsplk@gmx.com> wrote:
> >The "why called tOR" article says,
> >"/Note: even though it originally *came from an acronym,* Tor is not 
> >spelled "TOR"/.
> >And why would that be?  Other than in a kind of, "I'd now like to be 
> >known as _The Artist Formerly Known As Prince_" sort of way, who made
> >up 
> >the rule that an acronym would have only the first letter capitalized?
> >Even HAL 9000 - an "almost alive" computer - used all caps for an 
> >acronym. :-;
> >
> >Did "they" consider it alive, so Tor is a proper noun, 1st & only name 
> >(like Sting)?
> >If it's an acronym, it's supposed to be all caps (rarely, all lower 
> >case).  I doubt most people (not suffering from something) really care 
> >if it's Tor, TOR, tOR, tOr...
> >
> >And newer people coming in may think it a bit strange to make a serious
> >
> >point, to not spelling it correctly, per widely accepted, international
> >
> >convention. :D
> >My name's not Joe, it's jOe.  On rEmUlak, only interior vowels in
> >proper 
> >nouns are capitalized.  The Tor spelling issue sort of reminds me of 
> >_The Anal Retentive Chef_ sketch (phiLL harTMan), on Sat. Night Live.
> >
> >  * Cooking with the Anal Retentive Chef
> ><https://en.wikipedia.org/wiki/Recurring_Saturday_Night_Live_characters_and_sketches_introduced_1988%E2%80%931989#Cooking_with_the_Anal_Retentive_Chef>
> >    (Phil Hartman <https://en.wikipedia.org/wiki/Phil_Hartman>)
> 
> -- 
> Sent from my tracking device. Please excuse brevity and cat photos.
> -- 
> tor-talk mailing list - tor-talk@lists.torproject.org
> To unsubscribe or change other settings go to
> https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-talk
-- 
tor-talk mailing list - tor-talk@lists.torproject.org
To unsubscribe or change other settings go to
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-talk

