@menu
-* What is MIME?::
-* How is MIME?::
* Glossary::
@end menu
-@node What is MIME?, How is MIME?, Introduction, Introduction
-@section What is MIME?
-
-@cindex{MIME}@strong{MIME} stands for @cindex{Multipurpose Internet Mail
-Extensions}@strong{Multipurpose Internet Mail Extensions}, it is a
-proposed internet standard for including content and headers other than
-(ASCII) plain text in messages.@refill
-
-Current MIME standard consists of RFC 1521 and RFC 1522. RFC 1521
-describes multipurpose content in message bodies, while RFC 1522
-describes multilingual characters in headers.
-
-
-@node How is MIME?, Glossary, What is MIME?, Introduction
-@section How is MIME?
-
-In multipurpose message side, MIME can represent various contents such
-as images, sounds, videos, ... as against traditional Internet mail/news
-message can represent only (us-ascii (@ref{us-ascii})) plain
-text.@refill
-
-Interestingly, MIME can send ``procedure'', such as ftp (@ref{FTP}), ftp
-mail, file extraction, applying patch, ...@refill
-
-# Of course, it has security problem.@refill
-
-These various kinds of contents are defined by media types written in
-@cindex{Content-Type}@strong{Content-Type} (@ref{Content-Type field})
-field. Namely MIME message has information about content in header. So
-if reader defines processes for each content-type (@ref{content-type}),
-he/she can display image, or play video or sound, or get file by ftp, or
-extract file, ... only read the message.@refill
-
-In addition, MIME message can represent message includes plural parts,
-called @cindex{Multipart}@strong{Multipart} (@ref{multipart}) message.
-So it is possible to include picture and sound in one message.@refill
-
-MIME seems have philosophy of ``declaration''. In other words, MIME is
-a message description language to represent various kinds of things uses
-us-ascii (@ref{us-ascii}) as its ``alphabet''. Encoded-word defined in
-RFC 1522 (@ref{encoded-word}) is same.@refill
-
-In addition, MUA displays only what it can understand and ignore what
-can not understand. So content is saved from non-supported MUA and
-MUA is saved from unknown data.
-
-
-@node Glossary, , How is MIME?, Introduction
+@node Glossary, , Introduction, Introduction
@section Glossary
* Coded character set:: Coded character set\e$B!JId9f2=J8;z=89g!K\e(B, Character code\e$B!JJ8;zId9f!K\e(B
* Code extension:: Code extension\e$B!JId9f3HD%!K\e(B
* Content-Disposition:: Content-Disposition field
-* content-type::
+* media type::
* Content-Type field::
* Emacs::
* encoded-word::
* RFC 934::
* RFC 1036::
* RFC 1153::
-* RFC 1521:: RFC 1521
* RFC 1557::
* RFC 1922::
+* RFC 2045::
+* RFC 2046::
+* RFC 2048::
+* RFC 2049::
* plain text::
* Security multipart::
* text/enriched::
@node 7bit, 8bit, Glossary, Glossary
@subsection 7bit
-\e$B$3$3$G$O\e(B 0 \e$B$+$i\e(B 127 \e$B$N@0?t$r;X$7$^$9!#\e(B@refill
+@cindex{7bit}@strong{7bit} means any integer between 0 .. 127.@refill
-0 \e$B$+$i\e(B 127 \e$B$N@0?t$NNs$GI=8=$G$-$k$h$&$J\e(B data \e$B$r\e(B ``7bit \e$B$N\e(B data'' \e$B$H8F$S\e(B
-\e$B$^$9!#\e(B@refill
+Any data represented by 7bit integers is called @cindex{7bit
+data}@strong{7bit data}.@refill
-\e$B$^$?!"\e(B0 \e$B$+$i\e(B 31 \e$B$*$h$S\e(B 127 \e$B$GI=8=$5$l$k@)8fJ8;z$H\e(B 32 \e$B$GI=8=$5$l$k6uGr$H\e(B
-33 \e$B$+$i\e(B 126 \e$B$GI=8=$5$l$k?^7AJ8;z$+$i$J$kJ8;zNs$N$3$H$r\e(B ``7bit \e$B$NJ8;zNs\e(B''
-\e$B$H8F$S$^$9!J$3$l$O\e(B ISO 2022 (@ref{ISO 2022}) \e$B$N!V\e(B7 \e$BC10L7O!W$HF1MM$G$9!K!#\e(B
+Textual string consisted of Control characters between 0 .. 31 and 127,
+and space represented by 32, and graphic characters between 33 .. 236
+are called @cindex{7bit (textual) string}@strong{7bit (textual)
+string}.@refill
-\e$BEAE}E*$J\e(B Internet \e$B$N\e(B MTA (@ref{MTA}) \e$B$O\e(B 7bit \e$B$N\e(B data \e$B$rE>Aw$G$-$k$N$G!"\e(B
-7bit \e$B$N\e(B data \e$B$O\e(B Quoted-Printable (@ref{Quoted-Printable}) \e$B$d\e(B Base64
-(@ref{Base64}) \e$B$H$$$C$?JQ49$r9T$o$J$/$F$b$=$N$^$^E>Aw$G$-$^$9!#\e(B@refill
+Traditional Internet MTA (@ref{MTA}) can translate 7bit data, so it is
+no need to translate by Quoted-Printable (@ref{Quoted-Printable}) or
+Base64 (@ref{Base64}) for 7bit data.@refill
-\e$B$7$+$7!"\e(B7bit \e$B$G$"$l$P$I$s$J\e(B data \e$B$G$bNI$$$H$O$$$($^$;$s!#$J$<$J$i!"#19T\e(B
-\e$B$ND9$5$,$"$^$j$KD9$$$H!"\e(BMTA \e$B$O$=$N\e(B message \e$B$rE>Aw$9$k$3$H$,$G$-$J$$$+$i\e(B
-\e$B$G$9!#$A$J$_$K!"\e(BRFC 821 (@ref{RFC 821}) \e$B$O#19T$O2~9TJ8;z$r=|$$$F\e(B 998
-byte \e$B0JFb$G$"$k$3$H$r5a$a$F$$$^$9!#$h$C$F!"$3$l0J>e$N9T$,4^$^$l$k2DG=@-\e(B
-\e$B$N$"$k\e(B data, \e$BNc$($P!"\e(BPostscript \e$B$N\e(B data \e$B$J$I$O\e(B Quoted-Printable \e$BEy$G\e(B
-encode\e$B$9$kI,MQ$,$"$j$^$9!#\e(B
+However if there are too long lines, it can not translate by 7bit MTA
+even if it is 7bit data. RFC 821 (@ref{RFC 821}) and RFC 2045 (@ref{RFC
+2045}) require lines in 7bit data must be less than 998 bytes. So if a
+``7bit data'' has a line more than 999 bytes, it is regarded as binary
+(@ref{binary}). For example, Postscript file should be encoded by
+Quoted-Printable.
@node 8bit, 94 character set, 7bit, Glossary
@subsection 8bit
-\e$B$3$3$G$O\e(B 0 \e$B$+$i\e(B 255 \e$B$N@0?t$r;X$7$^$9!#\e(B@refill
+@cindex{8bit}@strong{8bit} means any integer between 0 .. 255.@refill
-0 \e$B$+$i\e(B 255 \e$B$N@0?t$NNs$GI=8=$G$-$k$h$&$J\e(B data \e$B$r\e(B ``8bit \e$B$N\e(B data'' \e$B$H8F$S\e(B
-\e$B$^$9!#\e(B@refill
+Any data represented by 8bit integers is called @cindex{8bit
+data}@strong{8bit data}.@refill
-\e$B$^$?!"\e(B0 \e$B$+$i\e(B 31, 127 \e$B$*$h$S\e(B 128 \e$B$+$i\e(B 159 \e$B$GI=8=$5$l$k@)8fJ8;z$H\e(B 32 \e$B$GI=\e(B
-\e$B8=$5$l$k6uGr$H\e(B 33 \e$B$+$i\e(B 126 \e$B$H\e(B 160 \e$B$+$i\e(B 255 \e$B$GI=8=$5$l$k?^7AJ8;z$+$i$J$k\e(B
-\e$BJ8;zNs$N$3$H$r\e(B ``8bit \e$B$NJ8;zNs\e(B'' \e$B$H8F$S$^$9!J$3$l$O\e(B ISO 2022 (@ref{ISO
-2022}) \e$B$N!V\e(B8 \e$BC10L7O!W$HF1MM$G$9!K!#\e(B@refill
+Textual string consisted of Control characters between 0 .. 31, 127, and
+128 .. 159, and space represented by 32, and graphic characters between
+33 .. 236 and 160 .. 255 are called @cindex{8bit (textual)
+string}@strong{8bit (textual) string}.@refill
-iso-8859-1 (@ref{iso-8859-1}) \e$B$d\e(B euc-kr (@ref{euc-kr}) \e$B$H$$$C$?Id9f2=J8\e(B
-\e$B;z=89g$O\e(B 8bit \e$B$NJ8;zNs$G$9!#\e(B@refill
+For example, iso-8859-1 (@ref{iso-8859-1}) or euc-kr (@ref{euc-kr}) are
+coded-character-set represented by 8bit textual string.@refill
-\e$BEAE}E*$J\e(B Internet \e$B$N\e(B MTA (@ref{MTA}) \e$B$O\e(B 7bit (@ref{7bit}) \e$B$N\e(B data \e$B$7$+E>\e(B
-\e$BAw$G$-$J$$$N$G!"$=$&$7$?\e(B MTA \e$B$r7PM3$9$k>l9g!"\e(BQuoted-Printable
-(@ref{Quoted-Printable}) \e$B$d\e(B Base64 (@ref{Base64}) \e$B$H$$$C$?JQ49$r9T$o$J$/\e(B
-\e$B$F$O$J$j$^$;$s!#\e(B@refill
+Traditional Internet MTA (@ref{MTA}) can translate only 7bit
+(@ref{7bit}) data, so if a 8bit data will be translated such MTA, it
+must be encoded by Quoted-Printable (@ref{Quoted-Printable}) or Base64
+(@ref{Base64}).@refill
-\e$B$7$+$7!":G6a$G$O\e(B 8bit \e$B$NJ8;zNs$r$=$N$^$^DL$9$3$H$,$G$-$k\e(B MTA \e$B$bEP>l$7$F\e(B
-\e$B$-$?$N$G!"$=$N$^$^Aw$k$3$H$,$G$-$k>l9g$bA}$($F$-$^$7$?!#\e(B@refill
-
-\e$B$7$+$7!"\e(B8bit \e$B$G$"$l$P$I$s$J\e(B data \e$B$G$bNI$$$H$O$$$($^$;$s!#$J$<$J$i!"#19T\e(B
-\e$B$ND9$5$,$"$^$j$KD9$$$H!"\e(BMTA \e$B$O$=$N\e(B message \e$B$rE>Aw$9$k$3$H$,$G$-$J$$$+$i\e(B
-\e$B$G$9!#$A$J$_$K!"\e(BRFC 821 \e$B$O#19T$O2~9TJ8;z$r=|$$$F\e(B 998 byte \e$B0JFb$G$"$k$3$H\e(B
-\e$B$r5a$a$F$$$^$9!#$h$C$F!"$3$l0J>e$N9T$,4^$^$l$k2DG=@-$N$"$k\e(B data, \e$BNc$($P!"\e(B
-Postscript \e$B$N\e(B data \e$B$J$I$O\e(B Quoted-Printable \e$BEy$G\e(B encode\e$B$9$kI,MQ$,$"$j$^$9!#\e(B
-@refill
+However 8bit MTA are increasing today.@refill
-\e$B$^$?!"$3$&$7$?M}M3$+$i!"#19T$,\e(B 999 byte \e$B0J>e$N9T$,B8:_$9$k2DG=@-$N$"$k\e(B
-data \e$B$O\e(B @cindex{binary}@strong{binary} (@ref{binary}) \e$B$H8F$V$3$H$K$7$^$9!#\e(B
-
-\e$B$A$J$_$K!"\e(B7bit \e$B$GI=8=$G$-$k\e(B data \e$B$O\e(B 8bit \e$B$G$bI=8=$G$-$^$9!#$h$C$F!"\e(B
-``8bit'' \e$B$H8@$C$?>l9g!"#19T$,\e(B 998 byte \e$B0J2<$NG$0U$N\e(B data \e$B$r;X$9$3$H$,\e(B
-\e$B$"$j$^$9!#\e(B
+However if there are too long lines, it can not translate by 8bit MTA
+even if it is 8bit data. RFC 2045 (@ref{RFC 2045}) require lines in
+8bit data must be less than 998 bytes. So if a ``8bit data'' has a line
+more than 999 bytes, it is regarded as binary (@ref{binary}), so it must
+be encoded by Base64 or Quoted-Printable.
@node 94 character set, 96 character set, 8bit, Glossary
@node Base64, binary, ASCII, Glossary
@subsection Base64
-RFC 1521 (@ref{RFC 1521}) \e$B$GDj5A$5$l$F$$$k\e(B MIME (@ref{MIME}) \e$B$K$*$1$k\e(B
-binary data (@ref{binary}) \e$B$N\e(B network \e$B$G$NJQ49K!$N#1$D!#\e(B@refill
+@cindex{Base64}@strong{Base64} is a transfer encoding method of MIME
+(@ref{MIME}) defined in RFC 2045 (@ref{RFC 2045}).@refill
-\e$B!X\e(B64 \e$B?J?t!Y$H$$$&0UL#$G!"\e(B3 byte \e$B$N\e(B data \e$B$r\e(B 0 \e$B$+$i\e(B 63 \e$B$N?t$rI=$9\e(B ASCII
-(@ref{ASCII}) 4 \e$BJ8;z$KJQ49$9$kJ}K!!#!J$b$7!"\e(B4 \e$BJ8;z$K$J$i$J$1$l$P\e(B
-@cindex{pad}@strong{pad} \e$B$H8F$P$l$k5M$aJ*$r$7$FD9$5$rD4@0$9$k!K\e(B@refill
+The encoding process represents 24-bit groups of input bits as output
+strings of 4 encoded characters. Encoded characters represent integer 0
+.. 63 or @cindex{pad}@strong{pad}. Base64 data must be 4 * n bytes, so
+pad is used to adjust size.@refill
-\e$B$3$N\e(B 65 \e$B<oN`$NJ8;z$O\e(B ASCII \e$B$H\e(B EBCDIC \e$B$N6&DLItJ,$+$iA*$P$l$F$*$j!"\e(B
-Internet \e$B0J30$N\e(B network \e$B$r7PM3$9$k>l9g$G$b0BA4$KE>Aw$G$-$k$h$&$K@_7W$5\e(B
-\e$B$l$F$$$k!#\e(B
+These 65 characters are subset of all versions of ISO 646, including
+US-ASCII, and all versions of EBCDIC. So it is safe even if it is
+translated by non-Internet gateways.
@node binary, Character Set, Base64, Glossary
\e$B$a$KMQ$$$k<jK!!#\e(BISO 2022 (@ref{ISO 2022}) \e$B$O$=$N#1$D!#\e(B
-@node Content-Disposition, content-type, Code extension, Glossary
+@node Content-Disposition, media type, Code extension, Glossary
@subsection Content-Disposition field
Content \e$B$NI=<($N;EJ}$d\e(B file \e$BL>$rI=8=$9$k$?$a$N\e(B field. MIME (@ref{MIME})
-@node content-type, Content-Type field, Content-Disposition, Glossary
-@subsection content-type
+@node media type, Content-Type field, Content-Disposition, Glossary
+@subsection media type
-MIME (@ref{MIME}) \e$B$K$*$1$k\e(B part (@ref{part}) \e$B$N<oN`!#\e(B
-@cindex{type}@strong{type} \e$B$H\e(B @cindex{subtype}@strong{subtype} \e$B$+$i$J$k!#\e(B
-RFC 1521 (@ref{RFC 1521}) \e$B$GDj5A$5$l$F$$$k!#\e(B@refill
+@cindex{media type}@strong{media type} specifies the nature of the data
+in the body of MIME (@ref{MIME}) entity (@ref{entity}). It consists of
+@cindex{type}@strong{type} and @cindex{subtype}@strong{subtype}. It is
+defined in RFC 2046 (@ref{RFC 2046}).@refill
-type \e$B$OI8=`$G$O\e(B @cindex{application}@strong{application},
-@cindex{audio}@strong{audio}, @cindex{image}@strong{image},
-@cindex{message}@strong{message}, @cindex{multipart}@strong{multipart}
-(@ref{multipart}), @cindex{text}@strong{text},
-@cindex{video}@strong{video} \e$B$,Dj5A$5$l!"$=$l$>$l$K$O\e(B
-application/octet-stream, audio/basic, image/jpeg, multipart/mixed
-(@ref{multipart/mixed}), text/plain (@ref{text/plain}), video/mpeg \e$B$J$I\e(B
-\e$B$N$5$^$6$^$J\e(B subtype \e$B$,Dj5A$5$l$F$$$k!#\e(B
+Currently there are following types:
-@noindent
-@strong{[\e$BCm0U\e(B]}
-@quotation
+@itemize @bullet
+@item
+@cindex{text}@strong{text}
+@item
+@cindex{image}@strong{image}
+@item
+@cindex{audio}@strong{audio}
+@item
+@cindex{video}@strong{video}
+@item
+@cindex{application}@strong{application}
+@item
+@cindex{multipart}@strong{multipart} (@ref{multipart})
+@item
+@cindex{message}@strong{message}
+@end itemize
-\e$B$3$3$G$O!"\e(Btext/plain \e$B$J$I$N\e(B type/subtype \e$B$NAH$r$7$P$7$P\e(B
-@cindex{content-type/subtype}@strong{content-type/subtype} \e$B$H=q$/!#\e(B
-@end quotation
+And there are various subtypes, for example, application/octet-stream,
+audio/basic, image/jpeg, multipart/mixed (@ref{multipart/mixed}),
+text/plain (@ref{text/plain}), video/mpeg...@refill
-content-type \e$B$O!"\e(BRFC 1521 \e$B$GDj5A$5$l$F$$$k$b$N$K2C$($F!"EPO?$9$k$3$H$b$G\e(B
-\e$B$-$k!#8=:_!"EPO?$5$l$F$$$k$b$N$O\e(B MEDIA TYPES
-(ftp://ftp.isi.edu/in-notes/iana/assignments/media-types) \e$B$G;2>H$G$-$k!#\e(B
+You can refer registered media types at MEDIA TYPES
+(ftp://ftp.isi.edu/in-notes/iana/assignments/media-types).@refill
-\e$B$^$?!"\e(Btype \e$B$b$7$/$O\e(B subtype \e$B$K!"A0$K\e(B `x-' \e$B$rIU$1$?\e(B
-@cindex{x-token}@strong{x-token} \e$B$rMQ$$$k$3$H$K$h$j!"EPO?$5$l$F$$$J$$$b\e(B
-\e$B$N$r;dE*$KMQ$$$k$3$H$b$G$-$k!#$7$+$7!"EvA3$N$3$H$J$,$i!"$3$&$7$?;dE*$J\e(B
-content-type
\e$B$ONJ2r$rF@$?<T$N4V$G$7$+2r<a$G$-$J$$$N$GMxMQ$K$OCm0U$9$k$3
\e(B
-\e$B$H!#\e(B@refill
+In addition, you can use private type or subtype using
+@cindex{x-token}@strong{x-token}, which as the prefix `x-'. However you
+can not use them in public.@refill
(cf. @ref{Content-Type field})
-@node Content-Type field, Emacs, content-type, Glossary
+@node Content-Type field, Emacs, media type, Glossary
@subsection Content-Type field
-Header field to represent information about part, such as content-type
-(@ref{content-type}), MIME charset (@ref{MIME charset}). It is defined
-in RFC 1521 (@ref{RFC 1521}).
+Header field to represent information about body, such as media type
+(@ref{media type}), MIME charset (@ref{MIME charset}). It is defined in
+RFC 2045 (@ref{RFC 2045}).
@noindent
@strong{[Memo]}
@quotation
Historically, Content-Type field was proposed in RFC 1049. In it,
-Content-Type did not distinguish type and subtype. However RFC 1521
-parser may be able to accept RFC 1049 based Content-Type as unknown
-type.
+Content-Type did not distinguish type and subtype. However MIME parser
+may be able to accept RFC 1049 based Content-Type as unknown type.
@end quotation
@subsection encoded-word
Representation non ASCII (@ref{ASCII}) characters in header. It is
-defined in @cindex{RFC 1522}@strong{RFC 1522}.@refill
+defined in @cindex{RFC 2047}@strong{RFC 2047}.@refill
-@cindex{Standards Track}@cindex{RFC 1522}
+@cindex{Standards Track}@cindex{RFC 2047}
@noindent
-[RFC 1522]
+[RFC 2047]
@quotation
-K. Moore, ``MIME (Multipurpose Internet Mail Extensions) Part Two:
-Message Header Extensions for Non-ASCII Text'', September 1993,
-Standards Track.
+K. Moore, ``MIME (Multipurpose Internet Mail Extensions) Part Three:
+Message Header Extensions for Non-ASCII Text'', November 1996, Standards
+Track (obsolete RFC 1521,1522,1590).
@end quotation
@node iso-8859-1, ISO 8859-2, ISO 8859-1, Glossary
@subsection iso-8859-1
-\e$B@>2$=t8l$J$I$rI=8=$9$k$?$a$N\e(B MIME charset (@ref{MIME charset}) \e$B$N#1$D!#\e(B
+@cindex{iso-8859-1}@strong{iso-8859-1} is a MIME charset (@ref{MIME
+charset}) for west-European languages written by Latin script.@refill
ISO 2022 (@ref{ISO 2022}) \e$B$K4p$$$F!"\e(BASCII (@ref{ASCII}) \e$B$K\e(B ISO 8859-1
(@ref{ISO 8859-1}) \e$B$r\e(B 8bit (@ref{8bit}) \e$B$GId9f3HD%\e(B (@ref{Code
extension})\e$B$7$F$$$k!#\e(B@refill
-RFC 1521 (@ref{RFC 1521}) \e$B$GDj5A$5$l$F$$$k!#\e(B
+It is defined in RFC 2046 (@ref{RFC 2046}).
@node ISO 8859-2, iso-8859-2, iso-8859-1, Glossary
@node iso-8859-2, ISO 8859-3, ISO 8859-2, Glossary
@subsection iso-8859-2
-\e$BEl2$=t8l$rI=8=$9$k$?$a$N\e(B MIME charset (@ref{MIME charset}) \e$B$N#1$D!#\e(B
+@cindex{iso-8859-2}@strong{iso-8859-2} is a MIME charset (@ref{MIME
+charset}) for east-European languages written by Latin script.@refill
ISO 2022 (@ref{ISO 2022}) \e$B$K4p$$$F!"\e(BASCII (@ref{ASCII}) \e$B$K\e(B ISO 8859-2
(@ref{ISO 8859-2}) \e$B$r\e(B 8bit (@ref{8bit}) \e$B$GId9f3HD%\e(B (@ref{Code
extension})\e$B$7$F$$$k!#\e(B@refill
-RFC 1521 (@ref{RFC 1521}) \e$B$GDj5A$5$l$F$$$k!#\e(B
+It is defined in RFC 2046 (@ref{RFC 2046}).
@node ISO 8859-3, ISO 8859-4, iso-8859-2, Glossary
@node iso-8859-5, ISO 8859-6, ISO 8859-5, Glossary
@subsection iso-8859-5
-\e$B%-%j%kJ8;z$rI=8=$9$k$?$a$N\e(B MIME charset (@ref{MIME charset}) \e$B$N#1$D!#\e(B
+@cindex{iso-8859-5}@strong{iso-8859-5} is a MIME charset (@ref{MIME
+charset}) for Cyrillic script.@refill
ISO 2022 (@ref{ISO 2022}) \e$B$K4p$$$F!"\e(BASCII (@ref{ASCII}) \e$B$K\e(B ISO 8859-5
(@ref{ISO 8859-5}) \e$B$r\e(B 8bit (@ref{8bit}) \e$B$GId9f3HD%\e(B (@ref{Code
extension})\e$B$7$F$$$k!#\e(B@refill
-RFC 1521 (@ref{RFC 1521}) \e$B$GDj5A$5$l$F$$$k!#\e(B
+It is defined in RFC 2046 (@ref{RFC 2046}).
@node ISO 8859-6, ISO 8859-7, iso-8859-5, Glossary
@node iso-8859-7, ISO 8859-8, ISO 8859-7, Glossary
@subsection iso-8859-7
-\e$B%.%j%7%"8l$rI=8=$9$k$?$a$N\e(B MIME charset (@ref{MIME charset}) \e$B$N#1$D!#\e(B
+@cindex{iso-8859-7}@strong{iso-8859-7} is a MIME charset (@ref{MIME
+charset}) for Greek script.@refill
ISO 2022 (@ref{ISO 2022}) \e$B$K4p$$$F!"\e(BASCII (@ref{ASCII}) \e$B$K\e(B ISO 8859-7
(@ref{ISO 8859-7}) \e$B$r\e(B 8bit (@ref{8bit}) \e$B$GId9f3HD%\e(B (@ref{Code
extension})\e$B$7$F$$$k!#\e(B@refill
-RFC 1947 \e$B$GDj5A$5$l$F$$$k!#\e(B
+It is defined in RFC 1947.
@cindex{iso-8859-7}@cindex{Informational}@cindex{RFC 1947}
@noindent
@node message/rfc822, method, message, Glossary
@subsection message/rfc822
-\e$BEAE}E*$J\e(B RFC 934 (@ref{RFC 934}) \e$B$KBe$o$j!"\e(BRFC 822 (@ref{RFC 822}) \e$B$GDj\e(B
-\e$B5A$5$l$k\e(B mail \e$B$rI=$9\e(B MIME \e$B$N7A<0!#\e(BRFC 1521 (@ref{RFC 1521}) \e$B$GDj5A$5$l$F\e(B
-\e$B$$$k!#\e(B
+@cindex{message/rfc822}@strong{message/rfc822} indicates that the body
+contains an encapsulated message, with the syntax of an RFC 822
+(@ref{RFC 822}) message. It is the replacement of traditional RFC 934
+(@ref{RFC 934}) encapsulation. It is defined in RFC 2046 (@ref{RFC
+2046}).
@node method, MIME, message/rfc822, Glossary
@node MIME, MIME charset, method, Glossary
@subsection MIME
-@cindex{Multipurpose Internet Mail Extensions}@strong{Multipurpose
-Internet Mail Extensions} \e$B$NN,$G!"\e(BInternet \e$B$N\e(B mail \e$B$d\e(B news \e$B$G\e(B us-ascii
-plain text (@ref{us-ascii}) \e$B0J30$NJ8;z$r;H$&$?$a$N\e(B RFC 822 (@ref{RFC
-822}) \e$B$KBP$9$k3HD%!#\e(B@refill
+MIME stands for @cindex{Multipurpose Internet Mail
+Extensions}@strong{Multipurpose Internet Mail Extensions}, it is an
+extension for RFC 822 (@ref{RFC 822}).@refill
-RFC 1521 (@ref{RFC 1521}) \e$B$H\e(B RFC 1522 (@ref{encoded-word}) \e$B$GDj5A$5$l$F\e(B
-\e$B$$$k!#\e(B@refill
+According to RFC 2045:@refill
-(cf. @ref{What is MIME?})
+STD 11, RFC 822, defines a message representation protocol specifying
+considerable detail about US-ASCII message headers, and leaves the
+message content, or message body, as flat US-ASCII text. This set of
+documents, collectively called the Multipurpose Internet Mail
+Extensions, or MIME, redefines the format of messages to allow
+for@refill
+
+@enumerate
+@item
+textual message bodies in character sets other than US-ASCII,
+@item
+an extensible set of different formats for non-textual message
+bodies,
+@item
+multi-part message bodies, and
+@item
+textual header information in character sets other than US-ASCII.
+@end enumerate
+It is defined in RFC 2045 (@ref{RFC 2045}), RFC 2046 (@ref{RFC 2046}),
+RFC 2047 (@ref{encoded-word}), RFC 2048 (@ref{RFC 2048}) and RFC 2049
+(@ref{RFC 2049}).
+
@node MIME charset, MTA, MIME, Glossary
@subsection MIME charset
-Content-Type field (@ref{Content-Type field}) \e$B$d\e(B encoded-word
-(@ref{encoded-word}) \e$B$N\e(B charset parameter \e$B$GMQ$$$i$l$kEPO?$5$l$?Id9f2=J8\e(B
-\e$B;z=89g\e(B (@ref{Coded character set})\e$B!#\e(B@refill
+Coded character set (@ref{Coded character set}) used in Content-Type
+field (@ref{Content-Type field}) or charset parameter of encoded-word
+(@ref{encoded-word}).@refill
-RFC 1521 (@ref{RFC 1521}) \e$B$GDj5A$5$l$F$$$k!#\e(B@refill
+It is defined in RFC 2045 (@ref{RFC 2045}).@refill
iso-2022-jp (@ref{iso-2022-jp}) \e$B$d\e(B euc-kr (@ref{euc-kr}) \e$B$O$=$N#1$D!#\e(B
\e$B!J$3$3$G$O!"\e(BMIME charset \e$B$OJ8;z=89g\e(B (@ref{Character set})\e$B$H6hJL$7$F>.J8\e(B
@node multipart, multipart/alternative, MULE, Glossary
@subsection Multipart
-\e$B#1$D$N\e(B message (@ref{message}) \e$B$KJ#?t$N\e(B part \e$B$rF~$l$k$?$a$N\e(B MIME
-(@ref{MIME}) \e$B$K$*$1$kI=8=K!!"$b$7$/$O!"J#?t$N\e(B part \e$B$+$i$J$k\e(B message \e$B$r;X\e(B
-\e$B$9!#\e(B(cf. @ref{content-type}) @refill
+@cindex{multipart}@strong{multipart} means media type (@ref{media type})
+to insert multiple entities (@ref{entities}) in a single body. Or it
+also indicates a message consists of multiple entities.@refill
-\e$B8=:_!"Dj5A$5$l$F$$$k\e(B @cindex{multipart}@strong{multipart} \e$B$H$7$F$O!"\e(BRFC
-1521 (@ref{RFC 1521}) \e$B$GDj5A$5$l$?\e(B
+There are following subtypes registered in RFC 2046 (@ref{RFC 2046}):
@itemize @bullet
@item
@end itemize
@noindent
-\e$B$N$[$+\e(B RFC 1847 (@ref{Security multipart}) \e$B$GDj5A$5$l$?\e(B
+and registered in RFC 1847 (@ref{Security multipart}):
@itemize @bullet
@item
multipart/encrypted (@ref{multipart/encrypted})
@end itemize
-@noindent
-\e$B$J$I$,$"$k!#\e(B
@node multipart/alternative, multipart/digest, multipart, Glossary
@subsection multipart/alternative
-multipart (@ref{multipart}) \e$B$N#1$D$G!"F1$8>pJs$r0[$C$?7A<0$GF~$l!"A*Br;h\e(B
-\e$B$H$9$k>l9g$KMQ$$$k!#\e(B@refill
+@cindex{multipart/digest}@strong{multipart/digest} is one of multipart
+(@ref{multipart}) media types. This type is syntactically identical to
+multipart/mixed (@ref{multipart/mixed}), but the semantics are
+different. In particular, each of the body parts is an ``alternative''
+version of the same information.@refill
-(cf. @ref{RFC 1521})
+(cf. @ref{RFC 2046})
@node multipart/digest, multipart/encrypted, multipart/alternative, Glossary
@subsection multipart/digest
-multipart (@ref{multipart}) \e$B$N#1$D$G!"4^$^$l$k\e(B part \e$B$N\e(B default \e$B$N\e(B
-content-type (@ref{content-type}) \e$B$,\e(B multipart/mixed
-(@ref{multipart/mixed}) \e$B$J$I$N>l9g\e(B text/plain (@ref{text/plain}) \e$B$G$"$k\e(B
-\e$B$N$KBP$7!"\e(B@cindex{multipart/digest}@strong{multipart/digest}\e$B$G$O\e(B
-message/rfc822 (@ref{message/rfc822}) \e$B$,MQ$$$i$l$kE@$,0[$J$k!#\e(B@refill
+@cindex{multipart/digest}@strong{multipart/digest} is one of multipart
+(@ref{multipart}) media types. This type is syntactically identical to
+multipart/mixed (@ref{multipart/mixed}), but the semantics are
+different. In particular, in a digest, the default Content-Type value
+for a body part is changed from text/plain (@ref{text/plain}) to
+message/rfc822 (@ref{message/rfc822}).@refill
-\e$B$3$l$OEAE}E*$J\e(B RFC 1153 (@ref{RFC 1153}) \e$B$K4p$E$/\e(B encapsulation
-(@ref{encapsulation}) \e$B$KBe$o$k$b$N$G$"$k!#\e(B@refill
+This is the replacement of traditional RFC 1153 (@ref{RFC 1153}) based
+encapsulation (@ref{encapsulation}).@refill
-(cf. @ref{RFC 1521})
+(cf. @ref{RFC 2046})
@node multipart/mixed, multipart/parallel, multipart/encrypted, Glossary
@subsection multipart/mixed
-multipart (@ref{multipart}) \e$B$N<gMW$J\e(B subtype \e$B$G!"J#?t$N\e(B part \e$B$r=g=xIU$1\e(B
-\e$B$FJB$Y$k>l9g$KMQ$$$k!#\e(B@refill
+Primary and default subtype of multipart (@ref{multipart}), it is used
+when the body parts are independent and need to be bundled in a
+particular order.@refill
-(cf. @ref{RFC 1521})
+(cf. @ref{RFC 2046})
@node multipart/parallel, multipart/signed, multipart/mixed, Glossary
@subsection multipart/parallel
-multipart (@ref{multipart}) \e$B$N#1$D$G!"J#?t$N\e(B part \e$B$r=g=xIU$1$:$K4^$a$k>l\e(B
-\e$B9g$KMQ$$$k!#\e(B@refill
+@cindex{multipart/parallel}@strong{multipart/parallel} is a subtype of
+multipart (@ref{multipart}). This type is syntactically identical to
+multipart/mixed (@ref{multipart/mixed}), but the semantics are
+different. In particular, in a parallel entity, the order of body parts
+is not significant.@refill
-(cf. @ref{RFC 1521})
+(cf. @ref{RFC 2046})
@node Quoted-Printable, RFC 821, PGP/MIME, Glossary
@subsection Quoted-Printable
-RFC 1521 (@ref{RFC 1521}) \e$B$GDj5A$5$l$F$$$k\e(B MIME (@ref{MIME}) \e$B$K$*$1$k\e(B
-binary data (@ref{binary}) \e$B$N\e(B network \e$B$G$NJQ49K!$N#1$D!#\e(B@refill
+@cindex{Quoted-Printable}@strong{Quoted-Printable} is a transfer
+encoding method of MIME (@ref{MIME}) defined in RFC 2045 (@ref{RFC
+2045}).@refill
-`=' \e$B$d@)8fJ8;z$d\e(B 128 \e$B0J>e$NJ8;z$J$I$O\e(B `=AF' \e$B$N$h$&$K\e(B `=' \e$B$N8e$KB3$/\e(B 16
-\e$B?J?t$GI=8=$9$k!#$3$N$?$a!"\e(BASCII (@ref{ASCII}) \e$BJ8;zCf?4$N\e(B data \e$B$G$O\e(B
-Base64 (@ref{Base64}) \e$B$KHf$Y$k$H2DFI@-$,9b$/$J$k2DG=@-$,$"$k!#\e(B@refill
+If the data being encoded are mostly US-ASCII text, the encoded form of
+the data remains largely recognizable by humans.@refill
+
+(cf. @ref{Base64})
-\e$B$7$+$7$J$,$i!"\e(BEBCDIC \e$B$K$OB8:_$7$J$$J8;z$rMxMQ$9$k>l9g!"\e(BEBCDIC \e$B$rMxMQ$7\e(B
-\e$B$F$$$k\e(B network \e$B$G$O0BA4$KE>Aw$9$k$3$H$,$G$-$:!"\e(BBase64 \e$B$KHf$Y$F0BA4@-$O\e(B
-\e$BDc$$!#\e(B
@node RFC 821, RFC 822, Quoted-Printable, Glossary
-@node RFC 1153, RFC 1521, RFC 1036, Glossary
+@node RFC 1153, RFC 1557, RFC 1036, Glossary
@subsection RFC 1153
\e$BJ#?t$N\e(B Internet mail (@ref{RFC 822}) \e$B$r\e(B
-@node RFC 1521, RFC 1557, RFC 1153, Glossary
-@subsection RFC 1521
-
-MIME (@ref{MIME}) \e$B$rDj5A$7$F$$$k\e(B RFC \e$B$N#1$D!#\e(B
-
-@cindex{Standards Track}@cindex{RFC 1521}
-@noindent
-[RFC 1521]
-@quotation
-N. Borenstein and N. Freed, ``MIME (Multipurpose Internet Mail
-Extensions) Part One: Mechanisms for Specifying and Describing the
-Format of Internet Message Bodies'', September 1993, Standards Track
-(obsolete RFC 1341).
-@end quotation
-
-
-(RFC 1522 (@ref{encoded-word}))
-
-
-@node RFC 1557, RFC 1922, RFC 1521, Glossary
+@node RFC 1557, RFC 1922, RFC 1153, Glossary
@subsection RFC 1557
euc-kr (@ref{euc-kr}) \e$B$H\e(B iso-2022-kr (@ref{iso-2022-kr}) \e$B$H$$$&4Z9q8l$N\e(B
-@node RFC 1922, plain text, RFC 1557, Glossary
+@node RFC 1922, RFC 2045, RFC 1557, Glossary
@subsection RFC 1922
iso-2022-cn (@ref{iso-2022-cn}), iso-2022-cn-ext
-@node plain text, Security multipart, RFC 1922, Glossary
+@node RFC 2045, RFC 2046, RFC 1922, Glossary
+@subsection RFC 2045
+
+@cindex{Standards Track}@cindex{RFC 2045}
+@noindent
+[RFC 2045]
+@quotation
+N. Freed and N. Borenstein, ``Multipurpose Internet Mail Extensions
+(MIME) Part One: Format of Internet Message Bodies'', November 1996,
+Standards Track (obsolete RFC 1521, 1522, 1590).
+@end quotation
+
+
+
+@node RFC 2046, RFC 2048, RFC 2045, Glossary
+@subsection RFC 2046
+
+@cindex{Standards Track}@cindex{RFC 2046}
+@noindent
+[RFC 2046]
+@quotation
+N. Freed and N. Borenstein, ``Multipurpose Internet Mail Extensions
+(MIME) Part Two: Media Types'', November 1996, Standards Track (obsolete
+RFC 1521, 1522, 1590).
+@end quotation
+
+
+
+@node RFC 2048, RFC 2049, RFC 2046, Glossary
+@subsection RFC 2048
+
+@cindex{Standards Track}@cindex{RFC 2048}
+@noindent
+[RFC 2048]
+@quotation
+N. Freed, J. Klensin and J. Postel, ``Multipurpose Internet Mail
+Extensions (MIME) Part Four: Registration Procedures'', November 1996,
+Standards Track (obsolete RFC 1521, 1522, 1590).
+@end quotation
+
+
+
+@node RFC 2049, plain text, RFC 2048, Glossary
+@subsection RFC 2049
+
+@cindex{Standards Track}@cindex{RFC 2049}
+@noindent
+[RFC 2049]
+@quotation
+N. Freed and N. Borenstein, ``Multipurpose Internet Mail Extensions
+(MIME) Part Five: Conformance Criteria and Examples'', November 1996,
+Standards Track (obsolete RFC 1521, 1522, 1590).
+@end quotation
+
+
+
+@node plain text, Security multipart, RFC 2049, Glossary
@subsection plain text
\e$B=qBN$dAHHG$K4X$9$k>pJs$r;}$?$J$$\e(B \e$BJ8;zId9f\e(B(@ref{Coded character set})\e$B$N$_\e(B
@node text/enriched, text/plain, Security multipart, Glossary
@subsection text/enriched
-RFC 1521 (@ref{RFC 1521}) \e$B$GDj5A$5$l$?\e(B
-@cindex{text/richtext}@strong{text/richtext} \e$B$KBe$o$C$F!"=qBN$dAHHG$K4X\e(B
-\e$B$9$k>pJs$r;}$C$?\e(B text\e$B$rI=8=$9$k$?$a$N\e(B content-type (@ref{content-type}).
+RFC 1521 \e$B$GDj5A$5$l$?\e(B @cindex{text/richtext}@strong{text/richtext} \e$B$KBe\e(B
+\e$B$o$C$F!"=qBN$dAHHG$K4X$9$k>pJs$r;}$C$?\e(B text\e$B$rI=8=$9$k$?$a$N\e(B media type
+(@ref{media type}).
@cindex{text/enriched}@cindex{RFC 1896}
@noindent
@node text/plain, tm-kernel, text/enriched, Glossary
@subsection text/plain
-RFC 1521 (@ref{RFC 1521}) \e$B$GDj5A$5$l$?!"\e(Bplain text (@ref{plain text}) \e$B$r\e(B
-\e$BI=8=$9$k$?$a$N\e(B content-type (@ref{content-type}).@refill
+@cindex{text/plain}@strong{text/plain} is a media type (@ref{media
+type}) for plain text (@ref{plain text}), defined in RFC 2046 (@ref{RFC
+2046}).@refill
+
+The default media type of ``text/plain; charset=us-ascii'' for Internet
+mail describes existing Internet practice. That is, it is the type of
+body defined by RFC 822 (@ref{RFC 822}).@refill
+
+(cf. @ref{MIME charset}) (cf. @ref{us-ascii})
-\e$BHs\e(B MIME message \e$B$J$I$N\e(B content-type \e$B$,Dj5A$5$l$J$$\e(B part \e$B$O\e(B MIME charset
-(@ref{MIME charset}) \e$B$,\e(B us-ascii (@ref{us-ascii}) \e$B$G$"$k\e(B
-@cindex{text/plain}@strong{text/plain} \e$B$N\e(B part \e$B$G$"$k$H8+Pv$5$l$k$3$H$K\e(B
-\e$B$J$C$F$$$k!#\e(B
@node tm-kernel, tm-MUA, text/plain, Glossary
@itemize @bullet
@item
- \e$BF|K\8l\e(B <tm-ja-admin@@chamonix.jaist.ac.jp>
+ Japanese <tm-ja-admin@@chamonix.jaist.ac.jp>
@item
- \e$B1Q8l\e(B <tm-en-admin@@chamonix.jaist.ac.jp>
+ English <tm-en-admin@@chamonix.jaist.ac.jp>
@end itemize
@noindent
projects / elisp / tm.git / blobdiff