7.3.3.5. Examples and Further Explanations (original) (raw)

Connected: An Internet Encyclopedia
7.3.3.5. Examples and Further Explanations

Up: Connected: An Internet Encyclopedia
Up: Requests For Comments
Up: RFC 1521
Up: 7. The Predefined Content-Type Values
Up: 7.3. The Message Content-Type
Up: 7.3.3. The Message/External-Body subtype

Prev: 7.3.3.4. The "mail-server" access-type
Next: 7.4. The Application Content-Type

7.3.3.5. Examples and Further Explanations

With the emerging possibility of very wide-area file systems, it becomes very hard to know in advance the set of machines where a file will and will not be accessible directly from the file system. Therefore it may make sense to provide both a file name, to be tried directly, and the name of one or more sites from which the file is known to be accessible. An implementation can try to retrieve remote files using FTP or any other protocol, using anonymous file retrieval or prompting the user for the necessary name and password. If an external body is accessible via multiple mechanisms, the sender may include multiple parts of type message/external-body within an entity of type multipart/alternative.

However, the external-body mechanism is not intended to be limited to file retrieval, as shown by the mail-server access-type. Beyond this, one can imagine, for example, using a video server for external references to video clips.

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 external location. This means that if the body of the "message/external-body" message contains two consecutive CRLFs, everything after those pairs is NOT part of the message itself. For most message/external-body messages, this trailing area must simply be ignored. However, it is a convenient place for additional data that cannot be included in the content-type header field. In particular, if the "access-type" value is "mail- server", then the trailing area must contain commands to be sent to the mail server at the address given by the value of the SERVER parameter.

The embedded message header fields which appear in the body of the message/external-body data must be used to declare the Content-type of the external body if it is anything other than plain ASCII text, since the external body does not have a header section to declare its type. Similarly, any Content-transfer-encoding other than "7bit" must also be declared here. Thus a complete message/external-body message, referring to a document in PostScript format, might look like this:

  From: Whomever
  To: Someone
  Subject: whatever
  MIME-Version: 1.0
  Message-ID: <id1@host.com>
  Content-Type: multipart/alternative; boundary=42
  Content-ID: <id001@guppylake.bellcore.com>

  --42
  Content-Type: message/external-body;
       name="BodyFormats.ps";
       site="thumper.bellcore.com";
       access-type=ANON-FTP;
       directory="pub";
       mode="image";
       expiration="Fri, 14 Jun 1991 19:13:14 -0400 (EDT)"

  Content-type: application/postscript
  Content-ID: <id42@guppylake.bellcore.com>

  --42
  Content-Type: message/external-body;
       name="/u/nsb/writing/rfcs/RFC-MIME.ps";
       site="thumper.bellcore.com";
       access-type=AFS
       expiration="Fri, 14 Jun 1991 19:13:14 -0400 (EDT)"

  Content-type: application/postscript
  Content-ID: <id42@guppylake.bellcore.com>

  --42
  Content-Type: message/external-body;
       access-type=mail-server
       server="listserv@bogus.bitnet";
       expiration="Fri, 14 Jun 1991 19:13:14 -0400 (EDT)"

  Content-type: application/postscript
  Content-ID: <id42@guppylake.bellcore.com>

  get RFC-MIME.DOC

  --42--

Note that in the above examples, the default Content-transfer- encoding of "7bit" is assumed for the external postscript data.

Like the message/partial type, the message/external-body type is intended to be transparent, that is, to convey the data type in the external body rather than to convey a message with a body of that type. Thus the headers on the outer and inner parts must be merged using the same rules as for message/partial. In particular, this means that the Content-type header is overridden, but the From and Subject headers are preserved.

Note that since the external bodies are not transported as mail, they need not conform to the 7-bit and line length requirements, but might in fact be binary files. Thus a Content-Transfer-Encoding is not generally necessary, though it is permitted.

Note that the body of a message of type "message/external-body" is governed by the basic syntax for an RFC 822 message. In particular, anything before the first consecutive pair of CRLFs is header information, while anything after it is body information, which is ignored for most access-types.

The formal grammar for content-type header fields for data of type message is given by:

message-type := "message" "/" message-subtype

message-subtype := "rfc822" / "partial" 2#3partial-param / "external-body" 1*external-param / extension-token

partial-param := (";" "id" "=" value) / (";" "number" "=" 1DIGIT) / (";" "total" "=" 1DIGIT) ; id & number required; total required for last part

external-param := (";" "access-type" "=" atype) / (";" "expiration" "=" date-time) ; Note that date-time is quoted / (";" "size" "=" 1*DIGIT) / (";" "permission" "=" ("read" / "read-write")) ; Permission is case-insensitive / (";" "name" "=" value) / (";" "site" "=" value) / (";" "dir" "=" value) / (";" "mode" "=" value) / (";" "server" "=" value) / (";" "subject" "=" value) ; access-type required;others required based on access-type

atype := "ftp" / "anon-ftp" / "tftp" / "local-file" / "afs" / "mail-server" / extension-token ; Case-insensitive

Next: 7.4. The Application Content-Type

Connected: An Internet Encyclopedia
7.3.3.5. Examples and Further Explanations