RE: [rohc] P bit role on INPUT-BYTES

["West, Mark" <mark.a.west at roke.co.uk>]

 

Hi Ranjith,

 

You are correct to say that the P-bit does *not* affect the reading of data in the INPUT-BYTES instruction.  INPUT-BYTES always returns only complete bytes, bit-for-bit as found in the input data, irrespective of the P-, F- or H- bits.  (The text is not perhaps quite as explicit about this as it could be!)

Cheers,

 

Mark.

 

 

 

-----Original Message-----
From: Ranjith.V at aricent.com [mailto:Ranjith.V at aricent.com]
Sent: 24 July 2007 11:17
To: rohc at ietf.org
Subject: [rohc] P bit role on INPUT-BYTES

Hi all,

I have a doubt in P-Bit of Input-Bit-Order register :

As per RFC 3320 , section 8.2 :-
      "Note that the INPUT-BITS and INPUT-HUFFMAN instructions retrieve a
   stream of individual compressed bits from the dispatcher.  To provide
   bitwise compatibility with various well-known compression algorithms,
   the input_bit_order register can modify the order in which individual
   bits are passed within a byte."

This points to the fact that P-Bit will not effect Input-Byte
instruction.
The register Input-Bit-Order shall effect only the "Input-Bits" and
"Input-Huffmann" instructions. Please clarify if the value of P-Bit
effect the order of reading bits in byte for INPUT-BYTES instruction.
(Some parts of the same section seems to suggest that P-Bit will
effect the order of bits in all the INPUT instructions.)


Thanks and Regards
Ranjith Reddy. V
Extn: 9134
Location : F4-122

***********************  Aricent- Confidential   ***********************

"DISCLAIMER: This message is proprietary to Aricent and is intended solely for the use of 
the individual to whom it is addressed. It may contain privileged or confidential information and should not be 
circulated or used for any purpose other than for what it is intended. If you have received this message in error, 
please notify the originator immediately. If you are not the intended recipient, you are notified that you are strictly
prohibited from using, copying, altering, or disclosing the contents of this message. Aricent accepts no responsibility for 
loss or damage arising from the use of the information transmitted by this email including damage from virus."

_______________________________________________
Rohc mailing list
Rohc at ietf.org
https://www1.ietf.org/mailman/listinfo/rohc