Network Working Group G. Klyne
Internet-Draft Nine by Nine
Expires: October 18, 2004 J. Palme
Stockholm University/KTH
April 19, 2004
Registration of mail and MIME header fields
draft-klyne-hdrreg-mail-04
Status of this Memo
This document is an Internet-Draft and is in full conformance with
all provisions of Section 10 of RFC2026.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that other
groups may also distribute working documents as Internet-Drafts.
Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at http://
www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html.
This Internet-Draft will expire on October 18, 2004.
Copyright Notice
Copyright (C) The Internet Society (2004). All Rights Reserved.
Abstract
This document defines the initial IANA registration for permanent
mail and MIME message header fields, per [[[RFC XXXX [1]]]].
Discussion of this document
Please send comments to <ietf-822@imc.org>. To subscribe to this
list, send a message with the body 'subscribe' to
<ietf-822-request@imc.org>.
Klyne & Palme Expires October 18, 2004 [Page 1]
Internet-Draft Mail and MIME header fields April 2004
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . 5
1.1 Structure of this document . . . . . . . . . . . . . . . . 5
1.2 Document terminology and conventions . . . . . . . . . . . 5
2. Registration templates . . . . . . . . . . . . . . . . . . 5
2.1 Permanent mail header field registrations . . . . . . . . 5
2.1.1 Header field: Date . . . . . . . . . . . . . . . . . . . . 8
2.1.2 Header field: From . . . . . . . . . . . . . . . . . . . . 8
2.1.3 Header field: Sender . . . . . . . . . . . . . . . . . . . 8
2.1.4 Header field: Reply-To . . . . . . . . . . . . . . . . . . 9
2.1.5 Header field: To . . . . . . . . . . . . . . . . . . . . . 9
2.1.6 Header field: Cc . . . . . . . . . . . . . . . . . . . . . 10
2.1.7 Header field: Bcc . . . . . . . . . . . . . . . . . . . . 10
2.1.8 Header field: Message-ID . . . . . . . . . . . . . . . . . 11
2.1.9 Header field: In-Reply-To . . . . . . . . . . . . . . . . 11
2.1.10 Header field: References . . . . . . . . . . . . . . . . . 12
2.1.11 Header field: Subject . . . . . . . . . . . . . . . . . . 12
2.1.12 Header field: Comments . . . . . . . . . . . . . . . . . . 13
2.1.13 Header field: Keywords . . . . . . . . . . . . . . . . . . 13
2.1.14 Header field: Resent-Date . . . . . . . . . . . . . . . . 14
2.1.15 Header field: Resent-From . . . . . . . . . . . . . . . . 14
2.1.16 Header field: Resent-Sender . . . . . . . . . . . . . . . 14
2.1.17 Header field: Resent-To . . . . . . . . . . . . . . . . . 15
2.1.18 Header field: Resent-Cc . . . . . . . . . . . . . . . . . 15
2.1.19 Header field: Resent-Bcc . . . . . . . . . . . . . . . . . 16
2.1.20 Header field: Resent-Reply-To . . . . . . . . . . . . . . 16
2.1.21 Header field: Resent-Message-ID . . . . . . . . . . . . . 17
2.1.22 Header field: Return-Path . . . . . . . . . . . . . . . . 17
2.1.23 Header field: Received . . . . . . . . . . . . . . . . . . 17
2.1.24 Header field: Disposition-Notification-To . . . . . . . . 18
2.1.25 Header field: Disposition-Notification-Options . . . . . . 18
2.1.26 Header field: Accept-Language . . . . . . . . . . . . . . 19
2.1.27 Header field: Original-Message-ID . . . . . . . . . . . . 19
2.1.28 Header field: PICS-Label . . . . . . . . . . . . . . . . . 20
2.1.29 Header field: Encoding . . . . . . . . . . . . . . . . . . 20
2.1.30 Header field: List-Archive . . . . . . . . . . . . . . . . 21
2.1.31 Header field: List-Help . . . . . . . . . . . . . . . . . 21
2.1.32 Header field: List-ID . . . . . . . . . . . . . . . . . . 22
2.1.33 Header field: List-Owner . . . . . . . . . . . . . . . . . 22
2.1.34 Header field: List-Post . . . . . . . . . . . . . . . . . 23
2.1.35 Header field: List-Subscribe . . . . . . . . . . . . . . . 23
2.1.36 Header field: List-Unsubscribe . . . . . . . . . . . . . . 24
2.1.37 Header field: Message-Context . . . . . . . . . . . . . . 24
2.1.38 Header field: DL-Expansion-History . . . . . . . . . . . . 24
2.1.39 Header field: Alternate-Recipient . . . . . . . . . . . . 25
2.1.40 Header field: Original-Encoded-Information-Types . . . . . 25
2.1.41 Header field: Content-Return . . . . . . . . . . . . . . . 26
Klyne & Palme Expires October 18, 2004 [Page 2]
Internet-Draft Mail and MIME header fields April 2004
2.1.42 Header field: Generate-Delivery-Report . . . . . . . . . . 26
2.1.43 Header field: Prevent-NonDelivery-Report . . . . . . . . . 27
2.1.44 Header field: Obsoletes . . . . . . . . . . . . . . . . . 27
2.1.45 Header field: Supersedes . . . . . . . . . . . . . . . . . 28
2.1.46 Header field: Content-Identifier . . . . . . . . . . . . . 28
2.1.47 Header field: Delivery-Date . . . . . . . . . . . . . . . 29
2.1.48 Header field: Expiry-Date . . . . . . . . . . . . . . . . 29
2.1.49 Header field: Expires . . . . . . . . . . . . . . . . . . 30
2.1.50 Header field: Reply-By . . . . . . . . . . . . . . . . . . 30
2.1.51 Header field: Importance . . . . . . . . . . . . . . . . . 31
2.1.52 Header field: Incomplete-Copy . . . . . . . . . . . . . . 31
2.1.53 Header field: Priority . . . . . . . . . . . . . . . . . . 31
2.1.54 Header field: Sensitivity . . . . . . . . . . . . . . . . 32
2.1.55 Header field: Language . . . . . . . . . . . . . . . . . . 32
2.1.56 Header field: Conversion . . . . . . . . . . . . . . . . . 33
2.1.57 Header field: Conversion-With-Loss . . . . . . . . . . . . 33
2.1.58 Header field: Message-Type . . . . . . . . . . . . . . . . 34
2.1.59 Header field: Autosubmitted . . . . . . . . . . . . . . . 34
2.1.60 Header field: Autoforwarded . . . . . . . . . . . . . . . 35
2.1.61 Header field: Discarded-X400-IPMS-Extensions . . . . . . . 35
2.1.62 Header field: Discarded-X400-MTS-Extensions . . . . . . . 36
2.1.63 Header field: Disclose-Recipients . . . . . . . . . . . . 36
2.1.64 Header field: Deferred-Delivery . . . . . . . . . . . . . 37
2.1.65 Header field: Latest-Delivery-Time . . . . . . . . . . . . 37
2.1.66 Header field: Originator-Return-Address . . . . . . . . . 38
2.1.67 Header field: X400-Content-Identifier . . . . . . . . . . 38
2.1.68 Header field: X400-Content-Return . . . . . . . . . . . . 39
2.1.69 Header field: X400-Content-Type . . . . . . . . . . . . . 39
2.1.70 Header field: X400-MTS-Identifier . . . . . . . . . . . . 39
2.1.71 Header field: X400-Originator . . . . . . . . . . . . . . 40
2.1.72 Header field: X400-Received . . . . . . . . . . . . . . . 40
2.1.73 Header field: X400-Recipients . . . . . . . . . . . . . . 41
2.1.74 Header field: X400-Trace . . . . . . . . . . . . . . . . . 41
2.2 Permanent MIME header field registrations . . . . . . . . 42
2.2.1 Header field: MIME-Version . . . . . . . . . . . . . . . . 42
2.2.2 Header field: Content-ID . . . . . . . . . . . . . . . . . 43
2.2.3 Header field: Content-Description . . . . . . . . . . . . 43
2.2.4 Header field: Content-Transfer-Encoding . . . . . . . . . 43
2.2.5 Header field: Content-Type . . . . . . . . . . . . . . . . 44
2.2.6 Header field: Content-Base . . . . . . . . . . . . . . . . 44
2.2.7 Header field: Content-Location . . . . . . . . . . . . . . 45
2.2.8 Header field: Content-features . . . . . . . . . . . . . . 45
2.2.9 Header field: Content-Disposition . . . . . . . . . . . . 46
2.2.10 Header field: Content-Language . . . . . . . . . . . . . . 46
2.2.11 Header field: Content-Alternative . . . . . . . . . . . . 47
2.2.12 Header field: Content-MD5 . . . . . . . . . . . . . . . . 47
2.2.13 Header field: Content-Duration . . . . . . . . . . . . . . 48
3. IANA considerations . . . . . . . . . . . . . . . . . . . 48
Klyne & Palme Expires October 18, 2004 [Page 3]
Internet-Draft Mail and MIME header fields April 2004
4. Security considerations . . . . . . . . . . . . . . . . . 48
5. Acknowledgements . . . . . . . . . . . . . . . . . . . . . 48
Normative references . . . . . . . . . . . . . . . . . . . 49
Informative references . . . . . . . . . . . . . . . . . . 50
Authors' Addresses . . . . . . . . . . . . . . . . . . . . 51
A. Revision history . . . . . . . . . . . . . . . . . . . . . 51
A.1 draft-klyne-hdrreg-mail-04 . . . . . . . . . . . . . . . . 51
A.2 draft-klyne-hdrreg-mail-03 . . . . . . . . . . . . . . . . 52
A.3 draft-klyne-hdrreg-mail-02 . . . . . . . . . . . . . . . . 52
A.4 draft-klyne-hdrreg-mail-01 . . . . . . . . . . . . . . . . 53
A.5 draft-klyne-hdrreg-mail-00 . . . . . . . . . . . . . . . . 53
B. TODO: . . . . . . . . . . . . . . . . . . . . . . . . . . 54
Intellectual Property and Copyright Statements . . . . . . 55
Klyne & Palme Expires October 18, 2004 [Page 4]
Internet-Draft Mail and MIME header fields April 2004
1. Introduction
This document defines IANA registration for a number of mail message
and MIME header fields, per Registration procedures for message
header fields [1].
The main body of this document is automatically generated from RDF/N3
data. Some experimental HTML registry pages have been prepared from
the same data, and can be found at [28].
1.1 Structure of this document
Section Section 2.1 contains the templates for initial registration
of mail message header fields.
Section Section 2.2 contains templates for initial registration of
MIME header fields.
1.2 Document terminology and conventions
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in RFC 2119 [10].
[[[Editorial comments and questions about outstanding issues are
provided in triple brackets like this. These working comments should
be resolved and removed prior to final publication.]]]
2. Registration templates
Header field registry entries are summarized in tabular form for
convenience of reference, and presented in full in the following
sections.
2.1 Permanent mail header field registrations
Header name Protocol
----------- --------
Date Mail Message date and time
From Mail Mailbox of message author
Sender Mail Mailbox of message sender
Reply-To Mail Mailbox for replies to message
To Mail Primary recipient mailbox
Cc Mail Carbon-copy recipient mailbox
Bcc Mail Blind-carbon-copy recipient
mailbox
Message-ID Mail Message identifier
Klyne & Palme Expires October 18, 2004 [Page 5]
Internet-Draft Mail and MIME header fields April 2004
In-Reply-To Mail Identify replied-to message(s)
References Mail Related message identifier(s)
Subject Mail Topic of message
Comments Mail Additional comments about the
message
Keywords Mail Message key words and/or phrases
Resent-Date Mail Date and time message is resent
Resent-From Mail Mailbox of person for whom message
is resent
Resent-Sender Mail Mailbox of person who actually
resends the message
Resent-To Mail Mailbox to which message is resent
Resent-Cc Mail Mailbox(es) to which message is
cc'ed on resend
Resent-Bcc Mail Mailbox(es) to which message is
bcc'ed on resend
Resent-Reply-To Mail Resent reply-to
Resent-Message-ID Mail Message identifier for resent
message
Return-Path Mail Message return path
Received Mail Mail transfer trace information
Disposition-Notification-To
Mail Mailbox for sending disposition
notification
Disposition-Notification-Options
Mail Disposition notification options
Accept-Language Mail Language(s) for auto-responses
Original-Message-ID Mail Original message identifier
PICS-Label Mail PICS rating label
Encoding Mail Message encoding and other
information
List-Archive Mail URL of mailing list archive
List-Help Mail URL for mailing list information
List-ID Mail Mailing list identifier
List-Owner Mail URL for mailing list owner's
mailbox
List-Post Mail URL for mailing list posting
List-Subscribe Mail URL for mailing list subscription
List-Unsubscribe Mail URL for mailing list
unsubscription
Message-Context Mail Type or context of message
DL-Expansion-History
Mail Trace of distribution lists passed
Alternate-Recipient Mail Controls forwarding to alternate
recipients
Original-Encoded-Information-Types
Mail Body part types in message
Content-Return Mail Return content on non-delivery?
Klyne & Palme Expires October 18, 2004 [Page 6]
Internet-Draft Mail and MIME header fields April 2004
Generate-Delivery-Report
Mail Request delivery report generation
Prevent-NonDelivery-Report
Mail Non-delivery report required?
Obsoletes Mail Reference message to be replaced
Supersedes Mail Reference message to be replaced
Content-Identifier Mail Message content identifier
Delivery-Date Mail Message delivery time
Expiry-Date Mail Message expiry time
Expires Mail Message expiry time
Reply-By Mail Time by which a reply is requested
Importance Mail Message importance
Incomplete-Copy Mail Body parts are missing.
Priority Mail Message priority
Sensitivity Mail Message content sensitivity
Language Mail X.400 message content lenguage
Conversion Mail Conversion allowed?
Conversion-With-Loss
Mail Lossy conversion allowed?
Message-Type Mail Message type: delivery report?
Autosubmitted Mail Automatically submitted indicator
Autoforwarded Mail Automatically forwarded indicator
Discarded-X400-IPMS-Extensions
Mail X.400 IPM extensions discarded
Discarded-X400-MTS-Extensions
Mail X.400 MTS extensions discarded
Disclose-Recipients Mail Disclose names of other
recipients?
Deferred-Delivery Mail Deferred delivery information
Latest-Delivery-Time
Mail Latest delivery time requested
Originator-Return-Address
Mail Originator return address
X400-Content-Identifier
Mail Message content identifier
X400-Content-Return Mail Return content on non-delivery?
X400-Content-Type Mail X400 content type
X400-MTS-Identifier Mail X400 MTS-Identifier
X400-Originator Mail X400 Originator
X400-Received Mail X400 Received
X400-Recipients Mail X400 Recipients
X400-Trace Mail X400 Trace
Figure 1
Klyne & Palme Expires October 18, 2004 [Page 7]
Internet-Draft Mail and MIME header fields April 2004
2.1.1 Header field: Date
Description:
Message date and time
Applicable protocol: Mail [19]
Status: standards-track
Author/change controller:
IETF (mailto:iesg@ietf.org)
Internet Engineering Task Force
Specification document(s):
RFC 2822 [19] (section 3.6.1)
Related information:
Specifies the date and time at which the creator of the message
indicated that the message was complete and ready to enter the
mail delivery system.
2.1.2 Header field: From
Description:
Mailbox of message author
Applicable protocol: Mail [19]
Status: standards-track
Author/change controller:
IETF (mailto:iesg@ietf.org)
Internet Engineering Task Force
Specification document(s):
RFC 2822 [19] (section 3.6.2)
Related information:
Specifies the author(s) of the message, that is, the mailbox(es)
of the person(s) or system(s) responsible for the writing of the
message.
2.1.3 Header field: Sender
Klyne & Palme Expires October 18, 2004 [Page 8]
Internet-Draft Mail and MIME header fields April 2004
Description:
Mailbox of message sender
Applicable protocol: Mail [19]
Status: standards-track
Author/change controller:
IETF (mailto:iesg@ietf.org)
Internet Engineering Task Force
Specification document(s):
RFC 2822 [19] (section 3.6.2)
Related information:
Specifies the mailbox of the agent responsible for the actual
transmission of the message.
2.1.4 Header field: Reply-To
Description:
Mailbox for replies to message
Applicable protocol: Mail [19]
Status: standards-track
Author/change controller:
IETF (mailto:iesg@ietf.org)
Internet Engineering Task Force
Specification document(s):
RFC 2822 [19] (section 3.6.2)
Related information:
When the "Reply-To:" field is present, it indicates the
mailbox(es) to which the author of the message suggests that
replies be sent.
2.1.5 Header field: To
Description:
Primary recipient mailbox
Klyne & Palme Expires October 18, 2004 [Page 9]
Internet-Draft Mail and MIME header fields April 2004
Applicable protocol: Mail [19]
Status: standards-track
Author/change controller:
IETF (mailto:iesg@ietf.org)
Internet Engineering Task Force
Specification document(s):
RFC 2822 [19] (section 3.6.3)
Related information:
Contains the address(es) of the primary recipient(s) of the
message.
2.1.6 Header field: Cc
Description:
Carbon-copy recipient mailbox
Applicable protocol: Mail [19]
Status: standards-track
Author/change controller:
IETF (mailto:iesg@ietf.org)
Internet Engineering Task Force
Specification document(s):
RFC 2822 [19] (section 3.6.3)
Related information:
Contains the addresses of others who are to receive the message,
though the content of the message may not be directed at them.
2.1.7 Header field: Bcc
Description:
Blind-carbon-copy recipient mailbox
Applicable protocol: Mail [19]
Status: standards-track
Klyne & Palme Expires October 18, 2004 [Page 10]
Internet-Draft Mail and MIME header fields April 2004
Author/change controller:
IETF (mailto:iesg@ietf.org)
Internet Engineering Task Force
Specification document(s):
RFC 2822 [19] (section 3.6.3)
Related information:
Contains addresses of recipients of the message whose addresses
are not to be revealed to other recipients of the message.
2.1.8 Header field: Message-ID
Description:
Message identifier
Applicable protocol: Mail [19]
Status: standards-track
Author/change controller:
IETF (mailto:iesg@ietf.org)
Internet Engineering Task Force
Specification document(s):
RFC 2822 [19] (section 3.6.4)
Related information:
Contains a single unique message identifier that refers to a
particular version of a particular message. If the message is
resent without changes, the original Message-ID is retained.
2.1.9 Header field: In-Reply-To
Description:
Identify replied-to message(s)
Applicable protocol: Mail [19]
Status: standards-track
Author/change controller:
IETF (mailto:iesg@ietf.org)
Internet Engineering Task Force
Klyne & Palme Expires October 18, 2004 [Page 11]
Internet-Draft Mail and MIME header fields April 2004
Specification document(s):
RFC 2822 [19] (section 3.6.4)
Related information:
The message identifier(s) of the original message(s) to which the
current message is a reply.
2.1.10 Header field: References
Description:
Related message identifier(s)
Applicable protocol: Mail [19]
Status: standards-track
Author/change controller:
IETF (mailto:iesg@ietf.org)
Internet Engineering Task Force
Specification document(s):
RFC 2822 [19] (section 3.6.4)
Related information:
The message identifier(s) of other message(s) to which the current
message may be related. In RFC2822, the definition was changed to
say that this header field contains a list of all Message-IDs of
messages in the preceding reply chain.
2.1.11 Header field: Subject
Description:
Topic of message
Applicable protocol: Mail [19]
Status: standards-track
Author/change controller:
IETF (mailto:iesg@ietf.org)
Internet Engineering Task Force
Specification document(s):
RFC 2822 [19] (section 3.6.5)
Klyne & Palme Expires October 18, 2004 [Page 12]
Internet-Draft Mail and MIME header fields April 2004
Related information:
Contains a short string identifying the topic of the message.
2.1.12 Header field: Comments
Description:
Additional comments about the message
Applicable protocol: Mail [19]
Status: standards-track
Author/change controller:
IETF (mailto:iesg@ietf.org)
Internet Engineering Task Force
Specification document(s):
RFC 2822 [19] (section 3.6.5)
Related information:
Contains any additional comments on the text of the body of the
message. Warning: Some mailers will not show this field to
recipients.
2.1.13 Header field: Keywords
Description:
Message key words and/or phrases
Applicable protocol: Mail [19]
Status: standards-track
Author/change controller:
IETF (mailto:iesg@ietf.org)
Internet Engineering Task Force
Specification document(s):
RFC 2822 [19] (section 3.6.5)
Related information:
Contains a comma-separated list of important words and phrases
that might be useful for the recipient.
Klyne & Palme Expires October 18, 2004 [Page 13]
Internet-Draft Mail and MIME header fields April 2004
2.1.14 Header field: Resent-Date
Description:
Date and time message is resent
Applicable protocol: Mail [19]
Status: standards-track
Author/change controller:
IETF (mailto:iesg@ietf.org)
Internet Engineering Task Force
Specification document(s):
RFC 2822 [19] (section 3.6.6)
Related information:
Contains the date and time that a message is reintroduced into the
message transfer system.
2.1.15 Header field: Resent-From
Description:
Mailbox of person for whom message is resent
Applicable protocol: Mail [19]
Status: standards-track
Author/change controller:
IETF (mailto:iesg@ietf.org)
Internet Engineering Task Force
Specification document(s):
RFC 2822 [19] (section 3.6.6)
Related information:
Contains the mailbox of the agent who has reintroduced the message
into the message transfer system, or on whose behanlf the message
has been resent.
2.1.16 Header field: Resent-Sender
Description:
Mailbox of person who actually resends the message
Klyne & Palme Expires October 18, 2004 [Page 14]
Internet-Draft Mail and MIME header fields April 2004
Applicable protocol: Mail [19]
Status: standards-track
Author/change controller:
IETF (mailto:iesg@ietf.org)
Internet Engineering Task Force
Specification document(s):
RFC 2822 [19] (section 3.6.6)
Related information:
Contains the mailbox of the agent who has reintroduced the message
into the message transfer system, if this is different from the
Resent-from value.
2.1.17 Header field: Resent-To
Description:
Mailbox to which message is resent
Applicable protocol: Mail [19]
Status: standards-track
Author/change controller:
IETF (mailto:iesg@ietf.org)
Internet Engineering Task Force
Specification document(s):
RFC 2822 [19] (section 3.6.6)
Related information:
Contains the mailbox(es) to which the message has been resent.
2.1.18 Header field: Resent-Cc
Description:
Mailbox(es) to which message is cc'ed on resend
Applicable protocol: Mail [19]
Status: standards-track
Klyne & Palme Expires October 18, 2004 [Page 15]
Internet-Draft Mail and MIME header fields April 2004
Author/change controller:
IETF (mailto:iesg@ietf.org)
Internet Engineering Task Force
Specification document(s):
RFC 2822 [19] (section 3.6.6)
Related information:
Containes the mailbox(es) to which message is cc'ed on resend
2.1.19 Header field: Resent-Bcc
Description:
Mailbox(es) to which message is bcc'ed on resend
Applicable protocol: Mail [19]
Status: standards-track
Author/change controller:
IETF (mailto:iesg@ietf.org)
Internet Engineering Task Force
Specification document(s):
RFC 2822 [19] (section 3.6.6)
Related information:
Containes the mailbox(es) to which message is bcc'ed on resend
2.1.20 Header field: Resent-Reply-To
Description:
Resent reply-to
Applicable protocol: Mail [19]
Status: obsolete
Author/change controller:
IETF (mailto:iesg@ietf.org)
Internet Engineering Task Force
Specification document(s):
RFC 2822 [19]
Klyne & Palme Expires October 18, 2004 [Page 16]
Internet-Draft Mail and MIME header fields April 2004
Related information:
Resent Reply-to. Defined by RFC 822, obsoleteed by RFC2822.
2.1.21 Header field: Resent-Message-ID
Description:
Message identifier for resent message
Applicable protocol: Mail [19]
Status: standards-track
Author/change controller:
IETF (mailto:iesg@ietf.org)
Internet Engineering Task Force
Specification document(s):
RFC 2822 [19] (section 3.6.6)
Related information:
Contains a message identifier for a resent message
2.1.22 Header field: Return-Path
Description:
Message return path
Applicable protocol: Mail [19]
Status: standards-track
Author/change controller:
IETF (mailto:iesg@ietf.org)
Internet Engineering Task Force
Specification document(s):
RFC 2822 [19] (section 3.6.7)
Related information:
Return path for message response diagnostics. See also, RFC 2821.
2.1.23 Header field: Received
Klyne & Palme Expires October 18, 2004 [Page 17]
Internet-Draft Mail and MIME header fields April 2004
Description:
Mail transfer trace information
Applicable protocol: Mail [19]
Status: standards-track
Author/change controller:
IETF (mailto:iesg@ietf.org)
Internet Engineering Task Force
Specification document(s):
RFC 2822 [19] (section 3.6.7)
Related information:
Contains information about receipt of the current message by a
mail transfer agent on the transfer path. See also, RFC 2821.
2.1.24 Header field: Disposition-Notification-To
Description:
Mailbox for sending disposition notification
Applicable protocol: Mail [19]
Status: standards-track
Author/change controller:
IETF (mailto:iesg@ietf.org)
Internet Engineering Task Force
Specification document(s):
RFC 2298 [13]
Related information:
Indicates that the sender wants a disposition notification when
this message is received (read, processed, etc.) by its
recipients.
2.1.25 Header field: Disposition-Notification-Options
Description:
Disposition notification options
Klyne & Palme Expires October 18, 2004 [Page 18]
Internet-Draft Mail and MIME header fields April 2004
Applicable protocol: Mail [19]
Status: standards-track
Author/change controller:
IETF (mailto:iesg@ietf.org)
Internet Engineering Task Force
Specification document(s):
RFC 2298 [13]
Related information:
For optional modifiers on disposition notification requests.
2.1.26 Header field: Accept-Language
Description:
Language(s) for auto-responses
Applicable protocol: Mail [19]
Status: standards-track
Author/change controller:
IETF (mailto:iesg@ietf.org)
Internet Engineering Task Force
Specification document(s):
RFC 3282 [22]
Related information:
Indicates a language that the message sender requests be used for
responses. Accept-language was not designed for email, but has
been considered to be useful as input to the generation of
automatic replies. Some problems have been noted concerning its
use with email, including but not limited to: determination of the
email address to which it refers; cost and lack of effective
internationalization of email responses; interpretation of
language subtags; determining what character set encoding should
be used.
2.1.27 Header field: Original-Message-ID
Description:
Original message identifier
Klyne & Palme Expires October 18, 2004 [Page 19]
Internet-Draft Mail and MIME header fields April 2004
Applicable protocol: Mail [19]
Status: standards-track
Author/change controller:
IETF (mailto:iesg@ietf.org)
Internet Engineering Task Force
Specification document(s):
RFC 3297 [23]
Related information:
Original message identifier used with resend of message with
alternative content format, identifies the original message data
to which it corresponds.
2.1.28 Header field: PICS-Label
Description:
PICS rating label
Applicable protocol: Mail [19]
Status: standard
Author/change controller:
W3C (mailto:web-human@w3.org)
World Wide Web Consortium
Specification document(s):
http://www.w3.org/TR/REC-PICS-labels [25]
Related information:
Ratings label to control selection (filtering) of messages
according to the PICS protocol. Specified for general use with
RFC822 message format, with HTTP-specific extensions
2.1.29 Header field: Encoding
Description:
Message encoding and other information
Applicable protocol: Mail [19]
Klyne & Palme Expires October 18, 2004 [Page 20]
Internet-Draft Mail and MIME header fields April 2004
Status: experimental
Author/change controller:
Albert K. Costanzo (mailto:AL@AKC.COM)
AKC Consulting Inc.
Specification document(s):
RFC 1505 [4]
Related information:
Used in several different ways by different mail systems. Some use
it for a kind of content-type information, some for encoding and
length information, some for a kind of boundary information, some
in other ways.
2.1.30 Header field: List-Archive
Description:
URL of mailing list archive
Applicable protocol: Mail [19]
Status: standards-track
Author/change controller:
IETF (mailto:iesg@ietf.org)
Internet Engineering Task Force
Specification document(s):
RFC 2369 [14]
Related information:
Contains URL to use to browse the archives of the mailing list
from which this message was relayed.
2.1.31 Header field: List-Help
Description:
URL for mailing list information
Applicable protocol: Mail [19]
Status: standards-track
Klyne & Palme Expires October 18, 2004 [Page 21]
Internet-Draft Mail and MIME header fields April 2004
Author/change controller:
IETF (mailto:iesg@ietf.org)
Internet Engineering Task Force
Specification document(s):
RFC 2369 [14]
Related information:
Contains URL to use to get a information about the mailing list
from which this message was relayed.
2.1.32 Header field: List-ID
Description:
Mailing list identifier
Applicable protocol: Mail [19]
Status: standards-track
Author/change controller:
IETF (mailto:iesg@ietf.org)
Internet Engineering Task Force
Specification document(s):
RFC 2919 [21]
Related information:
Stores an identification of the mailing list, through which this
message was distributed.
2.1.33 Header field: List-Owner
Description:
URL for mailing list owner's mailbox
Applicable protocol: Mail [19]
Status: standards-track
Author/change controller:
IETF (mailto:iesg@ietf.org)
Internet Engineering Task Force
Klyne & Palme Expires October 18, 2004 [Page 22]
Internet-Draft Mail and MIME header fields April 2004
Specification document(s):
RFC 2369 [14]
Related information:
Contains URL to send e-mail to the owner of the mailing list from
which this message was relayed.
2.1.34 Header field: List-Post
Description:
URL for mailing list posting
Applicable protocol: Mail [19]
Status: standards-track
Author/change controller:
IETF (mailto:iesg@ietf.org)
Internet Engineering Task Force
Specification document(s):
RFC 2369 [14]
Related information:
Contains URL to use to send contributions to the mailing list from
which this message was relayed.
2.1.35 Header field: List-Subscribe
Description:
URL for mailing list subscription
Applicable protocol: Mail [19]
Status: standards-track
Author/change controller:
IETF (mailto:iesg@ietf.org)
Internet Engineering Task Force
Specification document(s):
RFC 2369 [14]
Related information:
Contains URL to use to get a subscription to the mailing list from
which this message was relayed.
Klyne & Palme Expires October 18, 2004 [Page 23]
Internet-Draft Mail and MIME header fields April 2004
2.1.36 Header field: List-Unsubscribe
Description:
URL for mailing list unsubscription
Applicable protocol: Mail [19]
Status: standards-track
Author/change controller:
IETF (mailto:iesg@ietf.org)
Internet Engineering Task Force
Specification document(s):
RFC 2369 [14]
Related information:
Contains URL to use to unsubscribe the mailing list from which
this message was relayed.
2.1.37 Header field: Message-Context
Description:
Type or context of message
Applicable protocol: Mail [19]
Status: Standards track
Author/change controller:
IETF (mailto:iesg@ietf.org)
Internet Engineering Task Force
Specification document(s):
RFC3458 [24]
Related information:
Provides information about the context and presentation
characteristics of a message. Can have the values
'voice-message', 'fax-message', 'pager-message',
'multimedia-message', 'text-message', 'none'.
2.1.38 Header field: DL-Expansion-History
Klyne & Palme Expires October 18, 2004 [Page 24]
Internet-Draft Mail and MIME header fields April 2004
Description:
Trace of distribution lists passed
Applicable protocol: Mail [19]
Status: standards-track
Author/change controller:
IETF (mailto:iesg@ietf.org)
Internet Engineering Task Force
Specification document(s):
RFC 2156 [11]
Related information:
Trace of distribution lists passed. (MIXER X.400 mapping, not for
general use.)
2.1.39 Header field: Alternate-Recipient
Description:
Controls forwarding to alternate recipients
Applicable protocol: Mail [19]
Status: standards-track
Author/change controller:
IETF (mailto:iesg@ietf.org)
Internet Engineering Task Force
Specification document(s):
RFC 2156 [11]
Related information:
Controls whether this message may be forwarded to alternate
recipients such as a postmaster if delivery is not possible to the
intended recipient. Default: Allowed. RFC 2156 (MIXER), not for
general use.
2.1.40 Header field: Original-Encoded-Information-Types
Description:
Body part types in message
Klyne & Palme Expires October 18, 2004 [Page 25]
Internet-Draft Mail and MIME header fields April 2004
Applicable protocol: Mail [19]
Status: standards-track
Author/change controller:
IETF (mailto:iesg@ietf.org)
Internet Engineering Task Force
Specification document(s):
RFC 2156 [11]
Related information:
Which body part types occur in this message. RFC 2156 (MIXER), not
for general use.
2.1.41 Header field: Content-Return
Description:
Return content on non-delivery?
Applicable protocol: Mail [19]
Status: obsolete
Author/change controller:
IETF (mailto:iesg@ietf.org)
Internet Engineering Task Force
Specification document(s):
RFC 1327 [2]
Related information:
Indicates whether the content of a message is to be returned with
non-delivery notifications. Introduced by RFC 1327, and
subsequently changed by RFC 2156 to avoid confusion with MIME
defined fields.
2.1.42 Header field: Generate-Delivery-Report
Description:
Request delivery report generation
Applicable protocol: Mail [19]
Klyne & Palme Expires October 18, 2004 [Page 26]
Internet-Draft Mail and MIME header fields April 2004
Status: standards-track
Author/change controller:
IETF (mailto:iesg@ietf.org)
Internet Engineering Task Force
Specification document(s):
RFC 2156 [11]
Related information:
Indicates whether a delivery report is wanted at successful
delivery. Default is not to generate such a report. RFC 2156
(MIXER), not for general use.
2.1.43 Header field: Prevent-NonDelivery-Report
Description:
Non-delivery report required?
Applicable protocol: Mail [19]
Status: standards-track
Author/change controller:
IETF (mailto:iesg@ietf.org)
Internet Engineering Task Force
Specification document(s):
RFC 2156 [11]
Related information:
Indicates whether non-delivery report is wanted on delivery error.
Default is to generate such a report. RFC 2156 (MIXER), not for
general use.
2.1.44 Header field: Obsoletes
Description:
Reference message to be replaced
Applicable protocol: Mail [19]
Status: obsolete
Klyne & Palme Expires October 18, 2004 [Page 27]
Internet-Draft Mail and MIME header fields April 2004
Author/change controller:
IETF (mailto:iesg@ietf.org)
Internet Engineering Task Force
Specification document(s):
RFC 1327 [2]
Related information:
Reference to a previous message being corrected and replaced.
Compare to 'Supersedes:' used in Usenet News. Introduced by RFC
1327, and subsequently renamed by RFC 2156 to 'Supersedes'.
2.1.45 Header field: Supersedes
Description:
Reference message to be replaced
Applicable protocol: Mail [19]
Status: standards-track
Author/change controller:
IETF (mailto:iesg@ietf.org)
Internet Engineering Task Force
Specification document(s):
RFC 2156 [11]
Related information:
Reference to a previous message being corrected and replaced.
Renamed version of obsolete 'Obsoletes' header field. RFC 2156
(MIXER), not for general use.
2.1.46 Header field: Content-Identifier
Description:
Message content identifier
Applicable protocol: Mail [19]
Status: obsolete
Author/change controller:
IETF (mailto:iesg@ietf.org)
Internet Engineering Task Force
Klyne & Palme Expires October 18, 2004 [Page 28]
Internet-Draft Mail and MIME header fields April 2004
Specification document(s):
RFC 1327 [2]
Related information:
A text string which identifies the content of a message.
Introduced by RFC 1327, and subsequently changed by RFC 2156 to
avoid confusion with MIME defined fields. Gateways which reverse
map may support the old field.
2.1.47 Header field: Delivery-Date
Description:
Message delivery time
Applicable protocol: Mail [19]
Status: standards-track
Author/change controller:
IETF (mailto:iesg@ietf.org)
Internet Engineering Task Force
Specification document(s):
RFC 2156 [11]
Related information:
The time when a message was delivered to its recipient. RFC 2156
(MIXER), not for general use.
2.1.48 Header field: Expiry-Date
Description:
Message expiry time
Applicable protocol: Mail [19]
Status: obsolete
Author/change controller:
IETF (mailto:iesg@ietf.org)
Internet Engineering Task Force
Specification document(s):
RFC 1327 [2]
Klyne & Palme Expires October 18, 2004 [Page 29]
Internet-Draft Mail and MIME header fields April 2004
Related information:
Time at which a message loses its validity. Introduced by RFC
1327, and subsequently changed by RFC 2156 to 'Expires:'.
2.1.49 Header field: Expires
Description:
Message expiry time
Applicable protocol: Mail [19]
Status: standards-track
Author/change controller:
IETF (mailto:iesg@ietf.org)
Internet Engineering Task Force
Specification document(s):
RFC 2156 [11]
Related information:
Time at which a message loses its validity. Renamed version of
obsolete Expiry-Date header field. RFC 2156 (MIXER), not for
general use.
2.1.50 Header field: Reply-By
Description:
Time by which a reply is requested
Applicable protocol: Mail [19]
Status: standards-track
Author/change controller:
IETF (mailto:iesg@ietf.org)
Internet Engineering Task Force
Specification document(s):
RFC 2156 [11]
Related information:
Latest time at which a reply is requested (not demanded). RFC 2156
(MIXER), not for general use.
Klyne & Palme Expires October 18, 2004 [Page 30]
Internet-Draft Mail and MIME header fields April 2004
2.1.51 Header field: Importance
Description:
Message importance
Applicable protocol: Mail [19]
Status: standards-track
Author/change controller:
IETF (mailto:iesg@ietf.org)
Internet Engineering Task Force
Specification document(s):
RFC 2156 [11]
Related information:
A hint from the originator to the recipients about how important a
message is. Values: High, normal or low. Not used to control
transmission speed. Proposed for use with RFC 2156 (MIXER) and RFC
2421 (VPIM).
2.1.52 Header field: Incomplete-Copy
Description:
Body parts are missing.
Applicable protocol: Mail [19]
Status: standards-track
Author/change controller:
IETF (mailto:iesg@ietf.org)
Internet Engineering Task Force
Specification document(s):
RFC 2156 [11]
Related information:
Body parts are missing. RFC 2156 (MIXER), not for general use.
2.1.53 Header field: Priority
Description:
Message priority
Klyne & Palme Expires October 18, 2004 [Page 31]
Internet-Draft Mail and MIME header fields April 2004
Applicable protocol: Mail [19]
Status: standards-track
Author/change controller:
IETF (mailto:iesg@ietf.org)
Internet Engineering Task Force
Specification document(s):
RFC 2156 [11]
Related information:
Can be 'normal', 'urgent' or 'non-urgent' and can influence
transmission speed and delivery. RFC 2156 (MIXER), not for general
use.
2.1.54 Header field: Sensitivity
Description:
Message content sensitivity
Applicable protocol: Mail [19]
Status: standards-track
Author/change controller:
IETF (mailto:iesg@ietf.org)
Internet Engineering Task Force
Specification document(s):
RFC 2156 [11]
Related information:
How sensitive it is to disclose this message to other people than
the specified recipients. Values: Personal, private, company
confidential. The absence of this header field in messages
gatewayed from X.400 indicates that the message is not sensitive.
Proposed for use with RFC 2156 (MIXER) and RFC 2421 (VPIM).
2.1.55 Header field: Language
Description:
X.400 message content lenguage
Klyne & Palme Expires October 18, 2004 [Page 32]
Internet-Draft Mail and MIME header fields April 2004
Applicable protocol: Mail [19]
Status: standards-track
Author/change controller:
IETF (mailto:iesg@ietf.org)
Internet Engineering Task Force
Specification document(s):
RFC 2156 [11]
Related information:
Can include a code for the natural language used in a message,
e.g. 'en' for English. See also 'Content-Language'. RFC 2156
(MIXER), not for general use.
2.1.56 Header field: Conversion
Description:
Conversion allowed?
Applicable protocol: Mail [19]
Status: standards-track
Author/change controller:
IETF (mailto:iesg@ietf.org)
Internet Engineering Task Force
Specification document(s):
RFC 2156 [11]
Related information:
The body of this message may not be converted from one character
set to another. Values: Prohibited and allowed. RFC 2156 (MIXER),
not for general use.
2.1.57 Header field: Conversion-With-Loss
Description:
Lossy conversion allowed?
Applicable protocol: Mail [19]
Klyne & Palme Expires October 18, 2004 [Page 33]
Internet-Draft Mail and MIME header fields April 2004
Status: standards-track
Author/change controller:
IETF (mailto:iesg@ietf.org)
Internet Engineering Task Force
Specification document(s):
RFC 2156 [11]
Related information:
The body of this message may not be converted from one character
set to another if information will be lost. Values: Prohibited and
allowed. RFC 2156 (MIXER), not for general use.
2.1.58 Header field: Message-Type
Description:
Message type: delivery report?
Applicable protocol: Mail [19]
Status: standards-track
Author/change controller:
IETF (mailto:iesg@ietf.org)
Internet Engineering Task Force
Specification document(s):
RFC 2156 [11]
Related information:
Only used with the value 'Delivery Report' to indicates that this
is a delivery report gatewayed from X.400. RFC 2156 (MIXER), not
for general use.
2.1.59 Header field: Autosubmitted
Description:
Automatically submitted indicator
Applicable protocol: Mail [19]
Status: standards-track
Klyne & Palme Expires October 18, 2004 [Page 34]
Internet-Draft Mail and MIME header fields April 2004
Author/change controller:
IETF (mailto:iesg@ietf.org)
Internet Engineering Task Force
Specification document(s):
RFC 2156 [11]
Related information:
Has been automatically submitted. RFC 2156 (MIXER), not for
general use.
2.1.60 Header field: Autoforwarded
Description:
Automatically forwarded indicator
Applicable protocol: Mail [19]
Status: standards-track
Author/change controller:
IETF (mailto:iesg@ietf.org)
Internet Engineering Task Force
Specification document(s):
RFC 2156 [11]
Related information:
Has been automatically forwarded. RFC 2156 (MIXER), not for
general use.
2.1.61 Header field: Discarded-X400-IPMS-Extensions
Description:
X.400 IPM extensions discarded
Applicable protocol: Mail [19]
Status: standards-track
Author/change controller:
IETF (mailto:iesg@ietf.org)
Internet Engineering Task Force
Klyne & Palme Expires October 18, 2004 [Page 35]
Internet-Draft Mail and MIME header fields April 2004
Specification document(s):
RFC 2156 [11]
Related information:
Can be used in Internet mail to indicate X.400 IPM extensions
which could not be mapped to Internet mail format. RFC 2156
(MIXER), not for general use.
2.1.62 Header field: Discarded-X400-MTS-Extensions
Description:
X.400 MTS extensions discarded
Applicable protocol: Mail [19]
Status: standards-track
Author/change controller:
IETF (mailto:iesg@ietf.org)
Internet Engineering Task Force
Specification document(s):
RFC 2156 [11]
Related information:
Can be used in Internet mail to indicate X.400 MTS extensions
which could not be mapped to Internet mail format. RFC 2156
(MIXER), not for general use.
2.1.63 Header field: Disclose-Recipients
Description:
Disclose names of other recipients?
Applicable protocol: Mail [19]
Status: standards-track
Author/change controller:
IETF (mailto:iesg@ietf.org)
Internet Engineering Task Force
Specification document(s):
RFC 2156 [11]
Klyne & Palme Expires October 18, 2004 [Page 36]
Internet-Draft Mail and MIME header fields April 2004
Related information:
Tells whether recipients are to be told the names of other
recipients of the same message. This is primarily an X.400
facility. In X.400, this is an envelope attribute and refers to
disclosure of the envelope recipient list. Disclosure of other
recipients is in Internet mail done via the To:, cc: and bcc:
header fields. Not for general use.
2.1.64 Header field: Deferred-Delivery
Description:
Deferred delivery information
Applicable protocol: Mail [19]
Status: standards-track
Author/change controller:
IETF (mailto:iesg@ietf.org)
Internet Engineering Task Force
Specification document(s):
RFC 2156 [11]
Related information:
Provides information about deferred delivery service to the
recipient. RFC 2156 (MIXER), not for general use.
2.1.65 Header field: Latest-Delivery-Time
Description:
Latest delivery time requested
Applicable protocol: Mail [19]
Status: standards-track
Author/change controller:
IETF (mailto:iesg@ietf.org)
Internet Engineering Task Force
Specification document(s):
RFC 2156 [11]
Klyne & Palme Expires October 18, 2004 [Page 37]
Internet-Draft Mail and MIME header fields April 2004
Related information:
Provides the recipient information about requested delivery, but
will not be acted on by the SMTP infrastrucuture. RFC 2156
(MIXER), not for general use.
2.1.66 Header field: Originator-Return-Address
Description:
Originator return address
Applicable protocol: Mail [19]
Status: standards-track
Author/change controller:
IETF (mailto:iesg@ietf.org)
Internet Engineering Task Force
Specification document(s):
RFC 2156 [11]
Related information:
Originator return address. RFC 2156 (MIXER), not for general use.
2.1.67 Header field: X400-Content-Identifier
Description:
Message content identifier
Applicable protocol: Mail [19]
Status: standards-track
Author/change controller:
IETF (mailto:iesg@ietf.org)
Internet Engineering Task Force
Specification document(s):
RFC 2156 [11]
Related information:
A text string which identifies the content of a message. Renamed
version of obsolete Content-Identifier field. RFC 2156 (MIXER),
not for general use.
Klyne & Palme Expires October 18, 2004 [Page 38]
Internet-Draft Mail and MIME header fields April 2004
2.1.68 Header field: X400-Content-Return
Description:
Return content on non-delivery?
Applicable protocol: Mail [19]
Status: standards-track
Author/change controller:
IETF (mailto:iesg@ietf.org)
Internet Engineering Task Force
Specification document(s):
RFC 2156 [11]
Related information:
Indicates whether the content of a message is to be returned with
non-delivery notifications. Renamed version of obsolete
Content-Return field. RFC 2156 (MIXER), not for general use.
2.1.69 Header field: X400-Content-Type
Description:
X400 content type
Applicable protocol: Mail [19]
Status: standards-track
Author/change controller:
IETF (mailto:iesg@ietf.org)
Internet Engineering Task Force
Specification document(s):
RFC 2156 [11]
Related information:
X400 content type. RFC 2156 (MIXER), not for general use.
2.1.70 Header field: X400-MTS-Identifier
Description:
X400 MTS-Identifier
Klyne & Palme Expires October 18, 2004 [Page 39]
Internet-Draft Mail and MIME header fields April 2004
Applicable protocol: Mail [19]
Status: standards-track
Author/change controller:
IETF (mailto:iesg@ietf.org)
Internet Engineering Task Force
Specification document(s):
RFC 2156 [11]
Related information:
X400 MTS-Identifier. RFC 2156 (MIXER), not for general use.
2.1.71 Header field: X400-Originator
Description:
X400 Originator
Applicable protocol: Mail [19]
Status: standards-track
Author/change controller:
IETF (mailto:iesg@ietf.org)
Internet Engineering Task Force
Specification document(s):
RFC 2156 [11]
Related information:
X400 Originator. RFC 2156 (MIXER), not for general use.
2.1.72 Header field: X400-Received
Description:
X400 Received
Applicable protocol: Mail [19]
Status: standards-track
Author/change controller:
IETF (mailto:iesg@ietf.org)
Internet Engineering Task Force
Klyne & Palme Expires October 18, 2004 [Page 40]
Internet-Draft Mail and MIME header fields April 2004
Specification document(s):
RFC 2156 [11]
Related information:
X400 Received. RFC 2156 (MIXER), not for general use.
2.1.73 Header field: X400-Recipients
Description:
X400 Recipients
Applicable protocol: Mail [19]
Status: standards-track
Author/change controller:
IETF (mailto:iesg@ietf.org)
Internet Engineering Task Force
Specification document(s):
RFC 2156 [11]
Related information:
X400 Recipients. RFC 2156 (MIXER), not for general use.
2.1.74 Header field: X400-Trace
Description:
X400 Trace
Applicable protocol: Mail [19]
Status: standards-track
Author/change controller:
IETF (mailto:iesg@ietf.org)
Internet Engineering Task Force
Specification document(s):
RFC 2156 [11]
Related information:
X400 Trace. RFC 2156 (MIXER), not for general use.
Klyne & Palme Expires October 18, 2004 [Page 41]
Internet-Draft Mail and MIME header fields April 2004
2.2 Permanent MIME header field registrations
Header name Protocol
----------- --------
MIME-Version MIME MIME version number
Content-ID MIME Identify content body part
Content-Description MIME Description of message body part
Content-Transfer-Encoding
MIME Content transfer encoding applied
Content-Type MIME MIME content type
Content-Base MIME Base to be used for resolving
relative URIs within this content
part.
Content-Location MIME URI for retrieving a body part
Content-features MIME Indicates content features of a
MIME body part
Content-Disposition MIME Intended content disposition and
file name
Content-Language MIME Language of message content
Content-Alternative MIME Alternative content available
Content-MD5 MIME MD5 checksum of content
Content-Duration MIME Time duration of content
Figure 2
2.2.1 Header field: MIME-Version
Description:
MIME version number
Applicable protocol: MIME [7]
Status: standards-track
Author/change controller:
IETF (mailto:iesg@ietf.org)
Internet Engineering Task Force
Specification document(s):
RFC 2045 [7] (section 4)
Related information:
An indicator that this message is formatted according to the MIME
standard, and an indication of which version of MIME is utilized.
Klyne & Palme Expires October 18, 2004 [Page 42]
Internet-Draft Mail and MIME header fields April 2004
2.2.2 Header field: Content-ID
Description:
Identify content body part
Applicable protocol: MIME [7]
Status: standards-track
Author/change controller:
IETF (mailto:iesg@ietf.org)
Internet Engineering Task Force
Specification document(s):
RFC 2045 [7] (section 7)
Related information:
Specifies a Unique ID for one MIME body part of the content of a
message.
2.2.3 Header field: Content-Description
Description:
Description of message body part
Applicable protocol: MIME [7]
Status: standards-track
Author/change controller:
IETF (mailto:iesg@ietf.org)
Internet Engineering Task Force
Specification document(s):
RFC 2045 [7] (section 8)
Related information:
Description of a particular body part of a message, for example a
caption for an image body part.
2.2.4 Header field: Content-Transfer-Encoding
Description:
Content transfer encoding applied
Klyne & Palme Expires October 18, 2004 [Page 43]
Internet-Draft Mail and MIME header fields April 2004
Applicable protocol: MIME [7]
Status: standards-track
Author/change controller:
IETF (mailto:iesg@ietf.org)
Internet Engineering Task Force
Specification document(s):
RFC 2045 [7] (section 6)
Related information:
Coding method used in a MIME message body part.
2.2.5 Header field: Content-Type
Description:
MIME content type
Applicable protocol: MIME [7]
Status: standards-track
Author/change controller:
IETF (mailto:iesg@ietf.org)
Internet Engineering Task Force
Specification document(s):
RFC 2045 [7] (section 5)
Related information:
Format of content (character set etc.) Note that the values for
this header field are defined in different ways in RFC 1049 and in
MIME (RFC 2045), look for the 'MIME-version' header field to
understand if Content-Type is to be interpreted according to RFC
1049 or according to MIME. The MIME definition should be used in
generating mail. RFC 1049 has 'historic' status. RFC 1766 defines
a parameter 'difference' to this header field. Various other
Content-Type define various additional parameters. For example,
the parameter 'charset' is mandatory for all textual
Content-Types. See also: RFC 1049, RFC 1123: 5.2.13, RFC 1766:
4.1.
2.2.6 Header field: Content-Base
Klyne & Palme Expires October 18, 2004 [Page 44]
Internet-Draft Mail and MIME header fields April 2004
Description:
Base to be used for resolving relative URIs within this content
part.
Applicable protocol: MIME [7]
Status: standards-track
Author/change controller:
IETF (mailto:iesg@ietf.org)
Internet Engineering Task Force
Specification document(s):
RFC 2110 [9]
Related information:
Base to be used for resolving relative URIs within this content
part. See also Content-Location. This header was included in the
first version of MHTML and HTTP 1.1 but removed in the second
version (RFC2557).
2.2.7 Header field: Content-Location
Description:
URI for retrieving a body part
Applicable protocol: MIME [7]
Status: standards-track
Author/change controller:
IETF (mailto:iesg@ietf.org)
Internet Engineering Task Force
Specification document(s):
RFC 2557 [17]
Related information:
URI using which the content of this body-part part was retrieved,
might be retrievable, or which otherwise gives a globally unique
identification of the content.
2.2.8 Header field: Content-features
Klyne & Palme Expires October 18, 2004 [Page 45]
Internet-Draft Mail and MIME header fields April 2004
Description:
Indicates content features of a MIME body part
Applicable protocol: MIME [7]
Status: standards-track
Author/change controller:
IETF (mailto:iesg@ietf.org)
Internet Engineering Task Force
Specification document(s):
RFC 2912 [20] (section 3)
Related information:
The 'Content-features:' header can be used to annotate a MIME body
part with a media feature expression, to indicate features of the
body part content. See also: RFC 2533, RFC 2506, RFC 2045.
2.2.9 Header field: Content-Disposition
Description:
Intended content disposition and file name
Applicable protocol: MIME [7]
Status: experimental
Author/change controller:
IETF (mailto:iesg@ietf.org)
Internet Engineering Task Force
Specification document(s):
RFC 2183 [12]
Related information:
Whether a MIME body part is to be shown inline or is an
attachment; can also indicate a suggested filename for use when
saving an attachment to a file.
2.2.10 Header field: Content-Language
Description:
Language of message content
Klyne & Palme Expires October 18, 2004 [Page 46]
Internet-Draft Mail and MIME header fields April 2004
Applicable protocol: MIME [7]
Status: standards-track
Author/change controller:
IETF (mailto:iesg@ietf.org)
Internet Engineering Task Force
Specification document(s):
RFC 3282 [22]
Related information:
Can include a code for the natural language used in a message,
e.g. 'en' for English. Can also contain a list of languages for a
message containing more than one language.
2.2.11 Header field: Content-Alternative
Description:
Alternative content available
Applicable protocol: MIME [7]
Status: work-in-progress
Author/change controller:
IETF (mailto:iesg@ietf.org)
Internet Engineering Task Force
Specification document(s):
RFC 3297 [23]
Related information:
Information about the media features of alternative content
formats available for the current message.
2.2.12 Header field: Content-MD5
Description:
MD5 checksum of content
Applicable protocol: MIME [7]
Status: standards-track
Klyne & Palme Expires October 18, 2004 [Page 47]
Internet-Draft Mail and MIME header fields April 2004
Author/change controller:
IETF (mailto:iesg@ietf.org)
Internet Engineering Task Force
Specification document(s):
RFC 1864 [6]
Related information:
Checksum of content to ensure that it has not been modified.
2.2.13 Header field: Content-Duration
Description:
Time duration of content
Applicable protocol: MIME [7]
Status: standards-track
Author/change controller:
IETF (mailto:iesg@ietf.org)
Internet Engineering Task Force
Specification document(s):
RFC 2424 [16]
Related information:
Time duration of body part content, in seconds (e.g. for audio
message).
3. IANA considerations
This specification provides initial registrations of mail and MIME
header fields in the "Permanent Message Header Field Registry",
defined by Registration procedures for message header fields [1].
4. Security considerations
No security considerations are introduced by this registration
document beyond those already inherent in use of the mail message
header fields referenced.
5. Acknowledgements
Most of the information in this document has been derived from Jacob
Palme's work in RFC 2076 [26] and subsequent updates [27].
Klyne & Palme Expires October 18, 2004 [Page 48]
Internet-Draft Mail and MIME header fields April 2004
The authors also gratefully acknowledge contributions and
constructive input from: Mark Nottingham, Bruce Lilly, Keith Moore
and Charles Lindsey (the mention of whom is not intended to imply
their unqualified support for material herein).
Normative references
[1] Klyne, G., Nottingham, M. and J. Mogul, "Registration
procedures for message headers", Oct 2003, <http://
www.ietf.org/internet-drafts/
draft-klyne-msghdr-registry-07.txt>.
[2] Hardcastle-Kille, S., "Mapping between X.400(1988) / ISO 10021
and RFC 822", RFC 1327, May 1992.
[3] Alvestrand, H., Jordan, K. and J. Romaguera, "Rules for
downgrading messages from X.400/88 to X.400/84 when MIME
content-types are present in the messages", RFC 1496, August
1993.
[4] Costanzo, A., Robinson, D. and R. Ullmann, "Encoding Header
Field for Internet Messages", RFC 1505, August 1993.
[5] Alvestrand, H., "Tags for the Identification of Languages", RFC
1766, March 1995.
[6] Myers, J. and M. Rose, "The Content-MD5 Header Field", RFC
1864, October 1995.
[7] Freed, N. and N. Borenstein, "Multipurpose Internet Mail
Extensions (MIME) Part One: Format of Internet Message Bodies",
RFC 2045, November 1996.
[8] Freed, N. and N. Borenstein, "Multipurpose Internet Mail
Extensions (MIME) Part Two: Media Types", RFC 2046, November
1996.
[9] Palme, J. and A. Hopmann, "MIME E-mail Encapsulation of
Aggregate Documents, such as HTML (MHTML)", RFC 2110, March
1997.
[10] Bradner, S., "Key words for use in RFCs to Indicate Requirement
Levels", BCP 14, RFC 2119, March 1997.
[11] Kille, S., "MIXER (Mime Internet X.400 Enhanced Relay): Mapping
between X.400 and RFC 822/MIME", RFC 2156, January 1998.
[12] Troost, R., Dorner, S. and K. Moore, "Communicating
Klyne & Palme Expires October 18, 2004 [Page 49]
Internet-Draft Mail and MIME header fields April 2004
Presentation Information in Internet Messages: The
Content-Disposition Header Field", RFC 2183, August 1997.
[13] Fajman, R., "An Extensible Message Format for Message
Disposition Notifications", RFC 2298, March 1998.
[14] Neufeld, G. and J. Baer, "The Use of URLs as Meta-Syntax for
Core Mail List Commands and their Transport through Message
Header Fields", RFC 2369, July 1998.
[15] Vaudreuil, G. and G. Parsons, "Voice Profile for Internet Mail
- version 2", RFC 2421, September 1998.
[16] Vaudreuil, G. and G. Parsons, "Content Duration MIME Header
Definition", RFC 2424, September 1998.
[17] Palme, F., Hopmann, A., Shelness, N. and E. Stefferud, "MIME
Encapsulation of Aggregate Documents, such as HTML (MHTML)",
RFC 2557, March 1999.
[18] Klensin, J., "Simple Mail Transfer Protocol", RFC 2821, April
2001.
[19] Resnick, P., "Internet Message Format", RFC 2822, April 2001.
[20] Klyne, G., "Indicating Media Features for MIME Content", RFC
2912, September 2000.
[21] Chandhok, R. and G. Wenger, "List-Id: A Structured Field and
Namespace for the Identification of Mailing Lists", RFC 2919,
March 2001.
[22] Alvestrand, H., "Content Language Headers", RFC 3282, May 2002.
[23] Klyne, G., Iwazaki, R. and D. Crocker, "Content Negotiation for
Messaging Services based on Email", RFC 3297, July 2002.
[24] Burger, E., Candell, E., Eliot, C. and G. Klyne, "Message
Context for Internet Mail", RFC 3458, January 2003.
[25] Miller, J., Krauskopf, T., Resnick, P. and W. Treese, "PICS
Label Distribution Label Syntax and Communication Protocols",
W3C Recommendation REC-PICS-labels, October 1996, <http://
www.w3.org/TR/REC-PICS-labels>.
Informative references
[26] Palme, J., "Common Internet Message Headers", RFC 2076,
Klyne & Palme Expires October 18, 2004 [Page 50]
Internet-Draft Mail and MIME header fields April 2004
February 1997.
[27] Palme, J., "Common Internet Message Header Fields", Internet
draft draft-palme-mailext-headers-08, November 2001, <http://
www.ietf.org/internet-drafts/
draft-palme-mailext-headers-08.txt>.
URIs
[28] <http://www.ninebynine.org/IETF/Messaging/HdrRegistry/
Intro.html>
Authors' Addresses
Graham Klyne
Nine by Nine
UK
EMail: GK-IETF@ninebynine.org
URI: http://www.ninebynine.net/
Jacob Palme
Stockholm University/KTH
Forum 100
Kista S-164 40
Sweden
Phone: +46-8-16 16 67
EMail: jpalme@dsv.su.se
Appendix A. Revision history
[[[Please remove this section on final publication]]]
A.1 draft-klyne-hdrreg-mail-04
04b 19-Apr-2004:
* Final editorial tidying.
* Acknowledge additional contributions.
04a 14-Apr-2004:
* Minor editorial fixes.
Klyne & Palme Expires October 18, 2004 [Page 51]
Internet-Draft Mail and MIME header fields April 2004
* Fix up message-headers I-D reference. [27]
A.2 draft-klyne-hdrreg-mail-03
03c 13-Apr-2004:
* Added Accept-Language header, with some warning text concerning
its use with email.
* Removed Originator headere, since it is not used as a mail
message header.
* Fix up report generator error in author/change controller
handling.
03b 06-Apr-2004:
* Using a new version of the RDF-to-documentation generator for
registry entry data.
* Revised format of registry entries to avoid some duplication of
document and author details.
* Added documents referenced by the regsitration entries to the
references section, and added citations to the entries
themselves.
03a 15-Mar-2004:
* Added and revised header details, per comments from Bruce
Lilly.
A.3 draft-klyne-hdrreg-mail-02
02d 19-Feb-2004:
* Incorporated small changes to specific header field
descriptions, suggested by Jacob.
02c 18-Feb-2004:
* Separated Mail and MIME header fields.
* Corrected specification reference for MIXER headers (RFC 2156).
* Changed applicable protocol for MIME header fields.
Klyne & Palme Expires October 18, 2004 [Page 52]
Internet-Draft Mail and MIME header fields April 2004
* Other smaller corrections.
02b 17-Feb-2004:
* Removed provisional mail header registrations from this
document.
02a 05-Aug-2002:
* Added Jacob Palme as co-editor.
A.4 draft-klyne-hdrreg-mail-01
01c 05-Jun-2002:
* Minor editorial.
01b 10-May-2002:
* Updated some contact information.
* Regenerated registry tables with revised software.
01a 08-May-2002:
* Revised change controller information in line with registry
specification.
* Cleaned up some table layout.
A.5 draft-klyne-hdrreg-mail-00
00c 05-May-2002:
* Added data for permanent and provisional registries.
00b 01-May-2002:
* Revised form of registry entry content. (Auto-generated from
RDF data.)
00a 22-Jan-2002:
* Document initially created.
Klyne & Palme Expires October 18, 2004 [Page 53]
Internet-Draft Mail and MIME header fields April 2004
Appendix B. TODO:
[[[Please remove this section on final publication]]]
o Resolve reference to registration procedure RFC [1].
o Remove any remaining [[[editorial comments]]].
Klyne & Palme Expires October 18, 2004 [Page 54]
Internet-Draft Mail and MIME header fields April 2004
Intellectual Property Statement
The IETF takes no position regarding the validity or scope of any
intellectual property or other rights that might be claimed to
pertain to the implementation or use of the technology described in
this document or the extent to which any license under such rights
might or might not be available; neither does it represent that it
has made any effort to identify any such rights. Information on the
IETF's procedures with respect to rights in standards-track and
standards-related documentation can be found in BCP-11. Copies of
claims of rights made available for publication and any assurances of
licenses to be made available, or the result of an attempt made to
obtain a general license or permission for the use of such
proprietary rights by implementors or users of this specification can
be obtained from the IETF Secretariat.
The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary
rights which may cover technology that may be required to practice
this standard. Please address the information to the IETF Executive
Director.
Full Copyright Statement
Copyright (C) The Internet Society (2004). All Rights Reserved.
This document and translations of it may be copied and furnished to
others, and derivative works that comment on or otherwise explain it
or assist in its implementation may be prepared, copied, published
and distributed, in whole or in part, without restriction of any
kind, provided that the above copyright notice and this paragraph are
included on all such copies and derivative works. However, this
document itself may not be modified in any way, such as by removing
the copyright notice or references to the Internet Society or other
Internet organizations, except as needed for the purpose of
developing Internet standards in which case the procedures for
copyrights defined in the Internet Standards process must be
followed, or as required to translate it into languages other than
English.
The limited permissions granted above are perpetual and will not be
revoked by the Internet Society or its successors or assignees.
This document and the information contained herein is provided on an
"AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING
TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING
BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION
Klyne & Palme Expires October 18, 2004 [Page 55]
Internet-Draft Mail and MIME header fields April 2004
HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF
MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Acknowledgement
Funding for the RFC Editor function is currently provided by the
Internet Society.
Klyne & Palme Expires October 18, 2004 [Page 56]
