RFC 2112 (rfc2112) - Page 2 of 9

The MIME Multipart/Related Content-type

RFC 2112          MIME Multipart/Related Content-type         March 1997


2.  Multipart/Related Registration Information

   The following form is copied from RFC 1590, Appendix A.


   To:   Subject:  Registration of new Media Type content-
   type/subtype

   Media Type name:           Multipart

   Media subtype name:        Related

   Required parameters:       Type, a media type/subtype.

   Optional parameters:       Start
                     Start-info

   Encoding considerations:   Multipart content-types cannot have
                              encodings.

   Security considerations:   Depends solely on the referenced type.

   Published specification:   RFC-REL (this document).

   Person & email address to contact for further information:
                     Edward Levinson
                     47 Clive Street
                     Metuchen, NJ 08840-1060
                     +1 908 494 1606
                     

3.  Intended usage

   The Multipart/Related media type is intended for compound objects
   consisting of several inter-related body parts.  For a
   Multipart/Related object, proper display cannot be achieved by
   individually displaying the constituent body parts.  The content-type
   of the Multipart/Related object is specified by the type parameter.
   The "start" parameter, if given, points, via a content-ID, to the
   body part that contains the object root.  The default root is the
   first body part within the Multipart/Related body.










Levinson                    Standards Track