RObust Header Compression (ROHC): Requirements on TCP/IP Header Compression
draft-ietf-rohc-tcp-requirements-08

IANA Comments:
We understand this document to have NO IANA ACTIONS.  Per the IANA Considerations section, a protocol that meets the requirements in this document will require the IANA to assign various numbers, but these would need to be defined in other documents or via defined registration procedures.

Review from Michael Patton, Gen-ART

Summary:  This draft is ready for publication as an Informational RFC

I am moved to say that this is one of the best documents I've ever
reviewed.  It's complete, concise and very readable.  I didn't even
notice any typos (and as my other GenART reviews can attest, I usually
pick up a fair number).  I only noticed one improvement that I thought
it could use [next paragraph], but not something important enough to
delay publication at this point.

As I was reading Section 2.3 Item 3 which describes the decompressor
noting that an error occurred, it struck me that in a similar way the
compressor should note if the incoming TCP is already damaged...  It's
probably not too important for this document to mention that, and, of
course, algorithms and/or implementations might include it anyway, but
it might have been useful to mention it for completeness.  On the
other hand, at this stage I do not recommend making such a change to
the document since that would require re-review by many.  I only
mention it to bring it to your attention in case the document does
undergo a rewrite where it could be included.

[Ballot comment]
Reviewed by Michael Patton, Gen-ART
Review in document log; quote: "I am moved to say that this is one of the best documents I've ever reviewed.  It's complete, concise and very readable."