IETF Logo Mail Archive

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

Roman Shpount <roman@telurix.com> Fri, 18 December 2015 18:32 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 [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 182BA1B37F4 for <rtcweb@ietfa.amsl.com>; Fri, 18 Dec 2015 10:32:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.278
X-Spam-Level:
X-Spam-Status: No, score=-1.278 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=no
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 KYS4jqEXaC28 for <rtcweb@ietfa.amsl.com>; Fri, 18 Dec 2015 10:32:45 -0800 (PST)
Received: from mail-io0-x22c.google.com (mail-io0-x22c.google.com [IPv6:2607:f8b0:4001:c06::22c]) (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 449231B3767 for <rtcweb@ietf.org>; Fri, 18 Dec 2015 10:32:45 -0800 (PST)
Received: by mail-io0-x22c.google.com with SMTP id o67so98375694iof.3 for <rtcweb@ietf.org>; Fri, 18 Dec 2015 10:32:45 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=telurix-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=m9dr/0Fu9VIzi25FnYazmjAlMKY94GB59tkSE7MBTkk=; b=Hne5ZUfyswb8P0DnGgksPXsZ8F6SwKvR8eUQTjJhRHAyzSbFsoTqR5YKpsk1ns5BVo OPsh2NZ04iUIoXBcir9qz2SeE6bE2owqI80ClpVe7ZOOnM9p3lecRSR/ZjxG9DhpDLHI bDobvLocRgK+N1ze1y6tlx3MgwEe0+6dTet/JuBXM0RBdXVw+JViHHbnqtzeRj1dkELi mQ1fD+qTfqAQvitderE1xOm2k2Yfar+4XgJ487uPXjf284sqKbOQ8bh6ikzbVdwqZ82w hgpzitKX48fZzmk/kf0fljXJuviDqXkKx6fE+I+MCFUTwbDN5Q3qIawIw2BCdf0Vk+uA 9ZpQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=m9dr/0Fu9VIzi25FnYazmjAlMKY94GB59tkSE7MBTkk=; b=Zm/XzmT0wKTl1+lgzQ+drB1LUE9F0G2t3x9XO4LA3d1QAmLy4CByuSgpHN8skSrnFl 4LqJUyOgWMODPB2PlPnA86TWEBjtNz9RoWUmklYHtZgLfy/1T4buCicJ+gG+FBuGRS/3 FrUQVuAAmjgBcubVafwFA6kHctYYhS9sVQ7cC+X5FqneQstWSwDv9gA20s9DVgHH/c6n lPcne0j3GPrCADBRCgUXZd5gOukNKR4XuDyWus9Chm98qUuQGun+phBmgbrJbZnCULH4 sVXDa6UND1H670d8V4N/lhVq7Q8aqnHO0XCLZa+NCRbuojf6V2P5knFOm4SZr5bw09kk KqxQ==
X-Gm-Message-State: ALoCoQm/Qv7j5bSj9uhDS8DVjcYqo4rINUH8yYh8T779/TR8xtNx0timKnF66275TWbR2VLBO/QGZFFnFkpoC+mDiF0LlSYHlA==
X-Received: by 10.107.39.130 with SMTP id n124mr7161836ion.159.1450463564713; Fri, 18 Dec 2015 10:32:44 -0800 (PST)
Received: from mail-io0-f172.google.com (mail-io0-f172.google.com. [209.85.223.172]) by smtp.gmail.com with ESMTPSA id z6sm3085452ign.1.2015.12.18.10.32.43 for <rtcweb@ietf.org> (version=TLSv1/SSLv3 cipher=OTHER); Fri, 18 Dec 2015 10:32:43 -0800 (PST)
Received: by mail-io0-f172.google.com with SMTP id o67so98374768iof.3 for <rtcweb@ietf.org>; Fri, 18 Dec 2015 10:32:43 -0800 (PST)
MIME-Version: 1.0
X-Received: by 10.107.166.15 with SMTP id p15mr5957665ioe.38.1450463562696; Fri, 18 Dec 2015 10:32:42 -0800 (PST)
Received: by 10.36.105.15 with HTTP; Fri, 18 Dec 2015 10:32:42 -0800 (PST)
In-Reply-To: <CA+9kkMDAL1mKqt7cTRmU4YqX2S5QN4RKn2cfbPaBeDgx=yiN0Q@mail.gmail.com>
References: <CA+9kkMDAL1mKqt7cTRmU4YqX2S5QN4RKn2cfbPaBeDgx=yiN0Q@mail.gmail.com>
Date: Fri, 18 Dec 2015 13:32:42 -0500
X-Gmail-Original-Message-ID: <CAD5OKxtvhaqx=H10=fUiGAjvnGAb_g89p2TZT9iNEg2F9k+6FA@mail.gmail.com>
Message-ID: <CAD5OKxtvhaqx=H10=fUiGAjvnGAb_g89p2TZT9iNEg2F9k+6FA@mail.gmail.com>
From: Roman Shpount <roman@telurix.com>
To: Ted Hardie <ted.ietf@gmail.com>
Content-Type: multipart/alternative; boundary="001a1141cf946a12b40527305d74"
Archived-At: <http://mailarchive.ietf.org/arch/msg/rtcweb/kXg_Ed-1Zb3kja7RglFnbgNNHcc>
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 18:32:47 -0000

Hi All,

Since the decision not to support A-D DTMF digits was never made on the
IETF list (I have looked through the archive and cannot find it), I do not
think they should be removed.

Minimal DTMF tone duration and gap duration should be added to the document.

The meaning of "consuming" RFC 4733 events by WebRTC endpoints is unclear.

I suggest to change the following section of the document:

OLD TEXT:
The audio/telephone-event media format as specified in [RFC4733].
      WebRTC endpoints are REQUIRED to be able to generate and consume
      the following events:

         +------------+--------------------------------+-----------+
         |Event Code  | Event Name                     | Reference |
         +------------+--------------------------------+-----------+
         | 0          | DTMF digit "0"                 |  RFC4733  |
         | 1          | DTMF digit "1"                 |  RFC4733  |
         | 2          | DTMF digit "2"                 |  RFC4733  |
         | 3          | DTMF digit "3"                 |  RFC4733  |
         | 4          | DTMF digit "4"                 |  RFC4733  |
         | 5          | DTMF digit "5"                 |  RFC4733  |
         | 6          | DTMF digit "6"                 |  RFC4733  |
         | 7          | DTMF digit "7"                 |  RFC4733  |
         | 8          | DTMF digit "8"                 |  RFC4733  |
         | 9          | DTMF digit "9"                 |  RFC4733  |
         | 10         | DTMF digit "*"                 |  RFC4733  |
         | 11         | DTMF digit "#"                 |  RFC4733  |
         +------------+--------------------------------+-----------+


_____________
Roman Shpount

On Fri, Dec 18, 2015 at 1:13 PM, Ted Hardie <ted.ietf@gmail.com> wrote:

> The two issues that surfaced during this last call that needed resolution
> were DTMF and comfort noise.  Based on the discussion, we believe that the
> comfort noise requirement will be shifted to "WebRTC endpoints". 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).
>
> After the document is updated, the chairs plan to submit it to IETF last
> call.
>
> regards,
>
> Ted, Cullen, Sean
>
> _______________________________________________
> rtcweb mailing list
> rtcweb@ietf.org
> https://www.ietf.org/mailman/listinfo/rtcweb
>
>

v2.23.0 | Report a Bug | By Email