IPP> Re: MOD - Confusion about image/tiff MIME Content Type

IPP> Re: MOD - Confusion about image/tiff MIME Content Type

IPP> Re: MOD - Confusion about image/tiff MIME Content Type

James Rafferty jrafferty at worldnet.att.net
Fri Feb 19 17:34:58 EST 1999


At 10:29 AM 2/19/99 -0500, James  Rafferty wrote:
>Tom, 
>
>At 03:46 PM 2/18/99 -0800, Hastings, Tom N wrote:
>>Keith,
>>
>>Thanks.  So it looks like the IPP Model and Semantics 'mimeMediaType' value
>>of 'image/tiff' should point to the IANA Registry, not a particular RFC.  
>>
>Yes, I'd agree with this.   
>>For future work and an extension to IPP to be developed in the IFAX over IPP
>>WG, we will need to solve the Interoperability Considerations problem called
>>out below where there are different profiles for TIFF.
>>
>Please note that there is one additional IANA consideration that was
>specified in Annex B of RFC 2301, on the two values that HAVE been
>specified for the TIFF application parameter ("faxbw" and "faxcolor" ).   I
>have pointed out this omission to Keith Moore, so that IANA hopefully can
>finish bringing the image/tiff registry up to date.   Also, please note
>that RFC 2302 also contains a template for the registration of future TIFF
>application parameter values, if they are needed.     
>
The IANA image/tiff registration now also reflects this.  

see:  http://www.isi.edu/in-notes/iana/assignments/media-types/image/tiff

James

*------------------------------------------------*
James Rafferty			
President, Human Communications LLC	
12 Kevin Drive			
Danbury, CT  06811-2901		
USA					
Voice/Fax:  +1-203-746-4367
Email/Internet Fax:  JRafferty at worldnet.att.net
	 J_Rafferty_HC at compuserve.com
     jrafferty at humancomm.com

HC Web Site:  http://www.humancomm.com  
*---------------------------------------------------



More information about the Ipp mailing list