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

> Now that there will be TWO separated image/tiff and 
> image/tiff-fx MIME sub-types, I believe the Implementers 
> guide should at least point out that image/tiff is for some
> profiles only and the image/tiff-fx should be used
> for the other profiles. Implementers must be VERY aware of 
> this fact, and he Implementers guide must poit it out.
> Thus some revision seems necessary.

> Other opinions?
> 
> Regards,
> Claudio
> 
Claudio, here's my opinion ...
The Implementers Guide is informational and attempts to clarify, and reinforce text in the 'normative' RFCs that has been or could be misconstrued because of the manner in which the text was originally drafted.
If changes to the normative text are drafted so implementers are "VERY aware", and no misunderstanding is possible, then there's is no reason to do so again in the Implementers Guide.

So given that the normative text needs to be changed, we just need to make sure that it is very clear and there is no misunderstanding whatsoever as to how it should be used.

Vivian

> As a consequence there is a need for 3 documents:
> 
>  - a revised draft-ietf-fax-tiff-regbis which updates 
> image/tiff content type
> 
>  - a new registration draft registering image/tiff-fx MIME 
> sub-type and the corresponding file extension (.tfx)
>     
>  - a revised draft-ietf-fax-tiff-fx which defines which MIME 
> type to use, depending on the used profiles, and updates
> the rest of the specification as appropriate.
>