RFC 2920: SMTP Service Extension for Command Pipelining

In plain English — editorial summary, not part of the RFC

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. [STANDARDS-TRACK]

Document record

Document ID

RFC2920

Published

September 2000

Authors

N. Freed

Status

INTERNET STANDARD

Stream

Legacy

Area

—

Pages

9

Also known as

STD60

Obsoletes:

RFC 2197

• Read the full RFC text →
• Plain text version
• IETF Datatracker history
• DOI: 10.17487/RFC2920

Topics

• SMTP-Pipe
• simple mail transfer protocol
• TCP
• transmission control protocol

Standards lineage

This document is one revision in a chain of 3 RFCs, each formally replacing the one before it.

1. RFC 1854 (1995)
2. →RFC 2197 (1997)
3. →RFC 2920 (2000)

Read the full history of SMTP Service Extension for Command Pipelining →

Related documents

Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.

• RFC 2873TCP Processing of the IPv4 Precedence FieldObsoleted

  June 2000

• RFC 2883An Extension to the Selective Acknowledgement (SACK) Option for TCPCurrent

  July 2000

• RFC 2861TCP Congestion Window ValidationObsoleted

  June 2000

• RFC 2988Computing TCP's Retransmission TimerObsoleted

  November 2000

• RFC 3042Enhancing TCP's Loss Recovery Using Limited TransmitCurrent

  January 2001

• RFC 3081Mapping the BEEP Core onto TCPCurrent

  March 2001

• RFC 3293General Switch Management Protocol (GSMP) Packet Encapsulations for Asynchronous Transfer Mode (ATM), Ethernet and Transmission Control Protocol (TCP)Current

  June 2002

• RFC 2507IP Header CompressionCurrent

  February 1999

Also filed under

• INTERNET STANDARD
• 2000
• Legacy stream
• STD 60