draft-ietf-mhtml-spec-04.txt   draft-ietf-mhtml-spec-05.txt 
Network Working Group Jacob Palme Network Working Group Jacob Palme
Internet Draft Stockholm University/KTH Internet Draft Stockholm University/KTH
draft-ietf-mhtml-spec-04.txt Alexander Hopmann draft-ietf-mhtml-spec-05.txt Alexander Hopmann
Category-to-be: Proposed standard ResNova Software, Inc. Category-to-be: Proposed standard ResNova Software, Inc.
Expires: March 1997 October 1996 Expires: April 1997 November 1996
MIME E-mail Encapsulation of Aggregate Documents, such as HTML (MHTML) MIME E-mail 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
documents of the Internet Engineering Task Force (IETF), its areas, and documents of the Internet Engineering Task Force (IETF), its areas, and
its working groups. Note that other groups may also distribute working its working groups. Note that other groups may also distribute working
documents as Internet-Drafts. documents as Internet-Drafts.
skipping to change at page 1, line 298 skipping to change at page 1, line 298
Content-Type: Multipart/related; boundary="boundary-example-1"; Content-Type: Multipart/related; boundary="boundary-example-1";
type=Text/HTML; start=foo2*foo3@bar2.net type=Text/HTML; start=foo2*foo3@bar2.net
; A Content-Base header cannot be placed here, since this is a ; A Content-Base header cannot be placed here, since this is a
; multipart MIME object. ; multipart MIME object.
--boundary-example-1 --boundary-example-1
Part 1: Part 1:
Content-Type: Text/HTML; charset=US-ASCII Content-Type: Text/HTML; charset=US-ASCII
Content-ID: foo2*foo3@bar2.net Content-ID: <foo2*foo3@bar2.net>
Content-Location: "http/www.ietf.cnir.reston.va.us/images/foo1.bar1"; Content-Location: http/www.ietf.cnir.reston.va.us/images/foo1.bar1
; This Content-Location must contain an absolute URI, since no base ; This Content-Location must contain an absolute URI, since no base
; is valid here. ; is valid here.
--boundary-example-1 --boundary-example-1
Part 2: Part 2:
Content-Type: Text/HTML; charset=US-ASCII Content-Type: Text/HTML; charset=US-ASCII
Content-ID: foo4*foo5@bar2.net Content-ID: <foo4*foo5@bar2.net>
Content-Location: "foo1.bar1" ; The Content-Base below applies to Content-Location: foo1.bar1 ; The Content-Base below applies to
; this relative URI ; this relative URI
Content-Base: "http:/www.ietf.cnri.reston.va.us/images/" Content-Base: http:/www.ietf.cnri.reston.va.us/images/
--boundary-example-1-- --boundary-example-1--
4.3 The Content-Location Header 4.3 The Content-Location Header
The Content-Location header specifies the URI that corresponds to the The Content-Location header specifies the URI that corresponds to the
content of the body part in whose heading the header is placed. Its content of the body part in whose heading the header is placed. Its
value CAN be an absolute or relative URI. Any URI or URL scheme may be value CAN be an absolute or relative URI. Any URI or URL scheme may be
used, but use of non-standardized URI or URL schemes might entail some used, but use of non-standardized URI or URL schemes might entail some
risk that recipients cannot handle them correctly. risk that recipients cannot handle them correctly.
skipping to change at page 1, line 351 skipping to change at page 1, line 351
Part 1: Part 1:
Content-Type: Text/HTML; charset=US-ASCII Content-Type: Text/HTML; charset=US-ASCII
... ... <IMG SRC="fiction1/fiction2"> ... ... ... ... <IMG SRC="fiction1/fiction2"> ... ...
--boundary-example-1 --boundary-example-1
Part 2: Part 2:
Content-Type: Text/HTML; charset=US-ASCII Content-Type: Text/HTML; charset=US-ASCII
Content-Location: "fiction1/fiction2" Content-Location: fiction1/fiction2
--boundary-example-1-- --boundary-example-1--
4.4 Encoding of URIs in e-mail headers 4.4 Encoding of URIs in e-mail headers
Since MIME header fields have a limited length and URIs can get quite Since MIME header fields have a limited length and URIs can get quite
long, these lines may have to be folded. If such folding is done, the long, these lines may have to be folded. If such folding is done, the
algorithm defined in [URLBODY] section 3.1 should be employed. algorithm defined in [URLBODY] section 3.1 should be employed.
5. Base URIs for resolution of relative URIs 5. Base URIs for resolution of relative URIs
skipping to change at page 1, line 575 skipping to change at page 1, line 575
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-1"; Content-Type: Multipart/related; boundary="boundary-example-1";
type=Text/HTML; start=foo3*foo1@bar.net type=Text/HTML; start=foo3*foo1@bar.net
--boundary-example 1 --boundary-example 1
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 hyperlink ... text of the HTML document, which might contain a hyperlink
to the other body part, for example through a statement such as: to the other body part, for example 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">
--boundary-example-1 --boundary-example-1
Content-Location: Content-Location:
"http://www.ietf.cnri.reston.va.us/images/ietflogo.gif" http://www.ietf.cnri.reston.va.us/images/ietflogo.gif
Content-Type: IMAGE/GIF Content-Type: IMAGE/GIF
Content-Transfer-Encoding: BASE64 Content-Transfer-Encoding: BASE64
R0lGODlhGAGgAPEAAP/////ZRaCgoAAAACH+PUNvcHlyaWdodCAoQykgMTk5 R0lGODlhGAGgAPEAAP/////ZRaCgoAAAACH+PUNvcHlyaWdodCAoQykgMTk5
NSBJRVRGLiBVbmF1dGhvcml6ZWQgZHVwbGljYXRpb24gcHJvaGliaXRlZC4A NSBJRVRGLiBVbmF1dGhvcml6ZWQgZHVwbGljYXRpb24gcHJvaGliaXRlZC4A
etc... etc...
--boundary-example-1-- --boundary-example-1--
9.3 Example with relative URIs to an embedded GIF picture 9.3 Example with relative URIs to an embedded GIF picture
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-Base: "http://www.ietf.cnri.reston.va.us" Content-Base: http://www.ietf.cnri.reston.va.us
Content-Type: Multipart/related; boundary="boundary-example-1"; Content-Type: Multipart/related; boundary="boundary-example-1";
type=Text/HTML type=Text/HTML
--boundary-example 1 --boundary-example 1
Content-Type: Text/HTML; charset=ISO-8859-1 Content-Type: Text/HTML; charset=ISO-8859-1
Content-Transfer-Encoding: QUOTED-PRINTABLE Content-Transfer-Encoding: QUOTED-PRINTABLE
... text of the HTML document, which might contain a hyperlink ... text of the HTML document, which might contain a hyperlink
to the other body part, for example through a statement such as: to the other body part, for example through a statement such as:
<IMG SRC="/images/ietflogo.gif" ALT="IETF logo"> <IMG SRC="/images/ietflogo.gif" ALT="IETF logo">
Example of a copyright sign encoded with Quoted-Printable: =A9 Example of a copyright sign encoded with Quoted-Printable: =A9
skipping to change at page 1, line 642 skipping to change at page 1, line 642
type=Text/HTML type=Text/HTML
--boundary-example 1 --boundary-example 1
Content-Type: Text/HTML; charset=US-ASCII Content-Type: Text/HTML; charset=US-ASCII
... text of the HTML document, which might contain a hyperlink ... text of the HTML document, which might contain a hyperlink
to the other body part, for example through a statement such as: to the other body part, for example through a statement such as:
<IMG SRC="cid:foo4*foo1@bar.net" ALT="IETF logo"> <IMG SRC="cid:foo4*foo1@bar.net" ALT="IETF logo">
--boundary-example-1 --boundary-example-1
Content-ID: foo4*foo1@bar.net Content-ID: <foo4*foo1@bar.net>
Content-Type: IMAGE/GIF Content-Type: IMAGE/GIF
Content-Transfer-Encoding: BASE64 Content-Transfer-Encoding: BASE64
R0lGODlhGAGgAPEAAP/////ZRaCgoAAAACH+PUNvcHlyaWdodCAoQykgMTk5 R0lGODlhGAGgAPEAAP/////ZRaCgoAAAACH+PUNvcHlyaWdodCAoQykgMTk5
NSBJRVRGLiBVbmF1dGhvcml6ZWQgZHVwbGljYXRpb24gcHJvaGliaXRlZC4A NSBJRVRGLiBVbmF1dGhvcml6ZWQgZHVwbGljYXRpb24gcHJvaGliaXRlZC4A
etc... etc...
--boundary-example-1-- --boundary-example-1--
10. Content-Disposition header 10. Content-Disposition header
skipping to change at page 1, line 792 skipping to change at page 1, line 792
14. References 14. References
Ref. Author, title Ref. Author, title
--------- -------------------------------------------------------- --------- --------------------------------------------------------
[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 1806, June 1995.
[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,November 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 "Internationalization of the Hypertext Markup
Language". draft-ietf-html-i18n-04.txt, May 1996. Language". draft-ietf-html-i18n-05.txt, May 1996.
[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.
[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.
[MD5] R. Rivest: "The MD5 Message-Digest Algorithm", RFC 1321, [MD5] R. Rivest: "The MD5 Message-Digest Algorithm", RFC 1321,
April 1992. April 1992.
 End of changes. 12 change blocks. 
14 lines changed or deleted 14 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/