Protocol Action: SMTP Service Extension for Command Pipelining to Standard

The IESG <iesg-secretary@ietf.org> Wed, 12 July 2000 16:49 UTC

Received: from loki.ietf.org (loki [10.27.2.29]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA02002; Wed, 12 Jul 2000 12:49:47 -0400 (EDT)
Received: (from adm@localhost) by loki.ietf.org (8.9.1b+Sun/8.9.1) id MAA29791 for ietf-123-outbound.10@ietf.org; Wed, 12 Jul 2000 12:45:01 -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 HAA26534 for <all-ietf@loki.ietf.org>; Wed, 12 Jul 2000 07:32:51 -0400 (EDT)
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA16914; Wed, 12 Jul 2000 07:32:51 -0400 (EDT)
Message-Id: <200007121132.HAA16914@ietf.org>
To: IETF-Announce:;
Cc: RFC Editor <rfc-editor@isi.edu>
Cc: Internet Architecture Board <iab@isi.edu>
From: The IESG <iesg-secretary@ietf.org>
Subject: Protocol Action: SMTP Service Extension for Command Pipelining to Standard
Date: Wed, 12 Jul 2000 07:32:51 -0400
Sender: scoya@cnri.reston.va.us


The IESG has approved the Internet-Draft 'SMTP Service Extension for
Command Pipelining' <draft-freed-smtp-pipe-01.txt> as a Standard. This
document replaces RFC2197, currently a Draft Standard.

This has been reviewed in the IETF but is not the product of an IETF
Working Group.  The IESG contact person is Patrik Faltstrom.

 
Technical Summary
 
This memo defines an extension to the SMTP service whereby a
server can indicate the extent of its ability to accept
multiple commands in a single TCP send operation. Using a
single TCP send operation for multiple commands can improve
SMTP performance significantly.

Working Group Summary

The present document is an updated version of [RFC-2197],
which in turn was a revision of [RFC-1854]. Only textual and
editorial changes have been made; the protocol has not changed
in any way.

Protocol Quality

Patrik Faltstrom has reviewed the protocol for the IESG.

SMTP pipelining considerably reduces the number of round trips in the
SMTP protocol. Implementations of SMTP pipeliningg have experienced a
significant reduction in the average amount of time needed to transmit
a message, and a corresponding decrease in message latency.

Implementation information can be found at
http://www.ietf.org/IESG/SMTP-PIPELINING-Standard-implementation