Re: [AVT] Endianess issue
"Neo Anderson" <neo@wiseone.zzn.com> Wed, 03 September 2003 04:45 UTC
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA04898 for <avt-archive@odin.ietf.org>; Wed, 3 Sep 2003 00:45:37 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19uPW4-00044y-Nn for avt-archive@odin.ietf.org; Wed, 03 Sep 2003 00:45:13 -0400
Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h834jCYv015596 for avt-archive@odin.ietf.org; Wed, 3 Sep 2003 00:45:12 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19uPVv-000422-8j; Wed, 03 Sep 2003 00:45:03 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19uPVF-00040y-3b for avt@optimus.ietf.org; Wed, 03 Sep 2003 00:44:21 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA04756 for <avt@ietf.org>; Wed, 3 Sep 2003 00:44:14 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19uPVC-0006Wo-00 for avt@ietf.org; Wed, 03 Sep 2003 00:44:18 -0400
Received: from c2mailgwalt.mailcentro.com ([207.183.238.112]) by ietf-mx with esmtp (Exim 4.12) id 19uPVA-0006UV-00 for avt@ietf.org; Wed, 03 Sep 2003 00:44:16 -0400
Received: from c2web204 (c0mailgwalt4.prontomail.com [207.183.238.114]) by c2mailgwalt.mailcentro.com (8.12.8/8.12.0-c2mailgw04) with SMTP id h834hnLS019940; Tue, 2 Sep 2003 21:43:49 -0700
X-Version: Mailcentro(english)
X-SenderIP: 203.200.24.199
X-SenderID: 8114614
From: Neo Anderson <neo@wiseone.zzn.com>
Message-Id: <3ADBB8B95FB1EEF40BAD098EF056111C@neo.wiseone.zzn.com>
Date: Wed, 03 Sep 2003 10:11:46 +0530
X-Priority: Normal
Content-Type: text/html
To: bprashanth@neomagic.com, avt <avt@ietf.org>
Reply-To: Neo@wiseone.zzn.com
Subject: Re: [AVT] Endianess issue
X-Mailer: Web Based Pronto
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: by Mailcentro using amavisd-milter wirh reject option
Content-Transfer-Encoding: 7bit
Sender: avt-admin@ietf.org
Errors-To: avt-admin@ietf.org
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=unsubscribe>
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Comments inline.
>These calls work fine for the fields in the RTP and RTCP header that
>are either 8 or 16 or 32 bits long.
Yes, they are meant for 16/32 bit fields only. hence the "s" and "l"
in their names.
>However, such call won't be effective when we deal with header
>fields that are of length other than the ones specified above.
>For e.g. In RTCP header, the report block in a SR or RR report
>header has a 8-bit "fraction lost" field and a 24-bit "cummulative
>number of packets lost" field. It would worth noting that there are
>no OS utilities that can do "network to host order conversion" for a
>24 bit field of
>"cummulative number of packets lost" in the SR or RR report. How
>does one handle this situation.
Assigning the data from the integer (the 24 bits you may be having in
a 32 bit integer, let us say), octet by octet (say by masking the 32
bit integer) to the "char buffer" you are using to send the packet on
the network is one way to handle this. Care that it shold be in n/w
byte order.
afaik, there is no standard macro/function for doing this.
--Neo
Get your own Free E-mail at Witch Wisdom http://www.witchwisdom.com
__________________
http://www.zzn.com
- [AVT] Endianess issue B Prashanth
- Re: [AVT] Endianess issue Neo Anderson
- Re: [AVT] Endianess issue Neo Anderson