rohc team mailing list archive
-
rohc team
-
Mailing list archive
-
Message #00213
[Question #121378]: bug in UO-1-ID packet format?
New question #121378 on rohc:
https://answers.launchpad.net/rohc/+question/121378
Why in the code in c_generic.c, the UO-1-ID is written as follows:
0 1 2 3 4 5 6 7
+-----+-----+-----+-----+-----+-----+-----+-----+
| 1 0 |T=0 | IP-ID |
+===+===+====+====+====+====+====+
| M | SN | CRC |
+-----+-----+-----+-----+-----+-----+-----+-----+
although in the RFC3095 5.7.3 page 81 it has an extension bit instead of the M bit
0 1 2 3 4 5 6 7
+-----+-----+-----+-----+-----+-----+-----+-----+
| 1 0 |T=0 | IP-ID |
+===+===+====+====+====+====+====+
| X | SN | CRC |
+-----+-----+-----+-----+-----+-----+-----+-----+
Thanks,
Ahmed
--
You received this question notification because you are a member of ROHC
Team, which is an answer contact for rohc.