Proposed WG: SSH, Secure Shell (SECSH)

"Jeffrey I. Schiller" <jis@mit.edu> Fri, 14 February 1997 07:25 UTC

Received: from cnri by ietf.org id aa29752; 14 Feb 97 2:25 EST
Received: from ietf.org by CNRI.Reston.VA.US id aa12840; 14 Feb 97 2:25 EST
Received: from ietf.org by ietf.org id aa29739; 14 Feb 97 2:25 EST
Received: from BOZO.MIT.EDU by ietf.org id aa29734; 14 Feb 97 2:24 EST
Received: from 18.162.1.1 by bozo.MIT.EDU with SMTP id HAA05903; Fri, 14 Feb 1997 07:21:15 GMT
Message-ID: <330412AB.F9A@mit.edu>
Date: Fri, 14 Feb 1997 02:22:19 -0500
Sender: iesg-request@ietf.org
From: "Jeffrey I. Schiller" <jis@mit.edu>
Reply-To: jis@mit.edu
Organization: Massachusetts Institute of Technology
X-Mailer: Mozilla 3.0 (Macintosh; U; 68K)
MIME-Version: 1.0
To: The IESG <iesg@ietf.org>, The Internet Architecture Board <iab@ietf.org>
CC: perry@piermont.com, ylo@ssh.fi
Subject: Proposed WG: SSH, Secure Shell (SECSH)
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

-----BEGIN PGP SIGNED MESSAGE-----

Proposed Working Group:

SSH, Secure Shell, Working Group (SECSH)

Chair
  Perry E. Metzger <perry@piermont.com>

Area Director (Security):
  Jeffrey I. Schiller <jis@mit.edu>

Mailing list:
  ietf-ssh@clinet.fi; to subscribe, send mail to majordomo@clinet.fi
  with "subscribe ietf-ssh@clinet.fi" in body.

Archive: [TBD]

Charter
  The goal of the working group is to update and standardize the
  popular SSH protocol.  SSH provides support for secure remote login,
  secure file transfer, and secure TCP/IP and X11 forwardings.  It can
  automatically encrypt, authenticate, and compress transmitted data.
  The working group will attempt to assure that the SSH protocol
  - provides strong security against cryptanalysis and protocol attacks,
  - can work reasonably well without a global key management or
    certificate infrastructure,
  - can utilize existing certificate infrastructures (e.g., DNSSEC, SPKI,
    X.509) when available,
  - can be made easy to deploy and take into use,
  - requires minimum or no manual interaction from users,
  - is reasonably clean and simple to implement.
  The resulting protocol will operate over TCP/IP or other reliable
  but insecure transport.  It is intended to be implemented at the
  application level.
Milestones
  Dec 1996      Meets as informal BOF at San Jose IETF
  Feb 1997      Publish SSH-2.0 protocol as internet-draft
  Apr 1997      WG meets at Memphis: decide on transport layer protocol
  Jul 1997      WG meets at Munich: finalize upper level protocols
  Sep 1997      Submit protocols as proposed standard
  Dec 1997      WG meets

-----BEGIN PGP SIGNATURE-----
Version: 2.6.2

iQCVAwUBMwQSO8UtR20Nv5BtAQE1ogP/dbfyAfoQZj8TIYqpG6N5VfVJxgVm8BCA
4s/c5L/EQ6JhG++yhVBYZaHZDQVwM0LyB7nahb7gszIN3N1vfOJdCghMvlVpBrOT
shD+ADKBKhZ/4rSPwwY+u2aEVe9+KMuZnrRsJj3VdRrsvr6RKZxEg9lBXXiQLpQ9
yMV5vBNAgtQ=
=UYAe
-----END PGP SIGNATURE-----