=============== MIME TXT A1 LINE 253 ========================== 4. Two optional header fields that can be used to further describe the data in a message body or body part, the Content-ID and Content-Description header fields. --------------- MIMEAF TXT A1 LINE 253 4. Two optional header fields that can be used to further describe the data in a message body , the Content-ID and Content-Description header fields. =============== MIME TXT A1 LINE 336 ========================== In this document, all numeric and octet values are given in --------------- MIMEAF TXT A1 LINE 336 The term "message", when not further qualified, means either the (complete or "top-level") message being transferred on a network, or a message encapsulated in a body of type "message". The term "body part", in this document, means one of the parts of the body of a multipart entity. A body part has a header and a body, so it makes sense to speak about the body of a body part. The term "entity", in this document, means either a message or a body part. All kinds of entities share the property that they have a header and a body. The term "body", when not further qualified, means the body of an entity, that is the body of either a message or of a body part. Note : the above set of four definitions is clearly circular. This is unavoidable, since the overal structure of a MIME message is indeed recursive. In this document, all numeric and octet values are given in =============== MIME TXT A1 LINE 432 ========================== Note that the MIME-Version header field is required at the top level of a message. It is not required for each body part of a multipart message. It is required for the embedded headers of a body or body part of type "message" if and only if the embedded message is itself claimed to be --------------- MIMEAF TXT A1 LINE 451 Note that the MIME-Version header field is required for a top-level message only. It is not required for each body part of a multipart entity. It is required for the embedded headers in a body of type "message" if and only if the embedded message is itself claimed to be =============== MIME TXT A1 LINE 464 ========================== The purpose of the Content-Type field is to describe the data contained in the message body fully enough that the receiving user agent can pick an appropriate agent or --------------- MIMEAF TXT A1 LINE 483 The purpose of the Content-Type field is to describe the data contained in the body fully enough that the receiving user agent can pick an appropriate agent or =============== MIME TXT A1 LINE 476 ========================== The Content-Type header field is used to specify the nature of the data in a message, by giving type and subtype identifiers, and by providing auxiliary information that may --------------- MIMEAF TXT A1 LINE 495 The Content-Type header field is used to specify the nature of the data in the body of an entity, by giving type and subtype identifiers, and by providing auxiliary information that may =============== MIME TXT A1 LINE 484 ========================== Among the defined parameters is a "charset" parameter by which the character set used in the message body or body part may be declared. Comments are allowed in accordance with RFC 822 rules for structured header fields. --------------- MIMEAF TXT A1 LINE 504 Among the defined parameters is a "charset" parameter by which the character set used in the body may be declared. Comments are allowed in accordance with RFC 822 rules for structured header fields. =============== MIME TXT A1 LINE 623 ========================== but such software must not be required in order to get the general idea of the message. Possible subtypes thus include any readable word processor --------------- MIMEAF TXT A1 LINE 643 but such software must not be required in order to get the general idea of the content. Possible subtypes thus include any readable word processor =============== MIME TXT A1 LINE 633 ========================== intended to be viewed simultaneously, and "digest" for multipart messages in which each part is of type "message". message -- an encapsulated message. A message body of Content-Type "message" is itself a fully formatted --------------- MIMEAF TXT A1 LINE 653 intended to be viewed simultaneously, and "digest" for multipart entities in which each part is of type "message". message -- an encapsulated message. A body of Content-Type "message" is itself a fully formatted =============== MIME TXT A1 LINE 641 ========================== subtype is defined for partial messages, to permit the fragmented transmission of message bodies that are thought to be too large to be passed through --------------- MIMEAF TXT A1 LINE 661 subtype is defined for partial messages, to permit the fragmented transmission of bodies that are thought to be too large to be passed through =============== MIME TXT A1 LINE 656 ========================== message bodies by reference to an external data source. --------------- MIMEAF TXT A1 LINE 676 bodies by reference to an external data source. =============== MIME TXT A1 LINE 664 ========================== audio -- audio data, with initial subtype "basic". Such messages contain information which requires an audio output device (such as a speaker or a --------------- MIMEAF TXT A1 LINE 684 audio -- audio data, with initial subtype "basic". Audio requires an audio output device (such as a speaker or a =============== MIME TXT A1 LINE 680 ========================== are defined for transporting ODA and PostScript documents in message bodies. Other expected uses for "application" include spreadsheets, data for --------------- MIMEAF TXT A1 LINE 700 are defined for transporting ODA and PostScript documents in bodies. Other expected uses for "application" include spreadsheets, data for =============== MIME TXT A1 LINE 749 ========================== type of transformation that has been used in order to represent the message body part in an acceptable manner for transport. --------------- MIMEAF TXT A1 LINE 769 type of transformation that has been used in order to represent the body in an acceptable manner for transport. =============== MIME TXT A1 LINE 790 ========================== BASE64 and bAsE64 are all equivalent. An encoding type of 7BIT requires that the message is already in a seven-bit mail-ready representation. This is the default value -- --------------- MIMEAF TXT A1 LINE 810 BASE64 and bAsE64 are all equivalent. An encoding type of 7BIT requires that the body is already in a seven-bit mail-ready representation. This is the default value -- =============== MIME TXT A1 LINE 811 ========================== to the SMTP CR/LF semantics, while the bit-width tokens do require such adherence. If the message contains data in any bit-width other than 7-bit, the appropriate bit-width --------------- MIMEAF TXT A1 LINE 831 to the SMTP CR/LF semantics, while the bit-width tokens do require such adherence. If the body contains data in any bit-width other than 7-bit, the appropriate bit-width =============== MIME TXT A1 LINE 814 ========================== Content-Transfer-Encoding token must be used (e.g., "8bit" for unencoded 8 bit wide data). If the message contains binary data, the "binary" Content-Transfer-Encoding token --------------- MIMEAF TXT A1 LINE 834 Content-Transfer-Encoding token must be used (e.g., "8bit" for unencoded 8 bit wide data). If the body contains binary data, the "binary" Content-Transfer-Encoding token =============== MIME TXT A1 LINE 838 ========================== conjunction with any other 8-bit or binary-capable transport mechanism, 8-bit or binary messages should be labeled as such using this mechanism. --------------- MIMEAF TXT A1 LINE 858 conjunction with any other 8-bit or binary-capable transport mechanism, 8-bit or binary bodies should be labeled as such using this mechanism. =============== MIME TXT A1 LINE 869 ========================== If a Content-Transfer-Encoding header field appears as part of a message header, it applies to the entire message body. If a Content-Transfer-Encoding header field appears as part of a multipart message body part's headers, it applies only to the body part. If the body part is itself of type "multipart" or "message", the Content-Transfer-Encoding is --------------- MIMEAF TXT A1 LINE 889 If a Content-Transfer-Encoding header field appears as part of a message header, it applies to the entire body of that message. If a Content-Transfer-Encoding header field appears as part of a body part's headers, it applies only to the body of that body part. If an entity is of type "multipart" or "message", the Content-Transfer-Encoding is =============== MIME TXT A1 LINE 890 ========================== The encoding mechanisms defined here explicitly encode all data in ASCII. Thus, for example, suppose a message has header fields such as: --------------- MIMEAF TXT A1 LINE 912 The encoding mechanisms defined here explicitly encode all data in ASCII. Thus, for example, suppose an entity has header fields such as: =============== MIME TXT A1 LINE 896 ========================== This should be interpreted to mean that the message body (or body part) is a base64 ASCII encoding of data that was originally in ISO-8859-1, and will be in that character set --------------- MIMEAF TXT A1 LINE 918 This should be interpreted to mean that the body is a base64 ASCII encoding of data that was originally in ISO-8859-1, and will be in that character set =============== MIME TXT A1 LINE 928 ========================== bodies of type multipart or message must be done at the innermost level, by encoding the actual body part that needs to be encoded. --------------- MIMEAF TXT A1 LINE 950 bodies of type multipart or message must be done at the innermost level, by encoding the actual body that needs to be encoded. =============== MIME TXT A1 LINE 967 ========================== under different circumstances. For example, many PostScript messages might consist entirely of short lines of 7-bit data and hence require little or no encoding. Other PostScript messages --------------- MIMEAF TXT A1 LINE 989 under different circumstances. For example, many PostScript bodies might consist entirely of short lines of 7-bit data and hence require little or no encoding. Other PostScript bodies =============== MIME TXT A1 LINE 1003 ========================= mostly ASCII text, the encoded form of the data remains largely recognizable by humans. A message which is entirely ASCII may also be encoded in Quoted-Printable to ensure the --------------- MIMEAF TXT A1 LINE 1025 mostly ASCII text, the encoded form of the data remains largely recognizable by humans. A body which is entirely ASCII may also be encoded in Quoted-Printable to ensure the =============== MIME TXT A1 LINE 1061 ========================= characters from the end of a line. Therefore, when decoding a Quoted-Printable message, any trailing white space on a line must be deleted, as it will necessarily --------------- MIMEAF TXT A1 LINE 1083 characters from the end of a line. Therefore, when decoding a Quoted-Printable body , any trailing white space on a line must be deleted, as it will necessarily =============== MIME TXT A1 LINE 1113 ========================= the Quoted-Printable encoding, care must be taken, when encapsulating a quoted-printable encoded message or body part in a multipart message, to ensure that the encapsulation boundary does not appear anywhere in the message. (A good strategy is to choose a boundary that includes a character sequence such as "=_" which can never appear in a quoted-printable body part. See the definition of multipart messages later in this document.) --------------- MIMEAF TXT A1 LINE 1135 the Quoted-Printable encoding, care must be taken, when encapsulating a quoted-printable encoded body in a multipart entity , to ensure that the encapsulation boundary does not appear anywhere in the encoded body. (A good strategy is to choose a boundary that includes a character sequence such as "=_" which can never appear in a quoted-printable body. See the definition of multipart messages later in this document.) =============== MIME TXT A1 LINE 1123 ========================= something of a compromise between readability and reliability in transport. Message bodies encoded with the quoted-printable encoding will work --------------- MIMEAF TXT A1 LINE 1146 something of a compromise between readability and reliability in transport. Bodies encoded with the quoted-printable encoding will work =============== MIME TXT A1 LINE 1129 ========================= EBCDIC gateway could decode a quoted-printable message and re-encode it using base64, but such gateways do not yet exist.) A higher level of --------------- MIMEAF TXT A1 LINE 1152 EBCDIC gateway could decode a quoted-printable body and re-encode it using base64, but such gateways do not yet exist.) A higher level of =============== MIME TXT A1 LINE 1275 ========================= encoding quantum is always completed at the end of a message. When fewer than 24 input bits are available in an input group, zero bits are added (on the right) to form an --------------- MIMEAF TXT A1 LINE 1298 encoding quantum is always completed at the end of a body . When fewer than 24 input bits are available in an input group, zero bits are added (on the right) to form an =============== MIME TXT A1 LINE 1293 ========================= apparent encapsulation boundaries within base64- encoded parts of multipart messages because no hyphen characters are used in the base64 encoding. --------------- MIMEAF TXT A1 LINE 1316 apparent encapsulation boundaries within base64- encoded parts of multipart entities because no hyphen characters are used in the base64 encoding. =============== MIME TXT A1 LINE 1311 ========================= In constructing a high-level user agent, it may be desirable to allow one message body part to make reference to another. Accordingly, message body parts may be labeled using the "Content-ID" header field, which is syntactically identical --------------- MIMEAF TXT A1 LINE 1334 In constructing a high-level user agent, it may be desirable to allow one body to make reference to another. Accordingly, bodies may be labeled using the "Content-ID" header field, which is syntactically identical =============== MIME TXT A1 LINE 1324 ========================= The ability to associate some descriptive information with a given body part is often desirable. For example, it may be useful to mark an "image" body part as "a picture of the Space Shuttle Endeavor." Such text may be placed in the --------------- MIMEAF TXT A1 LINE 1347 The ability to associate some descriptive information with a given body is often desirable. For example, it may be useful to mark an "image" body as "a picture of the Space Shuttle Endeavor." Such text may be placed in the =============== MIME TXT A1 LINE 1439 ========================= Encoding header field and a corresponding encoding on the data are required in order to transmit the message via some mail transfer protocols, such as SMTP. --------------- MIMEAF TXT A1 LINE 1462 Encoding header field and a corresponding encoding on the data are required in order to transmit the body via some mail transfer protocols, such as SMTP. =============== MIME TXT A1 LINE 1450 ========================= does not indicate an arbitrary seven-bit character code, but specifies that the message body uses character coding that uses the exact correspondence of codes to characters --------------- MIMEAF TXT A1 LINE 1473 does not indicate an arbitrary seven-bit character code, but specifies that the body uses character coding that uses the exact correspondence of codes to characters =============== MIME TXT A1 LINE 1488 ========================= (counting the first column as column 0)." Apart from this, any use of the control characters or DEL in a message must be part of a private agreement between the sender and --------------- MIMEAF TXT A1 LINE 1511 (counting the first column as column 0)." Apart from this, any use of the control characters or DEL in a body must be part of a private agreement between the sender and =============== MIME TXT A1 LINE 1572 ========================= "lowest common denominator" character set possible. For example, if a message contains only US-ASCII characters, it should be marked as being in the US-ASCII character set, not --------------- MIMEAF TXT A1 LINE 1595 "lowest common denominator" character set possible. For example, if a body contains only US-ASCII characters, it should be marked as being in the US-ASCII character set, not =============== MIME TXT A1 LINE 1577 ========================= widely-used character set is a subset of another character set, and a message contains only characters in the widely- used subset, it should be labeled as being in that subset. --------------- MIMEAF TXT A1 LINE 1600 widely-used character set is a subset of another character set, and a body contains only characters in the widely- used subset, it should be labeled as being in that subset. =============== MIME TXT A1 LINE 1588 ========================= existing Internet practice, that is, it is the type of message body defined by RFC 822. --------------- MIMEAF TXT A1 LINE 1611 existing Internet practice, that is, it is the type of body defined by RFC 822. =============== MIME TXT A1 LINE 1724 ========================= Signature -- causes the subsequent text to be interpreted as a message "signature". Some systems may wish to display signatures in a smaller font --------------- MIMEAF TXT A1 LINE 1747 Signature -- causes the subsequent text to be interpreted as a "signature". Some systems may wish to display signatures in a smaller font =============== MIME TXT A1 LINE 1768 ========================= commands imposes a slightly higher burden upon the composers of richtext messages, but potentially simplifies richtext displayers by allowing them to --------------- MIMEAF TXT A1 LINE 1791 commands imposes a slightly higher burden upon the composers of richtext bodies, but potentially simplifies richtext displayers by allowing them to =============== MIME TXT A1 LINE 1958 ========================= In the case of multiple part messages, in which one or more different sets of data are combined in a single message, a "multipart" Content-Type field must appear in the RFC 822 message header. The message body must then contain one or more "body parts," each preceded by an encapsulation --------------- MIMEAF TXT A1 LINE 1981 In the case of multiple part bodies, in which one or more different sets of data are combined in a single body, a "multipart" Content-Type field must appear in the RFC 822 entity header. The body must then contain one or more "body parts," each preceded by an encapsulation =============== MIME TXT A1 LINE 1990 ========================= be able to tell the difference between a body part that consists of an image and a bodypart that consists of an encapsulated message, the body of which is an image. In order to represent the --------------- MIMEAF TXT A1 LINE 2013 be able to tell the difference between a body part that contains an image and a body part that contains an encapsulated message, the body of which is an image. In order to represent the =============== MIME TXT A1 LINE 2027 ========================= agents will at least be able to recognize and separate the parts of any multipart message, even of an unrecognized subtype. --------------- MIMEAF TXT A1 LINE 2050 agents will at least be able to recognize and separate the parts of any multipart entity , even of an unrecognized subtype. =============== MIME TXT A1 LINE 2032 ========================= field, no encoding other than "7bit", "8bit", or "binary" is permitted for messages or parts of type "multipart". The multipart delimiters and header fields are always 7-bit --------------- MIMEAF TXT A1 LINE 2055 field, no encoding other than "7bit", "8bit", or "binary" is permitted for entities of type "multipart". The multipart delimiters and header fields are always 7-bit =============== MIME TXT A1 LINE 2052 ========================= The Content-Type field for multipart messages requires one parameter, "boundary", which is used to specify the --------------- MIMEAF TXT A1 LINE 2075 The Content-Type field for multipart entities requires one parameter, "boundary", which is used to specify the =============== MIME TXT A1 LINE 2092 ========================= This indicates that the message consists of several parts, each itself with a structure that is syntactically identical --------------- MIMEAF TXT A1 LINE 2115 This indicates that the entity consists of several parts, each itself with a structure that is syntactically identical =============== MIME TXT A1 LINE 2120 ========================= The requirement that the encapsulation boundary begins with a CRLF implies that the body of a multipart message must itself begin with a CRLF before the first encapsulation line -- that is, if the "preamble" area is not used, the message headers must be followed by TWO CRLFs. This is indeed how such messages should be composed. A tolerant mail reading program, however, may interpret a body of type multipart --------------- MIMEAF TXT A1 LINE 2143 The requirement that the encapsulation boundary begins with a CRLF implies that the body of a multipart entity must itself begin with a CRLF before the first encapsulation line -- that is, if the "preamble" area is not used, the entity headers must be followed by TWO CRLFs. This is indeed how such entities should be composed. A tolerant mail reading program, however, may interpret a body of type multipart =============== MIME TXT A1 LINE 2129 ========================= compliant mail sending program must not generate such messages. --------------- MIMEAF TXT A1 LINE 2152 compliant mail sending program must not generate such entities. =============== MIME TXT A1 LINE 2222 ========================= The use of a Content-Type of multipart in a body part within another multipart message is explicitly allowed. In such cases, for obvious reasons, care must be taken to ensure that each nested multipart message must use a different boundary delimiter. See Appendix C for an example of nested multipart messages. --------------- MIMEAF TXT A1 LINE 2245 The use of a Content-Type of multipart in a body part within another multipart entity is explicitly allowed. In such cases, for obvious reasons, care must be taken to ensure that each nested multipart entity must use a different boundary delimiter. See Appendix C for an example of nested multipart entities. =============== MIME TXT A1 LINE 2249 ========================= Overall, the body of a multipart message may be specified as follows: --------------- MIMEAF TXT A1 LINE 2272 Overall, the body of a multipart entity may be specified as follows: =============== MIME TXT A1 LINE 2255 ========================= encapsulation := delimiter CRLF part-encapsulation --------------- MIMEAF TXT A1 LINE 2278 encapsulation := delimiter CRLF body-part =============== MIME TXT A1 LINE 2284 ========================= part-encapsulation = <"message" as defined in RFC 822, with all header fields optional, and with the --------------- MIMEAF TXT A1 LINE 2307 body-part = <"message" as defined in RFC 822, with all header fields optional, and with the =============== MIME TXT A1 LINE 2373 ========================= In general, user agents that compose multipart/alternative messages should place the body parts in increasing order of preference, that is, with the preferred format last. For --------------- MIMEAF TXT A1 LINE 2396 In general, user agents that compose multipart/alternative entities should place the body parts in increasing order of preference, that is, with the preferred format last. For =============== MIME TXT A1 LINE 2388 ========================= friendliest possible option when mutlipart/alternative messages are viewed using a non-MIME-compliant mail reader. While this --------------- MIMEAF TXT A1 LINE 2411 friendliest possible option when multipart/alternative entities are viewed using a non-MIME-compliant mail reader. While this =============== MIME TXT A1 LINE 2456 ========================= multipart/mixed, but the semantics are different. In particular, in a parallel message, all of the parts are intended to be presented in parallel, i.e., simultaneously, --------------- MIMEAF TXT A1 LINE 2479 multipart/mixed, but the semantics are different. In particular, in a parallel entity, all of the parts are intended to be presented in parallel, i.e., simultaneously, =============== MIME TXT A1 LINE 2503 ========================= message header fields are always US-ASCII in any case, and data within the body part can still be encoded, in which case the Content-Transfer-Encoding header field in the --------------- MIMEAF TXT A1 LINE 2526 message header fields are always US-ASCII in any case, and data within the body can still be encoded, in which case the Content-Transfer-Encoding header field in the =============== MIME TXT A1 LINE 2519 ========================= A Content-Type of "message/rfc822" indicates that the body or body part is an encapsulated message, with the syntax of an RFC 822 message. --------------- MIMEAF TXT A1 LINE 2542 A Content-Type of "message/rfc822" indicates that the body contains an encapsulated message, with the syntax of an RFC 822 message. =============== MIME TXT A1 LINE 2543 ========================= sent. Content-Type "message/partial" thus indicates that the body or body part is a fragment of a larger message. --------------- MIMEAF TXT A1 LINE 2566 sent. Content-Type "message/partial" thus indicates that the body contains a fragment of a larger message. =============== MIME TXT A1 LINE 2588 ========================= message. This makes it possible, for example, to send a large audio message as several partial messages, and still have it appear to the recipient as a simple audio message --------------- MIMEAF TXT A1 LINE 2611 message. This makes it possible, for example, to send a large audio message as several partial entities , and still have it appear to the recipient as a simple audio message =============== MIME TXT A1 LINE 2609 ========================= message must be merged with the headers of the enclosing messages. In this process the following rules must be observed: --------------- MIMEAF TXT A1 LINE 2632 message must be merged with the headers of the enclosing entities. In this process the following rules must be observed: =============== MIME TXT A1 LINE 2613 ========================= (1) All of the headers from the initial enclosing message (part one), except those that start with "Content-" and "Message-ID", must be copied, in --------------- MIMEAF TXT A1 LINE 2636 (1) All of the headers from the initial enclosing entity (part one), except those that start with "Content-" and "Message-ID", must be copied, in =============== MIME TXT A1 LINE 2703 ========================= The external-body subtype indicates that the actual body or body part data are not included, but merely referenced. In this case, the parameters describe a mechanism for accessing --------------- MIMEAF TXT A1 LINE 2726 The external-body subtype indicates that the actual body data are not included, but merely referenced. In this case, the parameters describe a mechanism for accessing =============== MIME TXT A1 LINE 2708 ========================= When a message body or body part is of type "message/external-body", it consists of a message header, two consecutive CRLFs, and the message header for the --------------- MIMEAF TXT A1 LINE 2731 When an entity is of type "message/external-body", it consists of a header, two consecutive CRLFs, and the message header for the =============== MIME TXT A1 LINE 2807 ========================= NAME -- The name of the file that contains the external body. --------------- MIMEAF TXT A1 LINE 2830 NAME -- The name of the file that contains the actual body data. =============== MIME TXT A1 LINE 2835 ========================= An access-type of "local-file" indicates that the message body is accessible as a file on the local machine. An --------------- MIMEAF TXT A1 LINE 2858 An access-type of "local-file" indicates that the actual body is accessible as a file on the local machine. An =============== MIME TXT A1 LINE 2842 ========================= NAME -- The name of the file that contains the external body data. --------------- MIMEAF TXT A1 LINE 2865 NAME -- The name of the file that contains the actual body data. =============== MIME TXT A1 LINE 2871 ========================= The "mail-server" access-type indicates that the message body is available from a mail server. The mandatory --------------- MIMEAF TXT A1 LINE 2894 The "mail-server" access-type indicates that the actual body is available from a mail server. The mandatory =============== MIME TXT A1 LINE 2876 ========================= SERVER -- The email address of the mail server from which the data can be obtained. --------------- MIMEAF TXT A1 LINE 2899 SERVER -- The email address of the mail server from which the actual body data can be obtained. =============== MIME TXT A1 LINE 2904 ========================= mechanisms, the sender may include multiple parts of type message/external-body within a part of type multipart/alternative. --------------- MIMEAF TXT A1 LINE 2927 mechanisms, the sender may include multiple parts of type message/external-body within an entity of type multipart/alternative. =============== MIME TXT A1 LINE 2912 ========================= If a message is of type "message/external-body", then the body of the message will contain the header fields of the encapsulated message. The body itself is to be found in the --------------- MIMEAF TXT A1 LINE 2935 If an entity is of type "message/external-body", then the body of the entity will contain the header fields of the encapsulated message. The body itself is to be found in the =============== MIME TXT A1 LINE 3097 ========================= The primary subtype of application, "octet-stream", may be used to indicate that a body or body part of a message is binary data. The set of possible parameters includes, but --------------- MIMEAF TXT A1 LINE 3120 The primary subtype of application, "octet-stream", may be used to indicate that a body contains binary data. The set of possible parameters includes, but =============== MIME TXT A1 LINE 3139 ========================= data. This is useful for enclosing a bitstream in a message when the total number of bits is not a multiple of the byte size. --------------- MIMEAF TXT A1 LINE 3162 data. This is useful for enclosing a bitstream in a body when the total number of bits is not a multiple of the byte size. =============== MIME TXT A1 LINE 3195 ========================= the following before they add interactive display of PostScript messages to their mail readers. --------------- MIMEAF TXT A1 LINE 3218 the following before they add interactive display of PostScript bodies to their mail readers. =============== MIME TXT A1 LINE 3325 ========================= The "ODA" subtype of application is used to mark message bodies or parts as being information encoded according to the Office Document Architecture [ODA] standards, using the --------------- MIMEAF TXT A1 LINE 3348 The "ODA" subtype of application is used to indicate that a body contains information encoded according to the Office Document Architecture [ODA] standards, using the =============== MIME TXT A1 LINE 3388 ========================= A Content-Type of "image" indicates that the body or body part contains an image. The subtype names the specific image format. These names are case insensitive. Three initial --------------- MIMEAF TXT A1 LINE 3411 A Content-Type of "image" indicates that the body contains an image. The subtype names the specific image format. These names are case insensitive. Three initial =============== MIME TXT A1 LINE 3411 ========================= A Content-Type of "audio" indicates that the body or body part contains audio data. Although there is not yet a consensus on an "ideal" audio format for use with computers, --------------- MIMEAF TXT A1 LINE 3434 A Content-Type of "audio" indicates that the body contains audio data. Although there is not yet a consensus on an "ideal" audio format for use with computers, =============== MIME TXT A1 LINE 3429 ========================= A Content-Type of "video" indicates that the body or body part contains a time-varying-picture image, possibly with color and coordinated sound. The term "video" is used --------------- MIMEAF TXT A1 LINE 3452 A Content-Type of "video" indicates that the body contains a time-varying-picture image, possibly with color and coordinated sound. The term "video" is used =============== MIME TXT A1 LINE 3451 ========================= part, it is recognized that many so-called "video" formats include a representation for synchronized audio, and this is --------------- MIMEAF TXT A1 LINE 3474 , it is recognized that many so-called "video" formats include a representation for synchronized audio, and this is =============== MIME TXT A1 LINE 4339 ========================= encapsulation := delimiter CRLF part-encapsulation --------------- MIMEAF TXT A1 LINE 4362 encapsulation := delimiter CRLF body-part =============== MIME TXT A1 LINE 4363 ========================= part-encapsulation = <"message" as defined in RFC 822, with all header fields optional, and with the --------------- MIMEAF TXT A1 LINE 4386 body-part = <"message" as defined in RFC 822, with all header fields optional, and with the