NOTE: This charter is a snapshot of the 51st IETF Meeting in London, England. It may now be out-of-date. Last Modified: 31-Jul-01
Bill Sommerfeld <sommerfeld@east.sun.com>
Jeffrey Schiller <jis@mit.edu>
Marcus Leech <mleech@nortelnetworks.com>
Jeffrey Schiller <jis@mit.edu>
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/
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.
Done |
|
Submit Internet-Draft on SSH-2.0 protocol |
Done |
|
Decide on Transport Layer protocol at Memphis IETF. |
Done |
|
Post revised core secsh drafts |
Feb 01 |
|
Submit core drafts to IESG for publication as proposed standard |
Feb 01 |
|
Post extensions drafts for review |
Feb 01 |
|
Start sending extensions drafts to Last Call |
· SSH Transport Layer Protocol
· Generic Message Exchange Authentication For SSH
· GSSAPI Authentication and Key Exchange for the Secure Shell Protocol
· SECSH Public Key File Format
· Diffie-Hellman Group Exchange for the SSH Transport Layer Protocol
None received.
None received.