IETF Header Field Registry

By Jacob Palme. Last revision: 8 January 1998.

(This is an incomplete proposal for format of the IETF Header Field Registry. For more information see URL http://dsv.su.se/jpalme/ietf/jp-ietf-home.html#registry)

The IETF Header Field Registry is a registry of e-mail, netnews and HTTP header fields as specified in RFC ????. The registry is at IANA stored in a data base, from which the following three files are automatically produced.

The registry is available in HTML format, plain text format and tab delimited ascii table format.

(In this draft, all three files are included in this HTML file. But in real usage, the three files will be three different files, one for each format.)

Header registry in HTML format

Table of contents

(Not yet complete)

  • Content-Base
  • Content-Conversion
  • Content-Description
  • Content-Disposition
  • Contetn-ID
  • Content-Identifier
  • Content-Language
  • Content-Length
  • Content-Location
  • Content-MD5
  • Content-Return
  • Content-SGML-Entity
  • Content-Transfer-Encoding
  • Content-Type

    • Content-Location

    Header name:

    Content-Location:

    Header status:

    IETF Proposed Standard

    Applicability:

    COMMON

    Use:

    Gives an URL corresponding to a content part. The content part may, but need not, be retrievable using this URL. Used when sending HTML combined with related objects as aggregate MIME objects.

    Who can set or modify:

    Creator of aggregate MIME object

    Protocols which use it:

    E-MAIL MESSAGE HEADING, E-MAIL CONTENT HEADING, HTTP HEADING, USENET NEWS HEADING

    Applications which use it:

    Several e-mail clients and web browsers

    Encoding considerations:

    MIME (RFC 2047) and URLBODY (RFC 2017)

    Security considerations:

    Various, none serious. Can be avoided by careful impelementation. See RFC 2110 for details.

    Interoperability considerations:

    Can interoperate with non-compliant software, body part will be provided without its URL.

    Published specification:

    RFC 2110: MIME Encapsulation of Aggregate Documents, such as HTML (MHTML), March 1997.

    Contact person:

    Jacob Palme <jpalme@dsv.su.se> and Alex Hopmann <alexhop@microsoft.com>

    Change controller:

    IETF (MHTML working group), chair Einar Stefferud <stef@nma.com>

    Other information:

    IETF is working on a revision of RFC 2110. See URL http://dsv.su.se/jpalme/ietf/mhtml.html for more information.

    Header registry in plain text format 

    Header name:             Content-Location:
Header status:           IETF Proposed Standard
Applicability:           COMMON
Use:                     Gives an URL corresponding to a content part.
                         The content part may, but need not, be
                         retrievable using this URL. Used when sending
                         HTML combined with related objects as
                         aggregate MIME objects.
Who can set or modify:   Creator of aggregate MIME object
Protocols which use it:  E-MAIL MESSAGE HEADING, E-MAIL CONTENT
                         HEADING, HTTP HEADING, USENET NEWS HEADING
Applications which use   Several e-mail clients and web browsers
it:
Encoding                 MIME (RFC 2047) and URLBODY (RFC 2017)
considerations:
Security                 Various, none serious. Can be avoided by
considerations:          careful impelementation. See RFC 2110 for
                         details.
Interoperability         Can interoperate with non-compliant software,
considerations:          body part will be provided without its URL.
Published                RFC 2110: MIME Encapsulation of Aggregate
specification:           Documents, such as HTML (MHTML), March 1997.
Contact person:          Jacob Palme <jpalme@dsv.su.se> and Alex
                         Hopmann <alexhop@microsoft.com>
Change controller:       IETF (MHTML working group), chair Einar
                         Stefferud <stef@nma.com>
Other information:       IETF is working on a revision of RFC 2110.
                         See URL
                         http://dsv.su.se/jpalme/ietf/mhtml.html
                         for more information.
 

    Header registry as a tab-separated table 

    Header name: 	Header status: 	Applicability: 	Use: 	Who can set or modify: 	Protocols which use it: 	Applications which use it: 	Encoding considerations: 	Security considerations: 	Interoperability considerations: 	Published specification: 	Contact person: 	Change controller: 	Other information:
Content-Location: 	IETF Proposed Standard 	COMMON 	Gives an URL corresponding to a content part. The content part may, but need not, be retrievable using this URL. Used when sending HTML combined with related objects as aggregate MIME objects. 	Creator of aggregate MIME object 	E-MAIL MESSAGE HEADING, E-MAIL CONTENT HEADING, HTTP HEADING, USENET NEWS HEADING 	Several e-mail clients and web browsers 	MIME (RFC 2047) and URLBODY (RFC 2017) 	Various, none serious. Can be avoided by careful impelementation. See RFC 2110 for details. 	Can interoperate with non-compliant software, body part will be provided without its URL. 	RFC 2110: MIME Encapsulation of Aggregate Documents, such as HTML (MHTML), March 1997. 	Jacob Palme <jpalme@dsv.su.se> and Alex Hopmann <alexhop@microsoft.com> 	IETF (MHTML working group), chair Einar Stefferud <stef@nma.com> 	IETF is working on a revision of RFC 2110. See URL http://dsv.su.se/jpalme/ietf/mhtml.html for more information.