1 |
<?xml version="1.0" encoding="iso-2022-jp"?> |
2 |
<!DOCTYPE rfc SYSTEM "rfc2629.dtd" [ |
3 |
<!ENTITY rfc.number "1873"> |
4 |
<!ENTITY ja.access "$B@\B3(B"> |
5 |
<!ENTITY ja.object "$BJ*BN(B"> |
6 |
<!ENTITY ja.optional "$B>JN,2DG=(B"> |
7 |
<!ENTITY ja.security "$B0BA4@-(B"> |
8 |
<!ENTITY ja.system "$B=hM}7O(B"> |
9 |
<!ENTITY ja.text "$B%F%-%9%H(B"> |
10 |
<!ENTITY ja.user-agent "$BMxMQ<TBeM}<T(B"> |
11 |
<!ENTITY ja.mail.body "$BK\J8(B"> |
12 |
<!ENTITY ja.mail.header "$BF,(B"> |
13 |
<!ENTITY ja.mime.body-part "$BK\J8ItJ,(B"> |
14 |
<!ENTITY ja.mime.entity "$B<BBN(B"> |
15 |
<!ENTITY ja.mime.multipart "$BB?ItJ,(B"> |
16 |
<!ENTITY ja.mime.part "$BItJ,(B"> |
17 |
<!ENTITY ja.mime.parameter "$B%Q%i%a!<%?!<(B"> |
18 |
]> |
19 |
<?rfc symrefs="yes"?> |
20 |
<rfc number="&rfc.number;" category="exp" |
21 |
xmlns:myns="mailto:julian.reschke@greenbytes.de?subject=rcf2629.xslt" |
22 |
xmlns:ja="http://suika.fam.cx/~wakaba/lang/rfc/translation/" |
23 |
xmlns:h="http://www.w3.org/1999/xhtml"> |
24 |
<front> |
25 |
<title>Message/External-Body Content-ID Access Type</title> |
26 |
<ja:title xml:lang="ja">Message/External-Body Content-ID &ja.access;$B7?(B</ja:title> |
27 |
<author initials="E." surname="Levinson" fullname="Edward Levinson"> |
28 |
<organization>Accurate Information Systems, Inc.</organization> |
29 |
<address> |
30 |
<postal> |
31 |
<street>2 Industrial Way</street> |
32 |
<city>Eatontown</city> <region>NJ</region> |
33 |
<code>07724-2265</code> |
34 |
<country ja:text="USA">US</country> |
35 |
</postal> |
36 |
<phone>+1 908 389 5550</phone> |
37 |
<email>ELevinson@Accurate.com</email> |
38 |
</address> |
39 |
</author> |
40 |
<author initials="J." surname="Clark" fullname="James Clark"> |
41 |
<address> |
42 |
<postal> |
43 |
<street>90 Clarendon Road</street> |
44 |
<city>London W11 2HR</city> |
45 |
<country ja:text="UK">GB</country> |
46 |
</postal> |
47 |
<email>jjc@jclark.com</email> |
48 |
</address> |
49 |
</author> |
50 |
<date month="December" year="1995" /> |
51 |
<abstract> |
52 |
<t> |
53 |
<ja:pair> |
54 |
<ja:l xml:lang="en"> |
55 |
When using MIME <xref target="MIME" /> to encapsulate a |
56 |
structured object that |
57 |
consist of many elements, for example an SGML <xref target="SGML" /> |
58 |
document, a |
59 |
single element may occur several times. An encapsulation normally |
60 |
maps each of the structured objects elements to a MIME entity. It is |
61 |
useful to include elements that occur multiple time exactly once. To |
62 |
accomplish that and to preserve the object structure it is desirable |
63 |
to unambiguously refer to another body part of the same message. |
64 |
</ja:l> |
65 |
<ja:l xml:lang="ja"> |
66 |
MIME <xref target="MIME" /> $B$r;H$C$FB?$/$NMWAG$G9=@.$5$l$k9=B$2=(B&ja.object;, |
67 |
$BNc$($P(B SGML <xref target="SGML" /> |
68 |
$BJ8=q$r%+%W%;%k2=$9$k;~!"0l$D$NMWAG$,4vEY$b=P8=$9$k$+$b$7$l$^$;$s!#%+%W%;%k2=$ODL>o3F9=B$2=(B&ja.object;$BMWAG$H(B |
69 |
MIME $B<BBN$rBP1~$5$;$^$9!#J#?t2s8=$l$kMWAG$r0l$D$@$14^$a$k$3$H$,=PMh$l$PJXMx$G$9!#$3$l$rC#@.$7$+$D(B&ja.object;$B9=B$$rJ]$D$?$a!"F1$8%a%C%;!<%8$NB>$N(B&ja.mime.body-part;$B$r[#KfL5$/;2>H=PMh$k$N$,K>$^$7$$$G$7$g$&!#(B |
70 |
</ja:l> |
71 |
</ja:pair> |
72 |
</t> |
73 |
<t> |
74 |
<ja:pair> |
75 |
<ja:l xml:lang="en"> |
76 |
The existing MIME Content-Type Message/External-Body access-types |
77 |
allow a MIME entity (body-part) to refer to an object that is not in |
78 |
the message by specifying how to access that object. The Content-ID |
79 |
access method described in this document provides the capability to |
80 |
refer to an object within the message. |
81 |
</ja:l> |
82 |
<ja:l xml:lang="ja"> |
83 |
$B4{B8$N(B MIME Content-Type Message/External-Body access-type |
84 |
$B$G$O(B MIME &ja.mime.entity; (&ja.mime.body-part;) |
85 |
$B$,!"%a%C%;!<%8Cf$KL5$$(B&ja.object;$B$r!";XDj$7$?(B&ja.object;$B$X$N(B&ja.access;$BJ}K!$G;2>H$9$k$3$H$,=PMh$^$7$?!#$3$NJ8=q$G@bL@$9$k(B |
86 |
Content-ID &ja.access;$BJ}K!$O!"%a%C%;!<%8Cf$N(B&ja.object;$B$r;2>H$9$kJ}K!$rDs6!$7$^$9!#(B |
87 |
</ja:l> |
88 |
</ja:pair> |
89 |
</t> |
90 |
</abstract> |
91 |
</front> |
92 |
<ja:front> |
93 |
<author fullname="$B$o$+$P(B" ja:id="wakaba"> |
94 |
<address> |
95 |
<email>w@suika.fam.cx</email> |
96 |
<uri>http://suika.fam.cx/~wakaba/</uri> |
97 |
</address> |
98 |
</author> |
99 |
<ja:change> |
100 |
<ja:item year="2002" month="05" day="20"><author ja:ref="wakaba" /> |
101 |
<t>$BF|K\8l$KK]Lu!#(B</t> |
102 |
</ja:item> |
103 |
<ja:item year="2002" month="07" day="26"><author ja:ref="wakaba" /> |
104 |
<t><ja:link type="rfc" number="2629" /> $B$G%^!<%/IU$1!#(B</t> |
105 |
</ja:item> |
106 |
</ja:change><!-- $Date: 2002/07/26 11:56:16 $ --> |
107 |
</ja:front> |
108 |
<middle> |
109 |
|
110 |
<section title="Introduction"> |
111 |
<t> |
112 |
<ja:pair> |
113 |
<ja:l xml:lang="en"> |
114 |
Consider a MIME multipart entity several of whose body parts contain |
115 |
the same data (body) but different parameters or Content-* headers. |
116 |
Representing those body parts without duplicating the data in each |
117 |
one promotes efficient use of resources (bandwidth and storage |
118 |
space). To achieve these benefits an access-type is defined that |
119 |
permits one message part to refer to another one in the same message. |
120 |
</ja:l> |
121 |
<ja:l xml:lang="ja"> |
122 |
MIME &ja.mime.multipart;&ja.mime.entity;$B$G!"$=$N(B&ja.mime.body-part;$B$N4v$D$+$OF1$8%G!<%?(B |
123 |
(&ja.mail.body;) $B$G$"$k$,!"%Q%i%a!<%?!<$d(B |
124 |
Content-* &ja.mail.header;$B$,0c$C$F$$$k>l9g$r9M$($F$_$F2<$5$$!#$3$l$i$N(B&ja.mime.body-part;$B$r!"%G!<%?$rFs=E$K$;$:$K$=$l$>$l0l2s$:$DI=8=$9$k$3$H$G!";q8;(B |
125 |
($BBS0h$dJ]4I6u4V(B) $B$rG=N(E*$K;H$&$3$H$rB%?J=PMh$^$9!#$=$3$G!"(B |
126 |
$B$"$k%a%C%;!<%8(B&ja.mime.part;$B$,F1$8%a%C%;!<%8Cf$NB>$N(B&ja.mime.part;$B$r;2>H=PMh$k(B |
127 |
access-type $B$rDj5A$7$^$9!#(B |
128 |
</ja:l> |
129 |
</ja:pair> |
130 |
</t> |
131 |
</section> |
132 |
|
133 |
<section title="The Content-ID Access Type" ja:title-ja="Content-ID &ja.access;$B7?(B"> |
134 |
|
135 |
<section title="Registration Information" ja:title-ja="$BEPO?>pJs(B"> |
136 |
<t> |
137 |
<list style="hanging"> |
138 |
<t hangText="MIME access-type name" ja:hangText-ja="MIME access-type $BL>(B">content-id</t> |
139 |
|
140 |
<t hangText="Required parameters" ja:hangText-ja="$BI,?\(B&ja.mime.parameter;"><ja:pair> |
141 |
<ja:l xml:lang="en">none</ja:l> |
142 |
<ja:l xml:lang="ja">$B$J$7(B</ja:l> |
143 |
</ja:pair></t> |
144 |
|
145 |
<t hangText="Optional parameters" ja:hangText-ja="&ja.optional;&ja.mime.parameter;"><ja:pair> |
146 |
<ja:l xml:lang="en">none</ja:l> |
147 |
<ja:l xml:lang="ja">$B$J$7(B</ja:l> |
148 |
</ja:pair></t> |
149 |
|
150 |
<t hangText="Published specification" ja:hangText-ja="$B=PHG$5$l$?;EMM=q(B"><ja:pair> |
151 |
<ja:l xml:lang="en">this document</ja:l> |
152 |
<ja:l xml:lang="ja">$B$3$NJ8=q(B</ja:l> |
153 |
</ja:pair></t> |
154 |
|
155 |
<t hangText="Person & email address to contact for further information" ja:hangText-ja="$B>\$7$$>pJs$NO"Mm@h$N?M$HEE;R%a%$%k!&%"%I%l%9(B"> |
156 |
Ed Levinson <ja:mail>ELevinson@accurate.com</ja:mail> |
157 |
</t> |
158 |
|
159 |
<t hangText="Additional requirements" ja:hangText-ja="$BDI2C$NMW7o(B"> |
160 |
|
161 |
<t> |
162 |
<ja:pair> |
163 |
<ja:l xml:lang="en"> |
164 |
The content-id header of the access-type=content-id MIME |
165 |
entity must match (be identical to) exactly one content-id |
166 |
in the same message, excluding other access-type=content-id |
167 |
entities. Thus, the content-id access type can only occur |
168 |
within a multipart message and can refer to another body |
169 |
part anywhere in the same message. |
170 |
</ja:l> |
171 |
<ja:l xml:lang="ja"> |
172 |
<h:code>access-type=content-id</h:code> MIME |
173 |
&ja.mime.entity;$B$N(B content-id &ja.mail.header;$B$O!"B>$N(B |
174 |
<h:code>access-type=content-id</h:code> |
175 |
$B$N(B&ja.mime.entity;$B$r=|$$$F!"F1$8%a%C%;!<%8Cf$NCzEY0l$D$N(B |
176 |
content-id $B$H$N$_0lCW$9$k(B ($BF10l$G$"$k(B) |
177 |
$B$b$N$G$J$1$l$P$J$j$^$;$s!#$G$9$+$i!"(B |
178 |
content-id &ja.access;$B7?$O(B&ja.mime.multipart;$B%a%C%;!<%8Cf$G$N$_;H$&$3$H$,=PMh$^$9$7!"F1$8%a%C%;!<%8Cf$N$I$3$K$"$kB>$N(B&ja.mime.body-part;$B$r$b;2>H$9$k$3$H$,=PMh$^$9!#(B |
179 |
</ja:l> |
180 |
</ja:pair> |
181 |
</t> |
182 |
|
183 |
<t> |
184 |
<ja:pair> |
185 |
<ja:l xml:lang="en"> |
186 |
A MIME User Agent (MUA) constructs the resultant MIME |
187 |
body part as described below. We call the |
188 |
access-type=content-id MIME entity the referring body |
189 |
part and the MIME body part to which it refers, |
190 |
the one with the matching content-id, the referenced |
191 |
body part. The MIME entity that results from |
192 |
content-id access type consists of: |
193 |
</ja:l> |
194 |
<ja:l xml:lang="ja"> |
195 |
MIME &ja.user-agent; (<h:abbr xml:lang="en">MUA</h:abbr>) |
196 |
$B$O7k2L$H$7$F@8$8$k(B MIME |
197 |
&ja.mime.body-part;$B$r<!$K@bL@$9$k$h$&$K$7$F9=C[$7$^$9!#$3$3$G!"(B |
198 |
<ja:definition word="referring body part" translation="$B;2>H$9$k(B&ja.mime.body-part;"><h:code>access-type=content-id</h:code> |
199 |
$B$N(B MIME |
200 |
&ja.mime.entity;</ja:definition>$B$r;2>H$9$k(B&ja.mime.body-part;$B$H(B, |
201 |
<ja:definition word="referenced body part" translation="$B;2>H$5$l$k(B&ja.mime.body-part;">$B;2>H$9$k(B&ja.mime.body-part;$B$,;2>H$9$k(B MIME &ja.mime.body-part;, |
202 |
$B$D$^$j0lCW$9$k(B content-id |
203 |
$B$r;}$D$b$N(B</ja:definition>$B$r;2>H$5$l$k(B&ja.mime.body-part;$B$H8F$S$^$9!#(B |
204 |
content-id &ja.access;$B7?$N7k2L$N(B MIME |
205 |
&ja.mime.entity;$B$O<!$N$b$N$+$i9=@.$5$l$^$9!#(B |
206 |
</ja:l> |
207 |
</ja:pair> |
208 |
|
209 |
<list style="hanging"> |
210 |
<t hangText="(a)"><ja:pair> |
211 |
<ja:l xml:lang="en"> |
212 |
the referenced body part's content-type header, |
213 |
</ja:l> |
214 |
<ja:l xml:lang="ja"> |
215 |
<ja:word name="referenced body part" />$B$N(B content-type |
216 |
&ja.mail.header; |
217 |
</ja:l> |
218 |
</ja:pair></t> |
219 |
<t hangText="(b)"><ja:pair> |
220 |
<ja:l xml:lang="en"> |
221 |
the referring body part's headers except its |
222 |
content-type header, |
223 |
</ja:l> |
224 |
<ja:l xml:lang="ja"> |
225 |
<ja:word name="referring body part" />$B$N(B content-type |
226 |
&ja.mail.header;$B0J30$N(B&ja.mail.header; |
227 |
</ja:l> |
228 |
</ja:pair></t> |
229 |
<t hangText="(c)"><ja:pair> |
230 |
<ja:l xml:lang="en"> |
231 |
any headers in the referenced body part not in the |
232 |
referring one, |
233 |
</ja:l> |
234 |
<ja:l xml:lang="ja"> |
235 |
<ja:word name="referenced body part" />$B$N!"(B<ja:word name="referring body part">$B;2>H$9$kJ}(B</ja:word>$B$K$J$$(B&ja.mail.header; |
236 |
</ja:l> |
237 |
</ja:pair></t> |
238 |
<t hangText="(d)"><ja:pair> |
239 |
<ja:l xml:lang="en"> |
240 |
the line separating the headers from the body, and |
241 |
</ja:l> |
242 |
<ja:l xml:lang="ja"> |
243 |
&ja.mail.header;$B$H(B&ja.mail.body;$B$r6h@Z$k9T(B |
244 |
</ja:l> |
245 |
</ja:pair></t> |
246 |
<t hangText="(e)"><ja:pair> |
247 |
<ja:l xml:lang="en"> |
248 |
the referenced body part's body. |
249 |
</ja:l> |
250 |
<ja:l xml:lang="ja"> |
251 |
<ja:word name="referenced body part" />$B$N(B&ja.mail.body; |
252 |
</ja:l> |
253 |
</ja:pair></t> |
254 |
</list><!-- hanging --> |
255 |
</t> |
256 |
</t><!-- additional requirements --> |
257 |
</list><!-- submit form --> |
258 |
</t> |
259 |
</section><!-- 2.1 --> |
260 |
|
261 |
<section title="Example Usage" ja:title-ja="$B;HMQNc(B"> |
262 |
<figure> |
263 |
<preamble> |
264 |
<ja:pair> |
265 |
<ja:l xml:lang="en"> |
266 |
The following example shows a message that consists of two identical images. |
267 |
</ja:l> |
268 |
<ja:l xml:lang="ja"> |
269 |
$B<!$NNc$O!"(B2$B$D$NF1$82hA|$+$i9=@.$5$l$k%a%C%;!<%8$G$9!#(B |
270 |
</ja:l> |
271 |
</ja:pair> |
272 |
</preamble> |
273 |
|
274 |
<ja:pair> |
275 |
<ja:l xml:lang="en"> |
276 |
|
277 |
|
278 |
<artwork xml:space="preserve"><![CDATA[ MIME-Version: 1.0 |
279 |
Content-Type: Multipart/Mixed; |
280 |
boundary=tiger-lily |
281 |
|
282 |
--tiger-lily |
283 |
Content-Type: image/jpeg |
284 |
Content-ID: <950323.1552@XIson.com> |
285 |
|
286 |
AAAcdb... |
287 |
--tiger-lily |
288 |
Content-type: Message/External-Body; |
289 |
access-type=content-id |
290 |
Content-ID: <950323.1552@XIson.com> |
291 |
Content-Description: |
292 |
This body part is duplicated by reference |
293 |
|
294 |
--tiger-lily-- |
295 |
]]></artwork> |
296 |
</ja:l> |
297 |
<ja:l xml:lang="ja"> |
298 |
<artwork xml:space="preserve"><![CDATA[ MIME-Version: 1.0 |
299 |
Content-Type: Multipart/Mixed; |
300 |
boundary=tiger-lily |
301 |
|
302 |
--tiger-lily |
303 |
Content-Type: image/jpeg |
304 |
Content-ID: <950323.1552@XIson.com> |
305 |
|
306 |
AAAcdb... |
307 |
--tiger-lily |
308 |
Content-type: Message/External-Body; |
309 |
access-type=content-id |
310 |
Content-ID: <950323.1552@XIson.com> |
311 |
Content-Description: |
312 |
$B$3$N(B&ja.mime.body-part;$B$O;2>H$GJ#@=$5$l$^$9!#(B |
313 |
|
314 |
--tiger-lily-- |
315 |
]]></artwork> |
316 |
</ja:l> |
317 |
</ja:pair> |
318 |
</figure> |
319 |
|
320 |
<figure> |
321 |
<preamble> |
322 |
<ja:pair> |
323 |
<ja:l xml:lang="en"> |
324 |
The equivalent MIME entity for the second body part is: |
325 |
</ja:l> |
326 |
<ja:l xml:lang="ja"> |
327 |
2$B$D$a$N(B&ja.mime.body-part;$B$HF1Ey$N(B |
328 |
MIME &ja.mime.entity;$B$r<!$K5s$2$^$9!#(B |
329 |
</ja:l> |
330 |
</ja:pair> |
331 |
</preamble> |
332 |
|
333 |
<ja:pair> |
334 |
<ja:l xml:lang="en"> |
335 |
<artwork xml:space="preserve"><![CDATA[ --tiger-lily |
336 |
Content-Type: image/jpeg |
337 |
Content-ID: <950323.1552@XIson.com> |
338 |
Content-Description: |
339 |
$B$3$N(B]]>&ja.mime.body-part;<![CDATA[$B$O;2>H$GJ#@=$5$l$^$9!#(B |
340 |
|
341 |
AAAcdb... |
342 |
--tiger-lily]]></artwork> |
343 |
</ja:l> |
344 |
<ja:l xml:lang="ja"> |
345 |
<artwork xml:space="preserve"><![CDATA[ --tiger-lily |
346 |
Content-Type: image/jpeg |
347 |
Content-ID: <950323.1552@XIson.com> |
348 |
Content-Description: |
349 |
This body part is duplicated by reference |
350 |
|
351 |
AAAcdb... |
352 |
--tiger-lily]]></artwork> |
353 |
</ja:l> |
354 |
</ja:pair> |
355 |
</figure> |
356 |
</section><!-- 2.2 --> |
357 |
</section><!-- 2 --> |
358 |
|
359 |
<section title="Security Considerations"> |
360 |
<t> |
361 |
<ja:pair> |
362 |
<ja:l xml:lang="en"> |
363 |
The content-id access-type does not impact the security of messages |
364 |
or systems. The referenced MIME entity may have security |
365 |
implications. |
366 |
</ja:l> |
367 |
<ja:l xml:lang="ja"> |
368 |
content-id access-type $B$O%a%C%;!<%8$d(B&ja.system;$B$N(B&ja.security;$B$K>W7b$rM?$($^$;$s!#(B<ja:word name="referenced body part">$B;2>H$5$l$?(B |
369 |
MIME &ja.mime.entity;</ja:word>$B$O(B&ja.security;$B$K4X78$9$k$+$b$7$l$^$;$s!#(B |
370 |
</ja:l> |
371 |
</ja:pair> |
372 |
</t> |
373 |
</section> |
374 |
|
375 |
<ja:insert section="references" ja:title-prefix="4. " /> |
376 |
<ja:insert section="author-address" ja:title-prefix="5. " /> |
377 |
</middle> |
378 |
|
379 |
<back> |
380 |
|
381 |
<references> |
382 |
<reference anchor="RFC822"> |
383 |
<front> |
384 |
<title>Standard for the format of ARPA Internet text messages</title> |
385 |
<ja:title xml:lang="ja">ARPA Internet |
386 |
&ja.text;$B%a%C%;!<%8$N=q<0$NI8=`(B</ja:title> |
387 |
<author initials="D." surname="Crocker" fullname="David H. Crocker"> |
388 |
<organization abbrev="UDEL">University of Delaware, |
389 |
Dept. of Electrical Engineering</organization> |
390 |
</author> |
391 |
<date month="August" year="1982" /> |
392 |
</front> |
393 |
<seriesInfo name="STD" value="11" /> |
394 |
<seriesInfo name="RFC" value="822" /> |
395 |
</reference> |
396 |
|
397 |
<reference anchor="SGML"> |
398 |
<front> |
399 |
<title>Information processing $B!=!=(B Text and office systems |
400 |
$B!=!=(B Standard Generalized Markup Language (SGML)</title> |
401 |
<ja:title xml:lang="ja">$B>pJs=hM}!=!=(B&ja.text;$B5Z$S;vL3=j7OE}!=!=I8=`HFMQ%^!<%/IU$18@8l(B (SGML)</ja:title> |
402 |
</front> |
403 |
<seriesInfo name="ISO" value="8879:1988" /> |
404 |
<ja:add-info> |
405 |
<ja:note>$BF|K\9)6H5,3J$G$O!"(B JIS X 4151 |
406 |
$B!XJ8=q5-=R8@8l(BSGML$B!Y$,BP1~$7$^$9!#(B |
407 |
($B;29M(B: |
408 |
<eref target="http://www1.u-netsurf.ne.jp/~7l1rll/SGMLindex.html">JIS X 4151-1992 (ISO 8859:1986 $B$KBP1~(B)</eref>)</ja:note> |
409 |
</ja:add-info> |
410 |
</reference> |
411 |
|
412 |
<reference anchor="MIME"> |
413 |
<front> |
414 |
<title>MIME (Multipurpose Internet Mail Extensions) |
415 |
Part One: Mechanisms for Specifying and Describing the Format |
416 |
of Internet Message Bodies</title> |
417 |
<ja:title xml:lang="ja">MIME ($BB?L\E*(B Internet $B%a%$%k3HD%(B) |
418 |
$BBh(B1$BIt(B: Internet $B%a%C%;!<%8K\J8$N=q<0$N;XDj@bL@5!9=(B</ja:title> |
419 |
<author initials="N." surname="Borenstein" fullname="Nathaniel S. Borenstein"> |
420 |
<organization>Bellcore</organization> |
421 |
</author> |
422 |
<author initials="N." surname="Freed" fullname="Ned Freed"> |
423 |
<organization abbrev="Innosoft">Innosoft International, |
424 |
Inc.</organization> |
425 |
</author> |
426 |
<date month="September" year="1993" /> |
427 |
</front> |
428 |
<seriesInfo name="RFC" value="1521" /> |
429 |
</reference> |
430 |
</references> |
431 |
</back> |
432 |
<ja:back xml:lang="ja"> |
433 |
<section title="Content-ID $B$N;XDj(B"> |
434 |
<t>MIME <xref target="MIME" /> $B$N5,Dj$H>H$i$79g$o$;$k$H!"(B |
435 |
<eref target="http://suika.fam.cx/~wakaba/-temp/wiki/wiki?message%2Fexternal%2Dbody%C7%DE%C2%CE%B7%BF">$B$I$3$K(B |
436 |
<h:code>Content-ID:</h:code> $BMs$r=q$/$N$+$K$D$$$F5?Ld$,$"$j$^$9(B</eref>$B!#(B</t> |
437 |
</section> |
438 |
<section title="IANA $B$K4X$7$F(B"> |
439 |
<t><eref target="http://www.iana.org/assignments/access-types">IANA |
440 |
$BEPO?Jm(B</eref>$B$K$O!"(B access-type "Content-ID" $B$OEPO?$5$l$F$$$^$;$s!#(B |
441 |
(2002$BG/(B7$B7n8=:_(B)</t> |
442 |
</section> |
443 |
</ja:back> |
444 |
</rfc> |