> I just joined this list so I have probably missed earlier parts of
> this conversation, but on a miknor point, why not just allow the
> "boundary=" parameter on top level Context-Type: headers that don't
> normally have this parameter instead of inventing a whole new
> Content-Terminator: header?
Because it would be wrong. The 'boundary' isn't a property of
image/gif. If you extract the document and then include it in a mail
message, you don't suddenly change it from "content-type: image/gif;
boundary=foo" to "content-type: image/gif". The content-type should
not change based on the method of transfer.
The boundary is best thought of as a property of the
content-transfer-encoding rather than of the content-type.