#?SuikaWiki/0.9 page-icon="メイル" -[[MIME用語の定義]] -[[MIME適合性]] *頭欄 -[[MIME頭欄]] -[[MIMEのparameter値拡張]] ([[RFC2231]]) -符号化語 [[encoded-word]] 出来れば無視したいもの・・・。 [[#comment]] *実体本文 entity body -[[HTTP実体とMIME実体]] -[[MIMEの正規符号化モデル]] Canonical Encoding Model -[[Base64]] -[[Quoted-Printable]] *[[媒体型]] -[[application/*媒体型]] -[[audio/*媒体型]] -[[image/*媒体型]] -[[message/*媒体型]] -[[multipart/*媒体型]] -[[text/*媒体型]] -[[video/*媒体型]] *仕様書 **MIME の本体 ***RFC 1341 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) ***[[RFC1342]] ***[[RFC1521]] 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) ***[[RFC1522]] 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) ***[[RFC2045]] 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) ***[[RFC2046]] 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) ***[[RFC2047]] 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) ***[[RFC2048]] 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) ***[[RFC2049]] 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) *MIME 以前 -[[RFC934]] -[[RFC1049]] -[[RFC1154]] -[[RFC1345]] -[[draft-ietf-822ext-qreadable]] --[[Content-Type:領域]] (古い定義を参照) --Content-Charset:領域 --Mnemonic-Intro:領域 --Orig-Content-Charset:領域 *SEE ALSO -[[RFC822と仲間達の頭領域名]] -[[RFC822]] -[[RFC1036]] -[[son-of-RFC1036]] -[[RFC2822]] -[[HTTP]] -[[符号化]] - [1] [WEAK[2002-12-05 (木) 20:46]] ''[[名無しさん]]'': 20:46 なので age - [2] ''TEXT version of Draft RFC'' 一番最初の MIME draft? (91/4) - [3] MIME は設計時は (7ビット) [[SMTP]] を念頭に置きながらも、8ビット転送やバイナリ転送も考慮に入れ、それなりに汎用性を持たせたつもりだったんでしょう。時代が変わって8ビットが当たり前で、めいるの規格上だけが7ビットの現在、時代錯誤な MIME の規定をニュース向けにはねじまげようと [[CharlesLindsey]] は頑張ってます。彼曰く、 [[HTTP]] だってそうしただろう、と。 MIME'r - [4] の言い分では、 HTTP は仕方なかったんだ、失敗だった (標準化以前にどんどん実装が進んじゃったんだから仕方ないよねぇ。) だけどこれ以上 MIME variant を増やして複雑化させるな、と。 - [5] >>3-4 どっちの言い分も分かるんだけど、ニュース版 MIME はちょっとこじつけの感があるし、実際ほとんどの MIME 実装は7ビットなメイル MIME で実装してる (ニュース向けにも。) 以上、混乱は必死だろうし。 - [6] >>3-5 HTTP MIME がメイル MIME と随分仕様が違うのは HTTP<=>メイル関門なんて存在しないから問題にならないけど、メイル<=>ニュースは大問題だしね。 - [7] >>3-6 いっそぼろぼろの MIME なんてやめて、 (822 を捨てた [[CPIM]] みたいに) 1からやりなおしたら、とも思うんだけど、 CPIM だって MIME を使うんだよなあ。