Nine by Nine

UK GK-IETF@ninebynine.org http://www.ninebynine.net/

Stockholm University/KTH

Forum 100 Kista S-164 40 Sweden +46-8-16 16 67 +46-8-783 08 29 jpalme@dsv.su.se

Application message header fields email headers RFC2822 MIME registration IANA This document defines the initial IANA registration for permanent mail and MIME message header fields, per [[[RFC XXXX (xref target="msghdr-registry" /)]]]. 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>.

This document defines IANA registration for a number of mail message and MIME header fields, per Registration procedures for message header fields. 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 .

Section contains the templates for initial registration of mail message header fields. Section contains templates for initial registration of MIME header fields.

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 . [[[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.]]]

Header field registry entries are summarized in tabular form for convenience of reference, and presented in full in the following sections.

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.

No security considerations are introduced by this registration document beyond those already inherent in use of the mail message header fields referenced.

Most of the information in this document has been derived from Jacob Palme's work in RFC 2076 and subsequent updates . 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).

Nine by Nine

UK GK-IETF@ninebynine.org http://www.ninebynine.net/

BEA Systems

235 Montgomery St. Level 15 San Francisco CA 94104 USA mnot@pobox.com

Western Research Laboratory, Compaq Computer Corporation

250 University Avenue Palo Alto CA 94305 US 1 650 617 3304 (email preferred) JeffMogul@acm.org

World Wide Web Consortium

jmiller@w3.org http://www.w3c.org

Spyglass

timk@spyglass.com

AT&T

presnick@research.att.com

OpenMarket

treese@OpenMarket.com

Stockholm University/KTH

[[[Please remove this section on final publication]]]

Change status of headers defined by RFC822 to standard, except Encrypted which is obsolete. Add RFC822 to references. Set ?RFC strict=yes, and clean up ID-nits.

Final editorial tidying. Acknowledge additional contributions. Minor editorial fixes. Fix up message-headers I-D reference.

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. 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. Added and revised header details, per comments from Bruce Lilly.

Incorporated small changes to specific header field descriptions, suggested by Jacob. Separated Mail and MIME header fields. Corrected specification reference for MIXER headers (RFC 2156). Changed applicable protocol for MIME header fields. Other smaller corrections. Removed provisional mail header registrations from this document. Added Jacob Palme as co-editor.

Minor editorial. Updated some contact information. Regenerated registry tables with revised software. Revised change controller information in line with registry specification. Cleaned up some table layout.

Added data for permanent and provisional registries. Revised form of registry entry content. (Auto-generated from RDF data.) Document initially created.

[[[Please remove this section on final publication]]] Resolve reference to registration procedure RFC . Remove any remaining [[[editorial comments]]].