SMTP Service Extension for Command Pipelining
Metadata
- Publisher
- IETF
- Doc Type
- Standard
- Pages
- 7
- 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
- 1995-10-01
- Status Note
- Proposed Standard
- DOI
10.17487/RFC1854- Link
- https://doi.org/10.17487/RFC1854
- Author(s)
- Ned Freed
- Keyword(s)
- SMTP
Latest version of IETF RFC 1854
Document Versions — IETF RFC 1854
-
▶ IETF RFC 1854 (1995-10-01)THIS DOC [SUPERSEDED] [LATEST VERSION]
Bibliographic Reference(s)
- IETF RFC 821 [Superseded*]
- IETF RFC 1651 [Superseded*]
Source Data (JSON)
Full registry record with provenance metadata. Open directly: /api/doc/RFC1854.json
Reference Tree
Explore all references and references to this document, as a navigable tree.
Open Reference TreeReference this Doc
Plain text (ISO 690 compliant)
Preview:
IETF RFC 1854, SMTP Service Extension for Command Pipelining. Available at https://doi.org/10.17487/RFC1854
Snippet:
IETF RFC 1854, SMTP Service Extension for Command Pipelining. Available at https://doi.org/10.17487/RFC1854
HTML (ISO 690 compliant)
Preview:
IETF RFC 1854, SMTP Service Extension for Command Pipelining. Available at https://doi.org/10.17487/RFC1854
Snippet:
<span class="citation"><cite>IETF RFC 1854</cite>, SMTP Service Extension for Command Pipelining. Available at <a href="https://doi.org/10.17487/RFC1854" target="_blank" rel="noopener">https://doi.org/10.17487/RFC1854</a></span>
SMPTE's HTML Pub
Preview:
IETF RFC 1854, SMTP Service Extension for Command Pipelining
doi: 10.17487/RFC1854
url: https://doi.org/10.17487/RFC1854
doi: 10.17487/RFC1854
url: https://doi.org/10.17487/RFC1854
Snippet:
<li> <cite id="bib-rfc1854">IETF RFC 1854</cite>, SMTP Service Extension for Command Pipelining <span class="doi">10.17487/RFC1854</span> </li>
Referenced By
- IETF draft-ema-vpim-06 [Active*]
- IETF RFC 1911 [Superseded*]
- IETF RFC 2033 [Active*]
- IETF RFC 2197 [Superseded*]
- IETF RFC 2421 [Superseded*]
- IETF RFC 2920 [Active*]