| 1 |
<?xml version="1.0" encoding="iso-2022-jp"?> |
| 2 |
<!DOCTYPE rfc SYSTEM "rfc2629.dtd" [ |
| 3 |
<!ENTITY rfc.number "1428"> |
| 4 |
<!ENTITY ja.agent "$BBeM}<T(B"> |
| 5 |
<!ENTITY ja.body "$BK\BN(B"> |
| 6 |
<!ENTITY ja.downgrade "$B3J2<$2(B"> |
| 7 |
<!ENTITY ja.outofband "out of band"> |
| 8 |
<!ENTITY ja.protocol "$B%W%m%H%3%k(B"> |
| 9 |
<!ENTITY ja.upgrade "$B3J>e$2(B"> |
| 10 |
<!ENTITY ja.UserAgent "$BMxMQ<TBeM}<T(B"> |
| 11 |
]> |
| 12 |
<?rfc-translation show-rfc-header-category="no" ?> |
| 13 |
<rfc number="1428" category="info" |
| 14 |
xmlns:myns="mailto:julian.reschke@greenbytes.de?subject=rcf2629.xslt" |
| 15 |
xmlns:ja="http://suika.fam.cx/~wakaba/lang/rfc/translation/" |
| 16 |
xmlns:h="http://www.w3.org/1999/xhtml"> |
| 17 |
<front> |
| 18 |
<title abbrev="Transition to 8bit-SMTP/MIME">Transition of Internet Mail from Just-Send-8 to 8bit-SMTP/MIME</title> |
| 19 |
<ja:title xml:lang="ja" abbrev="8$B%S%C%H(B SMTP/MIME $B$X$NJQ49(B">Internet $B%a%$%k$N(B8$B$^$s$^Aw$j$+$i(B8$B%S%C%H(B SMTP/MIME $B$X$NJQ49(B</ja:title> |
| 20 |
<author initials="G." surname="Vaudreuil" fullname="Greg Vaudreuil"> |
| 21 |
<organization abbrev="CNRI">Corporation for National Research Initiatives</organization> |
| 22 |
<address> |
| 23 |
<postal><street>1895 Preston White Drive, Suite 100</street> |
| 24 |
<city>Reston</city><!--, --><region>VA</region> <code>22091</code> |
| 25 |
<country ja:text="USA">US</country> |
| 26 |
</postal> |
| 27 |
<phone ja:text="(703) 620-8990">+1 703 620 8990</phone> |
| 28 |
<email>GVaudre@CNRI.Reston.VA.US</email> |
| 29 |
</address> |
| 30 |
</author> |
| 31 |
<date month="February" year="1993" /> |
| 32 |
<workgroup>SMTP Extensions Working Group</workgroup> |
| 33 |
<abstract> |
| 34 |
<t> |
| 35 |
<ja:pair> |
| 36 |
<ja:l xml:lang="en"> |
| 37 |
Protocols for extending SMTP to pass 8bit characters have been |
| 38 |
defined <xref target="refs.RFC1425" /> <xref target="refs.RFC1426" />. |
| 39 |
These protocols require that messages transported by |
| 40 |
the extended SMTP are to be encoded in MIME |
| 41 |
<xref target="refs.RFC1341" /> <xref target="refs.RFC1342" />. |
| 42 |
Before work began on these protocols, several SMTP implementations |
| 43 |
adopted ad-hoc mechanisms for sending 8bit data. It is desirable |
| 44 |
for the extended SMTP environment and these ad hoc mechanisms |
| 45 |
interoperate. This document outlines the problems in this |
| 46 |
environment and an approach to minimizing the cost of transition |
| 47 |
from current usage of non-MIME 8bit messages to MIME. |
| 48 |
</ja:l> |
| 49 |
<ja:l xml:lang="ja"> |
| 50 |
8$B%S%C%HJ8;z$rDL2a$5$;$k$h$&$K(B SMTP |
| 51 |
$B$r3HD%$9$k(B&ja.protocol;$B$,Dj5A$5$l$F$$$^$9(B |
| 52 |
<xref target="refs.RFC1425" /> <xref target="refs.RFC1426" />$B!#(B |
| 53 |
$B$3$l$i$N(B&ja.protocol;$B$G$O!"3HD%(B SMTP $B$GE>Aw$5$l$k%a%C%;!<%8$,(B |
| 54 |
MIME <xref target="refs.RFC1341" /> <xref target="refs.RFC1342" /> |
| 55 |
$B$GId9f2=$5$l$F$$$k$3$H$,I,MW$G$9!#$3$l$i$N(B&ja.protocol;$B$N:n6H$,;O$^$k0JA0!"4v$D$+$N(B |
| 56 |
SMTP $B<BAu$O(B8$B%S%C%H!&%G!<%?$rAw?.$9$k$?$a$NFC@_5!9=$r:NMQ$7$F$$$^$7$?!#3HD%(B |
| 57 |
SMTP $B4D6-$H$3$NMM$JFC@_5!9=$,6(D4$7$FF/$/$3$H$,K>$^$7$$$G$9!#$3$NJ8=q$O!"$3$l$i$N4D6-$G$NLdBj$H!"Hs(B MIME 8$B%S%C%H!&%a%C%;!<%8$N8=:_$NMxMQK!$+$i(B |
| 58 |
MIME $B$X$NJQ49$N7PHq$N:G>.2=$NJ}K!$K$D$$$F35@b$7$^$9!#(B |
| 59 |
</ja:l> |
| 60 |
</ja:pair> |
| 61 |
</t> |
| 62 |
</abstract> |
| 63 |
</front> |
| 64 |
<ja:front> |
| 65 |
<author fullname="$B$o$+$P(B" ja:id="wakaba"> |
| 66 |
<address> |
| 67 |
<email>w@suika.fam.cx</email> |
| 68 |
<uri>http://suika.fam.cx/~wakaba/</uri> |
| 69 |
</address> |
| 70 |
</author> |
| 71 |
<ja:copyright> |
| 72 |
<ja:item>Copyright © $B$o$+$P(B (2002)$B!#A48"J]N1!#(B</ja:item> |
| 73 |
</ja:copyright> |
| 74 |
<ja:change> |
| 75 |
<ja:item year="2002" month="05" day="08"><author ja:ref="wakaba" /> |
| 76 |
<t><ja:link type="rfc" number="2629" /> $B$G%^!<%/IU$1!#(B</t> |
| 77 |
<t>$BK]Lu40N;!#(B</t> |
| 78 |
</ja:item> |
| 79 |
</ja:change><!-- $Date: 2002/05/03 07:29:27 $ --> |
| 80 |
<h:style xml:space="preserve" type="text/css"> |
| 81 |
.rfc-t-artwork table |
| 82 |
{margin-left: 15%; margin-right: 15%; |
| 83 |
border-style: none} |
| 84 |
.rfc-t-artwork table thead th |
| 85 |
{border-left: thin ActiveBorder solid; |
| 86 |
padding: 0.2em; text-align: left} |
| 87 |
.rfc-t-artwork table thead th.css-first-child |
| 88 |
{border-left-style: none} |
| 89 |
.rfc-t-artwork table tbody th |
| 90 |
{border-top: thin ActiveBorder solid; |
| 91 |
padding: 0.2em; text-align: right; vertical-align: middle} |
| 92 |
.rfc-t-artwork table tbody td |
| 93 |
{border-top: thin ActiveBorder solid; |
| 94 |
border-left: thin ActiveBorder solid; |
| 95 |
padding: 0.2em; text-align: center; vertical-align: middle} |
| 96 |
</h:style> |
| 97 |
</ja:front> |
| 98 |
<middle> |
| 99 |
|
| 100 |
<section title="Terminology" ja:title-ja="$BMQ8l(B"><!-- 1. --> |
| 101 |
<t> |
| 102 |
<ja:pair> |
| 103 |
<ja:l xml:lang="en"> |
| 104 |
RFC 821 defines a 7bit transport. A transport agent which does not |
| 105 |
clear the high order bit upon receipt of octets with this bit set in |
| 106 |
SMTP messages is called 8 bit transparent in this document. An |
| 107 |
implementation of the general SMTP Extensions document |
| 108 |
<xref target="refs.RFC1425" /> and the |
| 109 |
8bit extensions protocol <xref target="refs.RFC1426" /> |
| 110 |
which passes MIME messages using all 8 |
| 111 |
bits of an octet is called 8bit ESMTP. An implementation of extended |
| 112 |
SMTP which does not accept 8bit characters is called 7bit ESMTP. A |
| 113 |
gateway is defined to be a transport agent with User Agent authority |
| 114 |
to alter or convert the content of a message. |
| 115 |
</ja:l> |
| 116 |
<ja:l xml:lang="ja"> |
| 117 |
<ja:link type="rfc" number="821" /> $B$O(B8$B%S%C%HE>Aw$rDj5A$7$F$$$^$9!#(B |
| 118 |
SMTP $B%a%C%;!<%8Cf$N<u$1<h$C$?%*%/%F%C%H$N:G>e0L%S%C%H$r!"$3$N%S%C%H$KCM$r@_Dj$9$k$3$H$G>C5n$7$J$$E>Aw(B&ja.agent;$B$r!"$3$NJ8=q$G$O(B8$B%S%C%HF)2a$H8F$S$^$9!#0lHL(B |
| 119 |
SMTP $B3HD%J8=q(B <xref target="refs.RFC1425" /> $B5Z$S(B |
| 120 |
MIME $B%a%C%;!<%8$r%*%/%F%C%H$N(B8$B%S%C%HA4$F$r;H$C$FEO$9(B8$B%S%C%H3HD%(B&ja.protocol; |
| 121 |
<xref target="refs.RFC1426" /> $B$N<BAu$r(B8$B%S%C%H(B |
| 122 |
ESMTP $B$H8F$S$^$9!#(B8$B%S%C%HJ8;z$r<u$1IU$1$J$$3HD%(B SMTP |
| 123 |
$B$N<BAu$r(B7$B%S%C%H(B ESMTP $B$H8F$S$^$9!#4XLg(B (gateway) |
| 124 |
$B$O!"%a%C%;!<%8$NFbMF$rJQ$($k!&JQ49$9$k(B&ja.UserAgent;$BEv6I$D$-E>Aw(B&ja.agent;$B$HDj5A$7$^$9!#(B |
| 125 |
</ja:l> |
| 126 |
</ja:pair> |
| 127 |
</t> |
| 128 |
</section> |
| 129 |
|
| 130 |
<section title="The Problem" ja:title-ja="$BLdBjE@(B"><!-- 2. --> |
| 131 |
<t> |
| 132 |
<ja:pair> |
| 133 |
<ja:l xml:lang="en"> |
| 134 |
SMTP as defined in RFC 821 limits the sending of Internet Mail to |
| 135 |
US-ASCII <xref target="refs.ASCII" /> characters. As the Internet |
| 136 |
has grown to include non-English correspondents, the need to |
| 137 |
communicate with character sets |
| 138 |
other than US-ASCII has prompted many vendors and users to extend |
| 139 |
SMTP or RFC 822 to use non-ASCII character sets. Common approaches |
| 140 |
are to send 7 bit national variant ISO 646 character sets over |
| 141 |
current RFC822/SMTP, to extend SMTP and RFC822 to use 8bit ISO 8859 |
| 142 |
character sets, and to use proprietary PC character sets. |
| 143 |
</ja:l> |
| 144 |
<ja:l xml:lang="ja"> |
| 145 |
<ja:link type="rfc" number="821" /> $B$GDj5A$5$l$?(B SMTP $B$O(B |
| 146 |
Internet $B%a%$%k$NAw?.$r(B US-ASCII <xref target="refs.ASCII" /> |
| 147 |
$BJ8;z$K@)8B$7$F$$$^$7$?!#(B Internet |
| 148 |
$B$,Hs1Q8lJ8DL<T$r4^$`MM$K@.D9$9$k$K=>$$!"Hs(B US-ASCII |
| 149 |
$BJ8;z=89g$K$h$k0U;WABDL$NI,MW@-$+$i!"B?$/$N@=B$<T$dMxMQ<T$,(B SMTP |
| 150 |
$B$d(B <ja:link type="rfc" number="822" /> $B$rHs(B ASCII |
| 151 |
$BJ8;z=89g$r;HMQ$9$k$h$&$K3HD%$7$h$&$H$7$^$7$?!#$=$N6&DL$N<jCJ$K$O(B7$B%S%C%H$N9q2HHG(B |
| 152 |
ISO 646 $BJ8;z=89g$r8=9T$N(B RFC 822/SMTP $B$GAw?.$9$k(B, SMTP $B$H(B |
| 153 |
RFC822 $B$r(B8$B%S%C%H$N(B ISO 8859 $BJ8;z=89g$r;HMQ$9$k$h$&$K3HD%$9$k(B, |
| 154 |
$BFH@j(B PC $BJ8;z=89g$r;HMQ$9$k(B, $B$,$"$j$^$9!#(B |
| 155 |
</ja:l> |
| 156 |
</ja:pair> |
| 157 |
</t> |
| 158 |
|
| 159 |
<t> |
| 160 |
<ja:pair> |
| 161 |
<ja:l xml:lang="en"> |
| 162 |
A third approach is used for Japanese mail. Japanese characters are |
| 163 |
represented by pairs of octets with the high order bit cleared. |
| 164 |
Switching between 14 bit character sets and 7 bit character sets is |
| 165 |
indicated within the message by ISO 2022 escape sequences. |
| 166 |
</ja:l> |
| 167 |
<ja:l xml:lang="ja"> |
| 168 |
$B;0HVL\$NJ}K!$OF|K\8l%a%$%k$K;H$o$l$F$$$^$9!#F|K\8lJ8;z$O:G>e0L%S%C%H$,>C5n$5$l$?%*%/%F%C%H$NAH9g$;$GI=8=$7$^$9!#(B14$B%S%C%HJ8;z=89g$H(B7$B%S%C%HJ8;z=89g$O%a%C%;!<%8Cf$G$O(B |
| 169 |
ISO 2022 $B%(%9%1!<%WNs$G@Z$jBX$($^$9!#(B |
| 170 |
</ja:l> |
| 171 |
</ja:pair> |
| 172 |
</t> |
| 173 |
<ja:note> |
| 174 |
<t>$B;0HVL\$NJ}K!$H$O!VFH@j(B PC $BJ8;z=89g$N;HMQ!W$G$9$+$i!"$3$N@bL@$G$O9gCW$7$^$;$s!#$*$=$i$/!";0HVL\$NJ}K!$O!"!V0lHVL\!&FsHVL\0J30$NJ}K!!W$H$G$b$7$?$+$C$?$N$G$7$g$&!#(B</t> |
| 175 |
</ja:note> |
| 176 |
|
| 177 |
<t> |
| 178 |
<ja:pair> |
| 179 |
<ja:l xml:lang="en"> |
| 180 |
So long as these implementations can communicate without intermediate |
| 181 |
transformations and have a loose private agreement on the use of a |
| 182 |
specific character set without tagging, basic mail service can be |
| 183 |
provided. |
| 184 |
</ja:l> |
| 185 |
<ja:l xml:lang="ja"> |
| 186 |
$B$3$l$i$N<BAu$OESCf7PO)$G$NJQ7AL5$7$KDL?.=PMh!"FCDjJ8;z=89g$N;%L5$7$G$N;HMQ$N4K$$;dE*$J9g0U$,$"$k$N$G!"4pK\E*$J%a%$%k!&%5!<%S%9$,Ds6!=PMh$^$9!#(B |
| 187 |
</ja:l> |
| 188 |
</ja:pair> |
| 189 |
</t> |
| 190 |
|
| 191 |
<t> |
| 192 |
<ja:pair> |
| 193 |
<ja:l xml:lang="en"> |
| 194 |
In the transition to the negotiated 8bit ESMTP/MIME environment, it |
| 195 |
is important that mail sent by a currently non-conforming user can be |
| 196 |
read by another non-conforming user. This existing functionality is |
| 197 |
reduced by conversion from 8bit text to text encoded in unreadable |
| 198 |
Base-64 or "garbled" text encoded in quoted printable. |
| 199 |
</ja:l> |
| 200 |
<ja:l xml:lang="ja"> |
| 201 |
$B@^>W(B8$B%S%C%H(B ESMTP/MIME |
| 202 |
$B4D6-$X$NJQ49$G!"8=:_HsE,9g$NMxMQ<T$,Aw?.$7$?%a%$%k$OB>$NHsE,9g$NMxMQ<T$,FI$`$3$H$,=PMh$k$3$H$O=EMW$G$9!#$3$N4{B85!G=@-$O!"(B8$B%S%C%HJ8$+$iIT2DFI(B |
| 203 |
Base-64 $B$GId9f2=$5$l$?J8$d(B quoted printable |
| 204 |
$B$GId9f2=$5$l$?!VJ8;z2=$1$7$?!WJ8$KJQ49$9$k$3$H$G8:>/$7$^$9!#(B |
| 205 |
</ja:l> |
| 206 |
</ja:pair> |
| 207 |
</t> |
| 208 |
|
| 209 |
<t> |
| 210 |
<ja:pair> |
| 211 |
<ja:l xml:lang="en"> |
| 212 |
There are several interesting non-interoperable cases that currently |
| 213 |
exist in non US-ASCII mail and several new ones likely to emerge in a |
| 214 |
transition to 8bit/MIME. Below is a listing of the |
| 215 |
transition-to-mime cases. Only solutions to <xref target="s2.i4" /> |
| 216 |
in the context of a translating gateway are discussed in this memo. |
| 217 |
</ja:l> |
| 218 |
<ja:l xml:lang="ja"> |
| 219 |
$B8=:_Hs(B US-ASCII $B%a%$%k$KB8:_$9$k6=L#?<$$Aj8_DL?.IT2D$J;vNc!"$"$k$$$O(B8$B%S%C%H(B/MIME |
| 220 |
$B$X$NJQ49$GIb>e$7$=$&$J?7$7$$;vNc$,4v$D$+$"$j$^$9!#2<$K5s$2$k$N$O!"(B |
| 221 |
MIME $B$X$NJQ49$N;vNc$G$9!#JQ494XLg$K$*$1$k(B <xref target="s2.i4" /> |
| 222 |
$B$N2r7h:v$N$_$r$3$N%a%b$G$O<h$j>e$2$^$9!#(B |
| 223 |
</ja:l> |
| 224 |
</ja:pair> |
| 225 |
</t> |
| 226 |
|
| 227 |
<figure> |
| 228 |
<ja:pair> |
| 229 |
<ja:l xml:lang="en"> |
| 230 |
<ja:artwork> |
| 231 |
<artwork> |
| 232 |
\ Receiver |
| 233 |
\ 7bit 8bit MIME/ |
| 234 |
Sender \| only | transparent | ESMTP |
| 235 |
---------------------------------------- |
| 236 |
7bit only | (1) | (1) | (1) |
| 237 |
---------------------------------------- |
| 238 |
8bit transparent | (2) | (3) | (4) |
| 239 |
---------------------------------------- |
| 240 |
MIME/ESMTP | (5) | (5) | (6) |
| 241 |
</artwork> |
| 242 |
<h:table> |
| 243 |
<h:thead> |
| 244 |
<h:tr> |
| 245 |
<h:th class="css-first-child">Sender\Receiver</h:th> |
| 246 |
<h:th>7bit only</h:th> |
| 247 |
<h:th>8bit transparent</h:th><h:th>MIME/ESMTP</h:th> |
| 248 |
</h:tr> |
| 249 |
</h:thead> |
| 250 |
<h:tbody> |
| 251 |
<h:tr> |
| 252 |
<h:th>7bit only</h:th> |
| 253 |
<h:td><xref target="s2.i1" /></h:td> |
| 254 |
<h:td><xref target="s2.i1" /></h:td> |
| 255 |
<h:td><xref target="s2.i1" /></h:td> |
| 256 |
</h:tr> |
| 257 |
<h:tr> |
| 258 |
<h:th>8bit transparent</h:th> |
| 259 |
<h:td><xref target="s2.i2" /></h:td> |
| 260 |
<h:td><xref target="s2.i3" /></h:td> |
| 261 |
<h:td><xref target="s2.i4" /></h:td> |
| 262 |
</h:tr> |
| 263 |
<h:tr> |
| 264 |
<h:th>MIME/ESMTP</h:th> |
| 265 |
<h:td><xref target="s2.i5" /></h:td> |
| 266 |
<h:td><xref target="s2.i5" /></h:td> |
| 267 |
<h:td><xref target="s2.i6" /></h:td> |
| 268 |
</h:tr> |
| 269 |
</h:tbody> |
| 270 |
</h:table> |
| 271 |
</ja:artwork> |
| 272 |
</ja:l> |
| 273 |
<ja:l xml:lang="ja"> |
| 274 |
<ja:artwork> |
| 275 |
<h:table> |
| 276 |
<h:thead> |
| 277 |
<h:tr> |
| 278 |
<h:th class="css-first-child">$BAw?.<T(B\$B<u?.<T(B</h:th> |
| 279 |
<h:th>7$B%S%C%H$N$_(B</h:th> |
| 280 |
<h:th>8$B%S%C%HF)2a(B</h:th><h:th>MIME/ESMTP</h:th> |
| 281 |
</h:tr> |
| 282 |
</h:thead> |
| 283 |
<h:tbody> |
| 284 |
<h:tr> |
| 285 |
<h:th>7$B%S%C%H$N$_(B</h:th> |
| 286 |
<h:td><xref target="s2.i1" /></h:td> |
| 287 |
<h:td><xref target="s2.i1" /></h:td> |
| 288 |
<h:td><xref target="s2.i1" /></h:td> |
| 289 |
</h:tr> |
| 290 |
<h:tr> |
| 291 |
<h:th>8$B%S%C%HF)2a(B</h:th> |
| 292 |
<h:td><xref target="s2.i2" /></h:td> |
| 293 |
<h:td><xref target="s2.i3" /></h:td> |
| 294 |
<h:td><xref target="s2.i4" /></h:td> |
| 295 |
</h:tr> |
| 296 |
<h:tr> |
| 297 |
<h:th>MIME/ESMTP</h:th> |
| 298 |
<h:td><xref target="s2.i5" /></h:td> |
| 299 |
<h:td><xref target="s2.i5" /></h:td> |
| 300 |
<h:td><xref target="s2.i6" /></h:td> |
| 301 |
</h:tr> |
| 302 |
</h:tbody> |
| 303 |
</h:table> |
| 304 |
</ja:artwork> |
| 305 |
</ja:l> |
| 306 |
</ja:pair> |
| 307 |
</figure> |
| 308 |
|
| 309 |
<list style="hanging"> |
| 310 |
<t hangText="(1)" ja:anchor="s2.i1"> |
| 311 |
<ja:pair> |
| 312 |
<ja:l xml:lang="en">7Bit non-MIME sender to 7bit, MIME, or |
| 313 |
8bit transparent receiver</ja:l> |
| 314 |
<ja:l xml:lang="ja">7$B%S%C%HHs(B MIME $BAw?.<T$+$i(B7$B%S%C%H$^$?$O(B |
| 315 |
MIME, 8$B%S%C%HF)2a<u?.<T$X(B</ja:l> |
| 316 |
</ja:pair> |
| 317 |
<vspace breakLines="1" /> |
| 318 |
<ja:pair> |
| 319 |
<ja:l xml:lang="en"> |
| 320 |
This will continue to work unchanged with nationally varient ISO |
| 321 |
646 or ISO 2022 character set shifting if an external "out of |
| 322 |
band" agreement exists between the sender and the receiver. A |
| 323 |
7bit to 8bit/ESMTP gateway need not alter the content of this |
| 324 |
message. |
| 325 |
</ja:l> |
| 326 |
<ja:l xml:lang="ja"> |
| 327 |
ISO 646 $B9q2HHG$d(B ISO 2022 $BJ8;z=89gE>0\$r!"30It!V(B&ja.outofband;$B!W9g0U$,Aw<u?.<T4V$GB8:_$9$k>l9g$OJQ99L5$/1?MQ$7B3$1$^$9!#(B7$B%S%C%H$+$i(B8$B%S%C%H(B/SMTP |
| 328 |
$B$X$N4XLg$O$3$N%a%C%;!<%8$NFbMF$rJQ$($kI,MW$O$"$j$^$;$s!#(B |
| 329 |
</ja:l> |
| 330 |
</ja:pair> |
| 331 |
</t> |
| 332 |
<ja:note> |
| 333 |
<t>Jargon File $B$K$O!"(B $B!V(Bout of band$B!W(B = |
| 334 |
<h:q title="Jargon File $B$+$i!V(Bout of band$B!W(B" xml:lang="en">sometimes |
| 335 |
used to describe what communications people call $B!F(Bshift characters$B!G(B, |
| 336 |
such as the <h:code>ESC</h:code> that leads control sequences for |
| 337 |
many terminals</h:q> $B$H=q$+$l$F$$$^$9!#(B</t> |
| 338 |
</ja:note> |
| 339 |
|
| 340 |
<t hangText="(2)" ja:anchor="s2.i2"> |
| 341 |
<ja:pair> |
| 342 |
<ja:l xml:lang="en">8bit sender to 7bit non-MIME receiver</ja:l> |
| 343 |
<ja:l xml:lang="ja">8$B%S%C%HAw?.<T$+$i(B7$B%S%C%HHs(B MIME $B<u?.<T$X(B</ja:l> |
| 344 |
</ja:pair> |
| 345 |
<vspace breakLines="1" /> |
| 346 |
<ja:pair> |
| 347 |
<ja:l xml:lang="en"> |
| 348 |
The receiver will receive bit-stripped mail which results in the |
| 349 |
mis-interpretation of the data and the wrong character being |
| 350 |
displayed or printed. Mail sent using languages where most |
| 351 |
characters are in the US-ASCII subset of ISO 8859 may be somewhat |
| 352 |
readable. |
| 353 |
</ja:l> |
| 354 |
<ja:l xml:lang="ja"> |
| 355 |
$B<u?.<T$O!"%G!<%?$N8m2r<a$N7k2L$?$k%S%C%HMn$A%a%$%k$r<u$1<h$j!"4V0c$C$?J8;z$,I=<(!&0u:~$5$l$k$3$H$K$J$k$G$7$g$&!#$[$H$s$I$NJ8;z$,(B |
| 356 |
ISO 8859 $B$N(B US-ASCII $BItJ,=89gCf$K$"$k8@8l$r;H$C$FAw$i$l$?%a%$%k$O$=$l$J$j$KFI$a$k$+$b$7$l$^$;$s!#(B |
| 357 |
</ja:l> |
| 358 |
</ja:pair> |
| 359 |
</t> |
| 360 |
|
| 361 |
<t hangText="(3)" ja:anchor="s2.i3"> |
| 362 |
<ja:pair> |
| 363 |
<ja:l xml:lang="en">8bit transparent sender to 8bit transparent receiver</ja:l> |
| 364 |
<ja:l xml:lang="ja">8$B%S%C%HF)2aAw?.<T$+$i(B8$B%S%C%HF)2a<u?.<T$X(B</ja:l> |
| 365 |
</ja:pair> |
| 366 |
<vspace breakLines="1" /> |
| 367 |
<ja:pair> |
| 368 |
<ja:l xml:lang="en"> |
| 369 |
Will work if an external agreement "out of band" to use a |
| 370 |
particular character set without tagging exists between the sender |
| 371 |
and the receiver. |
| 372 |
</ja:l> |
| 373 |
<ja:l xml:lang="ja"> |
| 374 |
$BFCDjJ8;z=89g$r;%L5$7$G;HMQ$9$k30It9g0U!V(B&ja.outofband;$B!W$,Aw<u?.4V$KB8:_$9$k>l9g$O$&$^$/F/$/$G$7$g$&!#(B |
| 375 |
</ja:l> |
| 376 |
</ja:pair> |
| 377 |
</t> |
| 378 |
|
| 379 |
<t hangText="(4)" ja:anchor="s2.i4"> |
| 380 |
<ja:pair> |
| 381 |
<ja:l xml:lang="en">8bit transparent sender to MIME/ESMTP conformant receiver</ja:l> |
| 382 |
<ja:l xml:lang="ja">8$B%S%C%HF)2aAw?.<T$+$i(B MIME/ESMTP $BE,9g<u?.<T$X(B</ja:l> |
| 383 |
</ja:pair> |
| 384 |
<vspace breakLines="1" /> |
| 385 |
<ja:pair> |
| 386 |
<ja:l xml:lang="en"> |
| 387 |
Will work if a reasonable upgrade path is provided via gateways, |
| 388 |
the indicated character set tag inserted by the gateway is correct |
| 389 |
and the receiver supports the character set chosen by the sender. |
| 390 |
This case is the focus of this memo. |
| 391 |
</ja:l> |
| 392 |
<ja:l xml:lang="ja"> |
| 393 |
$BJ,JL$"$k3J>e$27PO)$,4XLg7PM3$GDs6!$5$l$F$$$F!"4XLg$,A^F~$9$kJ8;z=89g;%$,@5$7$/$F!"<u?.<T$,Aw?.<T$NA*$s$@J8;z=89g$KBP1~$7$F$$$l$P!"$&$^$/F/$-$^$7$g$&!#$3$N>l9g$,$3$N%a%b$N>GE@$G$9!#(B |
| 394 |
</ja:l> |
| 395 |
</ja:pair> |
| 396 |
</t> |
| 397 |
|
| 398 |
<t hangText="(5)" ja:anchor="s2.i5"> |
| 399 |
<ja:pair> |
| 400 |
<ja:l xml:lang="en">MIME/ESMTP sender to non-MIME 7bit receiver</ja:l> |
| 401 |
<ja:l xml:lang="ja">MIME/ESMTP $BAw?.<T$+$iHs(B MIME 7$B%S%C%H<u?.<T$X(B</ja:l> |
| 402 |
</ja:pair> |
| 403 |
<vspace breakLines="1" /> |
| 404 |
<ja:pair> |
| 405 |
<ja:l xml:lang="en"> |
| 406 |
Because the ESMTP/MIME sender cannot know if the receiver will |
| 407 |
understand 8bits, the sender will encode the text into base-64 or |
| 408 |
quoted-printable which may be considered "garbled" by the |
| 409 |
receiver. To provide a useful downgrade path the gateway must |
| 410 |
have some knowledge about the capabilities of the receiver. When |
| 411 |
the character set can be clearly identified, techniques like the |
| 412 |
menmonic MNEM encoding described in RFC 1345 may be helpful in |
| 413 |
this case. |
| 414 |
</ja:l> |
| 415 |
<ja:l xml:lang="ja"> |
| 416 |
ESMTP/MIME $BAw?.<T$O<u?.<T$,(B8$B%S%C%H$rM}2r$9$k$+$I$&$+CN$jF@$J$$$N$G!"Aw?.<T$OJ8$r(B |
| 417 |
base-64 $B$+<u?.<T$K!VJ8;z2=$1$7$?!W$H;W$o$l$k$+$b$7$l$J$$(B |
| 418 |
quoted-printable $B$GId9f2=$9$k$G$7$g$&!#M-MQ$J3J2<$27PO)$rDs6!$9$k$K$O4XLg$O<u?.<T$NM}2rG=NO$K$D$$$F$NCN<1$rM-$9$kI,MW$,$"$j$^$9!#J8;z=89g$,L@3N$K<1JL=PMh$k;~$O!"(B |
| 419 |
<ja:link type="rfc" number="1345" /> $B$G@bL@$5$l$F$$$k5-K!(B MNEM |
| 420 |
$BId9f2=$NMM$J<jK!$,$3$N>l9g$K$OM-MQ$+$b$7$l$^$;$s!#(B |
| 421 |
</ja:l> |
| 422 |
</ja:pair> |
| 423 |
</t> |
| 424 |
|
| 425 |
<t hangText="(6)" ja:anchor="s2.i6"> |
| 426 |
<ja:pair> |
| 427 |
<ja:l xml:lang="en">MIME/ESMTP sender to MIME/ESMTP receiver</ja:l> |
| 428 |
<ja:l xml:lang="ja">MIME/ESMTP $BAw?.<T$+$i(B MIME/ESMTP $B<u?.<T$X(B</ja:l> |
| 429 |
</ja:pair> |
| 430 |
<vspace breakLines="1" /> |
| 431 |
<ja:pair> |
| 432 |
<ja:l xml:lang="en"> |
| 433 |
Interoperability will be attained provided the receiver supports |
| 434 |
the character set chosen by the sender. |
| 435 |
</ja:l> |
| 436 |
<ja:l xml:lang="ja">$BAj8_DL?.@-$OAw?.<T$,A*Br$7$?J8;z=89g$K<u?.<T$,BP1~$9$k$3$H$K$h$jK~$?$5$l$^$9!#(B</ja:l> |
| 437 |
</ja:pair> |
| 438 |
</t> |
| 439 |
</list> |
| 440 |
</section> |
| 441 |
|
| 442 |
<section title="Upgrade Path from 8bit Transparent to ESMTP/MIME" |
| 443 |
ja:title-ja="8$B%S%C%HF)2a$+$i(B ESMTP/MIME $B$X$N(B&ja.upgrade;$B7PO)(B"><!-- 3. --> |
| 444 |
|
| 445 |
<t> |
| 446 |
<ja:pair> |
| 447 |
<ja:l xml:lang="en"> |
| 448 |
A gateway which has been upgraded to support Extended SMTP may |
| 449 |
upgrade an 8bit message received to MIME. This is consistent with |
| 450 |
the requirement that all 8bit mail sent by ESMTP be encoded in MIME. |
| 451 |
The upgrade should be done using the best available information. |
| 452 |
</ja:l> |
| 453 |
<ja:l xml:lang="ja"> |
| 454 |
$B3HD%(B SMTP $B$KBP1~$9$k$h$&(B&ja.upgrade;$B$9$k4XLg$O!"<u?.$7$?(B8$B%S%C%H!&%a%C%;!<%8$r(B |
| 455 |
MIME $B$K(B&ja.upgrade;$B$7$F9=$$$^$;$s!#$3$l$O(B ESMTP $B$GAw?.$5$l$k(B8$B%S%C%H!&%a%$%k$OA4$F(B |
| 456 |
MIME $B$GId9f2=$5$l$F$$$J$1$l$P$J$i$J$$$H$$$&MW7o$rK~$?$7$^$9!#(B&ja.upgrade;$B$O0lHVMxMQ2DG=$J>pJs$r;H$C$F9T$&$Y$-$G$9!#(B |
| 457 |
</ja:l> |
| 458 |
</ja:pair> |
| 459 |
</t> |
| 460 |
|
| 461 |
<t> |
| 462 |
<ja:pair> |
| 463 |
<ja:l xml:lang="en"> |
| 464 |
A site may "upgrade" to MIME en-masse by implementing MIME conversion |
| 465 |
for all messages leaving the site. For text messages, the body can |
| 466 |
be converted by adding a MIME-version header and a Content-Type: |
| 467 |
Text/Plain with the character set in use in the site, provided the |
| 468 |
site uses a single character set. |
| 469 |
</ja:l> |
| 470 |
<ja:l xml:lang="ja"> |
| 471 |
$B%5%$%H$O!"%5%$%H$rN%$l$kA4$F$N%a%C%;!<%8$r!"(B |
| 472 |
MIME $B$r<BAu$9$k$3$H$G$^$H$a$F(B MIME $B$K!V(B&ja.upgrade;$B!W$7$F$b9=$$$^$;$s!#%F%-%9%H!&%a%C%;!<%8$K$D$$$F$O!"(B&ja.body;$B$O(B |
| 473 |
MIME-version $BF,$H(B Content-Type: Text/Plain |
| 474 |
$B$K%5%$%HFb$G;H$o$l$F$$$kJ8;z=89g$r$D$1$k$3$H$G!"%5%$%H$,C10lJ8;z=89g$r;H$C$F$$$k>l9g$OJQ49=PMh$^$9!#(B |
| 475 |
</ja:l> |
| 476 |
</ja:pair> |
| 477 |
</t> |
| 478 |
|
| 479 |
<t> |
| 480 |
<ja:pair> |
| 481 |
<ja:l xml:lang="en"> |
| 482 |
An appropriate Content-Transfer-Encoding header line must be added to |
| 483 |
indicate any encoding that may be necessary. |
| 484 |
</ja:l> |
| 485 |
<ja:l xml:lang="ja"> |
| 486 |
$BE,@Z$J(B Content-Transfer-Encoding |
| 487 |
$BF,9T$r!"I,MW$+$b$7$l$J$$Id9f2=$r<($9$N$K2C$($J$1$l$P$J$j$^$;$s!#(B |
| 488 |
</ja:l> |
| 489 |
</ja:pair> |
| 490 |
</t> |
| 491 |
|
| 492 |
<!-- |
| 493 |
Example: |
| 494 |
--><ja:example xml:space="preserve"> |
| 495 |
MIME-Version: 1.0 |
| 496 |
Content-Type: Text/Plain; Charset = ISO-8859-1 |
| 497 |
Content-Transfer-Encoding: 8bit |
| 498 |
</ja:example> |
| 499 |
|
| 500 |
<t> |
| 501 |
<ja:pair> |
| 502 |
<ja:l xml:lang="en"> |
| 503 |
If no information about the character set in use is available, the |
| 504 |
gateway should upgrade the content by using the character set |
| 505 |
"unknown-8bit". The unknown-8bit value of the charset parameter |
| 506 |
indicates only that no reliable information about the character |
| 507 |
set(s) used in the message was available. |
| 508 |
</ja:l> |
| 509 |
<ja:l xml:lang="ja"> |
| 510 |
$B;HMQ$5$l$F$$$kJ8;z=89g$K$D$$$F$N>pJs$,L5$$>l9g$O!"4XLg$OFbMF$rJ8;z=89g(B |
| 511 |
"unknown-8bit" $B$r;H$C$F(B&ja.upgrade;$B$9$k$Y$-$G$9!#(B charset |
| 512 |
$B%Q%i%a!<%?!<$N(B unknown-8bit |
| 513 |
$BCM$O%a%C%;!<%8$K;H$o$l$F$$$kJ8;z=89g$K$D$$$F$N3N<B$J>pJs$rF@$k$3$H$,=PMh$J$+$C$?$3$H$N$_$r<($7$^$9!#(B |
| 514 |
</ja:l> |
| 515 |
</ja:pair> |
| 516 |
</t> |
| 517 |
|
| 518 |
<t> |
| 519 |
<ja:pair> |
| 520 |
<ja:l xml:lang="en"> |
| 521 |
If a message body has been upgraded to MIME, the RFC 822 headers |
| 522 |
containing non US-ASCII characters must be upgraded to conform with |
| 523 |
the header encoding rules of RFC1342. A gateway should recode all |
| 524 |
unstructered header fields as well as RFC 822 "comment"s and |
| 525 |
"phrase"s according to the rules of RFC 1342. There is no equivalent |
| 526 |
in RFC 1342 to the "8bit" Content-Transfer-Encoding value for message |
| 527 |
bodies so all 8bit header text must be transformed according to |
| 528 |
either the "B" or the "Q" encoding method. For ISO 8859 character |
| 529 |
sets, the "Q" encoding will generally result in somewhat readable |
| 530 |
headers. |
| 531 |
</ja:l> |
| 532 |
<ja:l xml:lang="ja"> |
| 533 |
$B%a%C%;!<%8(B&ja.body;$B$,(B MIME $B$K(B&ja.upgrade;$B$5$l$k>l9g!"Hs(B US-ASCII |
| 534 |
$BJ8;z$r4^$`(B <ja:link type="rfc" number="822" /> $BF,$O(B |
| 535 |
RFC1342 $B$NF,Id9f2=5,B'$KE,9g$9$k$h$&(B&ja.upgtade;$B$7$J$1$l$P$J$j$^$;$s!#4XLg$OA4$F$NHs9=B$2=F,NN0h$H(B |
| 536 |
RFC 822 "comment" $B$H(B "phrase" $B$r(B RFC 1342 |
| 537 |
$B$N5,B'$K=>$$:FId9f2=$9$k$Y$-$G$9!#%a%C%;!<%8(B&ja.body;$B$N(B "8bit" |
| 538 |
$BFbMFE>AwId9f2=CM$KAjEv$9$k$b$N$O(B RFC 1342 |
| 539 |
$B$K$OL5$$$N$G!"A4$F$N(B8$B%S%C%HF,J8$O(B "B" $BId9f2=J}<0$^$?$O(B "Q" |
| 540 |
$BId9f2=J}<0$GId9f2=$7$J$1$l$P$J$j$^$;$s!#(B ISO 8859 $BJ8;z=89g$K$O!"(B |
| 541 |
"Q" $BId9f2=$r;H$&$H!"DL>o$d$d2DFI$JF,$H$J$j$^$9!#(B |
| 542 |
</ja:l> |
| 543 |
</ja:pair> |
| 544 |
</t> |
| 545 |
|
| 546 |
<figure> |
| 547 |
<preamble> |
| 548 |
<ja:pair> |
| 549 |
<ja:l xml:lang="en"> |
| 550 |
Trace information should be added to the document with a convert |
| 551 |
clause: "rfc822-to-8bit", "rfc822-to-base-64" or "rfc822-to-quoted- |
| 552 |
printable" e.g., |
| 553 |
</ja:l> |
| 554 |
<ja:l xml:lang="ja"> |
| 555 |
$BDI@W>pJs$r<!$NNc$N$h$&$KJQ49(B (convert) $B>r9`(B "rfc822-to-8bit", |
| 556 |
"rfc822-to-base-64", "rfc822-to-quoted-printable" |
| 557 |
$B$D$-$GJ8=q$KDI2C$9$k$Y$-$G$9!#(B |
| 558 |
</ja:l> |
| 559 |
</ja:pair> |
| 560 |
</preamble> |
| 561 |
|
| 562 |
<artwork xml:space="preserve"> |
| 563 |
Received: from dbc.mtview.ca.us by dbc.mtview.ca.us |
| 564 |
convert rfc822-to-8bit; Tue, 01 Sep 1992 01:18:00 -0700 |
| 565 |
</artwork> |
| 566 |
</figure> |
| 567 |
</section> |
| 568 |
|
| 569 |
<section title="Appendix $B!=(B The $B!H(Bunknown-8bit$B!I(B Character Set" |
| 570 |
ja:title-ja="$BImB0=q(B $B!=(B $B!V(Bunknown-8bit$B!WJ8;z=89g(B" myns:unnumbered="yes"> |
| 571 |
|
| 572 |
<t> |
| 573 |
<ja:pair> |
| 574 |
<ja:l xml:lang="en"> |
| 575 |
This section defines a "charset" parameter, for use in a MIME |
| 576 |
Content-Type field. |
| 577 |
</ja:l> |
| 578 |
<ja:l xml:lang="ja"> |
| 579 |
$B$3$N@a$G$O(B MIME Content-Type $BNN0h$G;H$&(B "charset" |
| 580 |
$B%Q%i%a!<%?!<$rDj5A$7$^$9!#(B |
| 581 |
</ja:l> |
| 582 |
</ja:pair> |
| 583 |
</t> |
| 584 |
|
| 585 |
<t> |
| 586 |
<ja:pair> |
| 587 |
<ja:l xml:lang="en"> |
| 588 |
A special purpose character set called "unknown-8bit" is defined to |
| 589 |
be an unknown 8bit character set, encoded into a sequence of octets. |
| 590 |
It can be used as a label for any character set from any language, |
| 591 |
using any encoding. It must not be further defined. |
| 592 |
</ja:l> |
| 593 |
<ja:l xml:lang="ja"> |
| 594 |
"unknown-8bit" $B$H$$$&FC<lL\E*J8;z=89g$r!"%*%/%F%C%HNs$KId9f2=$5$l$?L$CN$N(B8$B%S%C%HJ8;z=89gMQ$KDj5A$7$^$9!#$3$l$O$$$+$J$k8@8l$G$$$+$J$kId9f2=$rMQ$$$k$$$+$J$kJ8;z=89g$K$b;%$H$7$F;H$&$3$H$,=PMh$^$9!#$3$l0J>e$ODj5A$7$^$;$s!#(B |
| 595 |
</ja:l> |
| 596 |
</ja:pair> |
| 597 |
</t> |
| 598 |
|
| 599 |
<t> |
| 600 |
<ja:pair> |
| 601 |
<ja:l xml:lang="en"> |
| 602 |
The use of this token in a "charset=" field of a message indicates |
| 603 |
that nothing is known about the character set used. This marker is |
| 604 |
intended for use by non-MIME to MIME gateways; specifically in those |
| 605 |
which translate from SMTP to 8bit ESMTP/MIME. |
| 606 |
</ja:l> |
| 607 |
<ja:l xml:lang="ja"> |
| 608 |
$B$3$N;z6g$r%a%C%;!<%8$N(B "charset=" |
| 609 |
$BNN0h$G;H$&$3$H$G!";H$o$l$F$$$kJ8;z=89g$K$D$$$FA4$/$b$C$FITL@$G$"$k$3$H$r<($7$^$9!#$3$N0u$OHs(B MIME $B$+$i(B MIME $B$X$N4XLg!"6qBNE*$K$O(B SMTP |
| 610 |
$B$+$i(B8$B%S%C%H(B ESMTP/MIME $B$KJQ49$9$k4XLg$G;H$&$3$H$r0U?^$7$F$$$^$9!#(B |
| 611 |
</ja:l> |
| 612 |
</ja:pair> |
| 613 |
</t> |
| 614 |
|
| 615 |
<t> |
| 616 |
<ja:pair> |
| 617 |
<ja:l xml:lang="en"> |
| 618 |
This character set is not intended to be used by mail composers. |
| 619 |
It is assumed that the mail composer knows the character set in |
| 620 |
use and will mark it with a character set value as specified in |
| 621 |
<xref target="refs.RFC1341" />, as amended by current Assigned |
| 622 |
Numbers documents <xref target="refs.STD2" />. |
| 623 |
</ja:l> |
| 624 |
<ja:l xml:lang="ja"> |
| 625 |
$B$3$NJ8;z=89g$O%a%$%k:n@.<T$,;H$&$3$H$O0U?^$7$F$$$^$;$s!#%a%$%k:n@.<T$O;HMQ$9$kJ8;z=89g$rCN$C$F$$$F!"(B |
| 626 |
<xref target="refs.RFC1341" /> $B$G5,Dj$5$l$F8=9T$N3dEvHV9fJ8=q(B |
| 627 |
<xref target="refs.STD2" /> |
| 628 |
$B$G2~D{$5$l$?J8;z=89gCM$G0u$r$D$1$k$HA[Dj$7$F$$$^$9!#(B |
| 629 |
</ja:l> |
| 630 |
</ja:pair> |
| 631 |
</t> |
| 632 |
|
| 633 |
<t> |
| 634 |
<ja:pair> |
| 635 |
<ja:l xml:lang="en"> |
| 636 |
The use of the "unknown-8bit" label is intended only by mail gateway |
| 637 |
agents which cannot determine via out-of-band information the |
| 638 |
intended character set. |
| 639 |
</ja:l> |
| 640 |
<ja:l xml:lang="ja"> |
| 641 |
"unknown-8bit" $B;%$N;HMQ$O!"(B &ja.outofband; |
| 642 |
$B>pJs$K$h$j0U?^$5$l$?J8;z=89g$r7hDj=PMh$J$$%a%$%k4XLg(B&ja.agent;$B$K$h$j$N$_;H$o$l$k$3$H$rA[Dj$7$F$$$^$9!#(B |
| 643 |
</ja:l> |
| 644 |
</ja:pair> |
| 645 |
</t> |
| 646 |
|
| 647 |
<t> |
| 648 |
<ja:pair> |
| 649 |
<ja:l xml:lang="en"> |
| 650 |
The interpretation of the "unknown-8bit" is up to the mail reader. |
| 651 |
It is assumed that in many cases the human user will be able to |
| 652 |
interpret the information and choose an appropriate character set or |
| 653 |
pre-processor. |
| 654 |
</ja:l> |
| 655 |
<ja:l xml:lang="ja"> |
| 656 |
"unknown-8bit" $B$N2r<a$O%a%$%k!&%j!<%@!<$K0Q$M$i$l$^$9!#B?$/$N>l9g$G$O?M4VMxMQ<T$,>pJs$r2r<a$7$FE,@Z$JJ8;z=89g$"$k$$$OA0=hM}4o$rA*Br$G$-$k$H;W$o$l$^$9!#(B |
| 657 |
</ja:l> |
| 658 |
</ja:pair> |
| 659 |
</t> |
| 660 |
|
| 661 |
</section> |
| 662 |
|
| 663 |
<section title="Acknowledgements" myns:unnumbered="yes"> |
| 664 |
<t> |
| 665 |
<ja:pair> |
| 666 |
<ja:l xml:lang="en"> |
| 667 |
This document originated as a hallway conversation between |
| 668 |
Ned Freed, Neil Katin, and the author. Substantive input |
| 669 |
was received from Jonathan Laventhol, Craig Everhart, |
| 670 |
Olle Jarnefors, and Olafur Gudmundsson. The document was |
| 671 |
refined with the input of many participants in the IETF SMTP |
| 672 |
Extensions Working Group. |
| 673 |
</ja:l> |
| 674 |
<ja:l xml:lang="ja"> |
| 675 |
$B$3$NJ8=q$O(B Ned Freed, Neil Katin $B$HCx<T$N0f8MC<2q5D$+$i@8$^$l$^$7$?!#(B |
| 676 |
Jonathan Laventhol, Craig Everhart, |
| 677 |
Olle Jarnefors, Olafur Gudmundsson $B$,:2$r?a$-9~$s$G$/$l$^$7$?!#$3$NJ8=q$O(B |
| 678 |
IETF SMTP $B3HD%:n6HIt2q$N;22C<T$N0U8+$K$h$j@:O#$5$l$^$7$?!#(B |
| 679 |
</ja:l> |
| 680 |
</ja:pair> |
| 681 |
</t> |
| 682 |
</section> |
| 683 |
|
| 684 |
<ja:insert section="references" /> |
| 685 |
|
| 686 |
|
| 687 |
<section title="Security Considerations" myns:unnumbered="yes"> |
| 688 |
<t>Security issues are not discussed in this memo.</t> |
| 689 |
</section> |
| 690 |
|
| 691 |
</middle> |
| 692 |
<back> |
| 693 |
<references> |
| 694 |
<reference anchor="refs.RFC1341"><!-- [1] --> |
| 695 |
<front><title>Multipurpose Internet Mail Extensions</title> |
| 696 |
<ja:title xml:lang="ja">$BB?L\E*(B Internet $B%a%$%k3HD%(B</ja:title> |
| 697 |
<author initials="N." surname="Borenstein"> |
| 698 |
<organization>Bellcore</organization> |
| 699 |
</author> |
| 700 |
<author initials="N." surname="Freed"> |
| 701 |
<organization>Innosoft</organization> |
| 702 |
</author> |
| 703 |
<date month="June" year="1992" /> |
| 704 |
</front> |
| 705 |
<seriesInfo name="RFC" value="1341" /> |
| 706 |
</reference> |
| 707 |
<reference anchor="refs.RFC1342"><!-- [2] --> |
| 708 |
<front><title>Representation of Non-ASCII Text in Internet Message Headers</title> |
| 709 |
<ja:title xml:lang="ja">$BHs(B ASCII $BJ8$N(B Internet $B%a%C%;!<%8F,$K$*$1$kI=8=(B</ja:title> |
| 710 |
<author initials="K." surname="Moore"> |
| 711 |
<organization>University of Tennessee</organization> |
| 712 |
</author> |
| 713 |
<date month="June" year="1992" /> |
| 714 |
</front> |
| 715 |
<seriesInfo name="RFC" value="1342" /> |
| 716 |
</reference> |
| 717 |
<reference anchor="refs.RFC1425"><!-- [3] --> |
| 718 |
<front><title>SMTP Service Extensions</title> |
| 719 |
<ja:title xml:lang="ja">SMTP $B%5!<%S%93HD%(B</ja:title> |
| 720 |
<author initials="J." surname="Klensin" ja:text="Klensin, J., WG Chair"> |
| 721 |
<organization>United Nations University</organization> |
| 722 |
</author> |
| 723 |
<author initials="N." surname="Freed" ja:text="Freed, N., Editor"> |
| 724 |
<organization>Innosoft International, Inc.</organization> |
| 725 |
</author> |
| 726 |
<author initials="M." surname="Rose"> |
| 727 |
<organization>Dover Beach Consulting, Inc.</organization> |
| 728 |
</author> |
| 729 |
<author initials="E." surname="Stefferud"> |
| 730 |
<organization>Network Management Associates, Inc.</organization> |
| 731 |
</author> |
| 732 |
<author initials="D." surname="Crocker"> |
| 733 |
<organization>The Branch Office</organization> |
| 734 |
</author> |
| 735 |
<date month="February" year="1993" /> |
| 736 |
</front> |
| 737 |
<seriesInfo name="RFC" value="1425" /> |
| 738 |
</reference> |
| 739 |
<reference anchor="refs.RFC1426"><!-- [4] --> |
| 740 |
<front><title>SMTP Service Extensions for 8bit |
| 741 |
MIMEtransport</title> |
| 742 |
<ja:title xml:lang="ja">8$B%S%C%H(B MIME $BE>AwMQ(B SMTP $B%5!<%S%93HD%(B</ja:title> |
| 743 |
<author initials="J." surname="Klensin" ja:text="Klensin, J., WG Chair"> |
| 744 |
<organization>United Nations University</organization> |
| 745 |
</author> |
| 746 |
<author initials="N." surname="Freed" ja:text="Freed, N., Editor"> |
| 747 |
<organization>Innosoft International, Inc.</organization> |
| 748 |
</author> |
| 749 |
<author initials="M." surname="Rose"> |
| 750 |
<organization>Dover Beach Consulting, Inc.</organization> |
| 751 |
</author> |
| 752 |
<author initials="E." surname="Stefferud"> |
| 753 |
<organization>Network Management Associates, Inc.</organization> |
| 754 |
</author> |
| 755 |
<author initials="D." surname="Crocker"> |
| 756 |
<organization>The Branch Office</organization> |
| 757 |
</author> |
| 758 |
<date month="February" year="1993" /> |
| 759 |
</front> |
| 760 |
<seriesInfo name="RFC" value="1426" /> |
| 761 |
</reference> |
| 762 |
<reference anchor="refs.ASCII"><!-- [5] --> |
| 763 |
<front><title>Coded Character Set$B!=!=(B7-Bit American Standard Code |
| 764 |
for Information Interchange</title> |
| 765 |
<ja:title xml:lang="ja">$BId9f2=J8;z=89g!=!=(B7$B%S%C%H$N>pJs8r49MQ0!JFMx2CI8=`Id9f(B</ja:title> |
| 766 |
</front> |
| 767 |
<seriesInfo name="ANSI" value="X3.4-1986" /> |
| 768 |
</reference> |
| 769 |
<reference anchor="refs.STD2"><!-- [6] --> |
| 770 |
<front><title>Assigned Numbers</title> |
| 771 |
<ja:title xml:lang="ja">$B3dEvHV9f(B</ja:title> |
| 772 |
<author initials="J." surname="Reynolds"> |
| 773 |
<organization>USC/Information Sciences Institute</organization> |
| 774 |
</author> |
| 775 |
<author initials="J." surname="Postel"> |
| 776 |
<organization>USC/Information Sciences Institute</organization> |
| 777 |
</author> |
| 778 |
<date month="July" year="1992" /> |
| 779 |
</front> |
| 780 |
<seriesInfo name="STD" value="2" /> |
| 781 |
<seriesInfo name="RFC" value="1340" /> |
| 782 |
</reference> |
| 783 |
</references> |
| 784 |
</back> |
| 785 |
</rfc> |
Parent Directory
| 
Revision Log