IFX Mail Archive: RE: IFX> RE: Fax processing confirmation;

IFX Mail Archive: RE: IFX> RE: Fax processing confirmation;

RE: IFX> RE: Fax processing confirmation; document-formats

From: Carl Kugler (kugler@us.ibm.com)
Date: Mon Mar 12 2001 - 11:10:48 EST

  • Next message: ned.freed@mrochek.com: "RE: IFX> RE: Fax processing confirmation; document-formats"

    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.

    Bill wrote:
    > 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.


    ned.freed@mrochek.com@pwg.org on 03/11/2001 12:45:16 AM

    Sent by: owner-ifx@pwg.org

    To: Carl Kugler/Boulder/IBM@IBMUS
    cc: "Wagner,William" <wwagner@netsilicon.com>, "'MAEDA toru'"
          <maeda.toru@canon.co.jp>, ifx@pwg.org, ietf-fax@imc.org
    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
    > subtype.)

    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
    > paramater:

    > Content-type: text/line-data; charset=ibm500 (EBCDIC 500V1);
    > version=ibm3800

    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