[rtcweb] Comments regarding draft-ietf-rtcweb-audio-07.txt

Roman Shpount <roman@telurix.com> Sat, 25 October 2014 00:00 UTC

Return-Path: <roman@telurix.com>
X-Original-To: rtcweb@ietfa.amsl.com
Delivered-To: rtcweb@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com []) by ietfa.amsl.com (Postfix) with ESMTP id 179A41A1BB4 for <rtcweb@ietfa.amsl.com>; Fri, 24 Oct 2014 17:00:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.978
X-Spam-Status: No, score=-1.978 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id 3I__yMaiQRGc for <rtcweb@ietfa.amsl.com>; Fri, 24 Oct 2014 17:00:14 -0700 (PDT)
Received: from mail-wg0-f50.google.com (mail-wg0-f50.google.com []) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A58481A1C03 for <rtcweb@ietf.org>; Fri, 24 Oct 2014 17:00:12 -0700 (PDT)
Received: by mail-wg0-f50.google.com with SMTP id a1so2077064wgh.33 for <rtcweb@ietf.org>; Fri, 24 Oct 2014 17:00:11 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:date:message-id:subject:from:to :content-type; bh=lpKAv85V+bEz6MGDF32hET9Z7PFNxCG/KZ8Xe43RGRQ=; b=JaxCmqY6YphmCwGjixUKXPdt0BI9yIN+JM1eQX+m9M9k6fhieTNJXmSssh8Qm+E6Iv MwCz/Ey8sKmGjgl6iwiFDl6Ek/JMr6qhH41AH319fTlCvt9/1RtsTvyFoEmFtBlLMU+D sCbF35zjjgcOUsjHpRVquZhRNGqEoKdTX53DZ/RZzO38o0cwMx2PoPN7mMciyblC/4hl S38/pKvKuHH9fqlyaiWAbpi7l/8qv3cwMfJOHJ+7ify35hKu8YxQFMpcBUcZR1DN28Uv daIrPS7bhdvgFU4Yhqq+BoWCpCaD1oDx/68GVMoWR31HXbvNr61L7D8g7E2Vm74h77RP oFhQ==
X-Gm-Message-State: ALoCoQmZHxNqCczXX3+jvB0GW6ecLDqjPF6vyUJ3p/Eht3RGVQiKkNfv+Ytj48vXawM93bPGIQNP
X-Received: by with SMTP id ha5mr6897795wib.69.1414195211249; Fri, 24 Oct 2014 17:00:11 -0700 (PDT)
Received: from mail-wg0-f51.google.com (mail-wg0-f51.google.com. []) by mx.google.com with ESMTPSA id bi7sm3556975wib.17.2014. for <rtcweb@ietf.org> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 24 Oct 2014 17:00:10 -0700 (PDT)
Received: by mail-wg0-f51.google.com with SMTP id b13so2098688wgh.22 for <rtcweb@ietf.org>; Fri, 24 Oct 2014 17:00:09 -0700 (PDT)
MIME-Version: 1.0
X-Received: by with SMTP id bf6mr6929699wib.43.1414195209743; Fri, 24 Oct 2014 17:00:09 -0700 (PDT)
Received: by with HTTP; Fri, 24 Oct 2014 17:00:09 -0700 (PDT)
Date: Fri, 24 Oct 2014 20:00:09 -0400
Message-ID: <CAD5OKxvcr09hQTxxAetJEgN_6GHcDdqd-VJHEvc2vVp9LRDc8w@mail.gmail.com>
From: Roman Shpount <roman@telurix.com>
To: "rtcweb@ietf.org" <rtcweb@ietf.org>
Content-Type: multipart/alternative; boundary="f46d04428ab21eb58a050633fb98"
Archived-At: http://mailarchive.ietf.org/arch/msg/rtcweb/-dBz1M-3EgdoGxzvnA6wyzxfqHc
Subject: [rtcweb] Comments regarding draft-ietf-rtcweb-audio-07.txt
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: Sat, 25 Oct 2014 00:00:17 -0000

In section 3, draft states that: "WebRTC clients are REQUIRED to be able to
generate and consume the following events" followed by list of RFC4733
events. What does it mean by "consume"? Does it mean receive without
failure, while ignoring its contents or actually processing the events and
exposing them to the end point user in some way?

Supported RFC4733 event list does not match events listed in section 6.2.2
W3C TR (http://www.w3.org/TR/webrtc/#methods-4). W3C also lists support for
DTMF digits A through D.

Should the document state the duration and gap recommendations for RFC 4733
tones from section 6.2.2 of W3C document?

I did not know there is a consensus on must implement of CN.

Roman Shpount