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

> > 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)
> 
> I cannot see "type" feature tag in RFC2879.
> Could you tell us where it is defined, if you know?
> Or, can we use it, even if it is not defined?

The 'type' feature is defined in RFC 2913 "MIME Content Types
in Media Feature Expressions", G. Klyne, September 2000.

> > 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.
> 
> Yes. But is it really necessary information
> in capability description for sender side?
> It is different from necessary features such as 
> file-structure, density and paper-size.
> 
> This is just an example here.
> It is up to the editors to include, I think.

This is just in the example. It is useful to show how
content negotiation can be used with multiple MIME types.
As Graham pointed out, it is useful also in 'converted-'
headers to show, for example, if an image message was
converted from some other MIME type.

Larry
-- 
http://larry.masinter.net