IESG Review: draft-ietf-fax-ffpim-05.txt

The IESG reviewed draft-ietf-fax-ffpim-05.txt during today's telechat.  I've
included the comments below and request that the authors and WG chairs talk
to the ADs that provided the comments.  The document will definitely need to
be revised to address the "Discuss" issues described by Steve Bellovin and
Ted Hardie.  The actions to take with the other comments will likely depend
on the outcome of discussions with the reviewers.

These comments can also be found in the I-D tracker.

-Scott-
----------
Steve Bellovin:
Discuss:
[2004-07-06] Format conversions by intermediaries breaks S/MIME. 2305, on
which this builds, specifically suggests using S/MIME and PGP.

Ted Hardie:
Discuss:
[2004-07-06] This has a normative dependency on the ESMTP conneg mechanism,
which I
believe is not ready for widespread deployment.  As it stands, this document
specifies the use of RFC3297 at a MUST level, and the proposed ESMTP
conneg mechanism as a MAY.  I believe it would be wiser to remove the
ESMTP conneg mechanism.

The note on "direct mode" (Appendix A), is very useful to framing the
discussion, and I believe that the CONNEG mechanism has many fewer
problems in "direct mode".  If there were a way to specify that the
CONNEG mechanism such that it would only be used in direct mode,
I believe the resulting interaction would meet the timeliness and feature
requirements set out.  Unfortunatley, the fundamentally "store-
and-forward nature of email might make that difficult to achieve

Bert Wijnen:
Comment:
[2004-07-08] 
The text about IPR in the abstract does not belong there.
I assume RFC-Editor will take care of that