IMAP4 Binary Content Extension

Metadata

Publisher: IETF
Doc Type: Standard
Pages: 8
Abstract: This memo defines the Binary extension to the Internet Message Access Protocol (IMAP4). It provides a mechanism for IMAP4 clients and servers to exchange message body data without using a MIME content-transfer- encoding. [STANDARDS-TRACK]
Publication Date: 2003-04-01
Status Note: Proposed Standard
DOI: 10.17487/RFC3516
Link: https://doi.org/10.17487/RFC3516
Author(s): Lyndon Nerenberg
Keyword(s): IMAP

Latest version of IETF RFC 3516

Document Versions — IETF RFC 3516

▶ IETF RFC 3516 (2003-04-01)

THIS DOC [ACTIVE] [LATEST VERSION]

Amended by:

RFC4466 NOT IN REGISTRY

Normative Reference(s)

IETF RFC 2045 [Active*]
IETF RFC 2047 [Active*]
IETF RFC 2119 [Active*]
IETF RFC 2234 [Superseded*]
IETF RFC 3501 [Superseded*]

Source Data (JSON)

Full registry record with provenance metadata. Open directly: /api/doc/RFC3516.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 3516, IMAP4 Binary Content Extension. Available at https://doi.org/10.17487/RFC3516

Snippet:

IETF RFC 3516, IMAP4 Binary Content Extension. Available at https://doi.org/10.17487/RFC3516

HTML (ISO 690 compliant)

Preview:

IETF RFC 3516, IMAP4 Binary Content Extension. Available at https://doi.org/10.17487/RFC3516

Snippet:

<span class="citation"><cite>IETF RFC 3516</cite>, IMAP4 Binary Content Extension. Available at <a href="https://doi.org/10.17487/RFC3516" target="_blank" rel="noopener">https://doi.org/10.17487/RFC3516</a></span>

SMPTE's HTML Pub

Preview:

IETF RFC 3516, IMAP4 Binary Content Extension
doi: 10.17487/RFC3516
url: https://doi.org/10.17487/RFC3516

Snippet:

<li>
<cite id="bib-rfc3516">IETF RFC 3516</cite>, IMAP4 Binary Content Extension
<span class="doi">10.17487/RFC3516</span>
</li>

Referenced By

IETF RFC 4005 [Superseded*]