I agree that the IPP mimeMediaType must allow any parameters that have been
registered. If there are MANDATORY parameters in a registration then they
MUST be included. OPTIONAL parameters MAY be included.
So I'll change the wording as suggested by Larry in the next version of the
IPP/1.1 Model and Semantics document. I think we don't need to mention the
charset parameter in the description of the attribute syntax, since we have
several text/plain example values, one without the charset parameter and 3
with the charset parameter.
I've also suggested in other mail that we have 'image/tiff' without a
parameter and two more values with application parameters with faxbw and
>From: Larry Masinter [mailto:masinter at parc.xerox.com]
>Sent: Wednesday, February 17, 1999 18:41
>To: Hastings, Tom N; ipp
>Subject: RE: IPP> MOD - Ok to add 'image/tiff' and 'application/pdf' to
>IPP/1.1 Model document format list?
>>>I suggest that IPP/1.1 change, with regard to MIME types, from:
>># The value MAY include a charset parameter, depending on the
># specification of the Media Type in the IANA Registry [IANA-MT].
>># The value MAY include any number of parameters, depending
># on the specification of the Media Type in the IANA Registry
>>Many media type registrations have both required and optional
>parameters. A MIME type which requires a parameter is meaningless
>without the parameter, and there are many other parameters other
>>It is also true that most 'text' types allow a 'charset' parameter,
>and you can point this out if you want; the current wording, though,
>seems to imply that parameters other than 'charset' are not allowed,
>which would be wrong.