about Profile0x0000

Asked by regulararmy on 2013-12-23

hello Didier,
         As for your lib rohc-1.5.1, It seems as if there are some questions for profile0x0000, one of the questions is that it does not build the ACK feedback for profile0x0000, and the lib will also send NACK feedback when decompression failed, but profile0x0000 only has ACK feedback format(RFC3095). So, does the lib not supprot the profile0x0000 well? Thank.

Regards,
CXS

Question information

Language:
English Edit question
Status:
Solved
For:
rohc Edit question
Assignee:
No assignee Edit question
Solved by:
Didier Barvaux
Solved:
2014-03-04
Last query:
2014-03-04
Last reply:
2013-12-23

Hello,

You're right, the ROHC library does not conform to RFC 3095 for feedback. All 1.5.x and 1.6.x versions send ACK, NACK and SNACK and use FEEDBACK-2. They should:
 - send only ACK feedback (no NACK or SNACK).
 - use the FEEDBACK-1 format with 0 as profile-specific byte (no FEEDBACK-2 format).

RFC 3095, ยง5.10.4 entitled "Feedback" reads:
   The only kind of feedback in Profile 0x0000 is ACKs. Profile 0x0000
   MUST NOT be rejected. Profile 0x0000 SHOULD be associated with at
   most one CID. ACKs use the FEEDBACK-1 format of section 5.2. The
   value of the profile-specific octet in the FEEDBACK-1 ACK is 0
   (zero).

I opened a ticket in the bugtracker to fix this problem in next 1.7.0 release.

Didier

Thank you for spotting the problem!

regulararmy (regulararmy) said : #3

Thanks Didier Barvaux, that solved my question.