A new Request for Comments is now available in online RFC libraries.


        STD 60 
        RFC 2920

        Title:      SMTP Service Extension for Command Pipelining
        Author(s):  N. Freed
        Status:     Standards Track 
        Date:       September 2000
        Mailbox:    ned.freed@innosoft.com
        Pages:      9
        Characters: 17065
        Obsoletes:  2197

        I-D Tag:    draft-freed-smtp-pipe-01.txt

        URL:        ftp://ftp.isi.edu/in-notes/rfc2920.txt


This memo defines an extension to the Simple Mail Transfer Protocol
(SMTP) service whereby a server can indicate the extent of its ability
to accept multiple commands in a single Transmission Control Protocol
(TCP) send operation. Using a single TCP send operation for multiple
commands can improve SMTP performance significantly.

This is now a 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.


