IFX Mail Archive: (no subject)
IFX Mail Archive: (no subject)
Wed, 17 Feb 1999 15:41:53 -0600 (CST)
At 12:47 PM 2/17/1999 -0800, Hastings, Tom N wrote:
>Here is the current image/tiff entry in the IANA registry. Is it ok?
>>From firstname.lastname@example.org Sat Jul 31 20:04:51 1993
>Subject: Registration of new MIME content-type/subtype
>Content-Type: text/plain; charset="us-ascii"
>Date: Sat, 31 Jul 1993 20:04:00 -0700
>From: Marshall Rose <email@example.com>
>MIME type name: image
>MIME subtype name: tiff
>Required parameters: none
>Optional parameters: none
>Encoding considerations: base64
>Security considerations: none
>Published specification: TIFF class F, as defined in:
> Tag Image File Format (TIFF) revision 6.0
> Developer's Desk Aldus Corporation
> 411 First Ave. South Suite
> 200 Seattle, WA 98104
> Tile Format for Internet Fax
>Person & email address to contact for further information:
> Glenn Parsons <Glenn.Parsons@Nortel.ca>
>Are you suggesting that just identifying the document-format as 'image/tiff'
>For conformance in IFAX using IPP, we may need to specify that image/tiff
>includes some particular profile. Or are you suggesting that we need to
>specify the profile in the value of the IPP "document-format" attribute in
>Does the submitter (client software) have to identify the profile being used
>in what is being submitted to the IPP Printer, or is it sufficient for the
>IPP Printer to indicate the profile or profiles that it will accept and
>image correctly for documents submitted with the document-format attribute
>indicating 'image/tiff'? If the latter is sufficient, we could just add a
>Printer Description attribute, say, tiff-profiles-supported, in which the
>printer lists the tiff profiles that it supports. Such an attribute would
>not be submitted with the document, but would be queriable using
>If the submitter has to identify the profile being passed, then we would
>need to add a new Job Template attribute (or may a new Operation attribute?)
>that indicates the "tiff-profile" being submitted. This attribute would
>only be submitted when the "document-format" attribute also being submitted
>>From: Richard Shockey [mailto:firstname.lastname@example.org]
>>Sent: Wednesday, February 17, 1999 09:26
>>To: Ron Bergman; Hastings, Tom N
>>Cc: ipp; email@example.com
>>Subject: Re: IPP> MOD - Ok to add 'image/tiff' and 'application/pdf' to
>>IPP/1.1 Model document format list?
>>At 08:40 AM 2/17/1999 -0800, Ron Berman wrote:
>>>A good suggestion!
>>> Ron Bergman
>>> Dataproducts Corp.
>>I would take a look a the following draft that has just been
>>RFC status ..
>>There are specific profiles of TIFF that have to be addressed to insure
>>compatibility with RFC2305.
>>o Content feature schema for Internet fax
>>Shockey Consulting LLC
>>8045 Big Bend Blvd. Suite 110
>>St. Louis, MO 63119
>>INTERNET Mail & IFAX : firstname.lastname@example.org
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1
Date: Wed, 17 Feb 1999 15:45:30 -0600
To: "Hastings, Tom N" <email@example.com>,
Ron Bergman <firstname.lastname@example.org>,
From: Richard Shockey <email@example.com>
Subject: RE: IPP> MOD - Ok to add 'image/tiff' and 'application/pdf' to
IPP/1.1 Model document format list?
Cc: ipp <firstname.lastname@example.org>,email@example.com,Lloyd.McIntyre@pahv.xerox.com