uncompressed profile: feedback behavior does not conform to RFC 3095
Bug #1263693 reported by
Didier Barvaux
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | ||
|---|---|---|---|---|---|---|
| rohc | Status tracked in Rohc-main | |||||
| Rohc-1.5.x |
Won't Fix
|
Medium
|
Didier Barvaux | |||
| Rohc-1.6.x |
Won't Fix
|
Medium
|
Didier Barvaux | |||
| Rohc-main |
Fix Released
|
Medium
|
Didier Barvaux | |||
Bug Description
regulararmy reported the following problem:
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.
Revision history for this message
| Didier Barvaux (didier-barvaux) wrote | #1 |
| tags: | added: conformance library uncompressed |
To post a comment you must log in.
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).