IETF Last Call Results for FAX WG Documents

The IETF last call for these documents:

draft-ietf-fax-esmtp-conneg-09.txt
draft-ietf-fax-ffpim-04.txt
draft-ietf-fax-faxservice-enum-02.txt

has concluded.  The only comments received were those I provided and some
provided by IANA.  They can be found in the I-D tracker, but I will repea=
t
them here for the benefit of the WG.  Please note that all three document=
s
will need to be updated before I will ask the IESG to review them:

draft-ietf-fax-esmtp-conneg-09.txt
"SUMMARY" should be "ABSTRACT" on the title page.

[KEYWORDS] (RFC 2119?) is cited as a reference in the text, but it's not
listed among the normative references.
// End of comments.

draft-ietf-fax-ffpim-04.txt
IANA: "We understand there to be NO IANA Actions for this document."

Numerous occurrences of a "=C2" non-ASCII character must be removed.

Section 4: s/applies/apply/
// End of comments.

draft-ietf-fax-faxservice-enum-02.txt:
- There's a reference to [KEYWORDS] on the first page, but no such refere=
nce
exists.  Please add a reference to RFC 2119 if that's the reference being
described.

- The line lengths get a little long in section 3 (I-D nit, "No text beyo=
nd
the 72nd column of a line").

- In section 4, please change the example to use one of the example domai=
n
names cited in RFC 2606 instead of "ifax.com".  example.com perhaps?

- Please split references into normative and informative subsections in
section 6 (I-D nit).  You can leave informative out if all references are
normative.

- Update the [ENUMbis] reference to point to RFC 3761.

- Remove the reference for [FFPIM].  I don't see it used anywhere in the
document.

- The boilerplate is outdated, but the RFC Editor will fix that.
// End of comments.

Please update each document to address the last call comments.  Once upda=
ted
I will ask the IESG to review them.

-Scott-