As per Relevance of the word consider, we have this rfc below:
Network Working Group N.
Request for Comments: 1437
M.
Lonesome Dove Computing
1 April 1993
The Extension of MIME Content-Types to a New
Status of this
This memo provides information for the Internet community. It
not specify an Internet standard. Distribution of this memo
unlimited
A previous document, RFC 1341, defines a format and general
for the representation of a wide variety of data types in
mail. This document defines one particular type of MIME data,
matter-transport/sentient-life-form type. The matter
transport/sentient-life-form MIME type is intended to facilitate
wider interoperation of electronic mail messages that include
sentient life forms, such as human beings
Other informally proposed subtypes, such as "non-sentient-life-form",
"non-sentient-non-life-form", and the orthogonally necessary
nevertheless puzzling "sentient-non-life-form", are not described
this memo
The matter-transport/sentient-life-form MIME
In order to promote the wider interoperability of life-bearing email
this document defines a new MIME content-type, "matter-transport",
and for an initial subtype, "sentient-life-form". This subtype
designed to meet the following criteria
1. The syntax must be extremely simple to parse, to minimize
risk of accidental death due to misinterpretation of the standard
2. The data format must be extremely robust, with redundancy
ensure that individual life forms will survive and
reconstituted in such a form as to be nearly
from their initial state, no matter how many bizarre
gateways are encountered in transit
3. The syntax must be extensible to allow for the description
all yet-undiscovered aspects of life forms which will be
Borenstein & Linimon [Page 1]
RFC 1437 MIME Content-Types for a New Medium 1 April 1993
for the transport of non-human species (e.g. dolphins, Klingons
or politicians).
4. The syntax must be compatible with SGML, so that with
appropriate DTD (Document Type Definition -- the
mechanism for defining a document type using SGML), a general
parser could be written to parse the data structure and
directives to a lifeform-reconstitution mechanism. However
despite this compatibility, the syntax will most likely be
simpler than that of full SGML (so that no SGML knowledge
required in order to implement it), since it is anticipated
the full complexities of SGML will not be necessary for
description of even arbitrarily complex organic life forms
The syntax of the new content-type is very simple, and indeed
considerable sacrifice of efficiency in the interest of simplicity
It is assumed to describe a three-dimensional rectangular solid,
the height, width, and depth (calibrated in centimeters) specified
parameters on the content-type line. (In general, this should be
cube that completely contains the life form being transported; but
where high bandwidth is not available, a somewhat smaller cube can
used, provided that facilities are known to be available at
recipient's end to administer the medical first aid that could
necessary if an individual is reconstituted sans some of
extremities.) A fourth parameter gives the resolution of the
scan, calibrated in Angstroms. Thus, the following Content-
value
Content-type: matter-transport/sentient-life-form
height = 200; width = 60; depth=60; resolution=10
implies that the cube being described is 60 cm by 60 cm by 200 cm
and is described to a resolution of 10 Angstroms. The
gives the quantization unit, and therefore determines the quality
the reproduction. The data stream itself then consists of a
of the molecule found at each location, using the given resolution
If the resolution is high enough that more than one molecule is
in a given location, the molecule whose nucleus is closest to
center of the cube is used. Each molecule is described by
molecular formula, rendered in ASCII for maximum readability
matter-transport mail is inadvertently delivered to a human
and displayed on a terminal screen. Each molecule is followed by
space (ASCII 32) to separate it from the subsequent
description. Extremely long molecules may require the use of
content-transfer-encoding such as quoted-printable, to ensure
line-wrapping mail systems do not, for example, cause the
breakdown of complex proteins into their constituent elements
Borenstein & Linimon [Page 2]
RFC 1437 MIME Content-Types for a New Medium 1 April 1993
The following is a message that gives a somewhat simplified
of a well-known American politician, starting from the top
From: "Nathaniel S. Borenstein"
To: Mark Linimon
Subject: Think hard before
Content-description: Dan Quayle, low-res
Content-type: matter-transport/sentient-life-
height = 200; width = 60; depth=60; resolution=100000
Fe Fe Fe Fe Fe Fe Fe Fe Fe Fe Fe Fe Fe Fe Fe Fe Fe Fe Fe Fe Fe Fe
Fe Fe Fe Fe Fe Fe Fe Fe Fe Fe Fe Fe Fe Fe Fe Fe Fe Fe Fe Fe Fe Fe
Fe NO2 NO2 NO2 NO2 NO2 NO2 NO2 NO2 NO2 NO2 NO2 NO2 NO2 NO2 NO2 NO2
Fe NO2 NO2 NO2 NO2 NO2 NO2 NO2 NO2 NO2 NO2 NO2 NO2 NO2 NO2 NO2 NO2
Fe NO2 NO2 NO2 NO2 NO2 NO2 NO2 NO2 NO2 NO2 NO2 NO2 NO2 NO2 NO2 NO2
Fe NO2 NO2 NO2 NO2 NO2 NO2 NO2 NO2 NO2 NO2 NO2 NO2 NO2 NO2 NO2 NO2
Fe NO2 NO2 NO2 NO2 NO2 NO2 NO2 NO2 NO2 NO2 NO2 NO2 NO2 NO2 NO2 NO2
Fe NO2 NO2 NO2 NO2 NO2 NO2 NO2 NO2 NO2 NO2 NO2 NO2 NO2 NO2 NO2 NO2
Fe NO2 NO2 NO2 NO2 NO2 NO2 NO2 NO2 NO2 NO2 NO2 NO2 NO2 NO2 NO2 NO2
Fe NO2 NO2 NO2 NO2 NO2 NO2 NO2 NO2 NO2 NO2 NO2 NO2 NO2 NO2 NO2 NO2
Fe NO2 NO2 NO2 NO2 NO2 NO2 NO2 NO2 NO2 NO2 NO2 NO2 NO2 NO2 NO2 NO2
Fe NO2 NO2 NO2 NO2 NO2 NO2 NO2 NO2 NO2 NO2 NO2 NO2 NO2 NO2 NO2 NO2
Fe NO2 NO2 NO2 NO2 NO2 NO2 NO2 NO2 NO2 NO2 NO2 NO2 NO2 NO2 NO2 NO2
Fe NO2 NO2 NO2 NO2 NO2 NO2 NO2 NO2 NO2 NO2 NO2 NO2 NO2 NO2 NO2 NO2
Fe NO2 NO2 NO2 NO2 NO2 NO2 NO2 NO2 NO2 NO2 NO2 NO2 NO2 NO2 NO2 NO2
Fe Fe Fe Fe Fe Fe Fe Fe Fe Fe Fe Fe Fe Fe Fe Fe Fe Fe Fe Fe Fe Fe
Fe Fe Fe Fe Fe Fe Fe Fe Fe Fe Fe Fe Fe Fe Fe Fe Fe Fe Fe Fe Fe Fe
Obviously, a real politician's skull is more complex than pure iron
as is its interior, but this simplified example should give
general flavor of the protocol
(A caveat, however, in the reconstitution of Vice-Presidents of
United States: allegedly, some of the matter-reconstitution
currently under development are reputed to perform less
optimally while trying to reconstitute areas of relatively
vacuum; for instance, their skulls. A recommended acceptance
might be to experiment with subjects whose skulls are only at
vacuum, such as Vice-Presidents of Marketing.)
MHS (X.400) Gateway
The proper behavior of a MIME/MHS gateway with regard to
transmission of complex multimedia messages is a topic of
investigation under the auspices of the IETF. The addition of
transport should not significantly complicate that effort, as it
already necessary to specify gateway behavior for MIME types
have no X.400 equivalents, and matter transport is simply
Borenstein & Linimon [Page 3]
RFC 1437 MIME Content-Types for a New Medium 1 April 1993
such untranslatable type
However, real-world X.400 gateways might be considered
significantly increase the hazard that mail containing a human
will be rejected with a message so cryptic that the recipient
it without ever realizing that an embedded human being is enclosed
For this reason, it is recommended that the subject of
transport be explicitly marked "for further study" in the
generation of the X.400 specification, X.400-1996. This will
the community ample time to define a more complete specification
matter transport as part of X.400-2000, and possibly even a readily
implementable specification as part of X.400-2004, although some
no doubt argue that this would be too strong a break with tradition
Implementation
The user is cautioned against passing MIME transporter
through computers equipped with the NFS file system. A no-file
error caused one of the laboratory rats on our prototype system to
truncated to a zero-length file. Unfortunately we had neglected
mount a scratch rat. (We have decided to permanently retain
empty filename in his honor).
Byte swapping problems on other storage systems can be
annoying, but should not be a problem if network byte order is
maintained ocrrcelty
Despite the authors' belief in the robustness of the protocol
passage of email through certain systems seems to result in
sentient-life-form arriving at its destination upside down,
in an annoying "thud". The cause is still under investigation
Interoperation with matter-transporters using polar
systems is discouraged, due to round-off and other algorithmic
in certain ubiquitous floating-point implementations, leading
results which are best discreetly described as "disappointing."
Similarly, off-by-one errors should be avoided
Widespread adoption of this protocol may lead to an increase in
demand for reliable backup systems. More importantly, for the
time management may be motivated to adequately fund such systems
they discover the possibility that proper email backup may
upon them virtual immortality. (On the other hand,
should seriously consider the desirability of making their
immortal.)
Borenstein & Linimon [Page 4]
RFC 1437 MIME Content-Types for a New Medium 1 April 1993
An additional concern reflects the fact that, prior to
introduction of this content-type, duplicate mail delivery was
relatively minor nuisance. With the mail extensions described
this document, however, comes the possibility that duplicate
delivery will leave a user with, for example, multiple spouses
mothers-in-law. The relative weights of the desire to
duplicate delivery and the desire to avoid lost mail may
accordingly
Security
Security considerations are not discussed in this memo. However,
enforcement officials might wish to consider the possibility
this mechanism could be used by criminals, either to
extradition by mailing themselves outside of a legal jurisdiction,
to outwait the statute of limitations by mailing themselves
complex mail routes with long delays. (One supposes that they
also look on the bright side, and consider MIME as a
approach to solving the long-standing problem of
overcrowding.)
The authors of this document may be reconstituted by feeding
following data to an Internet-connected MIME reader
Content-type: multipart/mixed; boundary=
--
Content-type: message/external-body; access-type=anon-ftp
site=thumper.bellcore.com; directory=pub/nsb; name=nsb.
Content-Description: Nathaniel
Content-type: matter-transport/sentient-life-
height = 200; width = 60; depth=60; resolution=100000
--
Content-type: message/external-body; access-type=anon-ftp
site=thumper.bellcore.com; directory=pub/nsb; name=linimon.
Content-Description: Mark
Content-type: matter-transport/sentient-life-
height = 200; width = 60; depth=60; resolution=100000
--NextAuthor--
Borenstein & Linimon [Page 5]
RFC 1437 MIME Content-Types for a New Medium 1 April 1993
Authors'
Nathaniel
Bellcore Room MRE 2D-296
445 South
Morristown, NJ 07962-1910
Phone: (201) 829-4270
EMail: nsb@bellcore.
Mark
Lonesome Dove Computing
P.O. Box 20291
Roanoke, VA 24018
Phone: (703) 776-1004
EMail: linimon@LONESOME.
Borenstein & Linimon [Page 6]
if you see any problems within the linking, don't worry be happy,
this is version 0.1 of the Relevance System and you gotta expect some crappy subroutines sometimes,
just be content we did not write this in Java, which would have made this "bigger and better" HAHAHHA.
RFC documents can be found at I.E.T.F.
Relevance System Copyright © 2002 Spectrum WorldResearch
other technical nosh by ServerMasters Corporation
collaboration of BobX
