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
Entity
Click on the red underlined text to get to the source
...
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.
...
... 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 ...
...
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 previous four definitions are clearly circular. This is
...
... top level
of a message. It is not required for each body part of a multipart
entity. It is required for the embedded headers of a body of type
"message" if and only if the embedded message is itself claimed to be
...
... 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 be
...
... 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 not permitted to have any value other than a bit ...
... encoding mechanisms defined here explicitly encode all data in
ASCII. Thus, for example, suppose an entity has header fields such
as:
...
... 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
...
... "message/external-body". That is, each message/external-body entity
must have a Content-ID field to permit cacheing of such data.
...
... sets of data are combined in a single body, a "multipart" Content-
Type field must appear in the entity's header. The body must then
contain one or more "body parts," each preceded by an encapsulation ...
... that all conformant user agents will at least be able to recognize
and separate the parts of any multipart entity, even of an
unrecognized subtype.
...
... boundary="gc0p4Jq0M:2Yt08jU534c0p"
This indicates that the entity consists of several parts, each itself
with a structure that is syntactically identical to an RFC 822std11(-> 2822prop)
...
... 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 ...
... 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.
...
... / "," / "-" / "." / "/" / ":" / "=" / "?"
Overall, the body of a multipart entity may be specified as
follows:
...
... IN MULTIPART/ALTERNATIVE: Each
part of a multipart/alternative entity represents the same data, but
the mappings between the two are not necessarily without information
loss. For example, information is lost when translating ODA to
...
... Content-ID field. That is, one Content-ID value will refer to the
multipart/alternative entity, while one or more other Content-ID
values will refer to the parts inside it.
...
... multipart/mixed, but
the semantics are different. In particular, in a parallel entity,
the order of body parts is not significant.
...
... It should be noted that, despite the use of the numbers "822", a
message/rfc822 entity can include enhanced information as defined in
this document. In other words, a message/rfc822 message may be a
MIME message ...
...
together, the result is a complete MIME entity, which may have its
own Content-Type header field ...
...
(1) All of the header fields from the initial enclosing entity
(part one), except those that start with "Content-" and the
...
... mechanism by which the returned data can be matched up with the
original message/external-body entity. MIME mailservers must use the
same Content-ID ...
... Content-ID field on the returned message that was used in the
original message/external-body entity, to facilitate such matching.
...
... sender may
include multiple parts of type message/external-body within an entity
of type multipart/alternative.
...
... references to video clips.
If an entity is of type "message/external-body", then the body of the
entity ...
... entity is of type "message/external-body", then the body of the
entity will contain the header fields of the encapsulated message.
...
...
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
those steps used in RFC 1421hist ...
... counts which are specific to a given instance of a body.
Step 4. Insertion into entity.
The encoded object is inserted into a MIME ...
... entity with appropriate
headers. The entity is then inserted into the body of a higher-level
entity (message or multipart) if needed.
...
... headers. The entity is then inserted into the body of a higher-level
entity (message or multipart) if needed.
It is vital to note that these steps are only a model; they are
...