RFC 2554 on SMTP Authentication
RFC Editor <rfc-ed@ISI.EDU> Tue, 30 March 1999 18:05 UTC
Received: by ietf.org (8.9.1a/8.9.1a) id NAA22414 for ietf-123-outbound.10@ietf.org; Tue, 30 Mar 1999 13:05:03 -0500 (EST)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA21970 for <all-ietf@ietf.org>; Tue, 30 Mar 1999 12:47:42 -0500 (EST)
Received: from ISI.EDU (jet.isi.edu [128.9.160.87]) by boreas.isi.edu (8.8.7/8.8.6) with ESMTP id JAA09422; Tue, 30 Mar 1999 09:47:37 -0800 (PST)
Message-Id: <199903301747.JAA09422@boreas.isi.edu>
To: IETF-Announce:;
Subject: RFC 2554 on SMTP Authentication
Cc: rfc-ed@ISI.EDU
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
Date: Tue, 30 Mar 1999 09:47:37 -0800
From: RFC Editor <rfc-ed@ISI.EDU>
A new Request for Comments is now available in online RFC libraries. RFC 2554: Title: SMTP Service Extension for Authentication Author(s): J. Myers Status: Proposed Standard Date: March 1999 Mailbox: jgmyers@netscape.com Pages: 11 Characters: 20534 Updates/Obsoletes/See Also: None I-D Tag: draft-myers-smtp-auth-12.txt URL: ftp://ftp.isi.edu/in-notes/rfc2554.txt This document defines an SMTP service extension [ESMTP] 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. This extension is a profile of the Simple Authentication and Security Layer [SASL]. This is now a Proposed Standard Protocol. 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@IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info@RFC-EDITOR.ORG Subject: getting rfcs help: ways_to_get_rfcs Requests for special distribution should be addressed to either the author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution.echo Submissions for Requests for Comments should be sent to RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information. Joyce K. Reynolds and Alegre Ramos USC/Information Sciences Institute ... Below is the data which will enable a MIME compliant Mail Reader implementation to automatically retrieve the ASCII version of the RFCs.
- RFC 2554 on SMTP Authentication RFC Editor