STD 60, RFC 2920 on SMTP for Command Pipelining
RFC Editor <rfc-ed@ISI.EDU> Thu, 21 September 2000 17:49 UTC
Received: from loki.ietf.org (loki [10.27.2.29]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA11006; Thu, 21 Sep 2000 13:49:30 -0400 (EDT)
Received: (from adm@localhost) by loki.ietf.org (8.9.1b+Sun/8.9.1) id NAA16298 for ietf-123-outbound.10@ietf.org; Thu, 21 Sep 2000 13:35:02 -0400 (EDT)
Received: from ietf.org (odin.ietf.org [10.27.2.28]) by loki.ietf.org (8.9.1b+Sun/8.9.1) with ESMTP id NAA16222 for <all-ietf@loki.ietf.org>; Thu, 21 Sep 2000 13:22:10 -0400 (EDT)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by ietf.org (8.9.1a/8.9.1a) with SMTP id NAA10369 for <all-ietf@ietf.org>; Thu, 21 Sep 2000 13:22:00 -0400 (EDT)
Received: from ISI.EDU (jet.isi.edu [128.9.160.87]) by boreas.isi.edu (8.9.3/8.9.3) with ESMTP id KAA17720; Thu, 21 Sep 2000 10:21:59 -0700 (PDT)
Message-Id: <200009211721.KAA17720@boreas.isi.edu>
To: IETF-Announce:;
Subject: STD 60, RFC 2920 on SMTP for Command Pipelining
Cc: rfc-ed@ISI.EDU
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
Date: Thu, 21 Sep 2000 10:21:59 -0700
From: RFC Editor <rfc-ed@ISI.EDU>
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. Joyce K. Reynolds and Sandy Ginoza 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.