RFC1437 on MIME Content-Types for a New Medium

"Joyce K. Reynolds" <jkrey@isi.edu> Wed, 31 March 1993 20:52 UTC

Message-Id: <199303312051.AA21450@zephyr.isi.edu>
To: IETF-Announce:;
Subject: RFC1437 on MIME Content-Types for a New Medium
Cc: jkrey@isi.edu
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
Date: Wed, 31 Mar 1993 12:51:12 -0800
Sender: ietf-announce-request@IETF.CNRI.Reston.VA.US
From: "Joyce K. Reynolds" <jkrey@isi.edu>

A new Request for Comments is now available in online RFC libraries.


        RFC 1437:

        Title:      The Extension of MIME Content-Types to a New
                    Medium 
        Author:     N. Borenstein & M. Linimon
        Mailbox:    nsb@bellcore.com, linimon@LONESOME.COM
        Pages:      6
        Characters: 13,356
        Updates/Obsoletes:  none


A previous document, RFC 1341, defines a format and general framework
for the representation of a wide variety of data types in Internet
mail.  This document defines one particular type of MIME data, the
matter-transport/sentient-life-form type.  The
matter-transport/sentient-life-form MIME type is intended to
facilitate the wider interoperation of electronic mail messages that
include entire 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 but
nevertheless puzzling "sentient-non-life-form", are not described in
this memo.

This memo provides information for the Internet community.  It does
not specify an Internet standard.  Distribution of this memo is
unlimited.

This announcement is sent to the IETF list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST@CNRI.RESTON.VA.US.  Requests to be added
to or deleted from the RFC-DIST distribution list should be sent to
RFC-REQUEST@NIC.DDN.MIL.

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to "rfc-info@ISI.EDU" with the message body 
"help: ways_to_get_rfcs".  For example:

	To: rfc-info@ISI.EDU
	Subject: getting rfcs

	help: ways_to_get_rfcs

Requests for special distribution should be addressed to either the
author of the RFC in question, or to NIC@NIC.DDN.MIL.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

Submissions for Requests for Comments should be sent to
RFC-EDITOR@ISI.EDU.  Please consult RFC 1111, "Instructions to RFC
Authors", for further information.


Joyce K. Reynolds
USC/Information Sciences Institute

...

Below is the data which will enable a MIME compliant Mail Reader 
implementation to automatically retrieve the ASCII version
of the RFCs.

ftp://nic.ddn.mil/rfc/rfc1437.txt"><ftp://nic.ddn.mil/rfc/rfc1437.txt>

RFC1437 on MIME Content-Types for a New Medium Joyce K. Reynolds