draft-ietf-mhtml-related-v2-00.txt   draft-ietf-mhtml-related-v2-01.txt 
Network Working Group E. Levinson Network Working Group E. Levinson
Internet Draft J. Palme
IETF status to be: Proposed standard Expires: February 1999 IETF status to be: Proposed standard
Replaces: RFC 2112 Replaces: RFC 2112
The MIME Multipart/Related Content-type The MIME Multipart/Related Content-type
This draft document is being circulated for comment. Please send This draft document is being circulated for comment. Please send
your comments to the authors or to the mimesgml mail list your comments to the authors or to the mimesgml mail list
mhtml@segate.sunet.se. mhtml@segate.sunet.se.
Status of this Memo Status of this Memo
skipping to change at line 48 skipping to change at line 47
Changes from RFC 2112: Corrected cid urls to conform to RFC 2111; Changes from RFC 2112: Corrected cid urls to conform to RFC 2111;
the angle brackets were removed. the angle brackets were removed.
Changes from draft-ietf-mhtml-related-02.txt Changes from draft-ietf-mhtml-related-02.txt
....Added mandatory quoting on the type parameter, since it contains ....Added mandatory quoting on the type parameter, since it contains
special characters ("@") and since MIME (RFC 2045) requires quoting special characters ("@") and since MIME (RFC 2045) requires quoting
of all parameters to Content-Type which contain special characters. of all parameters to Content-Type which contain special characters.
Updated references. Updated references.
0.1 Changes from v2-00
Added mandatory quoting for the same reason as above to the start
parameter and the cid-list in the start-info parameter.
Corrected the syntax for cid-list by making cid-list token on the
rhs options (enclosed in square brackets).
1. Introduction 1. Introduction
Several applications of MIME, including MIME-PEM, and MIME-Macintosh Several applications of MIME, including MIME-PEM, and MIME-Macintosh
and other proposals, require multiple body parts that make sense only and other proposals, require multiple body parts that make sense only
in the aggregate. The present approach to these compound objects has in the aggregate. The present approach to these compound objects has
been to define specific multipart subtypes for each new object. In been to define specific multipart subtypes for each new object. In
keeping with the MIME philosophy of having one mechanism to achieve keeping with the MIME philosophy of having one mechanism to achieve
the same goal for different purposes, this document describes a the same goal for different purposes, this document describes a
single mechanism for such aggregate or compound objects. single mechanism for such aggregate or compound objects.
skipping to change at line 158 skipping to change at line 165
interpretation of start-info. User Agents shall provide the interpretation of start-info. User Agents shall provide the
parameter's value to the processing application. Processes can parameter's value to the processing application. Processes can
distinguish a start-info reference from a token or quoted-string by distinguish a start-info reference from a token or quoted-string by
examining the first non-white-space character, "<" indicates a examining the first non-white-space character, "<" indicates a
reference. reference.
3.4. Syntax 3.4. Syntax
related-param := [ ";" "start" "=" <"> cid <"> ] related-param := [ ";" "start" "=" <"> cid <"> ]
[ ";" "start-info" "=" [ ";" "start-info" "="
( cid-list / value ) ] ( <"> cid-list <"> / value ) ]
[ ";" "type" "=" type "/" subtype ] [ ";" "type" "=" <"> type "/" subtype <"> ]
; order independent ; order independent
cid-list := cid cid-list cid-list := cid [ cid-list ]
cid := msg-id ; c.f. [822] cid := msg-id ; c.f. [822]
value := token / quoted-string ; c.f. [MIME] value := token / quoted-string ; c.f. [MIME]
; value cannot begin with "<" ; value cannot begin with "<"
Note that the parameter values will usually require quoting. Msg-id Note that the parameter values will usually require quoting. Msg-id
contains the special characters "<", ">", "@", and perhaps other contains the special characters "<", ">", "@", and perhaps other
special characters. If msg-id contains quoted-strings, those quote special characters. If msg-id contains quoted-strings, those quote
marks must be escaped. Similarly, the type parameter contains the marks must be escaped. Similarly, the type parameter contains the
special character "/". special character "/". The syntax include the required quoting.
4. Handling Content-Disposition Headers 4. Handling Content-Disposition Headers
Content-Disposition Headers [DISP] suggest presentation styles for Content-Disposition Headers [DISP] suggest presentation styles for
MIME body parts. [DISP] describes two presentation styles, called MIME body parts. [DISP] describes two presentation styles, called
the disposition type, INLINE and ATTACHMENT. These, used within a the disposition type, INLINE and ATTACHMENT. These, used within a
multipart entity, allow the sender to suggest presentation multipart entity, allow the sender to suggest presentation
information. [DISP] also provides for an optional storage (file) information. [DISP] also provides for an optional storage (file)
name. Content-Disposition headers could appear in one or more body name. Content-Disposition headers could appear in one or more body
parts contained within a Multipart/Related entity. parts contained within a Multipart/Related entity.
skipping to change at line 418 skipping to change at line 425
[DISP] R. Troost, S. Dorner, "Communicating Presentation Informa- [DISP] R. Troost, S. Dorner, "Communicating Presentation Informa-
tion in Internet Messages: The Content-Disposition Header", tion in Internet Messages: The Content-Disposition Header",
August 1997, RFC 2183. August 1997, RFC 2183.
[MIME] Freed, N., Borenstein, N.: Multipurpose Internet Mail [MIME] Freed, N., Borenstein, N.: Multipurpose Internet Mail
Extensions (MIME) Part One: Format of Internet Message Extensions (MIME) Part One: Format of Internet Message
Bodies. November 1996, RFC 2045. Bodies. November 1996, RFC 2045.
9. Author's addresses 9. Author's addresses
Edward Levinson Jacob Palme Edward Levinson
47 Clive Street Stockholm University and KTH 47 Clive Street
Metuchen, NJ 08840-1060 Skeppargatan 73 Metuchen, NJ 08840-1060
USA SE-115 30 Stockholm, Sweden USA
Phone: +1 908 494 1606 Phone: +46-8-16 16 67 Phone: +1 908 494 1606
E-mail: XIson@cnj.digex.com E-mail: jpalme@dsv.su.se E-mail: XIson@cnj.digex.com
 End of changes. 7 change blocks. 
6 lines changed or deleted 13 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/