Re: TIFF-FX: technical changes since RFC 2301
Dave Crocker <[email protected]> Mon, 23 Dec 2002 13:51:19 -0800
| Newsgroups | gmane.ietf.fax |
|---|---|
| Organization | Brandenburg InternetWorking |
| Message-ID | <[email protected]> |
ned, since I asked the question(s), I'll respond to Ned's suggestions: Saturday, December 21, 2002, 8:57:33 AM, you wrote: >> Presumably there is a good reason to have tiff-fx contain this redundant >> capability. So, presumably, there are times when it IS a good thing to use? ned> I wouldn't call it a good thing but I can see some theoretical situations where ned> it might be necessary. For example, suppose you have an agent that sends out a ned> MIME object in serial fashion but which doesn't know initially which profile of ned> TIFF will be used. hence this argues in favor of having tiff-fx be a superset of tiff. that makes sense to me, except how can an agent not know which profile of TIFF it is using, at the start of the MIME body-part? Doesn't it need to provide the profile information right at the beginning of the body-part content? ned> Perhaps something along the lines of tiff-fx SHOULD NOT be used to label ned> profiles S and F except when the specific profile isn't available to the ned> labelling agent. right. d/ -- Dave <mailto:[email protected]> Brandenburg InternetWorking <http://www.brandenburg.com> t +1.408.246.8253; f +1.408.850.1850