IETF Logo Mail Archive

Re: [rtcweb] Working group last call for draft-ietf-rtcweb-audio

Bernard Aboba <bernard.aboba@gmail.com> Sat, 19 December 2015 00:24 UTC

Return-Path: <bernard.aboba@gmail.com>
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 E25EA1A0110 for <rtcweb@ietfa.amsl.com>; Fri, 18 Dec 2015 16:24:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] 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 2w8zW3MuHNtX for <rtcweb@ietfa.amsl.com>; Fri, 18 Dec 2015 16:24:18 -0800 (PST)
Received: from mail-yk0-x22e.google.com (mail-yk0-x22e.google.com [IPv6:2607:f8b0:4002:c07::22e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 964631A0114 for <rtcweb@ietf.org>; Fri, 18 Dec 2015 16:24:18 -0800 (PST)
Received: by mail-yk0-x22e.google.com with SMTP id p130so77141873yka.1 for <rtcweb@ietf.org>; Fri, 18 Dec 2015 16:24:18 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=LI/DNBiBilyGdh4btfpOWLGmDIeM8eLzhpaiYLpDGik=; b=chPWnw4FkBMXLNiSeG/hTsYxk1SW9aS5Gi9MMf+q+Zq0fTveN/OPJZYvw3B8ZIM270 QNboARmCrT/FzDwAH7V2Yjy9bSCac139eQUdiLpq0vlBicRfndEqXc9/RJngfKnd01RU XtJZ9qSYJn9MwueAMc6bXPuwRg8AxZsR4ifCpi1MimH56MtgDHBnWO+9eePy8c3UHFbR a/HSNEotXKRfnTM8tSXTa5EKFsnrLkn0AM1sP97fCy4NHdSq2CHZoj6aw/XXnXv8JGJn Ug6HHg7encVf7tykCY5di+EtOUJx5yGDz/Yhaajqfb41kzac+VhcYmI2eaI7qQuhbSvh +Dpw==
X-Received: by 10.13.253.7 with SMTP id n7mr5447843ywf.74.1450484657887; Fri, 18 Dec 2015 16:24:17 -0800 (PST)
Received: from [10.0.1.2] (c-73-49-202-70.hsd1.fl.comcast.net. [73.49.202.70]) by smtp.gmail.com with ESMTPSA id c67sm18530621ywe.31.2015.12.18.16.24.16 (version=TLSv1/SSLv3 cipher=OTHER); Fri, 18 Dec 2015 16:24:16 -0800 (PST)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (1.0)
From: Bernard Aboba <bernard.aboba@gmail.com>
X-Mailer: iPad Mail (13C75)
In-Reply-To: <56747874.2050508@nostrum.com>
Date: Fri, 18 Dec 2015 19:24:15 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <64791609-0D32-4202-AAC1-4CBD053FD0A3@gmail.com>
References: <CA+9kkMDAL1mKqt7cTRmU4YqX2S5QN4RKn2cfbPaBeDgx=yiN0Q@mail.gmail.com> <AE360F77-1902-412D-B5FF-6157D8D44C41@gmail.com> <56747874.2050508@nostrum.com>
To: Adam Roach <adam@nostrum.com>
Archived-At: <http://mailarchive.ietf.org/arch/msg/rtcweb/2AqIPFZdtFQKiCtB0PPbYgMxwTg>
Cc: Cullen Jennings <fluffy@cisco.com>, "rtcweb@ietf.org" <rtcweb@ietf.org>
Subject: Re: [rtcweb] Working group last call for draft-ietf-rtcweb-audio
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: <https://mailarchive.ietf.org/arch/browse/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: Sat, 19 Dec 2015 00:24:21 -0000

On Dec 18, 2015, at 16:19, Adam Roach <adam@nostrum.com> wrote:
> 
> I'm a little confused about where this leaves the state of play. You're proposing the the W3C spec leave it open as to whether sending an "A" through the API will work or throw an exception? 

[BA] Today this depends on whether an implementation supports sending "A" or not. As long as the audio document does not prohibit or mandate support for A-D, there may be some implementations that will recognize A-D and others that won't. The W3C API leaves it open to accommodate the options provided by the audio document.  

In the absence of a prohibition or requirement to support A-D, the best we can do is make it possible in the API for the application to discover what tones are supported, so it can adjust. RFC 4733 describes SDP that provides that information, and similar capabilities have been discussed in ORTC (though they are not currently in the spec since all existing implementations support the full range of tones).

v2.23.0 | Report a Bug | By Email