IETF Logo Mail Archive

Re: [AVT] Vorbis RTP issues list for Vienna

Ross Finlayson <finlayson@live.com> Thu, 10 July 2003 00:06 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 UAA29988 for <avt-archive@odin.ietf.org>; Wed, 9 Jul 2003 20:06:07 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19aOwM-0003v7-Ul for avt-archive@odin.ietf.org; Wed, 09 Jul 2003 20:05:39 -0400
Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h6A05cZD014995 for avt-archive@odin.ietf.org; Wed, 9 Jul 2003 20:05:38 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19aOvl-0003nD-9z; Wed, 09 Jul 2003 20:05:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19aOvZ-0003mm-4T for avt@optimus.ietf.org; Wed, 09 Jul 2003 20:04:50 -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 UAA29926 for <avt@ietf.org>; Wed, 9 Jul 2003 20:04:47 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19aOvX-0005Wp-00 for avt@ietf.org; Wed, 09 Jul 2003 20:04:47 -0400
Received: from ns.live.com ([66.80.62.34]) by ietf-mx with esmtp (Exim 4.12) id 19aOvW-0005Wl-00 for avt@ietf.org; Wed, 09 Jul 2003 20:04:46 -0400
Received: from ns.live.com (localhost.live.com [127.0.0.1]) by ns.live.com (8.12.9/8.12.9) with ESMTP id h6A03Pgi040599 for <avt@ietf.org>; Wed, 9 Jul 2003 17:04:44 -0700 (PDT) (envelope-from rsf@ns.live.com)
Received: (from rsf@localhost) by ns.live.com (8.12.9/8.12.9/Submit) id h6A03PLj040598; Wed, 9 Jul 2003 17:03:25 -0700 (PDT) (envelope-from rsf)
Message-Id: <4.3.1.1.20030709165921.00b806f0@laptop-localhost>
X-Sender: rsf@laptop-localhost
X-Mailer: QUALCOMM Windows Eudora Version 4.3.1
Date: Wed, 09 Jul 2003 17:03:03 -0700
To: avt@ietf.org
From: Ross Finlayson <finlayson@live.com>
Subject: Re: [AVT] Vorbis RTP issues list for Vienna
In-Reply-To: <1057793135.3f0ca46f5ad99@dlana.elec.gla.ac.uk>
References: <200307092202.h69M2gb27052@snap.CS.Berkeley.EDU> <200307092202.h69M2gb27052@snap.CS.Berkeley.EDU>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
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>

>Having a general purpose streaming codebook is a reasonable suggestion, 
>John and I discussed when we met, but it is uncertain if a fully generic 
>one can be produced which will cater for all scenarios.

There doesn't have to be just one 'codebook for streaming'.  Having a small 
number of pre-defined ones would be OK also.  E.g., if there were <= 256 
pre-defined 'codebooks for streaming', then you could use a 1-byte field 
within the RTP payload format to indicate which one.  But I suspect that <= 
16 pre-defined codebooks (i.e., 4 bits) would be enough.

         Ross.


_______________________________________________
Audio/Video Transport Working Group
avt@ietf.org
https://www1.ietf.org/mailman/listinfo/avt

v2.37.1 | Report a Bug | By Email | System Status