1 - 2 - 7 - 8 - A - B - C - D - E - F - G - H - I - J - L - M - N - O - P - Q - R - S - T - U - V - W - X
Internet
Click on the red underlined text to get to the source
... RFC-822] has defined
the standard format of textual mail messages on the Internet. Its
success has been such that the RFC 822std11(-> 2822prop) format has been adopted,
...
... success has been such that the RFC 822std11(-> 2822prop) format has been adopted,
wholly or partially, well beyond the confines of the Internet and the
Internet SMTP ...
... wholly or partially, well beyond the confines of the Internet and the
Internet SMTP transport defined by STD ...
... and receive mail). Examples of such encodings currently used in the
Internet include pure hexadecimal, uuencode, the 3-in-4 base 64
scheme specified in RFC 1421hist, the Andrew Toolkit Representation
...
... message
handling system (i.e., the X.400 message is "tunneled" through
Internet mail), where the non-textual information would definitely
become useful again.
...
... MIME defines a registration process which uses the
Internet Assigned Numbers Authority (IANA) as a central registry for
...
... Since RFC 822std11(-> 2822prop) was published in 1982, there has really been only one
format standard for Internet messages, and there has been little
perceived need to declare the format standard in use. This document
is an independent document that complements RFC 822std11(-> 2822prop) ...
... MIME-Version",
which is to be used to declare the version of the Internet message
body format standard in use.
...
... [RFC-1426]. As of the publication of this document, there are no
standardized Internet mail transports for which it is legitimate
to include unencoded binary data ...
... no circumstances in which the "binary" Content-Transfer-Encoding
is actually legal on the Internet. However, in the event that
binary mail transport becomes a reality in Internet mail ...
... Internet. However, in the event that
binary mail transport becomes a reality in Internet mail, or when
this document is used in conjunction with any other binary-capable
...
... transport, in the same manner that plain text mail has always been
altered in Internet mail when passing between systems with differing
newline conventions. If such alterations are likely to constitute a
corruption of the data, it is probably more sensible to use the
...
... text/plain", which indicates plain (unformatted) text. The
default Content-Type for Internet mail is "text/plain; charset=us-
...
... ISO-646] are NOT ASCII and their use in
Internet mail is explicitly discouraged. The omission of the ISO 646
character set ...
... character sets have deliberately been omitted in favor of
their 8859 replacements, which are the designated character
sets for Internet mail. As of the publication of this
document, the legitimate values for "X" are the digits 1
through 9.
...
...
No other character set name may be used in Internet mail without the
publication of a formal specification and its registration with IANA ...
... The primary subtype of text is "plain". This indicates plain
(unformatted) text. The default Content-Type for Internet mail,
"text/plain; charset ...
... "text/plain; charset=us-ascii", describes existing Internet practice.
That is, it is the type of body defined by RFC 822std11(-> 2822prop).
...
... 822std11(-> 2822prop) message and a body part
is subtle, but important. A gateway between Internet and X.400
mail, for example, must be able to tell the difference between a
...
... be in force. (That is, the transport domains may resemble
standard Internet mail transport as specified in RFC821std10(-> 2821prop) and
...
... is similar to IP fragmentation/reassembly in the basic Internet
Protocols.) This mechanism can be used when intermediate transport
agents ...
... violated, and care has been taken to avoid problems caused by
additional restrictions imposed by the characteristics of some
Internet mail transport mechanisms (see Appendix B). The "multipart"
and "message" Content-Types ...
...
For more information, the authors of this document may be contacted
via Internet mail:
Nathaniel S. Borenstein
...
...
Internet email is not a perfect, homogeneous system. Mail may become
corrupted at several stages in its travel to a final destination.
...
... destination.
Specifically, email sent throughout the Internet may travel across
many networking technologies. Many networking and mail technologies
do not support the full functionality possible in the SMTP ...
...
There exist many widely-deployed non-conformant MTAs in the Internet.
These MTAs, speaking the SMTP ...
... EBCDIC system. Similar problems can occur without crossing a
gateway, since many Internet hosts use character sets other than
...
... be in force. (That is, the transport domains may resemble
standard Internet mail transport as specified in RFC821std10(-> 2821prop) and
...
... MIME
defines a registration process which uses the Internet Assigned
Numbers Authority (IANA) as a central registry for such values.
...
... published as an RFC or submitted in a form suitable to become an RFC,
and be subject to the Internet standards process.
To: IANA ...
... Published specification:
(The published specification must be an Internet RFC or
RFC-to-be if a new top-level type is being defined, and
...
... Published specification:
(The published specification must be an Internet RFC or
RFC-to-be.)
...
... Crocker, D., "Standard for the Format of ARPA Internet Text Messages", STD 11, RFC 822std11(-> 2822prop) ...
... Sirbu, M., "Content-Type Header Field for Internet Messages", STD 11, RFC 1049hist, CMU, March 1988. ...
... Linn, J., "Privacy Enhancement for Internet Electronic Mail: Part I - Message Encryption and Authentication Procedures", RFC 1421hist ...
... Robinson, D. and R. Ullmann, "Encoding Header Field for Internet Messages", RFC 1154(-> 1505exp), Prime Computer, Inc., April 1990. ...
... 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)), Bellcore, Innosoft, June 1992. ...
... 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)), Bellcore, Innosoft, June 1992. ...
... Moore, K., "Representation of Non-Ascii Text in Internet Message Headers", RFC 1342(-> 1522(-> 2049draft | 2048(-> 4289 | 4288) | 2047draft | 2046draft | 2045draft)), University of Tennessee, June 1992. ...
... Borenstein, N., "Implications of MIME for Internet Mail Gateways", RFC 1344, Bellcore, June 1992. ...
... Moore, K., "Representation of Non-Ascii Text in Internet Message Headers" RFC 1522(-> 2049draft | 2048(-> 4289 | 4288) | 2047draft | 2046draft | 2045draft), University of Tennessee, September 1993. ...