bug in UO-1-ID packet format?

Asked by afathy on 2010-08-16

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

Question information

Language:
English Edit question
Status:
Answered
For:
rohc Edit question
Assignee:
No assignee Edit question
Last query:
2010-08-16
Last reply:
2010-08-22

Hi Ahmed,

This is a bug. Thank you for pointing it. I created a ticket to track the bug. See Bug #622402 (https://bugs.launchpad.net/rohc/trunk/+bug/622402).

Regards,
Didier Barvaux

Bug #622402 is now fixed.

Can you help with this problem?

Provide an answer of your own, or ask afathy for more information if necessary.

To post a message you must log in.