Secure Shell (secsh) Charter

2.6.7 Secure Shell (secsh)

Last Modified: 2003-06-20

Chair(s):

Bill Sommerfeld <sommerfeld@sun.com>

Security Area Director(s):

Russell Housley <housley@vigilsec.com>
Steven Bellovin <smb@research.att.com>

Security Area Advisor:

Russell Housley <housley@vigilsec.com>

Mailing Lists:

General Discussion: ietf-ssh@netbsd.org
To Subscribe: majordomo@netbsd.org
In Body: subscribe ietf-ssh
Archive: ftp://ftp.ietf.org/ietf-mail-archive/secsh/

Description of Working Group:

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

o provides strong security against cryptanalysis and protocol
attacks,

o can work reasonably well without a global key management or
certificate infrastructure,

o can utilize existing certificate infrastructures (e.g., DNSSEC,
SPKI, X.509) when available,

o can be made easy to deploy and take into use,

o requires minimum or no manual interaction from users,

o 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.

Goals and Milestones:

Done		Submit Internet-Draft on SSH-2.0 protocol
Done		Decide on Transport Layer protocol at Memphis IETF.
Done		Post revised core secsh drafts
Done		Submit core drafts to IESG for publication as proposed standard
Done		Post extensions drafts for review
Done		Start sending extensions drafts to Last Call
Apr 02		GSSAPI draft ready for last call
Apr 02		Publish draft on new crypto modes
May 02		Agent draft ready for last call
May 02		Publish draft on X.509v3/pkix support (or subsume into gssapi draft)
May 02		Publish draft on terminal server support
Dec 02		File transfer draft ready for last call