IETF Logo Mail Archive

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

Bernard Aboba <bernard.aboba@gmail.com> Fri, 18 December 2015 19:54 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 8713C1B3886 for <rtcweb@ietfa.amsl.com>; Fri, 18 Dec 2015 11:54:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 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, HTML_MESSAGE=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 mGt0VnnmNF9b for <rtcweb@ietfa.amsl.com>; Fri, 18 Dec 2015 11:54:38 -0800 (PST)
Received: from mail-yk0-x235.google.com (mail-yk0-x235.google.com [IPv6:2607:f8b0:4002:c07::235]) (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 2501C1B3885 for <rtcweb@ietf.org>; Fri, 18 Dec 2015 11:54:37 -0800 (PST)
Received: by mail-yk0-x235.google.com with SMTP id x184so70731876yka.3 for <rtcweb@ietf.org>; Fri, 18 Dec 2015 11:54:37 -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=3kgfAmquiW2zoHqf9n0gAzbxAPC6h5BhLzeudpPw4aU=; b=018tMsbyQE5zZEeBggnsgCEtW1ejvPgVnQRjvtwuzDYc8CGcFaZfMIuxVKLPgZdYnv Zo/YQuL1thYAlLEX3Ewmg7XoTOZXIJVxO0MtCTTaX5DkHXjNlReaG20nU5mtpgfMH0Tx uqfwWG2rrgutUIBjbvhYYOaGErFIwBPEydzPhBiWNx7wImR7GNT58h45fp0pk1FX68h+ RjaWsSNMNHZYQtXGy15DlMGlgDCce95D1GwPIEbcNCoI4VhU8ZZw3tu9CEBLH1g0LeTc V8h1vVaLGEVxOCOzLjIiW7nAZWuUmN8cyby0cdYzsE2yVOACH1D6xBrZWF0q4LjzLHyk F4AQ==
X-Received: by 10.129.51.210 with SMTP id z201mr5110246ywz.202.1450468477112; Fri, 18 Dec 2015 11:54:37 -0800 (PST)
Received: from [192.168.4.135] (ip-64-134-188-160.public.wayport.net. [64.134.188.160]) by smtp.gmail.com with ESMTPSA id h130sm17336524ywb.24.2015.12.18.11.54.35 (version=TLSv1/SSLv3 cipher=OTHER); Fri, 18 Dec 2015 11:54:35 -0800 (PST)
Content-Type: multipart/alternative; boundary="Apple-Mail-EDA88B73-A361-486D-9309-95B52041D7B0"
Mime-Version: 1.0 (1.0)
From: Bernard Aboba <bernard.aboba@gmail.com>
X-Mailer: iPhone Mail (13C75)
In-Reply-To: <CA+9kkMDAL1mKqt7cTRmU4YqX2S5QN4RKn2cfbPaBeDgx=yiN0Q@mail.gmail.com>
Date: Fri, 18 Dec 2015 14:54:34 -0500
Content-Transfer-Encoding: 7bit
Message-Id: <AE360F77-1902-412D-B5FF-6157D8D44C41@gmail.com>
References: <CA+9kkMDAL1mKqt7cTRmU4YqX2S5QN4RKn2cfbPaBeDgx=yiN0Q@mail.gmail.com>
To: Ted Hardie <ted.ietf@gmail.com>
Archived-At: <http://mailarchive.ietf.org/arch/msg/rtcweb/89zLKDcXjxGR_nJdcFpjHvc99ks>
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: Fri, 18 Dec 2015 19:54:39 -0000

The DTMF language will aligned with the W3C specification and clarified that A-D are not supported (as they will not be supported in the JavaScript).

[BA] I am not sure what "aligning the text" means. The W3C WEBRTC specification does not dictate that A-D be supported - it only describes how implementations should behave for supported tones, referencing the Audio document for DTMF requirements. If a tone is unsupported it is considered "unrecognized" in the API. It is the Audio document that provides the requirements, and as long as A-D aren't a MUST NOT, the API needs to allow implementations to send A-D if they choose to do so.

v2.23.0 | Report a Bug | By Email