Re: [codec] Frames to Packets in draft-ietf-codec-opus-07?

Ralph Giles <> Tue, 26 July 2011 18:01 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id CE37911E8135; Tue, 26 Jul 2011 11:01:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.048
X-Spam-Status: No, score=-2.048 tagged_above=-999 required=5 tests=[AWL=0.929, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-1]
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id nhMcz4qiBspi; Tue, 26 Jul 2011 11:01:50 -0700 (PDT)
Received: from ( []) by (Postfix) with ESMTP id 2C14711E8132; Tue, 26 Jul 2011 11:01:50 -0700 (PDT)
Received: by vws12 with SMTP id 12so646389vws.31 for <multiple recipients>; Tue, 26 Jul 2011 11:01:49 -0700 (PDT)
MIME-Version: 1.0
Received: by with SMTP id t8mr1639225vco.128.1311703309600; Tue, 26 Jul 2011 11:01:49 -0700 (PDT)
Received: by with HTTP; Tue, 26 Jul 2011 11:01:49 -0700 (PDT)
X-Originating-IP: []
In-Reply-To: <00ec01cc4ad6$8125b2d0$83711870$>
References: <00ec01cc4ad6$8125b2d0$83711870$>
Date: Tue, 26 Jul 2011 11:01:49 -0700
Message-ID: <>
From: Ralph Giles <>
To: Christian Hoene <>
Content-Type: text/plain; charset=UTF-8
Subject: Re: [codec] Frames to Packets in draft-ietf-codec-opus-07?
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Codec WG <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Tue, 26 Jul 2011 18:01:50 -0000

2011/7/25 Christian Hoene <>de>:

> I was wondering why the draft-ietf-codec-opus-07 draft has feature to
> concatenate multiple codec frames to packets. At the same time,
> draft-spittka-payload-rtp-opus-00 does not support to place multiple codec
> entities in on RTP packet.

I believe the codec authors have described some of their reasoning for
the internal framing. However, it sounds like your concern is the
presence of framing at the codec level, rather than at the RTP payload

There is precedent for this in previous specifications. "Guidelines for
Frame-Based Audio Encodings" says:

  "Frame-based encodings encode a fixed-length block of audio into
   another block of compressed data, typically also of fixed length.
   For frame-based encodings, the sender MAY choose to combine several
   such frames into a single RTP packet.  The receiver can tell the
   number of frames contained in an RTP packet, if all the frames have
   the same length, by dividing the RTP payload length by the audio
   frame size which is defined as part of the encoding.  This does not
   work when carrying frames of different sizes unless the frame sizes
   are relatively prime.  If not, the frames MUST indicate their size.


   All frame-oriented audio codecs SHOULD be able to encode and decode
   several consecutive frames within a single packet. [...]"

Opus can use variable length encoded frames, so the clause that
_frames_ must indicate their size, so that the codec can "decode
several consecutive frames within a single packet" applies. The
referent here is frames and codecs, not the payload format, so I don't
think we're breaking new ground here by having some framing at the
codec level.

I would also point out that the opus codec draft is nearly finished.
Continuing to specify framing there, rather than adding complication
to the newer RTP draft, is the quicker path to standardization of both