Document: draft-ietf-rohc-sigcomp-nack-02
Review: Lucy E. Lynch
Date: 9 december 2004 

A Negative Acknowledgement Mechanism for Signaling Compression
draft-ietf-rohc-sigcomp-nack-02

This draft is ready for publication as a Proposed Standard RFC

Note that it has a few small nits (see below) and some odd pagination
issues but the document is very well written. The case for NACK is clearly
explained and the draft has seen good discussion and review on the rohc
list and the updates listed at the end of the document reflect the
evolution of the draft and fairly represent the issues raised. See for
example: http://www1.ietf.org/mail-archive/web/rohc/current/msg02541.html

Some of the phrasing can be a bit stilted:
"Detection of support for the NACK mechanism may be beneficial in some
 certain circumstances.  For example, with the current definition of
 SigComp, acknowledgment of state receipt is required before a sender
 can reference such state."
but the intention is clear.
----------------------------------------------------------------------
idnits 1.51:

draft-ietf-rohc-sigcomp-nack-02.txt:

  Checking nits according to http://www.ietf.org/ID-Checklist.html:

    Checking conformance with RFC 3667/3668 boilerplate...
    the boilerplate looks good.
    There are 558 instances of lines with non-ascii characters in the
    document.

  Checking nits according to http://www.ietf.org/ietf/1id-guidelines.txt:

    The document seems to lack a 1id_guidelines paragraph about the list
    of current Internet-Drafts -- however, there's a paragraph with a
    matching beginning. Boilerplate error?

  Miscellaneous warnings:

  There are 1 instance of lines with hyphenated line breaks in the
  document.