Re: [codec] RTP Payload Format and File Storage Format for Opus Speech and Audio Codec - draft-spittka-payload-rtp-opus-00

Cullen Jennings <fluffy@cisco.com> Wed, 06 July 2011 16:43 UTC

Return-Path: <fluffy@cisco.com>
X-Original-To: codec@ietfa.amsl.com
Delivered-To: codec@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 691DB21F8894; Wed, 6 Jul 2011 09:43:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.504
X-Spam-Level:
X-Spam-Status: No, score=-110.504 tagged_above=-999 required=5 tests=[AWL=0.095, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
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 yd6fA1dJgcJj; Wed, 6 Jul 2011 09:43:44 -0700 (PDT)
Received: from sj-iport-5.cisco.com (sj-iport-5.cisco.com [171.68.10.87]) by ietfa.amsl.com (Postfix) with ESMTP id 9714C21F8895; Wed, 6 Jul 2011 09:43:44 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=fluffy@cisco.com; l=1121; q=dns/txt; s=iport; t=1309970624; x=1311180224; h=subject:mime-version:from:in-reply-to:date:cc: content-transfer-encoding:message-id:references:to; bh=HnvptrznsMrgGQcbY7JH82Ch6llBjjIZmfQHyXZtwZ0=; b=EM26xsNI2u7EYI5y3OxrogQOYQBQlX6twZGZdcThi1seyiQf6E6yVp9T CjKmYDrR+T3HV5IpS07bQTNc9pGS9h+Z+i4eIUG07CDqn9fIMPlwwP8hi GiL3PicZZV2T1jGlV32dS8S9phd3Oapdxa9gBvTnE0f1rCVMPvQIl5TdH Y=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av0EAHePFE6rRDoJ/2dsb2JhbABTqAV3iHqlO54WhjcEh0aKe4R6i2I
X-IronPort-AV: E=Sophos;i="4.65,488,1304294400"; d="scan'208";a="362469463"
Received: from mtv-core-4.cisco.com ([171.68.58.9]) by sj-iport-5.cisco.com with ESMTP; 06 Jul 2011 16:43:44 +0000
Received: from [192.168.4.100] (rcdn-fluffy-8712.cisco.com [10.99.9.19]) by mtv-core-4.cisco.com (8.14.3/8.14.3) with ESMTP id p66GhhRr021391; Wed, 6 Jul 2011 16:43:43 GMT
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Cullen Jennings <fluffy@cisco.com>
In-Reply-To: <00f501cc3aa7$551264c0$ff372e40$@spittka@skype.net>
Date: Wed, 6 Jul 2011 10:43:45 -0600
Content-Transfer-Encoding: quoted-printable
Message-Id: <75A39260-8D02-4F1F-B5F1-3A3BA09D8F43@cisco.com>
References: <00f501cc3aa7$551264c0$ff372e40$@spittka@skype.net>
To: julian.spittka@skype.net, payload@ietf.org
X-Mailer: Apple Mail (2.1084)
Cc: codec@ietf.org
Subject: Re: [codec] RTP Payload Format and File Storage Format for Opus Speech and Audio Codec - draft-spittka-payload-rtp-opus-00
X-BeenThere: codec@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Codec WG <codec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/codec>, <mailto:codec-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/codec>
List-Post: <mailto:codec@ietf.org>
List-Help: <mailto:codec-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/codec>, <mailto:codec-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 06 Jul 2011 16:43:45 -0000

I would prefer to see the file format separated into a separate draft for two reason. One, it allows an implementation to say they do RFC XXXX and have that be clear if the mean the RTP payload or the file format. Two, I suspect the file format conversation might take longer to resolve. 

Cullen

PS - this discussion and draft needs to happen in the payloads WG, feel free to CC the rtcweb@ietf.org mailing list.

On Jul 4, 2011, at 6:06 PM, Julian Spittka wrote:

> All,
> 
> Please find a first draft "draft-spittka-payload-rtp-opus-00" for the "RTP
> Payload Format and File Storage Format for Opus Speech and Audio Codec"
> uploaded at
> https://datatracker.ietf.org/doc/draft-spittka-payload-rtp-opus/. 
> 
> Any feedback, questions, or comments are highly welcome.
> 
> Best Regards,
> 
> Julian.
> 
> ---
> Julian Spittka
> Skype
> 
> see & chat: julian_spittka
> write: julian.spittka@skype.net
> 
> 
> _______________________________________________
> codec mailing list
> codec@ietf.org
> https://www.ietf.org/mailman/listinfo/codec