Since this document attempts to update the MIME content-disposition field,
Actually it doesn't do that. That was already done in RFC 3204. All this
document does is to try and insure that definition is consistent across
multiple applications of content-disposition.
not to mention the handling of DSNs, MDNs, and SIP (?!), it seems like a
good idea if folks on this list take a look at it.
Seems reasonable to me.
Personally, I think it's a mess.
Care to be more specific? This document is about to be last called for the
second time. It has been openly discussed in the working group on numerous
occasions. The SIP document was last called, approved, and published some time
ago. I don't recall receiving a single message from you expressing concern
about any of this.
(there's something terribly wrong if the VPIM working group can make updates
to mainstream email protocols without explicit review from the mainstream
folks)
That's why we have IETF last calls. The document title clearly indicates that
it is a general MIME mechanism. Frankly, if you want to be upset about
something, be upset about RFC 3204, where neither the title nor the abstract
indicate that a parameter has been added to content-disposition.
Ned