RFC 4996, "RObust Header Compression (ROHC): A Profile for TCP/IP (ROHC-TCP)", July 2007
Note: This RFC has been obsoleted by RFC 6846Source of RFC: rohc (tsv)
Errata ID: 1288
Publication Format(s) : TEXT
Reported By: Alfred Hoenes
Date Reported: 2008-01-21
Rejected by: Magnus Westerlund
Date Rejected: 2009-09-07
Throughout the document, when it says:
It should say:
IR and IR-DYN
RFC 4996 is very confusing regarding the ROHC packet types used.
Section 2 (on top of page 5) says only 3 types are used: IR, IR-CR, and CO.
This is restated in a few places.
But significant text in RFC 4996 also details the use of the IR-DYN
According to RFC 4995, IR-DYN is a distinct packet type.
It looks like the terminology has been floating for some time,
and the text of RFC 4996 has not been adjusted to the final
terminology used in RFC 4995, before publication as an RFC,
although both RFCs have been published in a coordinated way.
To give the reader a hint on the problem, I suggest a change note
for Section 2 -- this will be posted as a separate Errata Note --
and detail the other places in the text affected by this issue
in an accompanying message to be evalueated by the verifiers,
to avoid an email avalanche.
This report will also include other issues found not suitable for
reporting via this form based system.
Authors and WG chairs are of the opinion that it is reasonably clear that IR is both a class of packets type. So from the context it should be understandable when the class is meant rather than the specific type. And clarification would also require major changes in several docs.