RFC 5225, "RObust Header Compression Version 2 (ROHCv2): Profiles for RTP, UDP, IP, ESP and UDP-Lite", April 2008Source of RFC: rohc (tsv)
See Also: RFC 5225 w/ inline errata
Errata ID: 2703
Publication Format(s) : TEXT
Reported By: Carl Knutsson
Date Reported: 2011-02-03
Verifier Name: Wesley Eddy
Date Verified: 2012-06-05
Section 6.6.11 says:
o ip_id_behavior, one octet for each IP header in the compressible header chain starting from the outermost header. Each octet consists of 2 bits padded with 6 MSBs of zeroes.
It should say:
o ip_id_behavior_outer, one octet for each IPv4 header except the innermost in the compressible header chain starting from the outermost header. Each octet consists of 2 bits padded with 6 MSBs of zeroes. o ip_id_behavior_innermost, one octet if the innermost header is an IPv4 header. The octet consists of 2 bits padded with 6 MSBs of zeroes.
There is no control field called ip_id_behavior in the document. There are two control fields related to IP-ID behavior, ip_id_behavior_innermost and ip_id_behavior_outer. For IPv6, only the ip_id_behavior_innermost field exists and its value is always IP_ID_BEHAVIOR_RANDOM according to the FN. This makes it impossible to include ip_id_behavior_outer when calculating the crc for IPv6 headers. Furthermore, since the ip_id_behavior_innermost is constant it makes no sense to include it in the crc calculation.
This errata has been verified based on discussion on the ROHC mailing list involving the authors in February, 2011.