RE: No description for image/tiff in Impl-Guide

[James Rafferty <jraff@xxxxxxxxxxxxxx>]

Tamura-san,  

Some related edits could be:  

5.4 Content-Type for the file format

The content-type "image/tiff" should only be used for Profiles S and F.
Some existing implementations based on [RFC 2301] may use "image/tiff" for
other Profiles.
However, this usage is now deprecated.   Instead, the content-type
"image/tiff-fx" whose
registratin is being defined in [TIFF-FX-REG} should be used.    
Also, "image/tiff-fx" may be used for Profile S and F.

BTW, is the last sentence true, or would image/tiff always be used for S and
F?

James

> -----Original Message-----
> From: Hiroshi Tamura [mailto:tamura@xxxxxxxxxxxxxxxx]
> Sent: Tuesday, December 18, 2001 6:36 AM
> To: Claudio.Allocchio@xxxxxxx
> Cc: ietf-fax@xxxxxxx; Lloyd.McIntyre@xxxxxxxxxxxxxx
> Subject: Re: No description for image/tiff in Impl-Guide
> 
> 
> 
> Claudio,
> 
> Thanks for your comment.
> 
> > As I already said, the exact procedures for single cases 
> will be decided 
> > by IESG and IAB, as we know the situation for this case is 
> "very peculiar"
> 
> > The important action on us as a WG is to check now where 
> updates and 
> > clarifications are needed, and poit out immediately the new text.
> 
> OK. I will include something about content-type.
> I hope I can edit it by this month.
> 
> New-section:
> 
> -------------------------------------------------------------------
> 5.4 Content-Type for the file format
> 
> The content-type "image/tiff" should be only used for Profile S and F.
> Old implementations might use "image/tiff" for other Profiles.
> But, it should be avoided. The content-type "image/tiff-fx" 
> should be used
> for them. Also, "image/tiff-fx" can be used for Profile S and F.
> 
> -------------------------------------------------------------------
> 
> If anybody has good description about it, please let me know.
> Are the 2nd and the 3rd sentence unnecessary?
> 
> Regards,
> --
> Hiroshi Tamura, Ricoh Company, LTD.
> E-mail: tamura@xxxxxxxxxxxxxxxx
>