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).
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).