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: 1289
Publication Format(s) : TEXT
Reported By: Alfred Hoenes
Date Reported: 2008-01-21
Rejected by: Magnus Westerlund
Date Rejected: 2009-09-07
Section 2, pg. 5 says:
ROHC-TCP packet types ROHC-TCP uses three different packet types: the Initialization and Refresh (IR) packet type, the Context Replication (IR-CR) packet type, and the Compressed packet (CO) type.
It should say:
ROHC-TCP packet types ROHC-TCP uses four different packet types: the Initialization and Refresh (IR) packet type, the IR-DYN (IR, dynamic update) packet type, the Context Replication (IR-CR) packet type, and the Compressed packet (CO) type.
ROHC-TCP makes use of IR-DYN packets, as can be seen in other parts
of the text.
According to RFC 4995, IR-DYN is a distinct ROHC packet type,
and RFC 4995 does not contain the notion of a packet sub-type
that might have justified subsuming IR-DYN as a non-self-sustaining
packet always to be included/assumed as well when talking about the
IR packet type.
For more information see the GLOBAL Errata Report issued on this topic.
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.