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


        RFC 2110

        Title:      MIME E-mail Encapsulation of Aggregate 
                    Documents, such as HTML (MHTML)
        Author:     J. Palme, A. Hopmann
        Date:       March 1997
        Mailbox:    jpalme@dsv.su.se, alexhop@microsoft.com
        Pages:      19
        Characters: 41961
        Updates/Obsoletes: None


        URL:        ftp://ds.internic.net/rfc/rfc2110.txt


Although HTML [RFC 1866] was designed within the context of MIME, more
than the specification of HTML as defined in RFC 1866 is needed for
two electronic mail user agents to be able to interoperate using HTML
as a document format. This document describes a set of guidelines that
will allow conforming mail user agents to be able to send, deliver and
display these objects, such as HTML objects, that can contain links
represented by URIs. In order to be able to handle inter-linked
objects, the document uses the MIME type multipart/related and
specifies the MIME content-headers "Content-Location" and
"Content-Base". This document is a product of the MIME Encapsulation
of Aggregate HTML Documents Working Group of the IETF.

This is now a Proposed Standard Protocol.

This document specifies an Internet standards track protocol for the
Internet community, and requests discussion and suggestions for
improvements.  Please refer to the current edition of the "Internet
Official Protocol Standards" (STD 1) for the standardization state and
status of this protocol.  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-DIST-REQUEST@ISI.EDU.

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 admin@DS.INTERNIC.NET.  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 1543, Instructions to RFC
Authors, for further information.


Joyce K. Reynolds and Mary Kennedy
USC/Information Sciences Institute