RObust Header Compression (ROHC): Context Replication for ROHC Profiles
draft-ietf-rohc-context-replication-06

Review by Brian Carpenter, Gen-ART

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.

[Ballot comment]
Reviewed by Brian Carpenter, Gen-ART

Full review in document log. Apart from I-D Nits, he says that he'd like more info on the applicability of the document.

Writeup from L-E Jonsson:

ROHC WG Chair Writeup for <draft-ietf-rohc-context-replication>

The document was separated from the TCP profile document because
it was agreed that the content could be applicable also to future
profiles, and thus should be a separate add-on. The technical
solutions have been developed during a two-year period, in
parallel with the TCP profile development, and are solid, simple,
and straightforward. All technical decisions were based on open
mail list discussions, and there has been solid WG consensus on
the content. One discussion about opening up for additional IP
address optimizations with a proposal called "IP address compression"
led to a consensus call that concluded against the proposal, both
(mainly) based on the questionable and limited technical merit, as
well as the fact that there were IPR issues related to it. For
details about this issue, please consult the ROHC mail list archive
from 2003-11-19 to 2003-12-18, one single thread with subject:
"IP Address Compression for Context Replication".

The document has been extensively reviewed by both ROHC folks and
the chairs, and as with all ROHC documents, there have also been
comitted document reviewers assigned, who have provided extensive
detail review. An additional external review was also made by
Brian Carpenter during IETF last-call.

After WGLC and chair review, the chairs thus believe the document
is ready for consideration by the IESG.