RFC 2808: The SecurID(r) SASL Mechanism
In plain English — editorial summary, not part of the RFC
This document defines a SASL (Simple Authentication and Security Layer) authentication mechanism using SecurID (a hardware token card product (or software emulation thereof) produced by RSA Security Inc., which is used for end-user authentication), thereby providing a means for such tokens to be used in SASL environments. This mechanism is only is only for authentication, and has no effect on the protocol encoding and is not designed to provide integrity or confidentiality services. This memo provides information for the Internet community.
Document record
- Document ID
- RFC2808
- Published
- April 2000
- Authors
- M. Nystrom
- Status
- INFORMATIONAL
- Stream
- Legacy
- Area
- —
- Pages
- 11
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 2245Anonymous SASL MechanismObsoleted
November 1997
- RFC 4505Anonymous Simple Authentication and Security Layer (SASL) MechanismCurrent
June 2006
- RFC 2554SMTP Service Extension for AuthenticationObsoleted
March 1999
- RFC 2487SMTP Service Extension for Secure SMTP over TLSObsoleted
January 1999
- RFC 6331Moving DIGEST-MD5 to HistoricCurrent
July 2011
- RFC 2595Using TLS with IMAP, POP3 and ACAPUpdated
June 1999
- RFC 3206The SYS and AUTH POP Response CodesCurrent
February 2002
- RFC 2271An Architecture for Describing SNMP Management FrameworksObsoleted
January 1998
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?