Critical Content Multi-purpose Internet Mail Extensions (MIME) Parameter
Metadata
- Publisher
- IETF
- Doc Type
- Standard
- Pages
- 24
- Abstract
- This document describes the use of a mechanism for identifying body parts that a sender deems critical in a multi-part Internet mail message. The mechanism described is a parameter to Content-Disposition, as described by RFC 3204. By knowing what parts of a message the sender deems critical, a content gateway can intelligently handle multi-part messages when providing gateway services to systems of lesser capability. Critical content can help a content gateway to decide what parts to forward. It can indicate how hard a gateway should try to deliver a body part. It can help the gateway to pick body parts that are safe to silently delete when a system of lesser capability receives a message. In addition, critical content can help the gateway chose the notification strategy for the receiving system. Likewise, if the sender expects the destination to do some processing on a body part, critical content allows the sender to mark body parts that the receiver must process. [STANDARDS-TRACK]
- Publication Date
- 2003-01-01
- Status Note
- Proposed Standard
- DOI
10.17487/RFC3459- Link
- https://doi.org/10.17487/RFC3459
- Author(s)
- Eric Burger
- Keyword(s)
- MIME
Latest version of IETF RFC 3459
Document Versions — IETF RFC 3459
-
▶ IETF RFC 3459 (2003-01-01)THIS DOC [ACTIVE] [LATEST VERSION]
Normative Reference(s)
- IETF RFC 822 [Superseded*]
- IETF RFC 1847 [Active*]
- IETF RFC 2026 [Active*]
- IETF RFC 2045 [Active*]
- IETF RFC 2046 [Active, Amended*]
- IETF RFC 2119 [Active*]
- IETF RFC 2156 [Active*]
- IETF RFC 2183 [Active*]
- IETF RFC 2234 [Superseded*]
- IETF RFC 2298 [Superseded*]
- IETF RFC 2421 [Superseded*]
- IETF RFC 2426 [Superseded*]
- IETF RFC 2480 [Active*]
- IETF RFC 2821 [Superseded*]
- IETF RFC 3204 [Active*]
- IETF RFC 3238 [Active*]
- IETF RFC 3261 [Active*]
- IETF RFC 3461 [Active*]
- IETF RFC 3463 [Active*]
- IETF RFC 3464 [Active*]
Source Data (JSON)
Full registry record with provenance metadata. Open directly: /api/doc/RFC3459.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 3459, Critical Content Multi-purpose Internet Mail Extensions (MIME) Parameter. Available at https://doi.org/10.17487/RFC3459
Snippet:
IETF RFC 3459, Critical Content Multi-purpose Internet Mail Extensions (MIME) Parameter. Available at https://doi.org/10.17487/RFC3459
HTML (ISO 690 compliant)
Preview:
IETF RFC 3459, Critical Content Multi-purpose Internet Mail Extensions (MIME) Parameter. Available at https://doi.org/10.17487/RFC3459
Snippet:
<span class="citation"><cite>IETF RFC 3459</cite>, Critical Content Multi-purpose Internet Mail Extensions (MIME) Parameter. Available at <a href="https://doi.org/10.17487/RFC3459" target="_blank" rel="noopener">https://doi.org/10.17487/RFC3459</a></span>
SMPTE's HTML Pub
Preview:
IETF RFC 3459, Critical Content Multi-purpose Internet Mail Extensions (MIME) Parameter
doi: 10.17487/RFC3459
url: https://doi.org/10.17487/RFC3459
doi: 10.17487/RFC3459
url: https://doi.org/10.17487/RFC3459
Snippet:
<li> <cite id="bib-rfc3459">IETF RFC 3459</cite>, Critical Content Multi-purpose Internet Mail Extensions (MIME) Parameter <span class="doi">10.17487/RFC3459</span> </li>
Referenced By
- IETF RFC 3458 [Active*]
- IETF RFC 5621 [Active*]
- IETF RFC 7852 [Active*]