Add extension support for UO-1-ID packet

Bug #896842 reported by Didier Barvaux on 2011-11-27
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
rohc
Status tracked in Rohc-main
Rohc-main
Medium
Didier Barvaux

Bug Description

The UO-1-ID packet supports extensions through its X bit. The ROHC library supports X=0 only at the moment. Please add support for X=1.

Required work:
 - update the compressor function to code extensions at step 5,
 - update the decompressor function to decode extensions at step 5,
 - update the compressor algorithm that decides which packet type is
   the better one to make use of the UO-1-ID extensions.

Didier Barvaux (didier-barvaux) wrote :

Scheduled for 2.0.0.

description: updated
Didier Barvaux (didier-barvaux) wrote :

Support added in main branch. See http://bazaar.launchpad.net/~didier-barvaux/rohc/main/revision/788

* update the compressor function to code extensions for UO-1-ID,
* update the decompressor function to parse extensions for UO-1-ID,
* update the compressor algorithm that decides which packet type is
   the better one to make use of the UO-1-ID extensions,
    * the RTP Marker bit can now be updated by UO-1-ID with extension 3,
    * more than 1 IPv4 header with non-random IP-ID bits can now be
       transmitted with extension 3,
* always put the IP-ID bits of the innermost IPv4 header with non-random
   IP-ID in base UO-1-ID header,
* there is no reparse need for UO-1-ID extension 3 as there are for
   UOR-2* extension 3, but a check for changing RND bits was added,
* update the rtp_uor2_disambiguation test for UO-1-ID (renamed
   rtp_uo_disambiguation in consequence),
* update the output PCAP files of the non-regression test in
   consequence: some more bits are saved :)

tags: added: conformance rtp
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers