MIME (Multipurpose Internet Mail Extensions): Mechanisms for Specifying and Describing the Format of Internet Message Bodies. N. Borenstein, N. Freed. June 1992. (Format: TXT=211117, PS=347082, PDF=192244 bytes) (Obsoleted by RFC1521) (Status: PROPOSED STANDARD)
1521 MIME (Multipurpose Internet Mail Extensions) Part One: Mechanisms
for Specifying and Describing the Format of Internet Message Bodies.
N. Borenstein, N. Freed. September 1993. (Format: TXT=187424,
PS=393670, PDF=205091 bytes) (Obsoletes RFC1341) (Obsoleted by
RFC2045, RFC2046, RFC2047, RFC2048, RFC2049) (Updated by RFC1590)
(Status: DRAFT STANDARD)1522 MIME (Multipurpose Internet Mail Extensions) Part Two: Message
Header Extensions for Non-ASCII Text. K. Moore. September 1993.
(Format: TXT=22502 bytes) (Obsoletes RFC1342) (Obsoleted by RFC2045,
RFC2046, RFC2047, RFC2048, RFC2049) (Status: DRAFT STANDARD)1590 Media Type Registration Procedure. J. Postel. March 1994.
(Format: TXT=13044 bytes) (Obsoleted by RFC2045, RFC2046, RFC2047,
RFC2048, RFC2049) (Updates RFC1521) (Status: INFORMATIONAL)2045 Multipurpose Internet Mail Extensions (MIME) Part One: Format of
Internet Message Bodies. N. Freed, N. Borenstein. November 1996.
(Format: TXT=72932 bytes) (Obsoletes RFC1521, RFC1522, RFC1590)
(Updated by RFC2184, RFC2231) (Status: DRAFT STANDARD)2046 Multipurpose Internet Mail Extensions (MIME) Part Two: Media
Types. N. Freed, N. Borenstein. November 1996. (Format: TXT=105854
bytes) (Obsoletes RFC1521, RFC1522, RFC1590) (Updated by RFC2646)
(Status: DRAFT STANDARD)2047 MIME (Multipurpose Internet Mail Extensions) Part Three: Message
Header Extensions for Non-ASCII Text. K. Moore. November 1996.
(Format: TXT=33262 bytes) (Obsoletes RFC1521, RFC1522, RFC1590)
(Updated by RFC2184, RFC2231) (Status: DRAFT STANDARD)2048 Multipurpose Internet Mail Extensions (MIME) Part Four:
Registration Procedures. N. Freed, J. Klensin, J. Postel. November
1996. (Format: TXT=45033 bytes) (Obsoletes RFC1521, RFC1522, RFC1590)
(Updated by RFC3023) (Also BCP0013) (Status: BEST CURRENT PRACTICE)2049 Multipurpose Internet Mail Extensions (MIME) Part Five:
Conformance Criteria and Examples. N. Freed, N. Borenstein. November
1996. (Format: TXT=51207 bytes) (Obsoletes RFC1521, RFC1522, RFC1590)
(Status: DRAFT STANDARD)2184 MIME Parameter Value and Encoded Word Extensions: Character Sets,
Languages, and Continuations. N. Freed, K. Moore. August 1997.
(Format: TXT=17635 bytes) (Obsoleted by RFC2231) (Updates RFC2045,
RFC2047, RFC2183) (Status: PROPOSED STANDARD)2231 MIME Parameter Value and Encoded Word Extensions: Character Sets,
Languages, and Continuations. N. Freed, K. Moore. November 1997.
(Format: TXT=19280 bytes) (Obsoletes RFC2184) (Updates RFC2045,
RFC2047, RFC2183) (Status: PROPOSED STANDARD)1344 Implications of MIME for Internet Mail Gateways. N. Borenstein.
June 1992. (Format: TXT=25872, PS=51812, PDF=24430 bytes) (Status:
INFORMATIONAL)1820 Multimedia E-mail (MIME) User Agent Checklist. E. Huizer. August
1995. (Format: TXT=14672 bytes) (Obsoleted by RFC1844) (Status:
INFORMATIONAL)1844 Multimedia E-mail (MIME) User Agent Checklist. E. Huizer. August
1995. (Format: TXT=15072 bytes) (Obsoletes RFC1820) (Status:
INFORMATIONAL)7bit。拡張された SMTP
では 8bit や binary)8bit)OPTION MIME では MIME が使われます。
(転送路: 8bit)message/cpim の2番目の部分は MIME
が使われます。
(転送路: ?)TRACK
命令の応答に MIME が使われます。
(転送路: 8bit)binary)binary)binary)binary)[23] MSRP (RFC 4975): RFC 822/MIME もどきなメッセージの書式を使いますが、本体を含む場合、 MIME が用いられます。ただし、頭欄の構文に若干の (実用上は影響しない程度の) 違いがあります。
[24] POファイルは実際には MIME ではありませんが、 MIME 風の頭欄のようなものを記述することになっています。
[20]
インターネット媒体型のことを MIME
と呼ぶのは完全な誤りです。
MIME型
と呼ぶなら (よくないけど) まだしも。
(名無しさん [sage])
[21] RFC 2048 (登録手続き) は改訂され、 RFC 4289 (MIME の登録手続き) と RFC 4288 (媒体型の登録手続き) になりました。どちらも BCP 13 のようです。
(名無しさん 2005-12-21 08:43:47 +00:00)
[25] トルカ | サービス・機能 | NTTドコモ ( 版) <http://www.nttdocomo.co.jp/service/imode/make/content/toruca/index.html>