RFC 4954: SMTP Service Extension for Authentication
In plain English — editorial summary, not part of the RFC
This document defines a Simple Mail Transport Protocol (SMTP) extension whereby an SMTP client may indicate an authentication mechanism to the server, perform an authentication protocol exchange, and optionally negotiate a security layer for subsequent protocol interactions during this session. This extension includes a profile of the Simple Authentication and Security Layer (SASL) for SMTP. This document obsoletes RFC 2554. [STANDARDS-TRACK]
Document record
- Document ID
- RFC4954
- Published
- July 2007
- Authors
- R. Siemborski; A. Melnikov
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- —
- Pages
- 20
- Also known as
- —
Topics
Referenced by
One later RFC formally updates or obsoletes part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 4752The Kerberos V5 ("GSSAPI") Simple Authentication and Security Layer (SASL) MechanismCurrent
November 2006
- RFC 4643Network News Transfer Protocol (NNTP) Extension for AuthenticationCurrent
October 2006
- RFC 4422Simple Authentication and Security Layer (SASL)Current
June 2006
- RFC 5803Lightweight Directory Access Protocol (LDAP) Schema for Storing Salted Challenge Response Authentication Mechanism (SCRAM) SecretsCurrent
July 2010
- RFC 4013SASLprep: Stringprep Profile for User Names and PasswordsObsoleted
March 2005
- RFC 7804Salted Challenge Response HTTP Authentication MechanismCurrent
March 2016
- RFC 7832Application Bridging for Federated Access Beyond Web (ABFAB) Use CasesCurrent
May 2016
- RFC 8437IMAP UNAUTHENTICATE Extension for Connection ReuseCurrent
August 2018
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?