Re: [payload] Padding in draft-ietf-codec-opus-07?

Stephen Botzko <stephen.botzko@gmail.com> Mon, 25 July 2011 17:24 UTC

Return-Path: <stephen.botzko@gmail.com>
X-Original-To: payload@ietfa.amsl.com
Delivered-To: payload@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3F74A21F8BC1; Mon, 25 Jul 2011 10:24:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level:
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1dpifBAA-6wd; Mon, 25 Jul 2011 10:24:52 -0700 (PDT)
Received: from mail-pz0-f53.google.com (mail-pz0-f53.google.com [209.85.210.53]) by ietfa.amsl.com (Postfix) with ESMTP id 59FEB21F8BB6; Mon, 25 Jul 2011 10:24:49 -0700 (PDT)
Received: by pzk6 with SMTP id 6so8404488pzk.26 for <multiple recipients>; Mon, 25 Jul 2011 10:24:49 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=date:subject:message-id:from:to:mime-version:content-type :content-transfer-encoding; bh=SLRR4lgIytC/gesyQ6H1OeW4139SJdwqYjATvJLFFCc=; b=LKtgfM2cxFjwjrEsGZHaztDbtVIEyBe6lD5eGu73/jC8FOxQDk2TxeGVOl80zCnPSL ZhHKe1SXRXTZiVYnjXCDoLNJmyt23AaIFTPd7XDKWVxRBKiNMfcxu0QOO1Xnz9mbkAgw iD8y7gCt3DzkwOiMRdUDfqBM+blVdhE1TGJfw=
Received: by 10.68.66.170 with SMTP id g10mr8340090pbt.490.1311614688837; Mon, 25 Jul 2011 10:24:48 -0700 (PDT)
Received: from localhost (dhcp-15e4.meeting.ietf.org [130.129.21.228]) by mx.google.com with ESMTPS id k8sm4711769pbk.15.2011.07.25.10.24.46 (version=SSLv3 cipher=OTHER); Mon, 25 Jul 2011 10:24:47 -0700 (PDT)
Date: Mon, 25 Jul 2011 13:24:46 -0400
Message-ID: <alfa6gciihvgjrgt8pdpi6na.1311614686145@email.android.com>
From: Stephen Botzko <stephen.botzko@gmail.com>
To: hoene@uni-tuebingen.de, payload@ietf.org, codec@ietf.org
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
Subject: Re: [payload] Padding in draft-ietf-codec-opus-07?
X-BeenThere: payload@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Audio/Video Transport Payloads working group discussion list <payload.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/payload>, <mailto:payload-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/payload>
List-Post: <mailto:payload@ietf.org>
List-Help: <mailto:payload-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/payload>, <mailto:payload-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 25 Jul 2011 17:24:53 -0000

I think RTP padding should be sufficient.

Regards,
Stephen

Sent from my Verizon Wireless Device

Christian Hoene <hoene@uni-tuebingen.de> wrote:

>Hello,
>
>I am wondering about a padding feature in draft-ietf-codec-opus-07. It
>allows you to extend the frame size by filling it up with zeros.
>
> I just spoke with the Tim, Jean-Marc and Gregory about this feature. As far
>as I understood, this feature is required at transcoding gateways to enforce
>a stream of packets having a constant size (while using UDP). Otherwise,
>attackers could potentially follow the conversation by observing packet
>sizes. 
>
>To my understanding, padding is a feature that can be easily skipped from
>the codec specification. It violates the layering principle and is intended
>only for a very specific use cases. On the other side, constant sized frames
>can be easily supported by keeping the codec parameters fixed.
>
>With best regards,
>
> Christian Hoene
>
>
>
>----------------------------------------------------------------------------
>-----
>Dr.-Ing. Christian Hoene, University of Tübingen, Computer Science, Chair of
>Communication Networks, Research Group Interactive Communication Systems
>(ICS)
>Sand 13, 72076 Tübingen, Germany, Tel +49 7071 2970532,
>www.net.uni-tuebingen.de
>
>
>
>_______________________________________________
>payload mailing list
>payload@ietf.org
>https://www.ietf.org/mailman/listinfo/payload