[rfc-dist] RFC 4954 on SMTP Service Extension for Authentication
rfc-editor at rfc-editor.org
Mon Jul 23 11:47:03 PDT 2007
A new Request for Comments is now available in online RFC libraries.
Title: SMTP Service Extension for Authentication
Author: R. Siemborski, Ed.,
A. Melnikov, Ed.
Status: Standards Track
Date: July 2007
Mailbox: robsiemb at google.com,
Alexey.Melnikov at isode.com
I-D Tag: draft-siemborski-rfc2554bis-09.txt
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]
This is now a Proposed Standard Protocol.
STANDARDS TRACK: This document specifies an Internet standards track
protocol for the Internet community,and requests discussion and
suggestions for improvements.Please refer to the current edition of the
Internet Official Protocol Standards (STD 1) for the standardization
state and status of this protocol. Distribution of this memo is unlimited.
This announcement is sent to the IETF list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST at IETF.ORG. Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST at RFC-EDITOR.ORG.
Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info at RFC-EDITOR.ORG with the message body
help: ways_to_get_rfcs. For example:
To: rfc-info at RFC-EDITOR.ORG
Subject: getting rfcs
Requests for special distribution should be addressed to either the
author of the RFC in question, or to RFC-Manager at RFC-EDITOR.ORG. Unless
specifically noted otherwise on the RFC itself, all RFCs are for
Submissions for Requests for Comments should be sent to
RFC-EDITOR at RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC
Authors, for further information.
The RFC Editor Team
USC/Information Sciences Institute
More information about the rfc-dist