SMTP Service Extension for Command Pipelining

Metadata

Publisher: IETF
Doc Type: Standard
Pages: 8
Abstract: 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. [STANDARDS-TRACK]
Publication Date: 1997-09-01
Status Note: Draft Standard
DOI: 10.17487/RFC2197
Link: https://doi.org/10.17487/RFC2197
Author(s): Ned Freed
Keyword(s): SMTP-Pipe, SMTP, TCP

Latest version of IETF RFC 2197

Document Versions — IETF RFC 2197

▶ IETF RFC 2197 (1997-09-01)

THIS DOC [SUPERSEDED] [LATEST VERSION]

Superseded by:

IETF RFC 2920 [Active*]

Bibliographic Reference(s)

IETF RFC 821 [Superseded*]
IETF RFC 1854 [Superseded*]
IETF RFC 1869 [Superseded*]
IETF RFC 2119 [Active*]

Source Data (JSON)

Full registry record with provenance metadata. Open directly: /api/doc/RFC2197.json

Reference Tree

Explore all references and references to this document, as a navigable tree.

Open Reference Tree

Reference this Doc

Plain text (ISO 690 compliant)

Preview:

IETF RFC 2197, SMTP Service Extension for Command Pipelining. Available at https://doi.org/10.17487/RFC2197

Snippet:

IETF RFC 2197, SMTP Service Extension for Command Pipelining. Available at https://doi.org/10.17487/RFC2197

HTML (ISO 690 compliant)

Preview:

IETF RFC 2197, SMTP Service Extension for Command Pipelining. Available at https://doi.org/10.17487/RFC2197

Snippet:

<span class="citation"><cite>IETF RFC 2197</cite>, SMTP Service Extension for Command Pipelining. Available at <a href="https://doi.org/10.17487/RFC2197" target="_blank" rel="noopener">https://doi.org/10.17487/RFC2197</a></span>

SMPTE's HTML Pub

Preview:

IETF RFC 2197, SMTP Service Extension for Command Pipelining
doi: 10.17487/RFC2197
url: https://doi.org/10.17487/RFC2197

Snippet:

<li>
<cite id="bib-rfc2197">IETF RFC 2197</cite>, SMTP Service Extension for Command Pipelining
<span class="doi">10.17487/RFC2197</span>
</li>

Referenced By

IETF RFC 2449 [Active*]
IETF RFC 2476 [Superseded*]
IETF RFC 2920 [Active*]