RFC 3459: Critical Content Multi-purpose Internet Mail Extensions (MIME) Parameter
In plain English — editorial summary, not part of the RFC
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]
Document record
- Document ID
- RFC3459
- Published
- January 2003
- Authors
- E. Burger
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- app
- Pages
- 24
- Also known as
- —
Topics
Referenced by
One later RFC formally updates or obsoletes part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 3302Tag Image File Format (TIFF) - image/tiff MIME Sub-type RegistrationCurrent
September 2002
- RFC 3250Tag Image File Format Fax eXtended (TIFF-FX) - image/tiff-fx MIME Sub-type RegistrationObsoleted
September 2002
- RFC 3949File Format for Internet FaxCurrent
February 2005
- RFC 3950Tag Image File Format Fax eXtended (TIFF-FX) - image/tiff-fx MIME Sub-type RegistrationCurrent
February 2005
- RFC 2913MIME Content Types in Media Feature ExpressionsCurrent
September 2000
- RFC 2912Indicating Media Features for MIME ContentCurrent
September 2000
- RFC 2779Instant Messaging / Presence Protocol RequirementsCurrent
February 2000
- RFC 2778A Model for Presence and Instant MessagingCurrent
February 2000
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?