Connected: An Internet Encyclopedia
RFC 1521 - 6.1. Optional Content-ID Header Field

Top: Connected: An Internet Encyclopedia
Up: Requests For Comments
Up: RFC 1521
Up: 6. Additional Content-Header Fields
Prev: 6. Additional Content-Header Fields
Next: 6.2. Optional Content-Description Header Field

### 6.1. Optional Content-ID Header Field

In constructing a high-level user agent, it may be desirable to allow one body to make reference to another. Accordingly, bodies may be labeled using the "Content-ID" header field, which is syntactically identical to the "Message-ID" header field:

       id :=  "Content-ID" ":" msg-id

Like the Message-ID values, Content-ID values must be generated to be world-unique.

The Content-ID value may be used for uniquely identifying MIME entities in several contexts, particularly for cacheing data referenced by the message/external-body mechanism. Although the Content-ID header is generally optional, its use is mandatory in implementations which generate data of the optional MIME Content-type "message/external-body". That is, each message/external-body entity must have a Content-ID field to permit cacheing of such data.

It is also worth noting that the Content-ID value has special semantics in the case of the multipart/alternative content-type. This is explained in the section of this document dealing with multipart/alternative.

Next: 6.2. Optional Content-Description Header Field

Connected: An Internet Encyclopedia
RFC 1521 - 6.1. Optional Content-ID Header Field