Re: [rtcweb] Number of samples (ptime) to be supported by required codecs (draft-ietf-rtcweb-audio-05)

Harald Alvestrand <harald@alvestrand.no> Tue, 18 February 2014 22:58 UTC

Return-Path: <harald@alvestrand.no>
X-Original-To: rtcweb@ietfa.amsl.com
Delivered-To: rtcweb@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AD7131A0406 for <rtcweb@ietfa.amsl.com>; Tue, 18 Feb 2014 14:58:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.448
X-Spam-Level:
X-Spam-Status: No, score=-2.448 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.548] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1WWlLKWoAEdg for <rtcweb@ietfa.amsl.com>; Tue, 18 Feb 2014 14:58:07 -0800 (PST)
Received: from mork.alvestrand.no (mork.alvestrand.no [158.38.152.117]) by ietfa.amsl.com (Postfix) with ESMTP id DF2CD1A026A for <rtcweb@ietf.org>; Tue, 18 Feb 2014 14:58:06 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mork.alvestrand.no (Postfix) with ESMTP id 592AB7C4BAC for <rtcweb@ietf.org>; Tue, 18 Feb 2014 23:58:03 +0100 (CET)
X-Virus-Scanned: Debian amavisd-new at alvestrand.no
Received: from mork.alvestrand.no ([127.0.0.1]) by localhost (mork.alvestrand.no [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8QwFOUl335ZB for <rtcweb@ietf.org>; Tue, 18 Feb 2014 23:58:02 +0100 (CET)
Received: from [172.19.7.58] (unknown [216.239.45.90]) by mork.alvestrand.no (Postfix) with ESMTPSA id 4FB9C7C4BA0 for <rtcweb@ietf.org>; Tue, 18 Feb 2014 23:58:02 +0100 (CET)
Message-ID: <5303E578.3000207@alvestrand.no>
Date: Tue, 18 Feb 2014 23:58:00 +0100
From: Harald Alvestrand <harald@alvestrand.no>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: rtcweb@ietf.org
References: <530320F7.4090300@ericsson.com>
In-Reply-To: <530320F7.4090300@ericsson.com>
X-Enigmail-Version: 1.6
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/rtcweb/H_s7fbvxKqaB5w9fDCKIBynuMvs
Subject: Re: [rtcweb] Number of samples (ptime) to be supported by required codecs (draft-ietf-rtcweb-audio-05)
X-BeenThere: rtcweb@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Real-Time Communication in WEB-browsers working group list <rtcweb.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtcweb>, <mailto:rtcweb-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/rtcweb/>
List-Post: <mailto:rtcweb@ietf.org>
List-Help: <mailto:rtcweb-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtcweb>, <mailto:rtcweb-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 18 Feb 2014 22:58:10 -0000

I may be a little simple-minded, but if we have a recommendation that
receivers MUST be able to receive all packetizations of G.711 and OPUS
up to 200 ms per packet, and that receivers should signal this by
sending "a=maxptime:200" in their SDP, what situations exist where
interoperability is not going to be achieved?

I mean - if a G.711 receiver is able to handle any packet size thrown at
it, why do we need to put requirements on the sender (apart from "don't
send bigger packets than the maxptime")? For interoperability with
non-WebRTC endpoints?

Of course, I do have a question, now that all the ptime and maxtime
definitions have been put on the table:

Is it true that ptime and maxptime only specify the SDP sender's
declaration of his desires for incoming packet streams? That is, that
there is nowhere specified what the sender intends to send? I think that
is true for ptime in RFC 3264 offer/answer, and would assume that the
same is true for maxptime.