RE: I-D ACTION:draft-ietf-fax-esmtp-conneg-06.txt
"Larry Masinter" <[email protected]> Wed, 26 Feb 2003 21:45:53 -0800
| Newsgroups | gmane.ietf.fax |
|---|---|
| Message-ID | <003a01c2de23$7da71a00$b3422099@MASINTER> |
This is really a minor editorial suggestion. The example
in section 9.2
S: 250-CONNEG (&(image-file-structure=TIFF-minimal)
S: 250-CONNEG (MRC-mode=0)
should say
S: 250-CONNEG (&(type=image/tiff)
S: 250-CONNEG (image-file-structure=TIFF-minimal)
S: 250-CONNEG (MRC-mode=0)
because there is some possibility of using image/tiff
or image/tiff-fx, or at least it is not clear which is
mandated by the other parameters.
The example in section 9.1, instead of
Content-Convert:
(&(image-file-structure=TIFF-minimal)
could say
Content-Convert:
(&(type=image/tiff-fx)
(image-file-structure=TIFF-minimal)
and the example in section 9.3, instead of
(&(image-file-structure=TIFF-minimal)
(MRC-mode=0)
could say
(&(content-type=image/tiff-fx)
(image-file-structure=TIFF-minimal)
(MRC-mode=0)
In addition, the examples in section 9.1 and 9.2 which currently
say "RFC 2822 message with MIME Content-type:TIFF-FX"
should be changed to
"RFC 2822 message with MIME content-type: image/tiff-fx".
since both examples use JBIG which is consistent with image/tiff-fx.