Protocol Action: SMTP Service Extension for Command Pipelining to Draft Standard

The IESG <iesg-secretary@ietf.org> Wed, 03 September 1997 11:07 UTC

Received: from ietf.org by ietf.org id aa04200; 3 Sep 97 7:07 EDT
Received: from ietf.ietf.org by ietf.org id aa04047; 3 Sep 97 7:00 EDT
To: IETF-Announce:;
Cc: RFC Editor <rfc-editor@isi.edu>
Cc: Internet Architecture Board <iab@isi.edu>
Sender: ietf-announce-request@ietf.org
From: The IESG <iesg-secretary@ietf.org>
Subject: Protocol Action: SMTP Service Extension for Command Pipelining to Draft Standard
Date: Wed, 03 Sep 1997 07:00:15 -0400
X-Orig-Sender: scoya@ietf.org
Message-ID: <9709030700.aa04047@ietf.org>

  The IESG has approved the Internet-Draft "SMTP Service Extension for
  Command Pipelining" <draft-freed-smtp-pipeline-02.txt> as a Draft
  Standard. This document will update RFC1854, currently a Proposed
  Standard. The IESG contact person is Keith Moore.


Technical Summary

 Experience with traditional SMTP indicates that high response latency
 from SMTP servers is often responsible for significant delay in
 delivery of messages.  This extension provides a performance
 improvement for SMTP, allowing several SMTP commands to be issued by a
 client before it examines responses from the server.

Working Group Summary

 This revision is not the product of a working group.

Protocol Quality

 Keith Moore reviewed the specification for IESG. Multiple
 client implementations are known to exist and interoperate.

Implementation Statement:

  There are a bunch of independent implementations, but I can list two
  major ones right off: PMDF and software.com's post.office. Heck,
  there's even an implementation of SMTP pipelining in the MUMPS mail
  system, according to the folks at the USDA.