Jump to content

User:RokerHRO/MIME

From Wikipedia, the free encyclopedia

Collection of some e-mail- and MIME-related RFCs to help me to sort my mind. :-)

822

[edit]
RFC 822 – STANDARD FOR THE FORMAT OF ARPA INTERNET TEXT MESSAGES
  • The mother of the nightmare… ;-(
  • Obsoleted by: #2822

1847

[edit]
RFC 1847 – Security Multiparts for MIME: Multipart/Signed and Multipart/Encrypted
  • Refers to RFC 1521, but doesn't mention it in its "Updates" section. :-(
  • OLDER THAN #2046 that defines MIME "multipart" messages, but not mentioned there.

2044

[edit]
RFC 2044 – UTF-8, a transformation format of Unicode and ISO 10646
  • October 1996
  • Obsoleted by: #2279

2045

[edit]
RFC 2045 – "MIME Part One: Format of Internet Message Bodies"
  • November 1996
  • Obsoletes: 1521, 1522, 1590
  • Updated by: #2184, #2231, #5335, #6532
  • Defines "Quoted-Printable Content-Transfer-Encoding" and "Base64 Content-Transfer Encoding"

2046

[edit]
RFC 2046 – "MIME Part Two: Media Types"
  • November 1996
  • Obsoletes: 1521, 1522, 1590
  • Updated by: #2646, #3798, #5147, #6657, #8098
  • Content:
    • Explains Mime-Types "text" and its subtype "text/plain"
    • "message/rfc822"
    • "multipart/alternative"
    • "multipart/mixed" etc.

2047

[edit]
RFC 2047 – "MIME Part Three: Message Header Extensions for Non-ASCII Text"
* Obsoletes: 1521, 1522, 1590
  • Updated by: #2184, #2231
  • Content:
    • Defines encoded-word: =?charset?Q/B?encoded_text?=

2183

[edit]
RFC 2183 – Communicating Presentation Information in Internet Messages: The Content-Disposition Header Field
* August 1997
  • Updates: 1806
  • Updated by: 2184, 2231
  • Changes since 1806:
    • Added new parameter types: creation-date, modification-date, read-date, and size.

2184

[edit]
RFC 2184 – MIME Parameter Value and Encoded Word Extensions: Sets, Languages, and Continuations

2231

[edit]
RFC 2231 – MIME Parameter Value and Encoded Word Extensions: Character Sets, Languages, and Continuations
  • November 1997
  • Obsoletes: #2184
  • Updates: #2045, #2047, #2183
  • Content:
    • Extensions to #2045 and #2183 (Content-Dispositon) to allow Non-ASCII characters in values and how to split overlong values into several lines
    • Extensions to "Encoded Word" syntax from 2047 to contain a language tag
  • Changes to #2184: Hm, unclear: Not mentioned explicitly in this RFC. :-(

2279

[edit]
RFC 2279 – UTF-8, a transformation format of ISO 10646
  • Januar 1998
  • Obsoleted by: #3629

2646

[edit]
RFC 2646 –  The Text/Plain Format Parameter

2822

[edit]
RFC 2822 – "Internet Message Format"

3156

[edit]
RFC 3156 – MIME Security with OpenPGP
 
  • August 2001
  • Updates: RFC 2015 (and "implements" RFC #1847)
  • Content:
    • Defines PGP/MIME format according to #1847
 Content-Type: multipart/encrypted; boundary=foo;
        protocol="application/pgp-encrypted"
 
     --foo
     Content-Type: application/pgp-encrypted
 
     Version: 1
 
     --foo
     Content-Type: application/octet-stream
 
     -----BEGIN PGP MESSAGE-----
     Version: 2.6.2
 
     hIwDY32hYGCE8MkBA/wOu7d45aUxF4Q0RKJprD3v5Z9K1YcRJ2fve87lMlDlx4Oj
     eW4GDdBfLbJE7VUpp13N19GL8e/AqbyyjHH4aS0YoTk10QQ9nnRvjY8nZL3MPXSZ
     g9VGQxFeGqzykzmykU6A26MSMexR4ApeeON6xzZWfo+0yOqAq6lb46wsvldZ96YA
     AABH78hyX7YX4uT1tNCWEIIBoqqvCeIMpp7UQ2IzBrXg6GtukS8NxbukLeamqVW3
     1yt21DYOjuLzcMNe/JNsD9vDVCvOOG3OCi8=
     =zzaA
     -----END PGP MESSAGE-----
 
     --foo--
.

3629

[edit]
RFC 3629 – UTF-8, a transformation format of ISO 10646
  • November 2003
  • Obsoletes: #2279
  • Changes from RFC 2279:
    • Restricted the range of characters to 0000-10FFFF (the UTF-16 accessible range).
    • Turned the note warning against decoding of invalid sequences into a normative MUST NOT.
    • Expanded Security Considerations section, in particular impact of Unicode normalization

3676

[edit]
RFC 3676 – The Text/Plain Format and DelSp Parameters
  • February 2004
  • Obsoletes: #2646
  • Changes to 2646:
    • Changed the limits of 79 or 80 to be 78 in conformance with RFC 2822.
    • Added DelSp parameter to handle languages and coded character sets in which space is less common or not used.
    • Added recommendations for OpenPGP and OpenPGP-MIME.
    • Changed some SHOULDs to MUSTs (space-stuffing, quoted paragraphs).
    • (etc.)

3798

[edit]
RFC 3798 – Message Disposition Notification
  • May 2004
  • Obsoletes: #2298
  • Updates: #3461, #2046
  • Updated by: #5337, #6533
  • Obsoleted by: #8098
  • Changes to 2298:
    • The dispositions "denied", and "failed" were removed
    • The disposition modifiers "warning", "superseded", "expired", "mailbox-terminated" have […] been deleted from this document.

5147

[edit]
RFC 5147 – URI Fragment Identifiers for the text/plain Media Type
 

5198

[edit]
RFC 5198 – Unicode Format for Network Interchange
  • March 2008
  • Updates: 854
  • Obsoletes: 698
  • Content:
    • Defines "Net-Unicode" as successor to "Net-ASCII"
    • enforces UTF-8 and NFC, and CR LF as line ending, forbids BOM etc…

5322

[edit]
RFC 5322 – Internet Message Format
  • October 2008
  • Obsoletes: #2822
  • Updates: #4021
  • Updated by: #6854
  • Remarks:
    • Header field syntax is extended in #6532 for international values (but not mentioned in the "Updated by" line above)
  • Content:
    • Tightens the syntax rules for Header fields.
    • Allows a lot of older formats for parsers, but not for generators ("obs-" rules in the ABNF grammar, described in its own section 4.
    • Simplified "Bcc:" and "Resent-Bcc:" syntax.
    • Generalized "Received:" syntax to fix bugs and move definition out of this document. (now: RFC 5321)

5335

[edit]
RFC 5335 – Internationalized Email Headers

5336

[edit]
RFC 5336 – SMTP Extension for Internationalized Email Addresses
  • September 2008
  • Updates: 2821, 2822, 4952
  • Obsoleted by: #6531

6531

[edit]
RFC 6531 – SMTP Extension for Internationalized Email
  • February 2012
  • Obsoletes: #5336

6532

[edit]
RFC 6532 – Internationalized Email Headers
 
  • February 2012
  • Obsoletes: #5335
  • Updates: #2045
  • Remarks:
    • Extends syntax of header fields defined in #5322 to allow non-ASCII Unicode values. (This semantic link is not mentioned in the RFC headers… *sigh*)
    • Refers to RFC #5198 for Unicode normalization.
  • Content:
    • "The following rules extend the ABNF syntax defined in RFC 5322 and RFC 5234 in order to allow UTF-8 content. […] VCHAR, ctext, atext, qtext, text, dtext […]"
    • The new ABNF rule is: UTF8-non-ascii = UTF8-2 / UTF8-3 / UTF8-4

6657

[edit]
RFC 6657 – Update to MIME regarding "charset" Parameter Handling in Textual Media Types
 
  • July 2012
  • Updates: #2046
  • not relevant for e-Mail.

6854

[edit]
RFC 6854 – Update to Internet Message Format to Allow Group Syntax in the "From:" and "Sender:" Header Fields
  • March 2013
  • Updates: #5322

8098

[edit]
RFC 8098 – Message Disposition Notification
  • February 2017
  • Updates: #2046, #3461
  • Obsoletes: #3798
  • Changes to 3798:
    • "X-" fields no longer reserved for experimental use and can now be registered in compliance with RFC 6648.
    • many clarifications and errata fixes…
  • "Disposition-Notification-To" ":" mailbox-list CRLF
  • "Disposition-Notification-Options" ":" [FWS] disposition-notification-parameter-list CRLF
  • "Original-Recipient" ":" OWS address-type OWS ";" OWS generic-address OWS
Retrieved from "https://en.wikipedia.org/w/index.php?title=User:RokerHRO/MIME&oldid=1015754332"