Debian Codegraph @

rfc1873.html

raw
1 <pre>Network Working Group E. Levinson
2 Request for Comments: 1873 Accurate Information Systems, Inc.
3 Category: Experimental J. Clark
4 December 1995
5
6
7 <span class="h1">Message/External-Body Content-ID Access Type</span>
8
9 Status of this Memo
10
11 This memo defines an Experimental Protocol for the Internet
12 community. This memo does not specify an Internet standard of any
13 kind. Discussion and suggestions for improvement are requested.
14 Distribution of this memo is unlimited.
15
16 Abstract
17
18 When using MIME [<a href="#ref-MIME" title="&quot;MIME (Multipurpose Internet Mail Extensions) Part One: Mechanisms for Specifying and Describing the Format of Internet Message Bodies&quot;">MIME</a>] to encapsulate a structured object that
19 consist of many elements, for example an SGML [<a href="#ref-SGML">SGML</a>] document, a
20 single element may occur several times. An encapsulation normally
21 maps each of the structured objects elements to a MIME entity. It is
22 useful to include elements that occur multiple time exactly once. To
23 accomplish that and to preserve the object structure it is desirable
24 to unambiguously refer to another body part of the same message.
25
26 The existing MIME Content-Type Message/External-Body access-types
27 allow a MIME entity (body-part) to refer to an object that is not in
28 the message by specifying how to access that object. The Content-ID
29 access method described in this document provides the capability to
30 refer to an object within the message.
31
32 <span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. Introduction</span>
33
34 Consider a MIME multipart entity several of whose body parts contain
35 the same data (body) but different parameters or Content-* headers.
36 Representing those body parts without duplicating the data in each
37 one promotes efficient use of resources (bandwidth and storage
38 space). To achieve these benefits an access-type is defined that
39 permits one message part to refer to another one in the same message.
40
41
42
43
44
45
46
47
48
49
50
51
52 <span class="grey">Levinson &amp; Clark Experimental [Page 1]</span></pre>
53 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span>
54 <span class="grey"><a href="./rfc1873">RFC 1873</a> Access Type Content-ID December 1995</span>
55
56
57 <span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. The Content-ID Access Type</span>
58
59 <span class="h3"><a class="selflink" id="section-2.1" href="#section-2.1">2.1</a> Registration Information</span>
60
61 MIME access-type name: content-id
62
63 Required parameters: none
64
65 Optional parameters: none
66
67 Published specification: this document
68
69 Person &amp; email address
70 to contact for further
71 information: Ed Levinson &lt;[email protected]&gt;
72
73 Additional requirements:
74
75 The content-id header of the access-type=content-id MIME
76 entity must match (be identical to) exactly one content-id
77 in the same message, excluding other access-type=content-id
78 entities. Thus, the content-id access type can only occur
79 within a multipart message and can refer to another body
80 part anywhere in the same message.
81
82 A MIME User Agent (MUA) constructs the resultant MIME body
83 part as described below. We call the access-type=content-id
84 MIME entity the referring body part and the MIME body part
85 to which it refers, the one with the matching content-id,
86 the referenced body part. The MIME entity that results from
87 content-id access type consists of:
88
89 (a) the referenced body part's content-type header,
90
91 (b) the referring body part's headers except its content-type
92 header,
93
94 (c) any headers in the referenced body part not in the referring
95 one,
96
97 (d) the line separating the headers from the body, and
98
99 (e) the referenced body part's body.
100
101
102
103
104
105
106
107
108 <span class="grey">Levinson &amp; Clark Experimental [Page 2]</span></pre>
109 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-3" ></span>
110 <span class="grey"><a href="./rfc1873">RFC 1873</a> Access Type Content-ID December 1995</span>
111
112
113 <span class="h3"><a class="selflink" id="section-2.2" href="#section-2.2">2.2</a> Example Usage</span>
114
115 The following example shows a message that consists of two identical
116 images.
117
118 MIME-Version: 1.0
119 Content-Type: Multipart/Mixed;
120 boundary=tiger-lily
121
122 --tiger-lily
123 Content-Type: image/jpeg
124 Content-ID: &lt;[email protected]&gt;
125
126 AAAcdb...
127 --tiger-lily
128 Content-type: Message/External-Body;
129 access-type=content-id
130 Content-ID: &lt;[email protected]&gt;
131 Content-Description:
132 This body part is duplicated by reference
133
134 --tiger-lily--
135
136 The equivalent MIME entity for the second body part is:
137
138 --tiger-lily
139 Content-Type: image/jpeg
140 Content-ID: &lt;[email protected]&gt;
141 Content-Description:
142 This body part is duplicated by reference
143
144 AAAcdb...
145 --tiger-lily
146
147 <span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. Security Considerations</span>
148
149 The content-id access-type does not impact the security of messages
150 or systems. The referenced MIME entity may have security
151 implications.
152
153
154
155
156
157
158
159
160
161
162
163
164 <span class="grey">Levinson &amp; Clark Experimental [Page 3]</span></pre>
165 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-4" ></span>
166 <span class="grey"><a href="./rfc1873">RFC 1873</a> Access Type Content-ID December 1995</span>
167
168
169 <span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. References</span>
170
171
172 [<a id="ref-822">822</a>] Crocker, D., "Standard for the Format of ARPA Internet
173 Text Messages", STD 11, <a href="./rfc822">RFC 822</a>, UDEL, August 1982.
174
175 [<a id="ref-SGML">SGML</a>] ISO 8879:1988, Information processing -- Text and office
176 systems -- Standard Generalized Markup Language (SGML).
177
178 [<a id="ref-MIME">MIME</a>] Borenstein, N., and N. Freed, "MIME (Multipurpose
179 Internet Mail Extensions) Part One: Mechanisms for
180 Specifying and Describing the Format of Internet
181 Message Bodies", <a href="./rfc1521">RFC 1521</a>, Bellcore, Innosoft,
182 September 1993.
183
184 <span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>. Authors' Addresses</span>
185
186 Edward Levinson
187 Accurate Information Systems, Inc.
188 <span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a> Industrial Way</span>
189 Eatontown, NJ 07724-2265
190 USA
191
192 Phone: +1 908 389 5550
193 EMail: &lt;[email protected]&gt;
194
195
196 James Clark
197 <span class="h2"><a class="selflink" id="section-90" href="#section-90">90</a> Clarendon Road</span>
198 London W11 2HR
199 UK
200
201 EMail: &lt;[email protected]&gt;
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220 Levinson &amp; Clark Experimental [Page 4]
221 </pre>