draft-ietf-mhtml-rev-06.txt   draft-ietf-mhtml-rev-07.txt 
Network Working Group Jacob Palme Network Working Group Jacob Palme
Internet Draft Stockholm University/KTH Internet Draft Stockholm University/KTH
draft-ietf-mhtml-rev-06.txt Alexander Hopmann draft-ietf-mhtml-rev-07.txt Alexander Hopmann
IETF status to be: Proposed standard Microsoft Corporation IETF status to be: Proposed standard Microsoft Corporation
Replaces: RFC 2110 Nick Shelness Replaces: RFC 2110 Nick Shelness
Lotus Corporation Lotus Corporation
Expires: August 1998 February 1998 Expires: August 1998 February 1998
MIME Encapsulation of Aggregate Documents, such as HTML (MHTML) MIME Encapsulation of Aggregate Documents, such as HTML (MHTML)
Status of this Document Status of this Document
This document is an Internet-Draft. Internet-Drafts are working This document is an Internet-Draft. Internet-Drafts are working
skipping to change at line 105 skipping to change at line 103
11. Security Considerations 11. Security Considerations
11.1 Security considerations not related to caching 11.1 Security considerations not related to caching
11.2 Security considerations related to caching 11.2 Security considerations related to caching
12. Differences as compared to the previous version of this proposed 12. Differences as compared to the previous version of this proposed
standard in RFC 2110 standard in RFC 2110
13. Copyright 13. Copyright
14. Acknowledgments 14. Acknowledgments
15. References 15. References
16. Author's Addresses 16. Author's Addresses
Differences since version 06 of this draft
Changed the syntax of the start parameter in examples, to show that it
must always be quoted (since it contains the special character "@", and
all Content-Type parameters containing special characters must be
quoted according to MIME.
Also the list of references has been updated.
Differences since version 05 of this draft Differences since version 05 of this draft
The definition of "HTML aggregate objects" has been changed from The definition of "HTML aggregate objects" has been changed from
HTML objects together with some or all objects, to which the HTML HTML objects together with some or all objects, to which the HTML
object contains hyperlinks. object contains hyperlinks.
to to
HTML objects together with some or all objects, to which the HTML HTML objects together with some or all objects, to which the HTML
object contains hyperlinks, directly or indirectly. object contains hyperlinks, directly or indirectly.
Erroneous quotes around "multipart/related" have been removed in the Erroneous quotes around "multipart/related" have been removed in the
skipping to change at line 207 skipping to change at line 214
http://www.reference.com/cgi-bin/pn/listarch?list=MHTML@segate.sunet.se http://www.reference.com/cgi-bin/pn/listarch?list=MHTML@segate.sunet.se
Finally, the archives are available by email. Send a message to Finally, the archives are available by email. Send a message to
LISTSERV@SEGATE.SUNET.SE with the text "INDEX MHTML" to get a list LISTSERV@SEGATE.SUNET.SE with the text "INDEX MHTML" to get a list
of the archive files, and then a new message "GET <file name>" to of the archive files, and then a new message "GET <file name>" to
retrieve archive files. retrieve archive files.
More information More information
Information about the IETF work in developing this standard may Information about the IETF work in developing this standard may also
also be available at URL: be available at URL:
http://www.dsv.su.se/~jpalme/ietf/mhtml.html http://www.dsv.su.se/~jpalme/ietf/mhtml.html
A collection of test messages is available at A collection of test messages is available at
http://www.dsv.su.se/~jpalme/mimetest/MHTML-test-messages.html http://www.dsv.su.se/~jpalme/mimetest/MHTML-test-messages.html
An informational draft [INFO] with advice on how to implement this
standard is under development. You can find the most recent draft from
http://www.dsv.su.se/~jpalme/ietf/mhtml.html#drafts, or, after it has
been published, from
http://www.dsv.su.se/~jpalme/ietf/mhtml.html#published.
1. Introduction 1. Introduction
There are a number of document formats (Hypertext Markup Language There are a number of document formats (Hypertext Markup Language
[HTML2], Extended Markup Language [XML], Portable Document format [PDF] [HTML2], Extended Markup Language [XML], Portable Document format [PDF]
and Virtual Reality Markup Language [VRML]) that specify documents and Virtual Reality Markup Language [VRML]) that specify documents
consisting of a root resource and a number of distinct subsidiary consisting of a root resource and a number of distinct subsidiary
resources referenced by URIs within that root resource. There is an resources referenced by URIs within that root resource. There is an
obvious need to be able to send such multi-resource documents in e-mail obvious need to be able to send such multi-resource documents in e-mail
[SMTP], [RFC822] messages. [SMTP], [RFC822] messages.
skipping to change at line 377 skipping to change at line 387
Finally several other constraints on the problem arise. It is important Finally several other constraints on the problem arise. It is important
that it be possible for a document to be signed and for it to be that it be possible for a document to be signed and for it to be
transmitted and displayed without breaking the message integrity (MIC) transmitted and displayed without breaking the message integrity (MIC)
checksum that is part of the signature. checksum that is part of the signature.
4. The Content-Location MIME Content Header 4. The Content-Location MIME Content Header
4.1 MIME content headers 4.1 MIME content headers
In order to resolve URI references to resources in other body parts, In order to resolve URI references to resources in other body parts,
one MIME content headers is defined, Content-Location. This header can one MIME content header is defined, Content-Location. This header can
occur in any message or content heading. occur in any message or content heading.
The syntax for this header is, using the syntax definition tools from The syntax for this header is, using the syntax definition tools from
[ABNF]: [ABNF]:
quoted-pair = ("\" text) quoted-pair = ("\" text)
text = %d1-9 / ; Characters excluding CR and LF text = %d1-9 / ; Characters excluding CR and LF
%d11-12 / %d11-12 /
%d14-127 %d14-127
skipping to change at line 795 skipping to change at line 805
9.2 Example with an absolute URI to an embedded GIF picture 9.2 Example with an absolute URI to an embedded GIF picture
The second example is an HTML message which includes a single image, The second example is an HTML message which includes a single image,
referenced using the Content-Location mechanism. referenced using the Content-Location mechanism.
From: foo1@bar.net From: foo1@bar.net
To: foo2@bar.net To: foo2@bar.net
Subject: A simple example Subject: A simple example
Mime-Version: 1.0 Mime-Version: 1.0
Content-Type: multipart/related; boundary="boundary-example"; Content-Type: multipart/related; boundary="boundary-example";
type="text/html"; start=<foo3@foo1@bar.net> type="text/html"; start="<foo3@foo1@bar.net>"
--boundary-example --boundary-example
Content-Type: text/html;charset=US-ASCII Content-Type: text/html;charset=US-ASCII
Content-ID: <foo3@foo1@bar.net> Content-ID: <foo3@foo1@bar.net>
... text of the HTML document, which might contain a URI ... text of the HTML document, which might contain a URI
referencing a resource in another body part, for example referencing a resource in another body part, for example
through a statement such as: through a statement such as:
<IMG SRC="http://www.ietf.cnri.reston.va.us/images/ietflogo.gif" <IMG SRC="http://www.ietf.cnri.reston.va.us/images/ietflogo.gif"
ALT="IETF logo"> ALT="IETF logo">
skipping to change at line 995 skipping to change at line 1005
Content-Transfer-Encoding: BASE64 Content-Transfer-Encoding: BASE64
R0lGODlhGAGgAPEAAP/////ZRaCgoAAAACH+PUNvcHlyaWdodCAoQykgMTk5 R0lGODlhGAGgAPEAAP/////ZRaCgoAAAACH+PUNvcHlyaWdodCAoQykgMTk5
NSBJRVRGLiBVbmF1dGhvcml6ZWQgZHVwbGljYXRpb24gcHJvaGliaXRlZC4A NSBJRVRGLiBVbmF1dGhvcml6ZWQgZHVwbGljYXRpb24gcHJvaGliaXRlZC4A
etc... etc...
--boundary-example-1 --boundary-example-1
Content-Location: Content-Location:
http://www.ietf.cnri.reston.va.us/more-info http://www.ietf.cnri.reston.va.us/more-info
Content-Type: multipart/related; boundary="boundary-example-2"; Content-Type: multipart/related; boundary="boundary-example-2";
type="text/html"> type="text/html"
--boundary-example-2 --boundary-example-2
Content-Type: text/html;charset=US-ASCII Content-Type: text/html;charset=US-ASCII
Content-ID: <foo4@foo1@bar.net> Content-ID: <foo4@foo1@bar.net>
The image reference below will be resolved with the image The image reference below will be resolved with the image
in the surrounding multipart/related above. in the surrounding multipart/related above.
<IMG SRC=images/ietflogo.gif" <IMG SRC=images/ietflogo.gif"
ALT="IETF logo with white background"> ALT="IETF logo with white background">
The image reference below will be resolved with the image The image reference below will be resolved with the image
skipping to change at line 1024 skipping to change at line 1034
R0lGODlhGAGgANX/ACkpKTExMTk5OUJCQkpKSlJSUlpaWmNjY2tra3Nzc3t7e4 R0lGODlhGAGgANX/ACkpKTExMTk5OUJCQkpKSlJSUlpaWmNjY2tra3Nzc3t7e4
SEhIyMjJSUlJycnKWlpa2trbW1tcDAwM7Ozv/eQnNzjHNzlGtrjGNjhFpae1pa SEhIyMjJSUlJycnKWlpa2trbW1tcDAwM7Ozv/eQnNzjHNzlGtrjGNjhFpae1pa
etc... etc...
--boundary-example-2-- --boundary-example-2--
--boundary-example-1 --boundary-example-1
Content-Location: Content-Location:
http://www.ietf.cnri.reston.va.us/more-info http://www.ietf.cnri.reston.va.us/more-info
Content-Type: multipart/related; boundary="boundary-example-3"; Content-Type: multipart/related; boundary="boundary-example-3";
type="text/html"> type="text/html"
--boundary-example-3 --boundary-example-3
Content-Type: text/html;charset=US-ASCII Content-Type: text/html;charset=US-ASCII
Content-ID: <4@foo@bar.net> Content-ID: <4@foo@bar.net>
The image reference below will be resolved with the image The image reference below will be resolved with the image
inside the current nested multipart/related below. inside the current nested multipart/related below.
<IMG SRC=images/ietflogo2d.gif" <IMG SRC=images/ietflogo2d.gif"
ALT="IETF logo with shadows"> ALT="IETF logo with shadows">
The image reference below cannot be resolved according to The image reference below cannot be resolved according to
skipping to change at line 1263 skipping to change at line 1273
15. References 15. References
Ref. Author, title Ref. Author, title
--------- -------------------------------------------------------- --------- --------------------------------------------------------
|ABNF] D. Rocker, P. Overell: Augmented BNF for Syntax |ABNF] D. Rocker, P. Overell: Augmented BNF for Syntax
Specifications: ABNF, RFC 2234, November 1997. Specifications: ABNF, RFC 2234, November 1997.
[CONDISP] R. Troost, S. Dorner: "Communicating Presentation [CONDISP] R. Troost, S. Dorner: "Communicating Presentation
Information in Internet Messages: The Information in Internet Messages: The
Content-Disposition Header", RFC 1806, June 1995. Content-Disposition Header", RFC 2183, August 1997.
[HOSTS] R. Braden (editor): "Requirements for Internet Hosts -- [HOSTS] R. Braden (editor): "Requirements for Internet Hosts --
Application and Support", STD-3, RFC 1123, October 1989. Application and Support", STD-3, RFC 1123, October 1989.
[HTML-I18N] F. Yergeau, G. Nicol, G. Adams, & M. Duerst: [HTML-I18N] F. Yergeau, G. Nicol, G. Adams, & M. Duerst:
"Internationalization of the Hypertext Markup Language". "Internationalization of the Hypertext Markup Language".
RFC 2070, January 1997. RFC 2070, January 1997.
[HTML2] T. Berners-Lee, D. Connolly: "Hypertext Markup Language [HTML2] T. Berners-Lee, D. Connolly: "Hypertext Markup Language
- 2.0", RFC 1866, November 1995. - 2.0", RFC 1866, November 1995.
skipping to change at line 1285 skipping to change at line 1295
[HTML3.2] Dave Raggett: HTML 3.2 Reference Specification, W3C [HTML3.2] Dave Raggett: HTML 3.2 Reference Specification, W3C
Recommendation, January 1997, at URL Recommendation, January 1997, at URL
http://www.w3.org/TR/REC-html32.html http://www.w3.org/TR/REC-html32.html
[HTTP] T. Berners-Lee, R. Fielding, H. Frystyk: Hypertext [HTTP] T. Berners-Lee, R. Fielding, H. Frystyk: Hypertext
Transfer Protocol -- HTTP/1.0. RFC 1945, May 1996. Transfer Protocol -- HTTP/1.0. RFC 1945, May 1996.
[IETF-TERMS] S. Bradner: Key words for use in RFCs to Indicate [IETF-TERMS] S. Bradner: Key words for use in RFCs to Indicate
Requirements Levels. RFC 2119, March 1997. Requirements Levels. RFC 2119, March 1997.
[INFO] J. Palme: Sending HTML in MIME, an informational
supplement to the RFC: MIME Encapsulation of Aggregate
Documents, such as HTML (MHTML), work in progress within
IETF in April 1998.
[MD5] R. Rivest: "The MD5 Message-Digest Algorithm", RFC 1321, [MD5] R. Rivest: "The MD5 Message-Digest Algorithm", RFC 1321,
April 1992. April 1992.
[MIDCID] E. Levinson: Content-ID and Message-ID Uniform Resource [MIDCID] E. Levinson: Content-ID and Message-ID Uniform Resource
Locators", draft-ietf-mhtml-cid-v2-00.txt, July 1997. Locators", draft-ietf-mhtml-cid-v2-00.txt, July 1997.
[MIME1] N. Freed, N. Borenstein, "Multipurpose Internet Mail [MIME1] N. Freed, N. Borenstein, "Multipurpose Internet Mail
Extensions (MIME) Part One: Format of Internet Message Extensions (MIME) Part One: Format of Internet Message
Bodies", RFC 2045, December 1996. Bodies", RFC 2045, December 1996.
. .
[MIME-IMB] N. Freed & N. Borenstein, "Multipurpose Internet Mail
Extensions (MIME) Part One: Format of Internet Message
Bedies". RFC 2045, November 1996.
[MIME2] N. Freed, N. Borenstein, "Multipurpose Internet Mail [MIME2] N. Freed, N. Borenstein, "Multipurpose Internet Mail
Extensions (MIME) Part Two: Media Types", RFC 2046, Extensions (MIME) Part Two: Media Types", RFC 2046,
December 1996. December 1996.
[MIME3] K. Moore, "MIME (Multipurpose Internet Mail Extensions) [MIME3] K. Moore, "MIME (Multipurpose Internet Mail Extensions)
Part Three: Message Header Extensions for Non-ASCII Part Three: Message Header Extensions for Non-ASCII
Text", RFC 2047, December 1996. Text", RFC 2047, December 1996.
[MIME1] N. Borenstein & N. Freed: "MIME (Multipurpose Internet
Mail Extensions) Part One: Mechanisms for Specifying and
ing and Describing the Format of Internet Message
Bodies", RFC 1521, Sept 1993.
[MIME4] N. Freed, J. Klensin, J. Postel, "Multipurpose Internet [MIME4] N. Freed, J. Klensin, J. Postel, "Multipurpose Internet
Mail Extensions (MIME) Part Four: Registration Mail Extensions (MIME) Part Four: Registration
Procedures", RFC 2048, January 1997. Procedures", RFC 2048, January 1997.
[MIME5] "Multipurpose Internet Mail Extensions (MIME) Part Five: [MIME5] "Multipurpose Internet Mail Extensions (MIME) Part Five:
Conformance Criteria and Examples", RFC 2049, December Conformance Criteria and Examples", RFC 2049, December
1996. 1996.
[NEWS] M.R. Horton, R. Adams: "Standard for interchange of [NEWS] M.R. Horton, R. Adams: "Standard for interchange of
USENET messages", RFC 1036, December 1987. USENET messages", RFC 1036, December 1987.
 End of changes. 13 change blocks. 
18 lines changed or deleted 28 lines changed or added

This html diff was produced by rfcdiff 1.34. The latest version is available from http://tools.ietf.org/tools/rfcdiff/