7 - 8 - A - B - C - D - E - F - G - H - I - J - K - L - M - N - O - P - Q - R - S - T - U - V - W - X
MIME
Click on the red underlined text to get to the source
...
The first and second documents in this set define MIME header fields
and the initial set of MIME media types. The third document
...
... The first and second documents in this set define MIME header fields
and the initial set of MIME media types. The third document
describes extensions to RFC 822std11(-> 2822prop) formats to allow for character sets ...
... character sets
other than US-ASCII. This document describes what portions of MIME
must be supported by a conformant MIME implementation. It also
...
... US-ASCII. This document describes what portions of MIME
must be supported by a conformant MIME implementation. It also
describes various pitfalls of contemporary messaging systems as well
...
... MIME Conformance ...
... extensions. In order to promote interoperability, however, it is
useful to define the concept of "MIME-conformance" to define a
certain level of implementation that allows the useful interworking
...
...
A mail user agent that is MIME-conformant MUST:
...
... (8) Conformant user agents are required, if they provide
non-standard support for non-MIME messages employing
character sets other than US-ASCII ...
... received messages only. Conforming user agents must not
send non-MIME messages containing anything other than
US-ASCII text.
...
... In particular, the use of non-US-ASCII text in mail
messages without a MIME-Version field is strongly
discouraged as it impedes interoperability when sending
...
... conventions. Conforming user agents MUST include proper
MIME labelling when sending anything other than plain
text in the US-ASCII character set ...
... character set.
In addition, non-MIME user agents should be upgraded if
at all possible to include appropriate MIME header ...
... MIME user agents should be upgraded if
at all possible to include appropriate MIME header
information in the messages they send even if nothing
else in MIME ...
... MIME header
information in the messages they send even if nothing
else in MIME is supported. This upgrade will have
little, if any, effect on non-MIME recipients and will
...
... else in MIME is supported. This upgrade will have
little, if any, effect on non-MIME recipients and will
aid MIME in correctly displaying such messages. It
...
... little, if any, effect on non-MIME recipients and will
aid MIME in correctly displaying such messages. It
also provides a smooth transition path to eventual
adoption of other MIME ...
... MIME in correctly displaying such messages. It
also provides a smooth transition path to eventual
adoption of other MIME capabilities.
(9) Conforming user agents ...
...
A user agent that meets the above conditions is said to be MIME-
conformant. The meaning of this phrase is that it is assumed to be
"safe" to send virtually any kind of properly-marked data to users of
...
...
There is another sense in which it is always "safe" to send data in a
format that is MIME-conformant, which is that such data will not
break or be broken by any known systems that are conformant with RFC
821std10(-> 2821prop) ...
... 821std10(-> 2821prop) and RFC 822std11(-> 2822prop). User agents that are MIME-conformant have the
additional guarantee that the user will not be shown data that were
never intended to be viewed as text.
...
...
The process of composing a MIME entity can be modeled as being done
in a number of steps. Note that these steps are roughly similar to
...
... these formats are not canonical RFC 822std11(-> 2822prop)/MIME. These formats are
instead *encodings* of RFC 822std11(-> 2822prop) ...
... CRLF sequences as, for
example, LF are not capable of representing MIME messages containing
binary data which contains LF ...
...
This document defines what is meant by MIME Conformance. It also
details various problems known to exist in the Internet email system
...
... details various problems known to exist in the Internet email system
and how to use MIME to overcome them. Finally, it describes MIME's
canonical ...
... Internet email system
and how to use MIME to overcome them. Finally, it describes MIME's
canonical encoding ...
... EMail: nsb@nsb.fv.com
MIME is a result of the work of the Internet Engineering Task Force
Working Group ...
...
MIME-Version: 1.0
From: Nathaniel Borenstein <nsb@nsb.fv.com>
To: Ned Freed <ned@innosoft.com>
...
...
(2) BNF describing the overall structure of MIME object
headers has been added. This is a documentation change
only -- the underlying syntax has not changed in any
...
... since the type-independent BNF already fully specifies
the syntax of the various MIME headers, the type-
specific BNF was, in the final analysis, completely
...
... beginning with the boundary parameter string.
(9) In the rules on reassembling "message/partial" MIME
entities, "Subject" is added to the list of headers to
...
...
(10) "Message/partial" fragmenters are restricted to
splitting MIME objects only at line boundaries.
(11) In the discussion ...
... removed from the
discussion of the MIME-Version header: "However,
conformant software is encouraged to check the version
number ...
... conformant software is encouraged to check the version
number and at least warn the user if an unrecognized
MIME-version is encountered."
(14) A typo was fixed that said "application/external-body"
...
... as end-of-line sequences. The document also no longer
requires that NUL characters be preserved, which brings
MIME into alignment with real-world implementations.
(18) The definition of canonical ...
...
(18) The definition of canonical text in MIME has been
tightened so that line breaks must be represented by a
...
... 8bit" or "binary" data.
(21) In the section on MIME Conformance, "multipart/digest"
support was added to the list of requirements for
...
... support was added to the list of requirements for
minimal MIME conformance. Also, the requirement for
"message/rfc822" support were strengthened to clarify
...
... header field.
(27) MIME media types that are simply registered for use and
those that are standardized by the IETF are now
...
... BNF.
(28) All of the various MIME registration procedures have
been extensively revised. IANA registration procedures
...
... Borenstein, N., and N. Freed, "MIME (Multipurpose Internet Mail Extensions): Mechanisms for Specifying and Describing the Format of Internet Message Bodies", RFC 1341(-> 1521(-> 2049draft | 2048(-> 4289 | 4288) | 2047draft | 2046draft | 2045draft)) ...
... Borenstein, N., and Freed, N., "MIME (Multipurpose Internet Mail Extensions): Mechanisms for Specifying and Describing the Format of Internet Message Bodies", RFC 1521(-> 2049draft | 2048(-> 4289 | 4288) | 2047draft | 2046draft | 2045draft) ...
... Nussbacher, H., "Handling of Bi-directional Texts in MIME", RFC 1556, Israeli Inter-University Computer Center, December 1993. ...
... WG Chair), Freed, N., (Editor), Rose, M., Stefferud, E., and Crocker, D., "SMTP Service Extension for 8bit-MIME transport", RFC 1652draft, United Nations University, Innosoft, Dover Beach Consulting, Inc., Network Management ...
... Faltstrom, P., Crocker, D., and Fair, E., "MIME Content Type for BinHex Encoded Files", December 1994. ...
... Resnick, P., and A. Walker, "The text/enriched MIME Content-type", RFC 1896, February, 1996. ...
... Freed, N., and and N. Borenstein, "Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet Message Bodies", RFC 2045draft, Innosoft, First Virtual Holdings, November 1996. ...
... Freed, N., and N. Borenstein, "Multipurpose Internet Mail Extensions (MIME) Part Two: Media Types", RFC 2046draft, Innosoft, First Virtual Holdings, November 1996. ...
... Moore, K., "Multipurpose Internet Mail Extensions (MIME) Part Three: Representation of Non-ASCII Text in Internet Message Headers ...
... Freed, N., Klensin, J., and J. Postel, "Multipurpose Internet Mail Extensions (MIME) Part Four: MIME Registration Procedures", RFC 2048(-> 4289 | 4288), Innosoft, MCI, ISI, November 1996. ...
... Freed, N., Klensin, J., and J. Postel, "Multipurpose Internet Mail Extensions (MIME) Part Four: MIME Registration Procedures", RFC 2048(-> 4289 | 4288), Innosoft, MCI, ISI, November 1996. ...
... Freed, N. and N. Borenstein, "Multipurpose Internet Mail Extensions (MIME) Part Five: Conformance Criteria and Examples", RFC 2049draft (this document), Innosoft, First Virtual Holdings, November 1996. ...