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|
Current Meeting ReportNone received.