Re: I-D ACTION:draft-ietf-fax-esmtp-conneg-06.txt

Larry Masinter wrote:
>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.


I think that "type=image/tiff" should not be included in the reply 
to CONNEG because the reply is a capability of recipient. 
There is some possibilty that the capability of recipient allow 
sender to select which type of feature.
Sender can define the type after receiving the capability of 
recipient because the capability has the same information without 
"type" feature as Klein-san said.

>
>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)

This is the capability of sender. So, it deosn't need include "type"
feature as I said previously.

>
>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)
>

It might be usefull to include "type=image/tiff-fx" because 
it is the feature of document which the relay server received.


>
>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.
>

I agree that it should say 
"RFC 2822 message with MIME content-type: image/tiff-fx"

Thank you

Kiyoshi Toyoda