Re: TIFF-FX Safe subset

Iwazaki-san,

> TOSHIBA TEC has products which implement profileS, F and J.
> If a new MIME type (eg. image/tifffx) is defined for TIFF-FX,
> there is an interoperability issue between existing products and new
> products which
> deploy the new MIME type.
> It is very difficult to update the firmware of existing products in order to
> handle the new MIME type, because users can not update the firmware,
> service people of dealers or manufacturers have to update in users' site.
> 
> We can distinguish between TIFF V6 and TIFF-FX using RFC2302.
> IFAX products use the sub-type as follows.
> 
> Content-type: image/tiff; application=faxbw
> 
> That's my idea.

After the meeting, I talked and mailed more with lots of people.
I understand the situation.

Yes. You are right. RFC2302 intension is what you are suggesting.
But, unfortunately, it seems that the application parameter is not
handled by most viewers or something. This is one of the reason for
compatibility issue.

Even if Profile J will not be included in the safe subset,
it is better to address that some previous machines use image/tiff
for all Profiles in the new document. 

Any other implementation information is welcome.

Regards
--
Hiroshi Tamura, Co-chair of IETF-FAX WG
E-mail: [email protected]