Re: Proposed WG: SSH, Secure Shell (SECSH) - names, you want names??

Robert Elz <kre@munnari.oz.au> Sat, 15 February 1997 06:06 UTC

Received: from cnri by ietf.org id aa00668; 15 Feb 97 1:06 EST
Received: from ietf.org by CNRI.Reston.VA.US id aa08011; 15 Feb 97 1:06 EST
Received: from ietf.org by ietf.org id aa00656; 15 Feb 97 1:06 EST
Received: from munnari.OZ.AU by ietf.org id aa00650; 15 Feb 97 1:06 EST
Received: from mundamutti.cs.mu.OZ.AU by munnari.OZ.AU with SMTP (5.83--+1.3.1+0.56) id GA11256; Sat, 15 Feb 1997 17:03:07 +1100 (from kre@munnari.OZ.AU)
To: Mike O'Dell <mo@uu.net>
Cc: jis@mit.edu, The IESG <iesg@ietf.org>, The Internet Architecture Board <iab@ietf.org>, perry@piermont.com, ylo@ssh.fi
Subject: Re: Proposed WG: SSH, Secure Shell (SECSH) - names, you want names??
In-Reply-To: Your message of "Fri, 14 Feb 1997 07:04:17 CDT." <QQccvw28824.199702141204@rodan.UU.NET>
Date: Sat, 15 Feb 1997 17:03:06 +1100
Message-Id: <23522.855986586@munnari.OZ.AU>
Sender: iesg-request@ietf.org
From: Robert Elz <kre@munnari.oz.au>

    Date:        Fri, 14 Feb 1997 07:04:17 -0500
    From:        Mike O'Dell <mo@UU.NET>
    Message-ID:  <QQccvw28824.199702141204@rodan.UU.NET>

    How about "Secure Session Handyman"

(and all the others) - they're nice (cute), but address the wrong
problem - the number one issue is that "ssh" cannot be the
acronym (because the site security handbook WG has that one).

As I said, if the ssh label could be retained, inertia (general
familiarity) would argue in favour of it, and I wouldn't have
mentioned this at all.

However, as the new WG cannot be ssh, the opportunity arises to
give it a more meaningful name than "secure shell" (and the
current proposed "secsh" acronym from the draft charter).

kre