FW: review of draft-ietf-fax-ffpim-05.txt
"Scott Hollenbeck" <[email protected]> Fri, 9 Jul 2004 07:47:22 -0400
| Newsgroups | gmane.ietf.fax |
|---|---|
| Message-ID | <5BEA6CDB196A4241B8BE129D309AA4AF02E0F682@vsvapostal8.vcorp.ad.vrsn.com> |
Here are a few more late-breaking IESG review comments. These are mostly editorial, and can probably be addressed by ensuring that references are up-to-date and a few minor editorial changes are incorporated. -Scott- -----Original Message----- From: Alex Zinin [mailto:[email protected]] Sent: Friday, July 09, 2004 2:43 AM To: Scott Hollenbeck Subject: Fwd: review of draft-ietf-fax-ffpim-05.txt Scott- Here's the comments from Scott Brim about the refs I promised you. -- Alex http://www.psg.com/~zinin This is a forwarded message From: Scott W Brim <[email protected]> To: Alex Zinin <[email protected]> Cc: [email protected] Date: Tuesday, July 6, 2004, 12:36:41 AM Subject: review of draft-ietf-fax-ffpim-05.txt ===8<==============Original message text=============== It is targeted for Proposed Standard, but it depends overwhelmingly on other RFCs and drafts that are in flux. You need to decide on the order of doing things. It depends at least on RFCs 2305, 2532, and 3297, and draft-ietf-fax-esmtp-conneg-10.txt, which Joel reviewed. 2305 is currently being revised (draft-ietf-fax-service-v2-05.txt). 2532 is unassigned but a look at the 2305 replacement draft leads me to suspect that it will be revised after 2305. You saw Joel's review. What do you want to do with these dependencies? Personally I would hold off on this draft until those it depends on so heavily are dealt with. If you want to go forwardi, other than the dependencies there are no problems, modulo some nits: Nits: - the canonical headings for the references sections are "Normative References" and "Informative References". This has "References - Normative" and "References - Informative", and both are subsections under "References". - It has the 2026 boilerplate. That can also be fixed by rfc-editor. Nits that are insignificant on their own: - The first sentence of the introduction starts "The current specification defines". This is ambiguous, as proven by my misreading it. Just make it "This specification defines". ===8<===========End of original message text===========