Comment 4 for bug 1008329

hello,

“I disagree with your analysis of the RFC. The IP-ID field that is "passed as additional octets at the end of the compressed header, after any extensions" is not the optional IP-ID in extension 3 (optional field present if I=1 as you mentioned). This is clear in the general format of the ROHC header described on page 77 of RFC 3095 [1].”

I check the RFC 3095 and I was wrong. however,

"The UOR-2-TS packet type cannot be used if the IP-ID is not random (RND=1) and cannot be deduced from the reference IP-ID and the transmitted SN."
I think RND=1 means that ip-id is random. In RFC3095 page 82, UOR-2-TS cannot be used if there is no IPv4 header in the
context or if value(RND) and value(RND2) are both 1. It seems that you mean "The UOR-2-TS packet type can be used if the IP-ID is random (RND=1)"