My point is that if the purpose of the attribute exchange is to avoid
incompatibilities between sender and receiver, the current design isn't
going to work reliably. For example, there is the scenario of a client
sending a PS3 file to a PS2 IPP Printer.
> For the specific example, IPP includes
> the attribute "document-format" (mimeMediaType).
> Getting all current
> printer languages mime-typed is still in progress, but different document
> will be distinguishable.
However, this doesn't solve the problem in the example scenario. To solve
the problem we need to be able to distinguish versions of PS.
firstname.lastname@example.org@pwg.org on 03/11/2001 12:45:16 AM
Sent by: email@example.com
To: Carl Kugler/Boulder/IBM@IBMUS
cc: "Wagner,William" <firstname.lastname@example.org>, "'MAEDA toru'"
<email@example.com>, firstname.lastname@example.org, email@example.com
Subject: RE: IFX> RE: Fax processing confirmation; document-formats
> In general, I think it would be a good idea to register some standard
> Media Type "version" parameters. (Parameters are modifiers of the media
This has to be done as part of the registration of the media type itself.
You cannot register a parameter separately; there is no process for it.
> Some RFCs mention this possibility; for example, in RFC 2045:
> In particular, some formats (such as application/postscript) have
> version numbering conventions that are internal to the media format.
> Where such conventions exist, MIME does nothing to supersede them.
> no such conventions exist, a MIME media type might use a "version"
> parameter in the content-type field if necessary.
Correct, and several media types have been registered that have such
> I'm thinking of all the versions of PCL, for example: a particular
> may support some subset of existing PCL versions.
The current registration of PCL, application/vnd.hp-pcl, doesn't have such
parameter. The current change controller for this media type is HP; I
contacting someone there if you want to amend the registration and add
such a parameter.
> Here is a made-up example of a MIME content type field using the version
> Content-type: text/line-data; charset=ibm500 (EBCDIC 500V1);
Of course if you're registering such a media type yourself you can simply
such a parameter as part of your registration. Make sure you completely
the syntax of the parameter value.
This archive was generated by hypermail 2b29 : Mon Mar 12 2001 - 11:11:00 EST