RFC 1873 (rfc1873) - Page 2 of 4
Message/External-Body Content-ID Access Type
Alternative Format: Original Text Document
RFC 1873 Access Type Content-ID December 1995 2. The Content-ID Access Type 2.1 Registration Information MIME access-type name: content-id Required parameters: none Optional parameters: none Published specification: this document Person & email address to contact for further information: Ed Levinson <ELevinson@accurate.com> Additional requirements: The content-id header of the access-type=content-id MIME entity must match (be identical to) exactly one content-id in the same message, excluding other access-type=content-id entities. Thus, the content-id access type can only occur within a multipart message and can refer to another body part anywhere in the same message. A MIME User Agent (MUA) constructs the resultant MIME body part as described below. We call the access-type=content-id MIME entity the referring body part and the MIME body part to which it refers, the one with the matching content-id, the referenced body part. The MIME entity that results from content-id access type consists of: (a) the referenced body part's content-type header, (b) the referring body part's headers except its content-type header, (c) any headers in the referenced body part not in the referring one, (d) the line separating the headers from the body, and (e) the referenced body part's body. Levinson & Clark Experimental
