Jim,
The current IPP/1.1 I-D Model and Semantics draft has examples for
mimeMediaTypes to show some useful parameters for 'text/plain' so that
people get the idea about parameters on media types.
Should we add the faxbw and faxcolor parameters as examples to 'image/tiff'?
Then we would have three examples in the IPP Model and Semantics section
4.1.9:
'image/tiff': Tag Image Format - see IANA MIME Media Type registry
'image/tiff; application=faxbw': Tag Image Format - black and white
profile or subset of TIFF for Facsimile. see IANA MIME Media Type registry
'image/tiff; application=faxcolor': Tag Image Format - color profile or
subset of TIFF for Facsimile. see IANA MIME Media Type registry
Thanks,
Tom
Here is what we have in our Internet-Draft draft-ietf-ipp-model-v11-00.txt:
4.1.9 'mimeMediaType'
The 'mimeMediaType' attribute syntax is the Internet Media Type (sometimes
called MIME type) as defined by RFC 2046 [RFC2046] and registered according
to the procedures of RFC 2048 [RFC2048] for identifying a document format.
The value MAY include a charset parameter, depending on the specification of
the Media Type in the IANA Registry [IANA-MT]. Although most other IPP
syntax types allow for only lower-cased values, this syntax type allows for
mixed-case values which are case-insensitive.
Examples are:
'text/html': An HTML document
'text/plain': A plain text document in US-ASCII (RFC 2046 indicates that in
the absence of the charset parameter MUST mean US-ASCII rather than simply
unspecified) [RFC2046].
'text/plain; charset=US-ASCII': A plain text document in US-ASCII [52, 56].
'text/plain; charset=ISO-8859-1': A plain text document in ISO 8859-1
(Latin 1) [ISO8859-1].
'text/plain; charset=utf-8': A plain text document in ISO 10646 represented
as UTF-8 [RFC2279]
'application/postscript': A PostScript document [RFC2046]
'application/vnd.hp-PCL': A PCL document [IANA-MT] (charset escape sequence
embedded in the document data)
'image/tiff': Tag Image Format - see IANA MIME Media Type registry
'application/pdf': Portable Document Format - see IANA MIME Media Type
registry
'application/octet-stream': (REQUIRED) Auto-sense - see below
>-----Original Message-----
>From: James Rafferty [mailto:jrafferty at worldnet.att.net]
>Sent: Friday, February 19, 1999 07:29
>To: Hastings, Tom N; Keith Moore; Hastings, Tom N
>Cc: Masinter, Larry <masinter at parc.xerox.com>; McIntyre,
>Lloyd; Buckley,
>Robert R; Zilles, Steve; venable at wrc.xerox.com;
>Glenn.Parsons at nortel.ca;
>ipp; ifx at pwg.org>Subject: RE: IPP> Re: MOD - Confusion about image/tiff MIME
>Content Type
>>>>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.
>>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>*---------------------------------------------------
>