Document: draft-ietf-rohc-context-replication-06.txt
From: Brian E Carpenter 
Date: 18 januari 2005 

I think this is basically ready to go, but I have one comment,
and there are some nits.

This draft seems well written (not as a stand-alone,
but as part of the ROHC document set) and I didn't find
any obvious issues.

I would have appreciated more discussion of the applicability.
It is quite complex and is only of use if the two ends indulge
in a sequence of similar short sessions - typical
of HTTP 1.0 but not of HTTP 1.1. So are we sure that the
implementation cost is worthwhile? Where is the tradeoff point?
It is very hard to tell.

(There is a work in progress reference on this, but I would
have preferred a couple of paragraphs in the specification.)

The boilerplate is home-made.

There is no IANA Considerations section.

Other minor nits too:

idnits 1.58

tmp/draft-ietf-rohc-context-replication-06.txt:

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

  * The document seems to lack an IANA Considerations section.
    Checking conformance with RFC 3667/3668 boilerplate...
  * The document seems to lack an RFC 3667 Section 5.1 IPR Disclosure
    Acknowledgement  -- however, there's a paragraph with a matching beginning.
    Boilerplate error?
  * The document seems to lack an RFC 3668 Section 5, para 1 IPR Disclosure
    Acknowledgement.
  * The document seems to lack an RFC 3668 Section 5, para 2 IPR Disclosure
    Acknowledgement.
  * The document seems to lack an RFC 3668 Section 5, para 3 IPR Disclosure
    Invitation.

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

  * The document seems to lack a 1id_guidelines paragraph about 6 months
    document validity -- however, there's a paragraph with a matching beginning.
    Boilerplate error?
  * 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 4 instances of lines with hyphenated line breaks in the
    document.
  - Line 125 has weird spacing: '...tion by  reusi...'

    Run idnits with the --verbose option for more detailed information.