[rohc] Question regarding bit ordering in RTP headers packets RFC 3095

Mihir Mehta <mihirjm@gmail.com> Tue, 21 April 2009 01:59 UTC

Return-Path: <mihirjm@gmail.com>
X-Original-To: rohc@core3.amsl.com
Delivered-To: rohc@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 801093A680B for <rohc@core3.amsl.com>; Mon, 20 Apr 2009 18:59:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.669
X-Spam-Level:
X-Spam-Status: No, score=-1.669 tagged_above=-999 required=5 tests=[AWL=0.929, BAYES_00=-2.599, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PSG6WxJoZ+LF for <rohc@core3.amsl.com>; Mon, 20 Apr 2009 18:59:19 -0700 (PDT)
Received: from mail-gx0-f214.google.com (mail-gx0-f214.google.com [209.85.217.214]) by core3.amsl.com (Postfix) with ESMTP id B20383A6E35 for <Rohc@ietf.org>; Mon, 20 Apr 2009 18:59:19 -0700 (PDT)
Received: by gxk10 with SMTP id 10so1236533gxk.13 for <Rohc@ietf.org>; Mon, 20 Apr 2009 19:00:35 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:date:message-id:subject :from:to:content-type; bh=Rt56oKHC1oN3+7PkhFMH2oMRs94YqVhIbAzE/zOszvI=; b=BAlSsWZA4Rndlo1bgcEtEkD5Qvvo7gG2PfpK52BjgfT4xueySN98RC+xHyc7Y+HG+s ZkfkADB9RSlQBNkG5usZxIohhPvH+rLm+GpS6I0+m7ahi8EA9awYR4X6SEDuE2WpnvES DL3Zh6LmhUSzg2zLj6qNjdFyA3IlhU8onxX3s=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=hvSLlcB14d7GaFLpPMJa+dpjGX1dpFgHjsyv9TJBwmWkQuaDrItN2kzyb7hZCS9uq2 K6xOYHFkZ196uVunLbug2CDWgS5KF2T1KKsqH0Hc5AsqAFGGbnm8EzHL+UqZTEsC/EIQ 5FKToG7lDj9xOPdt9jjkSWWxqW/OdwCRGFZLk=
MIME-Version: 1.0
Received: by 10.231.19.72 with SMTP id z8mr3535338iba.42.1240279235409; Mon, 20 Apr 2009 19:00:35 -0700 (PDT)
Date: Tue, 21 Apr 2009 10:00:35 +0800
Message-ID: <86c08c690904201900i460dba07uc9c404ee7efaf9d7@mail.gmail.com>
From: Mihir Mehta <mihirjm@gmail.com>
To: Rohc@ietf.org
Content-Type: multipart/alternative; boundary="00221532cf343fb87d0468070392"
Subject: [rohc] Question regarding bit ordering in RTP headers packets RFC 3095
X-BeenThere: rohc@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Robust Header Compression <rohc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/rohc>, <mailto:rohc-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/rohc>
List-Post: <mailto:rohc@ietf.org>
List-Help: <mailto:rohc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rohc>, <mailto:rohc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 21 Apr 2009 01:59:20 -0000

Dear all,
I had a naive clarification on the bit ordering specified in the RFC 3095
for packets like RTP IR and IR-DYN.

Does the 0-7 bit labeling specified above the packet header diagrams specify
just the numbering of the bits or does it follow the same order too.

In other words, does it follow 0-7 or 7-0 (the least significant bit first
or most significant bit first) while formation and transmitting? It wasn't
very clear to me from the RFC.

Thanks in advance and best regards,
Mihir.