Telnet SASL Option
draft-newman-telnet-sasl-01
Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
---|---|---|---|
Author | Chris Newman | ||
Last updated | 1998-11-09 | ||
RFC stream | (None) | ||
Intended RFC status | (None) | ||
Formats | |||
Stream | Stream state | (No stream defined) | |
Consensus boilerplate | Unknown | ||
RFC Editor Note | (None) | ||
IESG | IESG state | Expired | |
Telechat date | (None) | ||
Responsible AD | (None) | ||
Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
It is common today for Internet client software to implement multiple Internet protocols. SASL [SASL] provides an authentication framework which permits multi-protocol clients and servers to reuse security-sensitive authentication code. This memo defines a SASL profile for the Telnet [TELNET] protocol. This proposal will be discussed on the telnet-ietf mailing list. To subscribe, send the word 'subscribe' to <telnet-ietf-request@bsdi.com>.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)