IFX Mail Archive: IFX> FW: IETF Last Call Results for FAX WG

IFX Mail Archive: IFX> FW: IETF Last Call Results for FAX WG

IFX> FW: IETF Last Call Results for FAX WG Documents

From: McDonald, Ira (imcdonald@sharplabs.com)
Date: Thu Jun 24 2004 - 13:00:11 EDT

  • Next message: McDonald, Ira: "IFX> FW: Protocol Action: 'File Format for Internet Fax' to Draft Sta ndard"


    FYI - Scott Hollenbeck's comments on the Internet Fax
    extension documents (Conneg, Full Mode, IFAX in ENUM).
    Scott is their IETF Applications Area Director.

    - Ira

    Ira McDonald (Musician / Software Architect)
    Blue Roof Music / High North Inc
    PO Box 221 Grand Marais, MI 49839
    phone: +1-906-494-2434
    email: imcdonald@sharplabs.com

    -----Original Message-----
    From: owner-ietf-fax@mail.imc.org [mailto:owner-ietf-fax@mail.imc.org]On
    Behalf Of Hollenbeck, Scott
    Sent: Thursday, June 24, 2004 10:24 AM
    To: 'ietf-fax@imc.org'
    Subject: IETF Last Call Results for FAX WG Documents
    Importance: High

    The IETF last call for these documents:


    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 repeat
    them here for the benefit of the WG. Please note that all three documents
    will need to be updated before I will ask the IESG to review them:

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

    IANA: "We understand there to be NO IANA Actions for this document."

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

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

    - There's a reference to [KEYWORDS] on the first page, but no such reference
    exists. Please add a reference to RFC 2119 if that's the reference being

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

    - In section 4, please change the example to use one of the example domain
    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

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

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

    - 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 updated
    I will ask the IESG to review them.


    This archive was generated by hypermail 2b29 : Thu Jun 24 2004 - 13:00:30 EDT