RFC 2557 on MIME Encapsulation of Aggregate Documents
RFC Editor <rfc-ed@ISI.EDU> Thu, 01 April 1999 01:15 UTC
Received: by ietf.org (8.9.1a/8.9.1a) id UAA06140 for ietf-123-outbound.10@ietf.org; Wed, 31 Mar 1999 20:15:02 -0500 (EST)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA06073 for <all-ietf@ietf.org>; Wed, 31 Mar 1999 20:09:35 -0500 (EST)
Received: from ISI.EDU (jet.isi.edu [128.9.160.87]) by boreas.isi.edu (8.8.7/8.8.6) with ESMTP id RAA04382; Wed, 31 Mar 1999 17:09:35 -0800 (PST)
Message-Id: <199904010109.RAA04382@boreas.isi.edu>
To: IETF-Announce:;
Subject: RFC 2557 on MIME Encapsulation of Aggregate Documents
Cc: rfc-ed@ISI.EDU
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
Date: Wed, 31 Mar 1999 17:09:35 -0800
From: RFC Editor <rfc-ed@ISI.EDU>
A new Request for Comments is now available in online RFC libraries. RFC 2557: Title: MIME Encapsulation of Aggregate Documents, such as HTML (MHTML) Author(s): J. Palme, A. Hopmann, N. Shelness Status: Proposed Standard Date: March 1999 Mailbox: jpalme@dsv.su.se, alexhop@microsoft.com, Shelness@lotus.com Pages: 28 Characters: 61854 Obsoletes: 2110 I-D Tag: draft-ietf-mhtml-rev-07.txt URL: ftp://ftp.isi.edu/in-notes/rfc2557.txt This document a) defines the use of a MIME multipart/related structure to aggregate a text/html root resource and the subsidiary resources it references, and b) specifies a MIME content-header (Content-Location) that allow URIs in a multipart/related text/html root body part to reference subsidiary resources in other body parts of the same multipart/related structure. 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@IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info@RFC-EDITOR.ORG 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 RFC-Manager@RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution.echo Submissions for Requests for Comments should be sent to RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information. Joyce K. Reynolds and Alegre Ramos 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.