[rtcweb] Alissa Cooper's Yes on draft-ietf-rtcweb-audio-10: (with COMMENT)

"Alissa Cooper" <alissa@cooperw.in> Thu, 14 April 2016 17:18 UTC

Return-Path: <alissa@cooperw.in>
X-Original-To: rtcweb@ietf.org
Delivered-To: rtcweb@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 4DD0212B071; Thu, 14 Apr 2016 10:18:46 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Alissa Cooper <alissa@cooperw.in>
To: The IESG <iesg@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 6.19.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20160414171846.6832.14090.idtracker@ietfa.amsl.com>
Date: Thu, 14 Apr 2016 10:18:46 -0700
Archived-At: <http://mailarchive.ietf.org/arch/msg/rtcweb/JHZgC7Jt-3UQo-MOapf3xbEfTTw>
Cc: rtcweb@ietf.org, draft-ietf-rtcweb-audio@ietf.org, rtcweb-chairs@ietf.org
Subject: [rtcweb] Alissa Cooper's Yes on draft-ietf-rtcweb-audio-10: (with COMMENT)
X-BeenThere: rtcweb@ietf.org
X-Mailman-Version: 2.1.17
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: Thu, 14 Apr 2016 17:18:46 -0000

Alissa Cooper has entered the following ballot position for
draft-ietf-rtcweb-audio-10: Yes

When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)

Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html
for more information about IESG DISCUSS and COMMENT positions.

The document, along with other ballot positions, can be found here:


The text below is due to be added in Section 3 of the document, pending
list confirmation of consensus in the room from IETF 95, which is due to
wrap up on April 20.

"DTMF events generated by a WebRTC endpoint MUST have a duration of no
more than 8000 ms and no less than 40 ms.  The recommended default
duration is 100 ms for each tone. The gap between events MUST be no less
than 30 ms; the recommended default gap duration is 70 ms.

WebRTC endpoints are not required to do anything with RFC 4733 tones sent
to them, except gracefully drop them. There is currently no API to inform
JavaScript about the received DTMF or other RFC 4733 tones."