My response to Rens answers most of the questions you raised. I'd say
we have agreement that the type parameter be required. My concern
focuses on what if media_type(start) != media_type(type)? I'd say UAs
can base their decision on the type value.
Question, what configuration entry does the UA use for the
Multipart/Related type? Could the behavour of Application/Spiffy
differ from Multipart/Related; type="Application/Spiffy"? My view:
On Thu, 18 May 1995 14:23:27 EDT Chris Newman wrote:
There are two distinct parsing cases for multipart/related. One case
is when you do understand the meta-format, the other case is when you
don't understand the meta-format. In the former case, it's processed
as you describe. In the latter case, it's processed in a fashion
similar to multipart/mixed.
The problem with the start parameter ...
... remedied if the type parameter were mandatory when the start
parameter was present.